Am 02.05.2014 21:00, schrieb Gert Doering:
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.
Yes, please see other e-mail in the thread for "justification" ;)
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... :-)
Yeah to turn it on on a given interface simply change the proto to
"hnet" (and remove any previous interface using the same interface in
/etc/config/network). If you want to not use bridging you need to create
one logical interface in /etc/config/network for each switch-port / vlan.
Once you have configured an interface e.g. like this:
config interface h1
option ifname eth1
option proto hnet
and brough it up with /etc/init.d/network reload && ifup h1 you can
watch its state using:
ifstatus h1. hnet also automatically creates a dhcp and dhcpv6 client
subinterface which you can also monitor using ifstatus h1_4 and ifstatus
h1_6. If there is 6rd or dslite provided by dhcp / dhcpv6 then there is
a in addition an interface h1_6rd or h1_dslite. All these virtual
interface are created automatically (you don't need to put then in
/etc/config/network).
Also hnetd at the moment is very talkative in syslog so you should get a
pretty good view of whats going on.
Forcing a certain prefix on an interface is implemented but not exposed
to interface config yet. I will try to put it on todo for sometime next
week and push a new version to OpenWrt once its working shouldn't be
very hard.
Regards,
Steven
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
