dhcpcd-discuss

Hi Amit

On 13/11/2014 01:31, Amit Uttamchandani wrote:
> I built a debian package for 6.6.1 using uupdate from 6.0.5. The install
> was successful.
> 
> However, using timeout 0 in 6.6.1 causes dhcpcd to always use the IPV4LL
> address instead of the offered address from DHCP server. Isn't *timeout
> 0* suppose to cause dhcpcd to wait forever to acquire a lease? In
> version 6.0.5, *timeout 0* waits forever till a lease is acquired.
> 
> 6.6.1 - With *timeout 0* parameter in dhcpcd.conf:
> Nov 12 16:54:23 falcon-UNKNOWN dhcpcd[613]: version 6.6.1 starting
> Nov 12 16:54:23 falcon-UNKNOWN dhcpcd[613]: eth0: adding address fe80::ba2a:8253:babc:7a54
> Nov 12 16:54:23 falcon-UNKNOWN dhcpcd[613]: eth0: waiting for carrier
> Nov 12 16:54:23 falcon-UNKNOWN dhcpcd[613]: eth0: carrier acquired
> Nov 12 16:54:23 falcon-UNKNOWN dhcpcd[613]: error writing DUID: /etc/dhcpcd.duid: Read-only file system
> Nov 12 16:54:23 falcon-UNKNOWN dhcpcd[613]: DUID 00:03:00:01:00:1f:f2:08:a7:b0
> Nov 12 16:54:23 falcon-UNKNOWN dhcpcd[613]: eth0: IAID f2:08:a7:b0
> Nov 12 16:54:24 falcon-UNKNOWN dhcpcd[613]: eth0: soliciting a DHCP lease
> Nov 12 16:54:24 falcon-UNKNOWN dhcpcd[613]: eth0: soliciting an IPv6 router
> Nov 12 16:54:26 falcon-UNKNOWN dhcpcd[613]: eth0: probing for an IPv4LL address
> Nov 12 16:54:31 falcon-UNKNOWN dhcpcd[613]: eth0: offered 192.168.1.215 from 192.168.1.83
> Nov 12 16:54:31 falcon-UNKNOWN dhcpcd[613]: eth0: using IPv4LL address 169.254.53.85
> Nov 12 16:54:31 falcon-UNKNOWN dhcpcd[613]: eth0: adding route to 169.254.0.0/16
> Nov 12 16:54:31 falcon-UNKNOWN dhcpcd[613]: forked to background, child pid 917
> Nov 12 16:54:36 falcon-UNKNOWN dhcpcd[917]: eth0: no IPv6 Routers available
> 
> 6.6.1 - No *timeout 0* parameter in dhcpcd.conf:
> Nov 12 17:05:35 falcon-UNKNOWN dhcpcd[615]: version 6.6.1 starting
> Nov 12 17:05:35 falcon-UNKNOWN dhcpcd[615]: eth0: adding address fe80::ba2a:8253:babc:7a54
> Nov 12 17:05:35 falcon-UNKNOWN dhcpcd[615]: eth0: waiting for carrier
> Nov 12 17:05:35 falcon-UNKNOWN dhcpcd[615]: eth0: carrier acquired
> Nov 12 17:05:35 falcon-UNKNOWN dhcpcd[615]: error writing DUID: /etc/dhcpcd.duid: Read-only file system
> Nov 12 17:05:35 falcon-UNKNOWN dhcpcd[615]: DUID 00:03:00:01:00:1f:f2:08:a7:b0
> Nov 12 17:05:35 falcon-UNKNOWN dhcpcd[615]: eth0: IAID f2:08:a7:b0
> Nov 12 17:05:35 falcon-UNKNOWN dhcpcd[615]: eth0: soliciting an IPv6 router
> Nov 12 17:05:36 falcon-UNKNOWN dhcpcd[615]: eth0: soliciting a DHCP lease
> Nov 12 17:05:39 falcon-UNKNOWN dhcpcd[615]: eth0: offered 192.168.1.215 from 192.168.1.83
> Nov 12 17:05:44 falcon-UNKNOWN dhcpcd[615]: eth0: leased 192.168.1.215 for 28800 seconds
> Nov 12 17:05:44 falcon-UNKNOWN dhcpcd[615]: eth0: adding route to 192.168.1.0/24
> Nov 12 17:05:44 falcon-UNKNOWN dhcpcd[615]: eth0: adding default route via 192.168.1.1
> Nov 12 17:05:44 falcon-UNKNOWN dhcpcd[615]: forked to background, child pid 960
> Nov 12 17:05:48 falcon-UNKNOWN dhcpcd[960]: eth0: no IPv6 Routers available

This looks like a bug and I'll try and look into it when I get the chance.
For the time being, you can disable IPv4LL by adding noipv4ll to the top
of dhcpcd.conf to hopefully get the behaviour you desire.

Roy