- May 30, 2021
-
-
Kasalehlia authored
-
Kasalehlia authored
-
- Apr 21, 2021
-
-
This change removes the prefix4 and prefix6 attributes from the site.conf. These do not make sense in the context of parker. Packages that are usually used in parker do not use these anymore. Some other packages do - you should not enable those :-) With this change a ipv6 route to prefix_6 will no longer be set on br-client. Systems that already have this route will keep it. With this change the (not working) redirect in the http status page has been removed. We should consider to add this later on.
-
Packets which have a destination MAC of other local nodes should not be redirected, as this possibly results in routing loops in networks with more than one uplink. Signed-off-by:
Jan Luebbe <sho@stratum0.net>
-
-
at least concerning traffic limits
-
This change let's uradvd deliver the v6 link-local of this node as DNS. With this change DNS-requests are not affected by the radv-filterd -rewrites during roaming. Signed-off-by:
Chrissi^ <chris@tinyhost.de>
-
Signed-off-by:
Jan Luebbe <jluebbe@debian.org>
-
When multiple routers are in the same local mesh and clients roam from one (A) to the next (B), the change of global IP and default gateway are not synchronized. This leads to packets with an address belonging to router A to be sent via router B (or the other way around). Those packets are then dropped by wireguard at the concentrator. To avoid this, we let gluon-radv-filterd monitor router advertisements and keep a list of neighbouring v6 networks. With this information, it can maintain a set of ebtables DNAT rules to redirect the packets to the matching gateway. Signed-off-by:
Jan Luebbe <jluebbe@debian.org>
-
-
Using this change an VPN-node announces it's own IPv6 as DNS server. /tmp/addr6 is written by nodeoute.lua during runtime configuration. Signed-off-by:
Chrissi^ <chris@tinyhost.de>
-
This change alles meshed PARKER-Nodes to forward IPv6 to the next node. Signed-off-by:
Chrissi^ <chris@tinyhost.de>
-
-
-
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.
-
-
-
Signed-off-by:
Jan Luebbe <jlu@pengutronix.de>
-
-
Signed-off-by:
Chrissi^ <chris@tinyhost.de>
-
Contact Info is no longer added on FFBS nodes since our gluon release of v2017.1.8. On nodes that have been running before this release this field is set to "Intentionally left blank". This Info should not be shown on the statuspage. Signed-off-by:
Chrissi^ <chris@tinyhost.de>
-
- Apr 05, 2021
-
-
Matthias Schiffer authored
No package uses l2tp_ip. (cherry picked from commit 2ecbe488)
-
- Jan 12, 2021
-
-
Matthias Schiffer authored
Fixes warnings about implicit pointer-to-int and int-to-pointer casts. Fixes: 59a4cd63 ("gluon-respondd: expose OWE clients in nodeinfo") (cherry picked from commit 17123aa4)
-
Matthias Schiffer authored
Fixes respondd on 64bit archs, as gluonutil_get_primary_domain() was assumed to return int without the prototype. Fixes: bcf57467 ("libgluonutil: implement gluonutil_get_primary_domain()") (cherry picked from commit 52ee93f1)
-
- Aug 22, 2020
-
-
Matthias Schiffer authored
Reorder scripts so that the mesh_lan interface is accounted for. Two other firewall upgrade scripts (mesh-babel and l3roamd) are reordered as well. While there seems to be no hard dependency at the moment, it makes sense to run the basic setup first, also to avoid problems with future changes. Closes: #2090 Fixes: ed094bc6 ("gluon-core: firewall: Allow custom gluon_wired interfaces (#2041)") (cherry picked from commit de5ebfa4)
-
- Jul 13, 2020
-
-
David Bauer authored
This will hide the outdoor mode setting on compatible devices in case the defined channels should be preserved. Otherwise a user might be under the impression their device is compliant with outdoor operation when in reality it still uses prohibited channels. (cherry picked from commit 73b830eb)
-
Matthias Schiffer authored
- #pragma once include guard - include string.h to get memset and memcmp prototypes to fix respondd provider build warning (cherry picked from commit e32fa5bc)
-
Matthias Schiffer authored
When the network connectivity is bad, routers may not appear in the translation tables, or there may be no originator with TQ >0. Such conditions to not warrant spamming the log with error messages. (cherry picked from commit fcd07de6)
-
Matthias Schiffer authored
(cherry picked from commit e384f899)
-
- Jun 14, 2020
-
-
David Bauer authored
Backporting the MFP patch allows us to utilize WPA3 features on this target. Tested on TP-Link Archer C20i
-
- Jun 13, 2020
-
-
Matthias Schiffer authored
With very bad timing, it is possible that the teardown script of a gluon_mesh interface runs when bat0 was just created, but primary0 is not yet added to it. Although there is no hardif to remove in this case, bat0 will still be deleted, because there is no hardif in bat0. Disable the interface removal logic by passing `-M` to `batctl interface`. (cherry picked from commit 92647cd4)
-
- Jun 12, 2020
-
-
Matthias Schiffer authored
There is no setting to explicitly enable mesh interfaces in the config wizard, so we need to enable mesh interfaces by default when the outdoor mode is disabled (unless site.conf dictates otherwise). The simplest way to achieve this is to delete the 5GHz mesh interface sections when outdoor mode is disabled: 200-wireless would delete and recreate them a moment later anyways, but by deleting them earlier we ensure that the disabled status is initialized from site.conf again. (cherry picked from commit 17bc6228)
-
Matthias Schiffer authored
When disabling outdoor mode, 5GHz mesh interfaces should be enabled by default again (unless disabled in site.conf). (cherry picked from commit d2052431)
-
Matthias Schiffer authored
Because is_disabled() was always returning true or false, the first_non_nil() would never actually check the default setting from site.conf. This was broken since v2017.1. Fixes: 6cf03bab ("treewide: replace normal uses of luci.model.uci with simple-uci to reduce LuCI dependencies") (cherry picked from commit 3c2593b6)
-
- Jun 07, 2020
-
-
Matthias Schiffer authored
The interfaces should always exist and just be disabled when outdoor mode is enabled. Not creating them at all leads to an issue in the advanced wifi settings where an additional reload of the page is necessary after enabling or disabling the ourdoor mode to make the mesh VIF options appear or disappear. (cherry picked from commit b15b008e)
-
Matthias Schiffer authored
Instead of relying on the existence of interface sections only (which is still used for the case of interface types that are not configured at all in the site config), add a proper dependency. This fixes section visiblity with enabled outdoor mode after the following fix, and gives the user immediate feedback (allowing to disable outdoor mode and enable meshing in a single step). (cherry picked from commit d012d7d3)
-
Matthias Schiffer authored
- Return early - Rename to has_active_interfaces(), as it returns a boolean (cherry picked from commit 53c33aca)
-
Matthias Schiffer authored
200-wireless will add or remove the mesh network sections of /etc/config/network. Commit this file, so the modified setting doesn't get lost on reboot. Fixes: #2048 (cherry picked from commit 600ab99f)
-
- Jun 04, 2020
-
-
Matthias Schiffer authored
- If luasrcdiet fails for a Lua script, this is a bug that should be noticed rather than including the unminified script - Use .tmp suffix for temporary file rather than .o - Replace chmod + stat + mv with simpler cp + rm to overwrite file while preserving file mode
-