dhcpcd-discuss

On 27/11/2013 4:40, Brian De Wolf wrote:
> You did skip over a second, hidden question, though.  Maybe it's a dumb
> one, I'm still new to IPv6.  Is it possible to make the interface
> receiving the PD still make up temporary addresses for itself?  I'm
> still clueless as to what makes that magic happen (is that on
> interfaces that come up via SLAAC?).

Through dhcpcd itself no.
You could add edit /etc/dhcpcd-{enter,exit}-hook.conf (see 
dhcpcd-run-hooks(8) for details) to create it when you get a PD.

> I also stumbled into another sort of problem.  While fiddling with
> dhcpcd at the beginning (figuring out IA_PD, IAIDs, etc), I somehow got
> several prefixes delegated to me.  I can only have one at a time, but
> restarting dhcpcd will randomly pull a different one from my ISP.  From
> a capture, it looks like this happens:
>
> Time Dir Action
> 0.0000 > Solicit PD
> 0.1186 < Advertise PD #1
> 0.1187 > Request PD #1
> 0.1195 < Advertise PD #2
> 0.2352 < Reply PD #1
>
> The packets do have the preference option, with different values
> (0x80 for PD#1, 0xff for PD#2).  Too bad the request packet was already
> in flight, I guess.
>
> I've also seen rebinds where the reply has two IA prefix sections in
> the IA_PD option, with PD#2 as the second one with zeroed timers.  Even
> after something like that, it still advertises PD#2 to me.
>
> My current solution is to stop touching things and wait for the timers
> to expire. Is there an equivalent to "DHCP release" that I can make
> dhcpcd do?

PD is made to expire off the given timers.
Because you used different IAIDs, you have many PD's.
This is actually fine, just let them expire by themselves.
You can only expire a PD dhcpcd knows about.

Say you configure eth0 to request a PD.
You can then expire eth0 like so:
    dhcpcd -k eth0

and the PD should be released. That isn't very well tested though.
If you change config and restart dhcpcd in the meantime, prior knowledge 
of the old PD is lost and you will have to let it expire.

Thanks

Roy