Bug#246220: dhcp failing first time common on sparc hardware
On Thu, 29 Apr 2004 17:39:38 +0200, Gaudenz Steinlin wrote:
>While netcfg presents the retry question the dhcp client is still
>running in the background. If it gets a lease in the meantime, the
>retry will exit immediatly and succeed. So this is the expected
>behaviour.
Just had a second look on the syslog file:
Apr 28 18:54:19 (none) user.info netcfg[2507]: /etc/dhclient-script: 99: sleep: not found
Apr 28 18:54:19 (none) daemon.info dhclient: Listening on LPF/eth0/08:00:20:19:99:3a
Apr 28 18:54:19 (none) daemon.info dhclient: Sending on LPF/eth0/08:00:20:19:99:3a
Apr 28 18:54:19 (none) daemon.info dhclient: Sending on Socket/fallback/fallback-net
Apr 28 18:54:19 (none) daemon.info dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Apr 28 18:54:19 (none) user.info netcfg[2507]: Listening on LPF/eth0/08:00:20:19:99:3a
Apr 28 18:54:19 (none) user.info netcfg[2507]: Sending on LPF/eth0/08:00:20:19:99:3a
Apr 28 18:54:19 (none) user.info netcfg[2507]: Sending on Socket/fallback/fallback-net
Apr 28 18:54:19 (none) daemon.info dhclient: DHCPOFFER from 192.168.200.123
Apr 28 18:54:19 (none) user.info netcfg[2507]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Apr 28 18:54:19 (none) user.info netcfg[2507]: DHCPOFFER from 192.168.200.123
Apr 28 18:54:22 (none) daemon.info dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Apr 28 18:54:22 (none) daemon.info dhclient: DHCPACK from 192.168.200.123
Apr 28 18:54:22 (none) user.info netcfg[2507]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Apr 28 18:54:22 (none) user.info netcfg[2507]: DHCPACK from 192.168.200.123
Apr 28 18:54:29 (none) daemon.info dhclient: bound to 192.168.200.101 -- renewal in 10800 seconds.
Two things seem strange to me:
1. /etc/dhclient-script: 99: sleep: not found
how can it wait 10 seconds w/o sleep?
2. it takes exactly 10 seconds between the first DHCPDISCOVER
message and the acceptance of the IP address. 7 of these 10
seconds pass between the last DHCPACK message and the
acceptance of the address with no other activity messages.
So to me it looks like the dhcp client accepts the IP not
because it got it but because it timed out. I would expect
it to also return a non-zero exit status then.
Herbert
Reply to: