On 22.02.2015 09:38, Dave Taht wrote:
OK, I think. So if I have a stanza like this?
config interface 'lan'
option ifname 'eth0.1'
option force_link '1'
option proto 'static'
option ipaddr '172.21.80.1'
option netmask '255.255.255.0'
option ip6assign '64'
config interface 'homenet1'
option ifname 'eth0.1'
option proto ´hnet'
option disable_pa 1
that interface would act as a relay, and not assign a /64 to the lan interface?
As noted please avoid assigning the names "lan" or "wan" to interfaces
running hnet on, but besides that it's worth a try. I'm sort of on
holiday for a few days, so I can try it out some time late next week.
I note the last time I tried to install hnet-full it bricked the
router, killing dnsmasq entirely, killing dhcp, etc, so I was leery of
experimenting again... but I am willing to try again, being a glutton
for pain at 1AM.
Was this with CeroWrt? I'd recommend starting with a vanilla OpenWrt.
moving on to more complexity, so getting that first 64 would look like?
config interface 'lan'
option ifname 'eth0.1'
option force_link '1'
option proto 'static'
option ipaddr '172.21.80.1'
option netmask '255.255.255.0'
config interface 'homenet1'
option ifname 'eth0.1'
option proto 'hnet'
option disable_pa 0
option p6_plen 64
?
Then getting a dynamic ipv4?
Just removing disable_pa and (i)p6_plen will resort to defaults, i.e. 1
/64 per link for IPv6 and 1 /24 for IPv4.
Moving into more functionality, I see the documentation recommends
against using the hnet protocol on predefined interfaces like lan
entirely... if I wanted ipv4 address assignment (and I dont - without
dns to ip mapping actually working finding a box again is impossible),
what happens to these two stanzas?
The only reason to not use "wan" or "lan" is that OpenWrt's firewall has
some special semantics for interface named after firewall zones. So you
can just rename the sections and it will work. Or as you noted
previously you can add an additional static-configuration section for
the same interface (you just shouldn't name it "lan" or "wan").
How does the firewall pick it all up?
hnetd tells the firewall which firewall zone ("lan" or "wan") an
interface should be assigned to. The zones depend on border discovery
(manual or automatic).
And then, there is the final caution to the winds, go pure hnetd
option. This is my freshly built, openwrt chaos calmer based config
file. It is an interior gw router (no nat):
http://snapon.lab.bufferbloat.net/~d/network
What changes are needed to drink the koolaid?
For each interfaces you want hnet to run on add a config section.
config interface homnet1
option ifname foo1
option proto hnet
If the original interface-name was "lan" or "wan" you should rename them
to something different (but do not need to change anything else).
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
