New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wireless: Modifications to wifi-iface or wifi-device can change network.$NET.ifname #5069
Comments
@jow- It seems like this issue is still persisting (at least in 21.02.x). Is there any chance that this will be looked at? |
Can't reproduce it locally. Can you arrange SSH access on an affected device? You can find my SSH public key at http://mein.io/id_rsa.pub |
Here are the steps to reproduce this in 21.02.1 wireless config before using luci
and network config looks like this
Change the 5GHz radio from 20MHz to 40MHz review of the changes are: And the router will time-out on "save and apply" and revert the changes. wireless config changes to this:
and more importantly, network config changes to this
|
note, if config wifi-iface is set to "wifinet0" then everything works as expected. when config wifi-iface is set to (for example) "wlan0lan5" or "wlan0_lan_5" the problem shows itself. |
…devices Only treat the given identifier as Linux netdev name if we can find a corresponding entry in the device info cache and do not consider strings starting with "wlan", "ath" or "wl" to be existing devices. This fixes incorrectly adding wireless sections as ifnames to network interfaces when the wifi-iface section name begins with one of the `iface_patterns_wireless` patterns. Fixes: #5069 Signed-off-by: Jo-Philipp Wich <jo@mein.io> (cherry picked from commit d4092b1)
…devices Only treat the given identifier as Linux netdev name if we can find a corresponding entry in the device info cache and do not consider strings starting with "wlan", "ath" or "wl" to be existing devices. This fixes incorrectly adding wireless sections as ifnames to network interfaces when the wifi-iface section name begins with one of the `iface_patterns_wireless` patterns. Fixes: #5069 Signed-off-by: Jo-Philipp Wich <jo@mein.io> (cherry picked from commit d4092b1)
Thanks, the naming was significant. Fixes pushed to all relevant branches. |
Wonderful! I also tested the change locally, both with a wireless interface bridged to physical ports and a wireless interface which has no physical ports. Really great!!! |
Tested with 19.07.7
We have come across a problem with Freifunk. This issue is: if someone wants to change (for example) the channel width of the 5GHz radio from 20MHz to 40MHz, then in the network config the value of network.$NET.ifname gets set to the wifi-iface section name.
To reproduce this, have the following setup in wireless:
wlan0_lan_5
and the ifname iswlan0-lan-5
.wlan0_mesh_5
so that we can properly programmatically modify the setting for client/mesh interfaces.And in network (standard config):
After clicking "Save" then viewing "Unsaved Changes" the following is shown:
"Save & Apply" causes the network interface to be
network.lan.ifname='eth0.1 wlan0_lan_5'
which is not correct. Note, the ifname in the wireless config is wlan0-lan-5 while the section name is wlan0_lan_5. Also, the wireless section name should simply not be included in the network config.The real problem comes with 802.11s mesh wifi-ifaces with OLSRd as the routing daemon. The interface stops working properly. Before "Save & Apply" the wifi-iface and interface section looks like this:
and
ip a
should look like this:After "Save & Apply" the interface section changes to this:
And as a visual representation:
Also, the interface no longer gets an IP address assigned
I see this as a critical problem which needs to be solved.
The text was updated successfully, but these errors were encountered: