wsupp waits forever for AP about minibase

[bkauler]

Oh, another point: There is a battery-saving mode in Android, that is turned off, and the mains adaptor is plugged in.

[arsv]

If it happens with wpa_supplicant as well, try running wpa_supplicant -dd ... to check what exactly goes on there. Maybe post the log somewhere. Just make sure to mask sensitive information there — it will contain, at least, BSSIDs (MACs) and SSIDs (names) of your AP and any other APs around you. What kind of client device you've got may be important as well.

It doesn't sound good however. I would guess the card takes a command but fails to generate completion event for that command. The card is effectively a black box if that's what happens.

I'll need to do something about wsupp's inability to detach from a stuck card, but it won't be any more effective than a simple restart.

By the way, can you scan a card that seems stuck?

[bkauler]

Well, not a card, it is my Android phone that is tethered, that is, the wifi hotspot. On my PC, currently using a USB wifi dongle, but the same situation happens whatever hardware is at the PC end (I have several PCs and laptops to test with).

Yes, "wifi scan" still works, and sees my phone SSID, even though wsupp is stuck waiting for an AP.

Yes, wsupp should at least timeout.

When I was testing wpa_supplicant, I did do some detailed logging. Can't recall exactly, but it was in a loop, timing out, then trying again, and I think it eventually gave up and terminated.

It really does annoy me that Win10 has no problem!

[arsv]

Retries likely indicate authentication error. EAPOL lacks error reporting, the AP just drops any packets it doesn't like. However, both wsupp and wpa_supplicant should be able to report that. Might be something else going on.

[rofl0r]

if you have a second wifi adapter you could put that one into monitor mode and sniff the packets flying through the air with wireshark. then compare the difference between what happens with windows 10 and wsupp/wpa_supp. the pcap recordings from wireshark could eventually give some clues.

[bkauler]

'wifi' hanging is causing me some trouble. I setup another AP to experiment with:

# wifi
AP -29   4b  2CC  TP-LINK_7F56
AP -49  11b  2CC  HUAWEINova2
AP -61   6b  2CC  Telstra7A2DCB
AP -73   9b  2CC  BuckRogers

Device wlan1 idle
# wifi connect TP-LINK_7F56
Passphrase: XXXXXXX
wifi: cannot connect to AP TP-LINK_7F56 (4b/2427MHz)

...hangs. In another terminal:

# wifi
AP -33   4b  2CC  TP-LINK_7F56
AP -49  11b  2CC  HUAWEINova2
AP -61   6b  2CC  Telstra7A2DCB
AP -73   9b  2CC  BuckRogers

Device wlan1 idle

TP-LINK_7F56 works, I am using it right now, using wpa_supplicant. But, apart from 'wifi' reporting "cannot connect", hanging forever should not happen, it should terminate.

[arsv]

Ok, I think I figured it out. It was a bug and it did not report no-connect at all.
Fixed, wifi should terminate properly now.

Also, disconnects are now timed, so wsupp should not get stuck in disconnecting state anymore. It does not guarantee the card will remain usable, but at least it should be possible now to command another connect attempt without restarting wsupp.

Please delete wifi-psk and let wifi re-create it, there's a minor format change there.

[bkauler]

I have tested, working great. Getting connections to the TP-Link AP, no failures.