Skip to content
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

Closed
psyborg55 opened this issue Nov 3, 2016 · 11 comments
Closed

wifi scan function broken #839

psyborg55 opened this issue Nov 3, 2016 · 11 comments

Comments

@psyborg55
Copy link
Contributor

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.

@jow-
Copy link
Contributor

jow- commented Nov 3, 2016

I do not understand the report. Isn't it normal that the pag does not load if the connection drops?

@psyborg55
Copy link
Contributor Author

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:

Screenshot
host image

@danielfdickinson
Copy link
Contributor

@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.

@psyborg55
Copy link
Contributor Author

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.

@danielfdickinson
Copy link
Contributor

@jow- @hnyman Any way of confirming if this is a driver issue? It sounds to me like when connection dies the driver resets and therefore scan fails.

@hnyman
Copy link
Contributor

hnyman commented Dec 22, 2016

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.

root@lede:~# iw wlan0 scan
BSS 10:bf:48:33:22:39(on wlan0)
        TSF: 711625688938 usec (8d, 05:40:25)
        freq: 5220
        beacon interval: 100 TUs
        capability: ESS (0x0001)
        signal: -79.00 dBm
        last seen: 3840 ms ago
        SSID: ASUS_5G
...

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?

@psyborg55
Copy link
Contributor Author

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.

@danielfdickinson
Copy link
Contributor

@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.

@psyborg55
Copy link
Contributor Author

got this:

root@OpenWrt:~# iwinfo wlan2 scan
No scan results

when it works, the iwinfo scan takes 15 seconds and luci scan 45 seconds - there's for sure something broken

@danielfdickinson
Copy link
Contributor

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.

@dji-transpire
Copy link

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants