- Jul 19, 2020
-
- Jun 03, 2020
-
-
David Bauer authored
Signed-off-by:
David Bauer <mail@david-bauer.net>
-
- May 30, 2020
-
-
Ruben Barkow-Kuder authored
-
- May 02, 2020
-
-
Martin Weinelt authored
(cherry picked from commit 7f3a3042)
-
- Mar 31, 2020
-
-
David Bauer authored
-
- Mar 07, 2020
-
-
David Bauer authored
(cherry picked from commit 447595f0)
-
- Feb 14, 2020
-
- Feb 04, 2020
-
-
David Bauer authored
(cherry picked from commit 63ebeb25)
-
- Jan 06, 2020
-
-
Andreas Ziegler authored
(cherry picked from commit 239c379d)
-
- Sep 22, 2019
-
-
Martin Weinelt authored
-
- Aug 22, 2019
-
-
Matthias Schiffer authored
-
- Apr 28, 2019
-
-
Martin Weinelt authored
Add the `wifi5.outdoor_chanlist` site configuration that allows specifying an outdoor channel range that can be switched to for regulatory compliance. Upon enabling the outdoor option the device will - configure the `outdoor_chanlist` on all 5 GHz radios - which may enable DFS/TPC, based on the regulatory domain - disable ibss/mesh on the 5 GHz radio, as DFS *will* break mesh connections - allow for htmode reconfiguration on 5 GHz radios The outdoor option can be toggled from - Advanced Settings - W-LAN - Outdoor Installation The `preserve_channel` flag overrules the outdoor channel selection.
-
Martin Weinelt authored
-
- Dec 29, 2018
-
-
Matthias Schiffer authored
-
- Nov 30, 2018
-
-
bobcanthelpyou authored
-
- Jul 08, 2018
-
-
Matthias Schiffer authored
-
Matthias Schiffer authored
-
- 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
-
- Mar 17, 2018
-
-
Matthias Schiffer authored
At the moment, we don't have a good guideline for package-specific configuration, but it seems like a good idea not to split configuration into too many tiny pages, especially for packages that aren't commonly selected explicitly. Some uncommon configuration is dropped from the example site.conf to remove clutter.
-
- Feb 16, 2018
-
-
Christof Schulze authored
* change type of next_node.name * create domain entry for each entry and add to dnsmasq configuration [Matthias Schiffer: reword documentation]
-
- Jan 19, 2018
-
-
lemoer authored
[Matthias Schiffer: rebase]
-
- Dec 27, 2017
-
-
Ruben Barkow authored
-
- Nov 15, 2017
-
-
Andreas Ziegler authored
-
- Oct 31, 2017
-
-
Matthias Schiffer authored
Without -v, hexdump would sometimes replace duplicate bytes with "*" and a newline.
-
- Oct 14, 2017
-
-
Martin Weinelt authored
-
- Jun 27, 2017
-
-
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.
-
- Jun 19, 2017
-
-
Ruben Barkow authored
The SSID for the mesh network should be cryptic, otherwise some users will try to connect to that network and have a bad user experience.
-
- Jun 10, 2017
-
-
Matthias Schiffer authored
-
- Mar 10, 2017
-
-
Matthias Schiffer authored
-
Matthias Schiffer authored
The fastd_mesh_vpn site.conf section is renamed to mesh_vpn.fastd.
-
- Dec 06, 2016
-
-
Ruben Barkow authored
-
- Nov 05, 2016
-
-
viisauksena authored
-
- Sep 21, 2016
-
-
Matthias Schiffer authored
-
- Sep 10, 2016
-
-
Matthias Schiffer authored
-