- Jul 10, 2016
-
-
Jan-Tarek Butt authored
-
Matthias Schiffer authored
-
- Jul 09, 2016
-
-
Matthias Schiffer authored
gluon-luci-wifi-config: fix to work with legacy configs using macaddr instead of path to identify radios
-
- 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>
-
- Jun 02, 2016
-
-
Thomas Weißschuh authored
-
- May 27, 2016
-
-
Jan-Philipp Litza authored
-
- May 26, 2016
-
-
Jan-Philipp Litza authored
Most doubles that are delivered via respondd have limited input precision, but are converted with up to 17 digits of precision. That can cause ugly blowups like 0.2800000000000001 in the output, which is avoided by specifying better format strings (like "%.2f" in most cases).
-
- 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 19, 2016
-
-
Matthias Schiffer authored
Don't fork reboot process before all package hooks have been handled and rendering is complete. Replace debug.setfenv hack to close stdout with nixio.dup. Fixes #772
-
- May 17, 2016
-
-
Matthias Schiffer authored
This was causing "recursive dependency" errors and potentially broken configurations.
-
- May 16, 2016
-
-
Sven Eckelmann authored
The image validation currently fails on some devices (tested OpenMesh) because it isn't done via sysupgrade. But the checks depend partially on the integration in sysupgrade (e.g. via loops that can be stopped via "break statements"). Instead of hacking its own version check, it is easier and better tested to just use 'sysupgrade -T' like it is already done by LuCI. 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.
-
Matthias Schiffer authored
Lua's tables are 1-based, so we must decrement the index by 1 to get the desired MAC addresses. By not doing this, the second IBSS interface would get the address with index 8, but only indices 0..7 are available. Fixes: c73a12e0
-
- Apr 28, 2016
-
-
kb-light authored
Signed-off-by:
kb-light <freifunk@kb-light.de>
-
- Apr 27, 2016
-
-
Matthias Schiffer authored
-
kb-light authored
-
kb-light authored
-
Matthias Schiffer authored
There are a few devices which have more than one LAN interface (for example some revision of the TL-WR941ND, which uses a DSA-based switch, so each switch port has its own netdev.) On these devices we need a bridge for mesh-on-lan (as the alternative of adding them to batman-adv individually would need too many MAC addresses.)
-
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]
-
corvusmo authored
-
- Apr 26, 2016
-
-
Matthias Schiffer authored
We have Git for history, there's no reason to keep old files that aren't used anymore.
-
- Apr 24, 2016
-
-
Matthias Schiffer authored
-
Matthias Schiffer authored
It is not used anymore.
-
- 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 08, 2016
-
-
corvusmo authored
Fixes #698
-
- 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.
-
Matthias Schiffer authored
It doesn't seem like this mistake had any effect.
-
- Mar 10, 2016
-
-
Linus Lüssing authored
We are mostly dealing with the 2.4GHz crap-band here, so increasing the IGMP/MLD robustness parameter to three to be able to compensate for up to two consecutive instead of just one lost packet. Signed-off-by:
Linus Lüssing <linus.luessing@c0d3.blue>
-
Linus Lüssing authored
There are some devices not acting properly to roaming events, in that they do not timely reissue IGMP/MLD reports after reconnecting. To compensate for that this commit reduces the query interval from 125 seconds to 20 and the query response interval from 20 seconds to 5. This reduces a timeout to 20+5 seconds in the worst-case (12.5s average) after a roaming event for such broken devices. This should be below the 30s "impatient user threshold" and below any connection timeout. Until the bridge multicast snooping + querier gets re-enabled this is a no-op. Signed-off-by:
Linus Lüssing <linus.luessing@c0d3.blue>
-
- Mar 08, 2016
-
-
Matthias Schiffer authored
This include wasn't actually missing, but well hidden behind the iwinfo.h include. Make this more obvious.
-
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>
-
Linus Lüssing authored
An IGMP/MLD domain split will prevent us from being able to track multicast listeners on other nodes. Therefore we need to always hand any multicast packets we received from local clients to batman-adv. With bridge multicast snooping disabled, the current setting in Gluon, this is already the case. However, in preparation to enabling multicast snooping, we need to enforce forwarding towards batman-adv by setting the bridge port option "multicast_router" to 2. Signed-off-by:
Linus Lüssing <linus.luessing@c0d3.blue>
-
- Feb 29, 2016
-
-
Matthias Schiffer authored
-
Matthias Schiffer authored
It is not supported by all browsers yet. Also change load display always to display 2 decimal digits (as it is read from the kernel with 2 decimal digits). Fixes #606
-
Matthias Schiffer authored
notUpdated is a Set, to a for-in loop doesn't work. Fixes #657
-