If changing the DSL router within my network (e.g., because it is damaged or failover to an UMTS-modem happened) it also changes the DHCP server with it.
So all connected clients need to fetch a new IP address - usually this works fine, but one Linux machine always gets stuck, even for several hours. Because it is a headless server without display, the fastest way to get a new IP address is to reboot the machine - this is what I want to prevent (and I want to prevent command to be typed in manually).
- The client is running Debian Squeeze
- I have access to the DHCP client configuration in /etc/dhcp/dhclient.conf
- I can submit a command on the machine as root as long it is connected, but not after the router was changed.
- But I have no access to the DHCP server configuration within the router.
The dhclient.conf currently looks like this:
option rfc3442-classless-static-routes code 121 = array of unsigned integer 8; request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, domain-search, host-name, netbios-name-servers, netbios-scope, interface-mtu, rfc3442-classless-static-routes, ntp-servers; send host-name "Achim-3c"; send dhcp-client-identifier "00:0c:c6:77:60:01"; retry 10;
How can I configure the DHCP client to automatically get a new IP address in case the DHCP server was changed in the network?
The problem only appears if the failover happens from DSL-Modem towards UMTS-Modem (Huawei E970). If the network run fine with UMTS-modem and I manually switch back to DSL-modem the Linux server smoothly get his new IP from the new DHCP server and therefore difficult to fix :-(
So it looks like it is a problem within the Huawei UMTS-modem configuration of DHCP server.