Prevent DHCP release upon shutdown?

[golfinguy]

Perhaps a strange need, but nonetheless I need to prevent the RPi from sending a 'release' to the server when it shuts down or reboots. I could not find anything obvious that I could turn on/off for this. I guess I could remove the ifdown from the shutdown altogether, but that seems harsh.

[ripat]

I am afraid that you can not prevent ifdown from sending a DHCPRELEASE without patching/recompiling the ifupdown sources. Sending a DHCPRELEASE on shutdown is not a RFC requirement but it isn't prohibited either. Just came accross this :
http://pureperl.blogspot.be/2013/01/the ... e-and.html

I am sure you know how that you can always reserve a fix IP on the DHCP server based on the RPi's mac address.

[ripat]

Edit:
I think I found a work around. When you shut down your RPi, the /etc/init.d/networking script is invoqued, called by the rc.d hooks. In turn, the /etc/init.d/networking execute ifdown -a in the "stop)" and the "reload)" case switches. Just comment out these lines. Even better, if you want to deconfigure gracefully the interfaces before shut down, replace the ifdown command by the appropriate ip link set eth0 down command. I just checked with tcpdump, no DHCPRELEASE is sent in that case.

[golfinguy]

Edit:
I think I found a work around. When you shut down your RPi, the /etc/init.d/networking script is invoqued, called by the rc.d hooks. In turn, the /etc/init.d/networking execute ifdown -a in the "stop)" and the "reload)" case switches. Just comment out these lines. Even better, if you want to deconfigure gracefully the interfaces before shut down, replace the ifdown command by the appropriate ip link set eth0 down command. I just checked with tcpdump, no DHCPRELEASE is sent in that case.

Thats what I ended up doing - just commenting out the lines. Which is why I didn't come back to the thread - thanks though!

[RaTTuS]

why do you want to do this ?

if it is to keep the same IP address then set it as fixed on your dhcp server

[ne3e]

If you really want to keep the same IP address. Program your router/DHCP server with the IP address you want. This way every time your Pi goes to get a new address if will be provided with the same one. If your router cannot do this build a little DHCP server on another machine. Look on Google on how to do this.

[Richard-TX]

Instead of doing dhcp, I just assign a fixed address. Solves all those dhcp issues

[tvjon]

My experience has been that in a relatively non-changing network, fixed is a good approach, but here devices are frequently added, & removed from the LAN, so fixed becomes awkward.

Usually I address devices as:

somedevice.local

which works just fine. The other day though I installed an "add-on" for openelec XBMC to monitor an ip camera. It didn't find said camera, so I did have to substitute its ip address. I think the source may be available for the add-on so I'll see if there's any way to change that behaviour.

[Tarcas]

My experience has been that in a relatively non-changing network, fixed is a good approach, but here devices are frequently added, & removed from the LAN, so fixed becomes awkward.

Usually I address devices as:

somedevice.local

which works just fine. The other day though I installed an "add-on" for openelec XBMC to monitor an ip camera. It didn't find said camera, so I did have to substitute its ip address. I think the source may be available for the add-on so I'll see if there's any way to change that behaviour.

You might try adding an entry for the camera in the /etc/hosts file if you want to reference it by name.