On 23.4.2016, at 19.39, Juliusz Chroboczek <[email protected]> wrote: >> I’m starting by running shncpd on a boundary router and tried a trivial >> installation. > Excellent, thanks. > >> I don’t see how dns gets updated. Are such updates out of scope of >> shncpd? > > Do you mean, (1) how is a DNS resolver advertised to clients, or > (2) how clients are registered in DNS ? > > (1) is done by using the -N flag on the router advertising an external > connection (-E). This flag can be repeated multiple times.
hnetd grabs this automatically from wan-facing DHCP client, but again, requires integration to work nicely (odhcp6c glue script supported on most Linux platforms). Clients on the other hand are given always just first-hop router address. > (2) is a host issue, so I believe it is better handled outside of shncpd, > but I'm quite willing to be convinced otherwise. (The obvious alternative > would be to have shncpd update DNS when it gives out a DHCP lease, but > that would mean giving up on stateless autoconf.) Well, DHCPv4 is stateful anyway, and you could in theory bind state from there as well (at least if you do IPv4). >> Are they in scope for the other homenet protocols? > Markus, Steven, Ted? What's the plan here? Do we count on mDNS proxying, > or should we be advertising an RFC 2136 server over HNCP? I think the plan varies ;-) hnetd (and current HNCP + my expired autoconf draft) are based on the idea of using mDNS _and/or stateful DHCPv4 and/or stateful DHCPv6 to determine what’s on each link, and advertise the routers responsible for each link across the homenet. It does work with ‘current stuff’ for some relatively high % of likelihood. Ted’s draft proposes either learn-from-mDNS (=proxy DNS-update) and/or (manually/automatically configured client-sourced) DNS-update scheme. I am worried about zone merging + conflict resolution, although if it works out it sounds like a good solution. (Zone merging + plain hybrid proxy is at least very problematic, if you want hybrid proxies to remain stateless. I have looked at it and it is neither pretty nor efficient.) Cheers, -Markus _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
