I have experienced this, same WiFi SSID for 2.4 and 5GHz - it simply does work. My amateur analysis is that the network ID’s are not enumerated and thus tries to connect to both causing the connection to drop intermittently. In my case, waiting for this to be resolved, I changed the SSID of one of the networks to something logical. This works but is not ideal.
That would also explain why auto-connecting works fine for me on devices that support only 2.4GHz but I have to manually connect on devices that support both.
I thought it’s just coincidence, but Haiku trying to connect to both at the same time is obviously a better explanation.
It doesn’t try to connect to both at the same time, though it does try to connect just by name. If you have different passwords, the one that doesn’t match may answer first and fail.
It has recently failed a few times for me too. In all of them it was the opposite problem: no known network was found in the neighbours enumeration. In one case it was not found for a few minutes, so I could not even associate manually. It has also happened with Android and Fedora, so I guess it’s either my AP or the environment. Sometimes I get two or three devices with a stronger signal than my AP, even when I’m sitting just two meters away with direct line of sight.
One thing I don’t see Haiku doing is keep trying if at first no known network is found. That would help at least for this case.
1 Like
It simply does NOT work - apologies for the typo!
Works for me, though.
1 Like
Very Not helpful answer thanks!
IIRC, on linux, wpa_supplicant is responsible of doing scans when you have declared an encrypted network.
I’m surprised that on Haiku it isn’t launch at boot when you have one declared.
The net_server starts the wpa_supplicant.
From what I’ve seen, after scanning.
That’s correct. I’m thinking of just passing all the known networks to wpa_supplicant and just let it do its job.
2 Likes