Hi,
I want to continue the upstream maintenance of bmx6 documentation in the
master branch itself.
Therefore I've translated the wiki to markdown syntax which is nicely
represented by some code management systems like here
https://github.com/axn/bmx6/blob/master/README.md
As a consequence, the current wiki at
http://bmx6.net/projects/bmx6/wiki
will mostly point to the above link but remains open for user contributions
which shall eventually be merged into the upstream README.md.
I also added your points. See inline...
> 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?
https://github.com/axn/bmx6/blob/master/README.md#tunnel-requirements
>> 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?
https://github.com/axn/bmx6/blob/master/README.md#address-auto-and-manual-c…
>>
>> 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/
yea, I must look into this...
>
>
>
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
>>
> _______________________________________________ Dev mailing list
> Dev(a)lists.libre-mesh.org
>
https://lists.libre-mesh.org/mailman/listinfo/dev
- --
./p4u
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)
iQEcBAEBAgAGBQJSU84ZAAoJEAX7rWpc+YnNa8gIAK+9OQVHDoqrsgqlEus/wSYd
IrnhSN5/oAilEVm7fHlxHKmztl8kPyMv7y7hDed822ArXxPrynjXL2NmPxQSXFsw
SXIb4+NGmw3pJ2dDB/DLqUUOOAv1mlVNt3lY9e2lbNCXiRZd6p2i1sYgjOnkugLV
oQIG2dky6Z4uUCAyr1Uh/2t+xYzzUQo+a3+geShbO42icTJBGFGfLZcUX4UFwesr
o/7ixUJwb+XIdnRqcUUIa1e+30hzGdoshMEBi5mZAimFT2z0MbTizpYEYmXfMxcU
jQmASuGihFXyy9HWNsmc49PEWRm5+hQ0xSfuk4z8LUDOh6i1gVwkv8jewNP5/jY=
=DcR1
-----END PGP SIGNATURE-----
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev