- Apr 21, 2021
-
-
For parker we need DHCP on the client interface. Ths rule prevents us from doing so. In addition: make sure old rules will be deleted on upgrade.
-
- May 28, 2020
-
-
David Bauer authored
Separate wireless-related helper methods from the util module to a new wireless module. This keeps them separated, as the amount of wireless helpers increased in the past, justifying a separate module.
-
- May 24, 2020
-
-
Ruben Barkow-Kuder authored
-
- Mar 31, 2020
-
-
David Bauer authored
-
- Dec 07, 2018
-
-
Martin Weinelt authored
Allow odhcp6c to fork the script to handle router advertisments in 30 seconds intervals. This is the value that was previously used in Gluon v2018.1 / LEDE 17.01. The default value is 3 seconds and while it is RFC compliant it can put alot of pressure on even moderately sized devices. Signed-off-by:
Martin Weinelt <martin@darmstadt.freifunk.net>
-
- Jul 22, 2018
-
-
Sven Eckelmann authored
The commit b3762fc6 ("gluon-client-bridge: move IPv4 local subnet route to br-client (#1312)") moves the IPv4 prefix from the local-port interface to br-client. A client requesting an IPv4 connection to the IPv4 anycast address of the node (the device running gluon) will create following packets: 1. ARP packet from client to get the MAC of the mac address of the anycast IPv4 address 2. ARP reply from node to client with the anycast MAC address for the IPv4 anycast address 3. IPv4 packet from client which requires reply (for example ICMP echo request) 4. ARP request for the client MAC address for its IPv4 address in prefix4 (done with the mac address of br-client and transmitted over br-client) 5. IPv4 packet from node (transmitted over br-client with br-client MAC address) as reply for the client IPv4 packet (for example ICMP echo reply) The step 4 and 5 are problematic here because packets use the node specific MAC addresses from br-client instead of the anycast MAC address. The client will receive the ARP packet with the node specific MAC address and change their own neighbor IP (translation) table. This will for example break the access to the status page to the connected device or the anycast DNS forwarder implementation when the client roams to a different node. This reverts commit b3762fc6 and adds an upgrade code to remove local_node_route on on existing installations.
-
- Apr 13, 2018
-
-
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.
-
- Feb 15, 2018
-
-
T-X authored
This patch moves the prefix4 subnet route from the local-node veth device to br-client (while keeping the next node ipv4 address on the local node device). This is in preparation to allow routing over the br-client interface later.
-
Matthias Schiffer authored
Allows to remove some redundant UCI lookups.
-
- Jan 11, 2018
-
-
Matthias Schiffer authored
The 'auto' attribute still allows enabling the interface using ifup, which is not intended when wired mesh is disabled.
-
- Dec 27, 2017
-
-
Matthias Schiffer authored
As core defines basic rules for this zone, it makes sense to create it there.
-
- Nov 25, 2017
-
-
Christof Schulze authored
* gluon-core, gluon-client-bridge: introduce new firewall zone: local_client * gluon-core: put clients in local_client zone, introduce drop-zone, set dns-rules and zones * gluon-respondd: allow respondd on mesh * gluon-status-page-api: allow http input on mesh and client
-
- Aug 11, 2017
-
-
Matthias Schiffer authored
Some files have received some additional refactoring.
-
- Aug 08, 2017
-
-
Matthias Schiffer authored
In particular, this affects users of gluon.util.iterate_radios.
-
Matthias Schiffer authored
-
Matthias Schiffer authored
-
- Jun 26, 2017
-
-
Matthias Schiffer authored
The next-node MAC address doesn't need to be unique in different communities, so we can as well add a default value.
-
- Apr 13, 2017
-
-
Linus Lüssing authored
LEDE recently disabled multicast snooping by default: https://git.lede-project.org/?p=project/netifd.git;a=commitdiff;h=52541140f8138e31958cdc3d7e42a4029fa6bbc9 Reenable it for Gluon as there have been no confirmed issues for LEDE and no negative reports concerning Gluon v2016.2.x so far. Closes #1025. Signed-off-by:
Linus Lüssing <linus.luessing@c0d3.blue>
-
- Apr 10, 2017
-
-
Matthias Schiffer authored
-
Matthias Schiffer authored
gluon-core: gluon.util: pass UCI cursor as argument to iterate_radios() instead of using local context
-
- Feb 23, 2017
-
-
Matthias Schiffer authored
We always want to prefer the unique node address for outgoing traffic. Note that this doesn't have an effect with batman-adv, as usually br-client will be the outgoing interface, so the unique address would be chosen anyways.
-
- Feb 10, 2017
-
-
Matthias Schiffer authored
macvlan interfaces never directly exchange traffic with the underlying interface, but only with other hosts behind the interface. In consequence, router advertisements from the uradvd running on br-client could never reach local-node, preventing it from getting an IPv6 address without RAs from an external radvd. Fix this be replacing the macvlan interface with a veth pair (with the peer interface in br-client). As a side effect, this saves about 5KB of flash, as the veth module is simpler than macvlan.
-
Matthias Schiffer authored
When preparing the migration from macvlan to veth for local-node, MAC address conflicts occurred as some ports of br-client had the same address as local-node. Reverting the roles of both interfaces fixes this. By default, br-client is left as an interface without addresses and firewall rules that drop everything, so the bridge is used to connect its ports only. gluon-mesh-batman-adv-core changes this to the usual set of addresses and firewall rules.
-
Matthias Schiffer authored
Prepare reverting the roles of br-client and local-node to their state before 8c4403ba.
-
Matthias Schiffer authored
Also simplify the local_node.peerdns setting.
-
Matthias Schiffer authored
-
Matthias Schiffer authored
-
Matthias Schiffer authored
We also make use of the boolean support of simple-uci to make scripts clearer.
-
- Jan 18, 2017
-
-
Matthias Schiffer authored
-
- Dec 10, 2016
-
-
Matthias Schiffer authored
gluon-client-bridge, gluon-mesh-batman-adv-core: switch roles of br-client and local-node interfaces MAC and IP addresses are switched. This makes the gluon-client-bridge package more useful for different routing protocols that don't need a unique address on the client bridge. As a side effect, gluon-radvd is now using the next-node address, which had been considered before, but was dismissed to avoid having gluon-radvd depend on gluon-next-node and gluon-mesh-batman-adv. This will be useful for announcing default routes via gluon-radvd. One downside is that this introduces a minor dependency on batman-adv in gluon-respondd: the hotplug script that checked for the client interface before will now check for local-node. This doesn't really matter: for mesh protocols without a local-node interface, the check will do nothing (which makes sense, as there is no interface to bind to for mesh-wide respondd).
-
- Sep 07, 2016
-
-
Matthias Schiffer authored
gluon-client-bridge: add LAN interfaces to client bridge by default (instead of doing this in the batman-adv-specific scripts) This allows to weaken the gluon-mesh-batman-adv-core dependency of gluon-luci-portconfig to gluon-client-bridge.
-
- Jul 27, 2016
-
-
Matthias Schiffer authored
-
- Jul 20, 2016
-
-
Matthias Schiffer authored
Some drivers (mt76) don't support arbitrary MAC addresses. Use the addresses provided by the driver (avoiding the primary address) by default, but fall back to our has-based scheme when the driver doesn't provide (enough) addresses.
-
Matthias Schiffer authored
-
- Jul 10, 2016
-
-
Jan-Tarek Butt authored
-