Hi,

besides Android I've tried mer on my n810 now.
As there are almost no programs on the default install, getting wifi to work is a #1 priority imo.
Now with my hidden essid wpa-psk network I'm manually adding a hidden network in the applet. I can then enter my wpa key correctly (as shown in the input line) and n-m applet goes on to connect. Which in fact is never successfull...
After a while n-m applet comes back and wants another key. If I select "show key" then, I see some form of hashed key in the input line, which is not the correct plaintext psk I entered. Subsequent attempts with reentering the correct psk always lead to similar results.
Anybody knows what might cause this?

I had similar issues with my WPA network until I unhid the SSID. Not the best solution.. but it worked for me.

You can try, instead of using nm-applet, doing it by hand and creating /etc/wpa_supplicant.conf .. the import piece to have is an option "scan_ssid = 1".

I never got deblet working with a hidden WPA SSID.. Haven't bothered trying in Mer since it was already unhidden.

same here.

there's also an open bug stating that this very behavior is caused by WPA2...

Hmm... seems same bug as Kubuntu 9.04 Jaunty.
Wifi does not work either so I keep 8.10 on my laptop until further notice...

That WPA2-only networks are not working very well together with hidden SSIDs is not a bug. That's that expected behaviour.

Hiding SSIDs is and always was a clear violation of the WLAN standards (IEEE 802.11). That's just some vendor specific hack, which might or might not work, depending on which devices you want to connect.

The addendum IEEE 802.11i (which also introduced "WPA2") even explicitely states, that a client can refuse to connect to an AP with hidden SSID.

iskarion, none of this explains the behavior we see in mer:

the mysterious new key and the fact that it takes ages for anything to happen at all... at least it's a serious UI problem. it doesn't look at all like a client refusing to connect to a hidden network on purpose, espacially as this client explicitly offers an option to "connect to hidden networks" in the UI.

Since NetworkManager is using wpa_supplicant, if it works using wpa_supplicant I guess this must be a NetworkManager bug?

OK, tried Mer 0.16l same thing... as expected: AFAIK, the bug is fixed upstream in NM 0.8.

BUT:
One of the workarounds I found for Ubuntu requires editing values for NM in
.gconf/system/networking/wireless/<network name>/%gconf.xml

I don't find this in Mer, nor do I find something similar in /etc/gconf.

Any ideas where to manually edit NM files...?


EDIT: Found it. It's in /root/.gconf/
Doesn't help, though, the link to Ubuntu seems to describe a different version or a different problem.