-------- Forwarded Message -------- Subject: [gluon] [SITE] Site seeds and VXLANs Date: Tue, 27 Jun 2017 23:41:46 +0200 From: Matthias Schiffer mschiffer@universe-factory.net To: gluon@luebeck.freifunk.net gluon@luebeck.freifunk.net
Hi, I've just pushed a bunch of commits adding support for wired meshing over VXLANs.
What does this mean?
- Newly setup Gluon nodes will encapsulate wired mesh traffic (Mesh-on-LAN/WAN) in UDP packets using the VXLAN protocol. Instead of the batman-adv ethertype, the packets will be normal IPv6 UDP on port 4789 using link-local adresses for unicast, and the address ff02::15c for multicast
- Nodes upgraded from Gluon v2017.1 or older will continue to use the "legacy" wired meshing without VLXANs for now.
- Gluon v2017.2 will support both VXLANs and the legacy protocol. The setting can be changed in the Advanced Settings of the Config Mode, or by setting the "legacy" attribute of the mesh_wan and mesh_lan UCI sections. Both sides of a wired mesh connection must be set to the same protocol for the link to work.
- Gluon v2017.2 + 1 will drop legacy support, settings will be upgraded to use VXLANs automatically
- Each mesh domain / site will use a unique VXLAN ID, ensuring that accidental wired mesh connections between different sites won't bridge the meshes (especially important in sites that automatically assign nodes to mesh domains using tools like the Hood Selector)
To assign a unique VXLAN ID to a site, a new setting must be added to site.conf: the site seed. The site seed simply consists of 32 bytes of random data in hexadecimal representation. Please refer to the documentation and the included example at [1] for the recommended way to generate a site seed.
-- NeoRaider