Something Wacky in Wireless World

Sigh. I just updated a year-old, working Haiku installation to hrev46368, and for a while I thought the whole wireless stuff was broken. Not so, it seems – if I wait long enough.

Let me clarify: if I try to connect to a WPA/WPA2 network using the atheroswifi, the Connect Wireless Network window will fail if I try to connect immediately, nor will it allow me to save the password. However – and I only learned this because I was writing this post – given some time, like a few minutes, it will connect and allow a password save. On the other hand, it connects to the wireless network with what is listed sometimes as a WEP connection, other times as what it is, a WPA connection. Huh? Anyone have any idea what’s going on?

I’d like to automate the wireless connection and login at start-up, but I’m a bit concerned with the apparent “lag.” Any ideas?

The best way is to report a bug with this description and logs so the developers can investigate.
(BugTracker has its own user handling, so you might need to register.

Well, what I ended up doing was to drop back to hrev46360 and all is good. The system is far more responsive, sound and networking works, and I was able to script the wireless connection at boot with no problem.

I’m not sure what bug to report, really: hrev46368 was sluggish from first install, networking was unreliable, I had a number of unrelated trips to KDL, etc. A bit of a nightmare.

Welcome to the Haiku shell.

~> listdev

??? atheros…

/boot/system/settings/network/wireless_networks —?