GitLab

Some devices (e.g., ath79 MikroTik) have their MAC addresses configured
via /etc/config/network in "Xan_ethN_dev" device sections (e.g.,
lan_eth0_dev"). When removing old network settings, to not remove MAC
address settings.

Fixes #485.
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>

Continues 7c75474e,
cb7fd04423ce05fa64b96efb6667421b33bf100c,
6c5212f1 and
b45499e1

.

Fixes #481.
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>

Continues 7c75474e,
cb7fd04423ce05fa64b96efb6667421b33bf100c,
6c5212f1 and
b45499e1

.

Fixes #481.
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>

Still with #481, for some devices, qmp_get_wifi_devices() reports less
devices than actually present. Add an additional source of devices and
some verbosity.

Continues cb7fd04423ce05fa64b96efb6667421b33bf100c,
6c5212f1 and
b45499e1

.
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>

Continues 6c5212f1 and
b45499e1

.

Still some devices that take extremely long to initialize the wifi
seem to put mesh wlan0 in the lan bridge. Add some verbosity and
an additional check.
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>

Continues b45499e1

.

Still, for some devices, wlan0 is not considered to be a wifi
device. Add an additional check for that.
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>

On first boot, routers with a single 2.4 GHz radio had it auto-
configured as 80211s_aplan, with interface wlan0 as 80211s and
wlan0ap as AP. However, the wlan0 interface was wrongly considered
as being inside the virtual interface (viface) "lan" instead of
"mesh_w0". This was a corner case in the qmp_get_virtual_iface()
function, which ultimately made rescue_ip 169.254.x.y to be
incorrectly assigned to "br-lan" instead of "mesh_w0".

Fixes #481.
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>

Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>

Certain combinations of wireless drivers (e.g., ath10k, mt7615) and
wireless modes (e.g., adhoc, 80211s) end up with the radio interfaces
not being risen up and not appearing in /sys/class/net/. Therefore, they
are never detected as wireless interfaces and, upon reconfiguration,
they are treated as wired ones, leading to wrong settings in
/etc/config/network. To avoid this behaviour, wireless interfaces are
now tested for *not* being "non-wireless.

Fixes #473
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>

Fixes #462
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>

This commit sets the "Ad hoc (mesh)" wireless mode as "Ad hoc (legacy
mesh)" on the web GUI.

It also introduces a backwards-compatible mode, the "802.11s (mesh) + Ad
hoc (legacy mesh)", on the web GUI and adds code to the configuration
scripts to handle it properly.

This whole thing will ease the transition from current Ad hoc mesh
networks towards 802.11s mesh networks (e.g. Guifi.net networks in
Barcelona like Sants-Les Corts-UPC).
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>

[qmp-system] 802.1ad VLANs for the routing protocol are created on top of the physical interface (II)

Fix VLANs for wireless interfaces, which were broken by previous commit.

Previously, when an interface (i.e. eth0) was configured as "lan" and "mesh",
it was added to the LAN bridge and, on top of the virtual "br-lan" interface,
the VLAN for the routing protocol was created (i.e. lan_12). This was wrong in
some cases, for example, when another interface was in the bridge but not meant
to be meshing. Now the VLANs are created on the interfaces actually configured
as "mesh".

 · Drop community_id and community_node_id and replace it with community_name, mesh_name, device_name and mesh_id when appropriate
 · Revamp qMp easy setup
 · Rename node to device to avoid confusions (node == physical/geographical location, device == router)

[qmp-system] [QinQ] Use 802.1ad VLANs on wired interfaces to enable compatibility with switched Ethernet ports already using 802.1q

This breaks backwards compatibility with devices using previous qMp versions connected via cable.

This commit fixes issue #377, regarding the ways VLANs are specified in
/etc/config/network. The previous method (with @wlan0-like stuff) was never
meant to work, although it just happened to work. Recent OpenWrt changes
have deprecated that *unsupported* way to declare VLANs. Backporting the
work in branch QinQ and adding a couple of changes (e.g. linklayer details
for BMX6) fixes the problem.

Use rescue virtual interface for VLAN tagging in WAN+MESH mode to have the interface despite not having DHCP lease

Use rescue virtual interface for VLAN tagging in WAN+MESH mode to have the interface despite not having DHCP lease

Add new option to enable dhcp server in mesh interfaces (so dhcp client to adhoc devices is possible)

Remove all license references for individual files and add a single file COPYING and AUTHORS

sed -i -e "s/\s*$//g" packages/qmp-system/files/etc/qmp/*.sh

Change default dhcp metric from 2048 to non-specified since netifd seems to be buggy with dhcp metric

The VPN, Captive Portal, Maps, etc. Can be controled from the web interface (configuration/services).
Adds a new section in the qMp config file to specify which services should run and which ones not.

Move some networking functions from qmp_functions.sh to qmp_network.sh
Change VLAN options approach: vid_offset is removed and protocol_vids specify the full VLAN tag (bmx6:2 -> bmx6:12). In case VLAN is not specified, tagging is not used.
Adapt the default configuration file to the new syntax
Add uci-default scripts to adapt the qmp config file to this new approach
Minor changes in the code

Add function to create/remove TCP clamp MSS rule. It is executed when a network device is configured as WAN.

ULA/LAN autogenerated address now uses the crc16 hash
Fix issue with gateways offer (translation was not done properly)

Cosmetic changes
Moved some functions from qmp_funcions.sh to qmp_network.sh

removed qmp_wifi_restart uci-default script, it is not longer needed

By default the prefix fd00:1714:1714::/48 is used
Radvd is configured and started to get IPv6 to end users

Modified gw functions to be compatible with last bmx6. Disabled publish_lan because HNA is deprecated

New config option publish_lan to publish lan network using HNA. New functions in qmpcontrol: publish_hna and unpublish_hna