Hello, I have the following problem on Debian 5: * I have a router that reboots longer than 45 seconds * When router is rebooted, the link goes down and then up again * When the link goes up, Debian tries to do DHCPDISCOVER * However, as the DHCP server (integrated into the router) is still starting up, no reply comes in 45 seconds * At this point NetworkManager decides to stop doing DHCP and switches to Zeroconf (see the log below).
Question: how to make NetworkManager to try doing DHCP indefinitely? Thank You for Your answers! Oleg Mürk Feb 25 12:35:34 frontend dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 Feb 25 12:35:41 frontend NetworkManager: <info> Device 'eth0' DHCP transaction took too long (>45s), stopping it. Feb 25 12:35:41 frontend dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 10955 Feb 25 12:35:41 frontend dhclient: killed old client process, removed PID file Feb 25 12:35:41 frontend dhclient: DHCPRELEASE on eth0 to 192.168.1.254 port 67 Feb 25 12:35:41 frontend dhclient: send_packet: Network is unreachable Feb 25 12:35:41 frontend dhclient: send_packet: please consult README file regarding broadcast address. Feb 25 12:35:42 frontend NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled... Feb 25 12:35:42 frontend NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started... Feb 25 12:35:42 frontend NetworkManager: <info> No DHCP reply received. Automatically obtaining IP via Zeroconf.
