dhclient3 fails to acquire address with default settings

[John Novak]

With the default parameters used by dhclient3 in dhclient.conf, most systems fail to acquire a DHCP address following reboot.

I have changed perms on /var/lib/dhcp3 to dhcp:dchp to fix the leases error.

Changing timeout to 60 and retry to 10 has the server with an IP address when the boot sequence completes.

I have seen this behavior on two different network segments using two different DHCP servers. Examining the DHCP server logs seems to indicate that the servers are not seeing DHCPDISCOVER packets until the default 5 minute retry interval expired.

The hardware exhibiting this behavior are Intel s3000PT boards with dual GB adapters and quad core X3220 processors. Both Feisty and Gusty show similar behavior. Enabling one or both adapters does not change behavior.

Might this be a timing problem where dhclient3 is trying to acquire an address before some network component is ready ?

[SilvaRizla (silvarizla5)]

My bug https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/408306 may be related, could you please describe what you mean/did by "I have changed perms on /var/lib/dhcp3 to dhcp:dchp to fix the leases error." as I would like to see if this helps my problem

[Launchpad Janitor (janitor)]

[Expired for dhcp3 (Ubuntu) because there has been no activity for 60 days.]