> Right now HNCP doesn't actually seem to have a TLV for advertising
> resolvers.
That's exactly what I was trying to get at.
> How does this work now?
Not very well.
HNCP announces *external* resolvers in the DHCPv4- and DHCPv6-DATA
sub-TLVs of the EXTERNAL-CONNECTION TLV. Hnetd uses this data to set up
a recursive DNS server which has all the usual smarts for selecting the
server to forward to, and also acts as an authoritative server for some
local zones (I'm shaky on the exact details). Shncpd is much dumber, it
just merges all the EXTERNAL-CONNECTIONs' data and pushes the result to
the client using RA and DHCPv4 (shcnpd has no support for DHCPv6 yet).
There is no provision for advertising a DNS server that's not associated
with an external connection, i.e. that's within the Homenet.
> I think the election process is probably the hardest thing in this
> solution, and I am hoping someone already knows how to do it... :)
HNCP does perform a number of link-local elections, and uses two different
mechanisms:
- for advertising assigned prefixes, it uses an OSPF-like election
mechanism, but with no pre-elected backup;
- for choosing e.g. DHCPv4 servers, it uses an ISIS-like election
mechanism, which I happen to believe is a bad choice.
It should be possible to add a Homenet-local election mechanism to HNCP in
order to pick a recursive DNS server, but this would constitute a non-trivial
change to the protocol. (Elections are fun, except in the UK, so I'd be
quite willing to help.)
-- Juliusz
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
