forked from freifunk-franken/firmware
Adrian Schmutzler
24be8ecdda
For historic reasons, the wan interface is set to eth1 as default value. When updating the config for one-port devices in configurenetwork, the same value is put there again if the mode is switched to something != WAN, instead of just removing the value. While ifname actually is a mandatory value, this has been handled inconsistently in the past, where ethmesh ifname was deleted, and wan ifname was just changed back to eth1, when assigning the actually relevant eth0 to a different task. This concept was set up with a one-port device in mind, i.e. a device where there is no eth1. However, this very setup routine got applied to the Nanostation M as well (which is treated as as one-port), where we suddenly have two interfaces and the eth1 exists. So, while the user assumes it's unconfigured, the second port actually becomes set up as WAN if the first one is != WAN. If connected to a second device with CLIENT (=default) to provide PoE there, this will create a loop. So, finally, in order to somehow fix this mess, this patch just changes the hardcoded "eth1" to "eth2". While this is no proper fix, it perpetuates the original idea of keeping wan set to something, but nothing which actually exists. However, there are no sideeffects and we keep this minimal-invasive. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Reviewed-by: Fabian Bläse <fabian@blaese.de> |
||
|---|---|---|
| .. | ||
| alfred-json | ||
| fff | ||
| fff-alfred | ||
| fff-alfred-monitoring-proxy | ||
| fff-babeld | ||
| fff-batman-adv | ||
| fff-boardname | ||
| fff-config | ||
| fff-dhcp | ||
| fff-fastd | ||
| fff-firewall | ||
| fff-gateway | ||
| fff-hoods | ||
| fff-hoodutils | ||
| fff-macnock | ||
| fff-network | ||
| fff-node | ||
| fff-nodewatcher | ||
| fff-ra | ||
| fff-random | ||
| fff-simple-tc | ||
| fff-support | ||
| fff-sysupgrade | ||
| fff-timeserver | ||
| fff-uradvd | ||
| fff-vpn-select | ||
| fff-web | ||
| fff-wireguard | ||
| fff-wireless | ||