On Mon, Jan 7, 2013 at 11:10 AM, Juliusz Chroboczek <[email protected]> wrote: >> One of the things I was hoping ahcp would gain one day would be a way >> to suggest a name to the ahcp server, and the ahcp server assign one, >> much like how dhcp works today. > > I happen to prefer the model where the client registers its preferred > name with a dynamic DNS service rather than having the DHCP/AHCP > server do it on its behalf.
I used to feel that way. Now I feel that getting names in a *locally* unified manner is more important... > What application do you have in mind? Assume no global connectivity, where do you register? Assuming IPs you'd rather keep private, where do you register? Since dnsmasq is rather common on just about everything embedded, and doesn't support a dynupdate facility, but DOES: assign names to ipv4 addresses via dhcpv4 assign name to slaac addresses that line up with the dhcpv4 supports dhcpv6 and naming those... AHCP was looking kind of lonely, and indeed, the latest set of updates in openwrt barrier breaker, break core AHCP ideas such as single IP address for all interfaces... and don't co-exist with the netifd system well... I had hoped to get the time to blend in ahcp server support to dnsmasq as well (thus gaining two interoparable implementations), but never got further than an outline and something that compiled, briefly. >> I've often thought adding names to the fe80:: addresses as well might >> be useful. > > ? thought was: fe80::whatever routername.routers.mydomain.com Would make interpreting babelweb data in particular easier. > -- Juliusz -- Dave Täht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html _______________________________________________ Babel-users mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
