dhcpcd-discuss

So, is this a related problem? :

I noticed that each time I start dhcpcd for eth2, it always says this (and
it's always the same address ending in d416, which is to be expected with
autoconf):

eth2: adding address 2600:1004:b15b:f338:a00:27ff:fe21:d416/64

However, it actually adds TWO global addresses to the interface, not just
that one ending in d416, and the second address is always different. Okay,
no biggie ... this still isn't the problem.

The problem is that every time I call --release on the interface, dhcpcd
ONLY removes d416 from the interface. It doesn't remove the other, random
address. So, after I've started and stopped dhcpcd multiple times, my
interface now looks like this:

$ ifconfig eth2
eth2      Link encap:Ethernet  HWaddr 08:00:27:21:d4:16
          inet6 addr: 2600:1004:b15b:f338:9942:2bce:84dd:405c/64
Scope:Global
          inet6 addr: 2600:1004:b15b:f338:3c48:2061:7d2c:6704/64
Scope:Global
          inet6 addr: 2600:1004:b15b:f338:418f:2787:73c8:3485/64
Scope:Global
          inet6 addr: 2600:1004:b15b:f338:84ce:c34b:f8ff:b137/64
Scope:Global
          inet6 addr: fe80::a00:27ff:fe21:d416/64 Scope:Link
          inet6 addr: 2600:1004:b15b:f338:5940:6213:627c:84a7/64
Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5319 errors:0 dropped:0 overruns:0 frame:0
          TX packets:108 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:612072 (612.0 KB)  TX bytes:13206 (13.2 KB)

Also note that I can still ping IPv6 addresses. That's expected given that
there are still addresses configured, but unexpected given that I've
stopped dhcpcd with --release.

So, why isn't dhcpcd removing all addresses it adds to the interface when
called with --release?

Here's the full start-and-stop log for dhcpcd:

$ more /tmp/dhcpcd.log
Feb 03 13:35:37 DUID 00:01:00:01:1e:43:88:3a:08:00:27:21:d4:16
Feb 03 13:35:37 eth2: IAID 27:21:d4:16
Feb 03 13:35:37 eth2: soliciting a DHCPv6 lease
Feb 03 13:35:37 eth2: DHCPv6 REPLY: No addresses available for this
interface.
Feb 03 13:35:38 eth2: soliciting an IPv6 router
Feb 03 13:35:38 eth2: Router Advertisement from fe80::11:d44a:76e0:6ab5
Feb 03 13:35:38 eth2: adding address
2600:1004:b15b:f338:a00:27ff:fe21:d416/64
Feb 03 13:35:38 eth2: DHCPv6 REPLY: No addresses available for this
interface.
Feb 03 13:35:40 forked to background, child pid 5757
Feb 03 13:35:40 eth2: DHCPv6 REPLY: No addresses available for this
interface.
Feb 03 13:35:44 eth2: DHCPv6 REPLY: No addresses available for this
interface.
Feb 03 13:35:50 received SIGALRM, releasing
Feb 03 13:35:50 eth2: removing interface
Feb 03 13:35:50 eth2: deleting address
2600:1004:b15b:f338:a00:27ff:fe21:d416/64
Feb 03 13:35:50 dhcpcd exited

Thanks,

Nick


On Wed, Feb 3, 2016 at 7:22 AM, Roy Marples <roy@xxxxxxxxxxxx> wrote:

> 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
>