23.05.3 iwinfo scan disconnects AP
-
@crispyoz yes tested it, keeps disconnecting
-
@DocHardinger That was OpenWrt 23.05 with the OpenWrt 22 MT76 driver code merged in. I tested on my Windows 11 machine, ran 6 or 7 scans and it never disconnected. May I suggest, if you have not already, power your Omega2 using a USB power adapter. Wifi scanning typically shows a spike in current, so I wonder if that's the issue.
-
@crispyoz said in 23.05.3 iwinfo scan disconnects AP:
@DocHardinger That was OpenWrt 23.05 with the OpenWrt 22 MT76 driver code merged in. I tested on my Windows 11 machine, ran 6 or 7 scans and it never disconnected. May I suggest, if you have not already, power your Omega2 using a USB power adapter. Wifi scanning typically shows a spike in current, so I wonder if that's the issue.
Of cause i used an usb power adapter, but thats a good point i didnt checked with another one. Or better i will use my laboratory power supply. We got this problem before but with also modem and other stuff connected and this was a bad power adapter, but with modem its a lot of more current needed.
Anyway i will test it.
-
Tested it and keeps disconnecting. And i used the same power supply when running 22.03. and this keeps stable. Hmhm will, just to be sure, test again with 22.03. on different omegas. But when this is 23.05. with old mt76 driver and it disconnects it cant be the driver, right?
-
@DocHardinger said in 23.05.3 iwinfo scan disconnects AP:
with old mt76 driver and it disconnects it cant be the driver, right?
Well. The Mediatek driver is broken up so that the various Mediatek hardware drivers use various shared code, and leverage the kernel and other kmods so that can also be a factor, but I built on the 6.6 kernel whereas the Onion build uses 5.15.
I have more things to test, this will also impact my own devices so I am keen to get to the bottom of the issue before it bites me in the ass.
Tonight I'll add some logging to the kmod and see if it gives some hints as to where to look next. My main issue is being able to reliably cause the dropout. My guess is it is lost packets perhaps due to power issues and or the windows driver's tolerance of these. The hardware and/or drivers on my Windows notebook may be more tolerant than yours, so I tried it on an old Mickey$oft Surface device, it never dropped out and that's a pretty crappy piece of hardware.
-
@crispyoz i tested on two omega2pro and an omega2s+ (running 23.05.3) on our custom pcb. Both disconnects on laptop and pc. I will now get another old pc and check again with this one.
-
@DocHardinger Can you set option disassoc_low_ack '0' on your AP and see if it makes any difference. I need it on my sta when connecting to one of Unifi APs.
-
Yes i already thought about this but makes no difference
-
@crispyoz ok now tested with an old surface book 2, this one keeps the connection. My gaming pc and a new Dell Precision Laptop still keeps disconnecting.
-
@DocHardinger I think I have a clue. I managed to reliably reproduce the issue on a Lenovo P15s notebook running windoze 10. It will reliably disconnect if I run iw ra0 scan in a loop on OpenWrt 23. So I ran Wireshark to check for lost packets, acks etc, nothing notable to report. However I did notice the Wifi signal strength kept dropping and then the SSID disappears. If I set the saved network to autoconnect, it reconnects fine. But as the loop runs it disconnects again and then reconnects etc. I put my iPhone and Android 11 devices next to the P15s at the same so they are the same distance from the Omage2p and neither of them disconnect when the windoze device disconnects.
This Lenovo P15s can dual boot either windoze 10 or Ubuntu 24.10, so this time I booted into Ubuntu and ran the same test, it doesn't disconnect. So the problem is isolated to windoze.
I ran LinSSID on Ubuntu and it does not detect any notable drop in signal strength, so I rebooted in windoze and ran Acrylic WiFi Analyser, it shows a short-lived drop in signal strength when I'm running iw ra0 scan in a loop.
My working hypothesis is that windoze is aggressively monitoring connectivity and the faster the machine the more likely it is to disconnect, but slower devices like iphones, android phones and old Surface devices are simply not noticing the short lived signal drop.
OpenWrt 22 uses iw v5.16 OpenWrt 23 uses iw v5.19, so I wondered if the newer iw is doing something different. Looking at the code the changes are minimal, so I installed iw v5.16 on OpenWrt 23 but the issue persists.
Both 22 and 23 use the same mt76 firmware release, so I'm looking at the driver code for some hints.