Hey Gui
Thanks for that info. I'll add it...
/axel
On 10/05/2013 10:48 PM, Gui Iribarren wrote:
just to note down what we talked yesterday:
1) on the wiki,
http://bmx6.net/projects/bmx6/wiki/Wiki#Blocked-Nodes
there's no mention at all that the module "ip6_tunnel" is needed,
probably useful to note on compile/install section?
2) there's also no documentation whatsoever about globalPrefix
only thing i could find is on the help:
--globalPrefix <NETWORK>/<PREFIX-LENGTH>
specify global prefix for interfaces
but from what i tried, if a globalPrefix is set for an interface (or
globally) and the interface doesn't have any ip on that prefix, then
it does not get an autoconfigured fd66:66:66 either, and the interface
stays disabled.
I don't know if that's on purpose, i expected that if the interface
had no address in that prefix, it would get activated anyway with the
usual fd66:66:66.
in any case maybe doc should be more verbose about how it works?
finally,
3) you asked for some links about tunnels:
tinc-vpn is the mesh vpn, that works perfectly and is a great idea,
but being userspace it kills cpu with high traffic
http://tinc-vpn.org/
tunneldigger was made by slovenian people, is a simple userspace
daemon that sets up L2TP tunnels (kernelspace) to a set of tunnel
"servers"
https://wlan-si.net/en/blog/2012/10/29/tunneldigger-the-new-vpn-solution/
high traffic is not an issue, but it works in a hub-and-spoke model,
there's no mesh concept whatsoever
cheers!
gui
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev