Modifying the timeout and retry values of dhclient.conf does not seem to change the length of time that dhclient waits for a response. Furthermore, executing /sbin/dhclient -cf /etc/dhcp/dhclient.conf causes dhclient to complain that the -cf option does not exist. The usage message that follows does NOT list a -cf option. Reproducible: Always Steps to Reproduce: 0. Execute dhclient. 1. Copy /etc/dhcp/dhclient.conf.sample to /etc/dhcp/dhclient.conf and change "ep0" to "eth0" 2. Change timeout and retry to rediculously small values. 3. Execute dhclient using -cf option. Actual Results: A. dhclient failed to load the predefined lease (included in the sample configuration file) when it could not find a DHCP server. B. dhclient complains that the -cf option is not recognized. Expected Results: A. dhclient should have configured eth0 using the predefined lease when it could not find a DHCP server. B. Modifying the timeout and retry values should have reduced the amount of time before dhclient gave-up. from the dhclient man-page: A mobile host which may sometimes need to access a network on which no DHCP server exists may be preloaded with a lease for a fixed address on that network. When all attempts to contact a DHCP server have failed, dhclient will try to validate the static lease, and if it succeeds, will use that lease until it is restarted. from the dhclient.conf man-page: The DHCP client may decide after some period of time (see PROTOCOL TIMING) decide that it is not going to succeed in contacting a server. At that time, it consults its own database of old leases and tests each one that has not yet timed out by pinging the listed router for that lease to see if that lease could work. It is possible to define one or more fixed leases in the client configuration file for networks where there is no DHCP or BOOTP service, so that the client can still automatically configure its address. This is done with the lease statement.
This bug is NOT a duplicate of 27079: Bug 27079 relates to dhcpd-3.0. This bug relates to dhcpcd-1.3.
Eric, is this bug still valid? Seemant, reassigned from Will Woods to you.
vapier knows this sort of voodoo, dunno why I got this
I use dhclient (from net-misc/dhcp-3.0.1-r1) and it works fine with the -cf command line option.
this bug does not relate to dhcpcd-1.3 ... that package does not provide 'dhclient', net-misc/dhcp does that said, dhcp-3.0.1 works for me over here using your example, and Benoit confirms that the '-cf' option works fine for him
