- Apr 27, 2018
-
-
Matthias Schiffer authored
In multidomain setups, VXLAN is enabled by default, but can be disabled in domain configs using the mesh/vxlan option. In single domain setups, the mesh/vxlan option is mandatory. The UCI option for legacy mode is removed. Fixes #1364
-
- Apr 15, 2018
-
-
Christof Schulze authored
gluon-core, gluon-l3roamd: introduce script gluon-list-mesh-interfaces that lists all currently active mesh interfaces
-
- Apr 13, 2018
-
-
Matthias Schiffer authored
The script cleaned up an old setting that was removed in 2014.
-
Matthias Schiffer authored
-
Matthias Schiffer authored
net.ipv6.conf.br-client.forwarding is moved from gluon-client-bridge to gluon-mesh-batman-adv, as the setting is not useful with non-bridged protocols.
-
- Apr 11, 2018
-
-
Matthias Schiffer authored
-
- Mar 16, 2018
-
-
Matthias Schiffer authored
Our VXLAN setup was changed to accept VXLAN packets without checksum almost 2 months ago, so we can disable sending the checksums now as well. Slightly improves performance.
-
- Jan 24, 2018
-
-
Matthias Schiffer authored
Also disabling TX checksums and not only allowing incoming packets without checksum will provide another small speedup. As doing so would break wired meshing with VXLAN-enabled nodes that require non-zero checksums, we will wait a few days before this step.
-
- Jan 19, 2018
- Jan 18, 2018
-
-
lemoer authored
[Matthias Schiffer: change section name and commit message]
-
- Jun 27, 2017
-
-
Matthias Schiffer authored
Based-on-patch-by:
Christof Schulze <christof.schulze@gmx.net>
-
Christof Schulze authored
-
Matthias Schiffer authored
-
Matthias Schiffer authored
The new proto will simplify the switch to VXLAN encapsulation.
-
- Apr 12, 2017
-
-
Matthias Schiffer authored
In addition, transitive and fixed_mtu now default to 0 instead of an empty string.
-
- Feb 24, 2017
-
-
Christof Schulze authored
-
- Sep 07, 2016
-
-
Matthias Schiffer authored
This new protocol will allow configuring mesh interfaces independently of the used mesh protocol.
-
- Jul 10, 2016
-
-
Jan-Tarek Butt authored
-
Matthias Schiffer authored
-
- Jun 22, 2016
-
-
Matthias Schiffer authored
Fixes #121 Based-on-patch-by:
Tobias Hachmer <tobias@hachmer.de>
-
Matthias Schiffer authored
-
- Jun 17, 2016
-
-
Sven Eckelmann authored
The new MR1750v2 device support is only available in LEDE master. The relevant patches have to backported to add support for them in Gluon Signed-off-by:
Sven Eckelmann <sven.eckelmann@open-mesh.com>
-
Sven Eckelmann authored
The new OM2P-HSv3 device support is only available in LEDE master. The relevant patches have to backported to add support for them in Gluon Signed-off-by:
Sven Eckelmann <sven.eckelmann@open-mesh.com>
-
- May 23, 2016
-
-
Sven Eckelmann authored
The OpenMesh devices have a sticker with the eth0 mac address on the bottom. Also all other mac addresses are calculated based on this address. Therefore, it is better to use this as primary mac address instead of the WiFi mac address. Signed-off-by:
Sven Eckelmann <sven.eckelmann@open-mesh.com>
-
- May 13, 2016
-
-
Matthias Schiffer authored
Fixes #764
-
Matthias Schiffer authored
Also backport some patches improving QCA956x support.
-
- Apr 27, 2016
-
-
lemoer authored
While ath9k/ath10k devices can supprt VIFs with any combination of MAC addresses, there are also adapters which have a hardware MAC filter which only allows a few bits to differ. This commit changes the addresses of all VIFs to ony differ in the last 3 bits, which is required to support many Ralink/Mediatek based WLAN adapters. Technically, the new addresses are generated by calculating an MD5 hash of the primary MAC address and using a part of this hash as a prefix for the MAC addresses. The addresses (BSSIDs) of the AP VIFs are also reused for the LAN and WAN interfaces in mesh-on-LAN/WAN mode to reduce the number of needed addresses, and thus reduce the chance of collisions. This is not a problem as the MAC addresses of the AP VIFs are never used except as BSSID, and thus not seen by routing protocols like batman-adv. Fixes #648 [Matthias Schiffer: rewrote commit message]
-
- Apr 24, 2016
-
-
Matthias Schiffer authored
-
- Apr 22, 2016
-
-
Jan Niehusmann authored
Device information can be found at: http://www.8devices.com/products/carambola-2 https://wiki.openwrt.org/toh/8devices/carambola2 I only did some minimal testing of gluon on the carambola 2 development board: - Config mode works - Connects to Wifi Mesh - Allows clients to connect Notably, autoupgrade has not yet been tested. Change to 010-primary-mac is necessary as the mac address printed on the sticker is the one of eth0, not the wifi mac.
-
- Apr 03, 2016
-
-
Jan-Philipp Litza authored
-
- Apr 02, 2016
-
-
Matthias Schiffer authored
Avoid commiting configs inbetween to decrease number of flash writes. Fixes #714.
-
- Mar 08, 2016
-
-
Linus Lüssing authored
Adopt the according modifications to the default firewall settings of the WAN interface from OpenWRT, revision 45613. Signed-off-by:
Linus Lüssing <linus.luessing@c0d3.blue>
-
- Feb 10, 2016
-
-
Kokel authored
This new feature introduces the new uci section 'gluon-core.wireless' with a preserve_channels option: * preserve_channels (boolean) By setting this option to 1 (true) wifi channels will be preserved during upgrades.
-
- Jan 02, 2016
-
-
Matthias Schiffer authored
This will allow us to use its content from other languages than Lua as well.
-
- Oct 28, 2015
-
-
Matthias Schiffer authored
Fixes #534
-
- Oct 27, 2015
-
-
Matthias Schiffer authored
Fixes #487
-
- Oct 26, 2015
-
-
Matthias Schiffer authored
gluon-radio-config contained only a single file. The code has been adjusted to allow creating a Gluon configuration without WLAN support by removing the wifi24 and wifi5 sections from site.conf.
-
- Oct 14, 2015
-
-
Matthias Schiffer authored
The new options allow specifying custom repositories and are evaluated in an upgrade script, not during build.
-
- Sep 13, 2015
-