dhcpcd-discuss

On Sat, 18 Jan 2014 06:39:24 +0600
Mike Kazantsev <mike_kazantsev@xxxxxxxxxxx> wrote:

> > 
> > So basically dhcpcd is designed to work with either PD or NA/TA.
> > I don't see a good reason for allowing PD and NA/TA on the same 
> > interface.
> > 
> 
...
> 
> Given that IA_NA seem to hand out an IP from delegated range anyway, I
> don't see much point in using it with IA_PD here either, at least now.
> 

That was incorrect - IPv6 from IA_NA and IA_PD range doesn't intersect
here.


> >    interface ext1
> >    ia_pd b9:86:f4:39 int1/0/56
> > 
> > So the last block says "the below config is for ext1 only. We will use 
> > an IAID of b9:86:fe:39 to request a PD and then assign the result to 
> > interface int1 with a /56 prefix length"
> > 
> 
...
> 
> Will try fixing it now, should probably work for my case, but I still
> wonder - shouldn't there be a hook when this delegation happens anyway?
> 
...
> 
> Not sure if I just didn't get that hook due to that misconfiguration
> though, so pls nevermind if that should be the case.
> 
> 

Trying suggested configuration (with assign-to interface being "enp1s0"
instead of "int1") and running dhcpcd for just "ext1" interface
("dhcpcd --nogateway -f /etc/dhcpcd.myisp.conf ext1"), got this:

  enp1s0: interface does not exist for delegation

And requested IPv6 range was not assigned there.

Guess in my case, dhcpcd needs to be able to "discover" both ext1 and
enp1s0 (assigning static IPs/routes via "interface + static" directives
where necessary, e.g. on the latter).

Hooks seem to be run this time for BIND6/REBIND6 events, passing
delegated range in env, so I guess previous behavior (not running
hooks for ipv6 ia_pd events) was related to that misconfiguration.


vendor* and waitip options work as well, when used as suggested.


Again, thanks for helping me figure it out, and sorry for lack of basic
knowledge in the area, leading to all that confusion.


-- 
Mike Kazantsev // fraggod.net

Attachment: signature.asc
Description: PGP signature