dhcpcd-discuss

Hi,

On 21.05.2016 19:02, Juliusz Chroboczek wrote:
> That's a hot topic at the IETF (RTGWG, MIF, Homenet).  My take is that
> it'll require extensions to RAs, but I'd be glad to be proved wrong.

I have found a way for a simple workaround using slaac, dhcpcd and a
hook script for most of the necessary steps to explicitly use an uplink.
Sending additional information about a gateway uplink will require a new
RA option though, because afaik rfc 4861 did not specify a way for
vendor specific options like in dhcp. I think it might be possible to
combine slaac and dhcpv6 in a static setup with multiple uplinks -
currently working on that. Has the drawback of not allowing dynamic
joining and leaving of gateway routers on a link, e.g. your smartphone.

>>> RDNSS and DNSSL are still a little problem though, because resolvconf
>>> only uses the top three nameservers reported from all interfaces. Maybe
>>> adding prefix information via a hook script will help me on that.
> 
> I'm confused.  How do you get the prefix information in the first place?

Usually RDNSS and DNSSL information is sent out via RAs that also
contain routes and prefix information. My base assumption is that an
announced DNS server should be accessed via that prefix with the
announced routes. A smart enough hook script could gather that
information from the RA and store a mapping from prefix to DNSSL and
RDNSS. This in turn could then be accessed by software smart enough to
make a choice, e.g. socket-intents or other network middleware.

Regards,

-- 
Bernd May

Attachment: signature.asc
Description: OpenPGP digital signature