> On 24 Nov 2016, at 11.36, Juliusz Chroboczek <[email protected]> wrote: > >>> - who merges data from multiple links? (I'd wish that the hybrid >>> proxies compute a minimal spanning tree and perform peer-to-peer >>> magic, but I suspect you're generating a config file dynamically >>> and restarting dnsmasq whenever the set of hybrid proxies changes.) > >> There is no need for merging, there are only few zones. They are all in >> DNS-SD browse/legacy browse path, and also in DNS search path. The >> configuration is actually static in my case. The benefit of merging is >> limited as there are only few subnets. > > I'm probably just being slow, please bear with me. There's one hybrid > proxy on each link, right? Each of these only learns about the mDNS > announcements done on this particular link, right? Dnsmasq must somehow > get the union of all of these data, right? > > So is dnsmasq speaking to localhost:54 only, and localhost:54 somehow > learns all the data, or is dnsmasq speaking too foo:54 for all values of > foo? If the latter (which I suspect), how does hnetd communicate the list > of foos to dnsmasq?
When done dynamically (i.e. by hnetd), dnsmasqs are configured to: - forward requests for non-local zones to nodes where they are based (based on HNCP state) - forward locally to the ohp local zones In my static config (which is 'official' HNCP free), I just have configuration files which mirror this idea. Cheers, -Markus _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
