dhcpcd-discuss

On Sun, 19 Jan 2014 07:11:26 +0600
Mike Kazantsev <mike_kazantsev@xxxxxxxxxxx> wrote:

> > > 
> > > Again, thanks for helping me figure it out, and sorry for lack of basic
> > > knowledge in the area, leading to all that confusion.
> > 
> > Great! So you're all up and running fine now?
> > 
> > Also, can you think of any extra improvements that could be made on top 
> > of the fixes I've just made?
> > 
> 
> Yeah, it kinda works...
> 
> Resulting configuration (/etc/dhcpcd.myisp.conf) I have is:
> 
>   duid
>   persistent
>   option rapid_commit, classless_static_routes
>   require dhcp_server_identifier
>   nohook resolv.conf, lookup-hostname, hostname, ntp.conf, yp.conf
>   noipv4ll
>   
>   vendorclassid dhcpcd:Linux-3.X.X:x86_64
>   vendclass 40712 dhcpcd:Linux-3.X.X:x86_64
>   
>   noipv6rs
> 
>   waitip 46
>   timeout 10
>   
>   #debug
>   
>   interface ext1
>    iaid b9:86:f4:39
>    ia_pd b9:86:f4:39 enp1s0/0/56
>   
>   interface enp1s0
>    noipv4
>    noipv6
> 
> And running dhcpcd as:
> 
>   dhcpcd -f /etc/dhcpcd.myisp.conf --nogateway ext1 enp1s0
...
> 
> I thought "noipv6rs" (which I have in the config globally) was supposed
> to disable whole router solicitation mechanism?
> 
> It is explicitly mentioned as "to disable" thing for ia_pd (and I guess
> it's also an obvious thing related to RFCs which I just don't know), so
> assume that hint is there so that RS requests won't get sent anywhere
> but on ia_pd-context interface, where they get implicitly (and
> forcefully) enabled.
> 
> If so, maybe that's the thing worth mentioning that reasoning and
> implicit RS being always enabled where IA_PD is?
> 

One other thing - even though RS seem to succeed here eventually (and
dhcpcd saying "dhcpcd[8382]: ext1: Router Advertisement from
fe80::201:c9ff:fee5:6000"), when hook gets REBIND6 event, that
information is nowhere to be found, and there are no ROUTERADVERT
events neither on dhcpcd startup or later, it seems, even with explicit
"ipv6rs" for ext1 interface there.

This differs from situation with IPv4, where even with --nogateway,
dhcpcd passes routing information as "new_routers" env var to hooks.

With IPv6 RS and IA_PD, RS information that it still (implicitly) gets,
doesn't seem to be exposed to any hooks at all.

Use-case can be policy routing, when you want e.g. add that RS info to
some routing tables, but not "main", maybe with their own metric
values, etc - which dhcpcd probably shouldn't do on its own.


-- 
Mike Kazantsev // fraggod.net

Attachment: signature.asc
Description: PGP signature