dhcpcd-discuss

Hi Juliusz

On 2016-01-31 14:39, Juliusz Chroboczek wrote:
> Both the native OpenWRT stack and the Homenet stack send Router
> Information Options (RIOs).  This is actually a requirement of RFC 7084
> (requirement L-3).
>
> The idea is the following.  Suppose that you've got two routers A and
> B that have distinct delegations, say A/60 and B/60.  Then A announces
> a RIO for A/60, and B a RIO for B/60, which causes hosts to route each 
> /60
> through the right router.  If that were not the case, you could get
> spurious redirects, suboptimal routing, or, worse, edge filtering.
>
> Note that the same RIO can be announced by multiple routers.  In a 
> Homenet
> domain, for example, all routers announce the same set of RIOs (after 
> HNCP
> convergence).
>
> It looks like dhcpcd is ignoring the received RIOs.  Is that just that
> RIOs haven't been implemented yet, or do you have good reasons to 
> ignore
> them?  Do you know of any DHCPv6 client that I can use for testing our 
> RIO
> support?


Reading through RFC 7084, it seems to be describing a Customer Edge 
Router?
I've not read that RFC in any great detail, I suppose I should to ensure 
dhcpcd complies where it can.

Now, as to RIO in the RA. dhcpcd isn't going out of it's way to ignore 
it - you are correct in that there is no code in dhcpcd for it.
In the normal case, RIO would be handled by the kernel - as dhcpcd 
overrides the kernel for routing on RA, dhcpcd needs code for it as 
well.
So basically dhcpcd needs to support RFC4191 and we're all happy?

Roy