Hi, On Fri, May 02, 2014 at 08:44:06PM +0200, Steven Barth wrote: > In regular OpenWrt ip6assign means that - as already written - a /60 (if > available) is taken from the DP and the assigned to the given interface. > That value was chosen rather arbitrarily. The first /64 of that DP is > handed out via RA and stateful DHCPv6 (IA_NA). The rest of the /60 (or > whatever you set in ip6assign) can be acquired by downstream routers on > that interface via DHCPv6-PD.
Ah! So it's a "reservation" for downstream-DHCPv6-PD. It's still slightly confusing, tbh, to see the ifconfig and route values point the /60 towards the actual interface. But maybe that's just me :-) - it certainly isn't causing problems, just to say that again. > Regarding homenet / hnetd, please see http://www.homewrt.org for some > documentation. Also feel free to ask me (I'm one of the authors of the > draft and implementation) or join us on #hnet-hackers on freenode about > anything you might need / want to know. Thanks for the offer. Right now, only one of the routers is life (due to convenience of access to "stuff", like "arbitrary upstream routers", I'm building this at office, and 3 out of 4 boxes are still at home...), but I'm planning to have this operational in the next few days - and I'm sure questions will come. I've read everything that's linked from the start page on http://www.homewrt.org/ - but it's not really much as far as "how can I see what it does? how can I debug it? Is there only one single option to turn this on and off ("option proto 'hnet'"), or is there more? Does hnetd handle IPv4 and IPv6 today? How do I force selection of a certain /64 on a specific interface?" question go... :-) (I *have* read all the *-homenet-* drafts, so I feel I understand the basic concepts and requirements, but now I need to "see" it) > hnetd implements its own prefix delegation algorithm (as its managed > throughout the homenet) so usual ip6assign-stuff doesn't apply here. You Understood. I was just curious what it was, spending too much time on "side-track" curiousity again :-) > can also use it with bridges but it might make more sense to use > individual ports instead to e.g. avoid unnecessary traffic on WiFi or > make proper use of the border detection (e.g. use one switch-port for a > second uplink and another for downstream or so). I think the "does not like bridges" thing came from the old stuff on http://github.org/fingon/hnet-core/ or something like that - can't find it right now. It's good to know that it works, though I'm fully intending to not use bridging anyway :-) - I really really like the hnet approach. Will let you know how it works out! thanks, gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany [email protected] fax: +49-89-35655025 [email protected]
pgpnvZ5qjUsp7.pgp
Description: PGP signature
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
