dhcpcd-discuss

On 03/02/2016 12:59, Nicholas Williams wrote:
> $ sudo dhcpcd --logfile /tmp/dhcpcd.log -6 eth2
> 
> And here's the log:
> 
> $ cat /tmp/dhcpcd.log 
> Feb 03 12:48:11 DUID 00:01:00:01:1e:43:88:3a:08:00:27:21:d4:16
> Feb 03 12:48:11 eth2: IAID 27:21:d4:16
> Feb 03 12:48:11 eth2: soliciting a DHCPv6 lease
> Feb 03 12:48:11 eth2: soliciting an IPv6 router
> Feb 03 12:48:11 eth2: Router Advertisement from fe80::1423:8585:11f5:dfc8
> Feb 03 12:48:11 eth2: adding address
> 2600:1004:b15b:f338:a00:27ff:fe21:d416/64
> Feb 03 12:48:11 forked to background, child pid 1406
> Feb 03 12:48:12 eth2: DHCPv6 REPLY: No addresses available for this
> interface.
> Feb 03 12:48:13 eth2: DHCPv6 REPLY: No addresses available for this
> interface.
> Feb 03 12:48:15 eth2: DHCPv6 REPLY: No addresses available for this
> interface.
> Feb 03 12:48:19 eth2: DHCPv6 REPLY: No addresses available for this
> interface.
> 
> So it sounds like I'm definitely getting autoconfiguration and not
> DHCPv6, which I'm guessing is why I have no lease. The problem probably
> stems from the fact that I'm using a Verizon LTE connection to test
> this. At the time, I wasn't able to test this on my VyOS router, and my
> VyOS router kept me from having access to IPv6, so I had to use my
> hotspot to test IPv6 (because Verizon has global IPv6 support).
> Apparently Verizon doesn't do DHCPv6, just autoconfiguration (in
> contrast to Comcast, which supports either).

Great!

Well, you can now remove the ia_na instruction from your dhcpcd.conf
If you then re-run the above test with the -d flag dhcpcd should tell
you that it won't automatically start DHCPv6 because there is no
instrution to do so in the RA received.

> My apologies for wasting any of your time. :-/

It's never time wasted if you've learned something :)
Roy