dhcpcd-discuss

Hi Roy,

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?

-- Juliusz