Unable to connect to WPA after updates

Question

I'm trying to connect to a WPA2 AP with hidden ssid via wpa_supplicant (tried NM also, don't say that please).
I have two machines:
1) rt61pci driver, wifi works, can connect to open APs, can't connect to WPA2 hidden ssid AP
This machine used to be able to connect to the AP sometime in Feb I think was the latest time I tried. (it connects via giga ethernet since then)
While installing machine #2, I've re-tried connecting with this machine using the exact same script, wpa_supp conf, etc, I get the same result as machine #2.
2) iwl3945 driver, as #1, can connect to open APs, can't connect to WPA2 AP with hidden ssid
I've recently installed this machine: here's what happened:
I installed it, I could connect, ran pacman -Syu: could no longer connect
After a LOT of trying out things, I got the idea to try to boot the arch 02.09 LiveCD (from which I installed): this worked, I could connect.
So I guess this is a regression somewhere.
I've tried downgrading wpa_supplicant: the latest version in the repo is 0.6.9, I've downgraded to 0.5.11 (which is on the LiveCD also), I still can't connect, so I guess the problem is somewhere else.
Exactly what happens is that:
- wpa_supplicant finds the AP (shows empty ssid string and i've confirmed the mac addr)
- wpa_supplicant goes over all APs in WPA and non-WPA modes
- when going over the right AP it discards it with "skip - SSID mismatch"
- when finished, it says "No suitable AP found."
I've tried setting the ssid in both hex and string, tried setting the psk key in both string and wpa_passphrase format (is that hex?), no change.
I believe other people are having this sort of trouble, I found a few topics describing very lightly what could be my exact came problem (about WPA AP with hidden ssid).
Does anyone know of a fix for this? Or a way I can further debug it?
Edit: some more info I missed out:
My AP uses WPA1,2 with a AES PSK.
I've also tried specifying the ap ssid and bssid via iwconfig before running wpa_supplicant.
I've also tried setting the bssid in the network block of the config file.
Here's my wpa.conf:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
ap_scan=1
update_config=1
network={
scan_ssid=1
#ssid=<hexSsid>
ssid="myssid"
#psk="myStringKey"
psk=<key generated by wpa_passphrase here>
Last edited by Frantic (2009-06-01 17:03:02)

Answer 1

Frantic wrote:Well, I don't think it's an option when I take my laptop somewhere to ask the person to turn on his ssid broadcast because the "so cool" laptop can't connect to it otherwise
I wasn't aware this was not on your own network. That of course narrows down your options considerably.
Please don't hijack the thread on this, but by hiding the ssid vs just setting a obfuscated name lets this decision pass as a network security and not as a social or privacy-related concern (which it really is).
I don't see in the slightest how I would be hijacking your thread. Hijacking a thread means asking your own question in someone else's thread. I am merely pointing out it might help during troubleshooting, and that it is frequently known to cause problems with Linux.
And no - hidden SSIDs aren't a 'security' feature. It's not because you can't see it scanners can't see it or intercept the SSID in traffic . I'll leave it at that.
Also - and this might be relevant to your problem - I found this article which states
It's a violation of the 802.11 specification to keep your SSID hidden; the 802.11i specification amendment (which defines WPA2, discussed later) even states that a computer can refuse to communicate with an access point that doesn't broadcast its SSID.
And, for the incredulous:
And, even if you think your SSID is hidden, it really isn't.
Maybe the IPW3495 driver's 802.11 implementation got tightened, have you tried using an older kernel?