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
wifi scan function broken #839
Comments
I do not understand the report. Isn't it normal that the pag does not load if the connection drops? |
sorry, should've make it more clear, client device on openwrt that connects to upstream network not client device that connects to openwrt. this has always worked with previous revisions. screenshot added: |
@psyborg55 Are you saying that the issue is that if the upstream device reboots while doing a wireless scan on the device running openwrt that you get an empty wireless scan page? If so, this is most likely an issue with the underlying wireless driver in which the disconnection resets the associated interface. |
as soon as client connection to the upstream AP is lost the scan function returns this empty page. while connected it's listing networks as usual. |
Well, to my knowledge LuCI contains no wifi scanning logic by itself. All scanning is done by the wifi driver and LuCI just parses the output of the driver scanning command, which I think is "iw wlan0 scan" (or wlan1) and displays that output. The scanning works also from console. If iw fails also there, there is no way LuCI could fix that.
In general it sounds strange that scanning would be dependent on existing connections, as the purpose of scanning is to find new available networks. Which router and wifi driver we are talking about? |
xiaomi mini, happens with both ar9271 and rt3070 usb devices. after the connection is lost (remote AP restart) scan doesn't work and as soon as it's re-established (remote AP up) scan works again. |
@psyborg55 can you test iw and iwinfo scans and see it happens from the command line too? It doesn't seem like a LuCI issue but core. |
got this:
when it works, the iwinfo scan takes 15 seconds and luci scan 45 seconds - there's for sure something broken |
luci scan time is just UI load time I think (yeah LuCI has performance issues; hence the desire for LuCI-ng); if iwinfo is not working then it's a driver issue and not a LuCI issue. |
This is indeed an issue, Luci scans, or tries to do so, and hangs. on the command line, it works. iw wlan0 scan is fine, the GUI command hangs and does not produce results chaos calmer 15.05 on a HooToo TM06 (with GL-TM300N firmware, since it uses the same ramips chipset) |
running R49946 while client device is connected scanning for other networks works as expected, if the connection drops because of for example remote device reboot scanning does not work but displays empty page.
The text was updated successfully, but these errors were encountered: