Bug 356041

Created attachment 241011 [details]
NetworkManager log

Created attachment 241031 [details]
wpa_supplicant logfile

Could you provide the output of 'iwlist wlan0 scan' for your AP, obscuring the
BSSID if you like?

[root@localhost ~]# iwlist wlan0 scan
wlan0     Interface doesn't support scanning.

[root@localhost ~]# iwlist ath0_rename scan

 Cell 03 - Address: 00:14:51:78:01:89
                    ESSID:"*******"
                    Mode:Master
                    Frequency:2.412 GHz (Channel 1)
                    Quality=29/70  Signal level=-66 dBm  Noise level=-95 dBm
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Extra:bcn_int=100
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK

I was able to get wpa_supplicant working with this
/etc/wpa_supplicant/wpa_supplicant.conf file (psk and ssid edited out)

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=1

network={
        ssid="<SSID>"
        key_mgmt=WPA-PSK
        proto=WPA
        scan_ssid=1
        psk=<PSK>
}

The option of note is ap_scan=1. When set to 0 or 2 it will not work. After
wpa_supplicant is started I can start NetworkManager again it it will get and ip
address.

wpa_supplicant standalone works fine, with or without the ap_scan option. It's
the combination of wpa_supplicant with NM that doesn't work.

are you hiding the SSID of your AP?

No, I'm not.

I'm not hiding my ssid, either.

This problem has re-appeared for me, too (there was a similar situation earlier
on in the F8 development cycle).

I am not hiding my SSID.

Just confirming that the same is happening to me on an x86_64 system (no idea 
if that makes a difference) with a Broadcom 4311 card, so this clearly is not 
unique to any particular card/manufacturer.  Also, a lot of people with 
various cards have reported the same or similar problems on FedoraForums, so 
evidently this is quite a widespread problem.

Actually, I take that back.  I'm no longer having this problem after the 
latest round of updates.

Chris, which version of NM are you running?  Which kernel?

If others could report their kernel and NM versions as well, that would be great.

Created attachment 277271 [details]
Output from nm-applet when run from terminal as root

Well, the issue had been resolved (at least for me) but went back to the same 
behavior after the latest round of updates yesterday.  My current NM and 
kernel versions are:

NetworkManager 0.7.0-0.6.6.svn3109
linux 2.6.23.8-63

That's what I have now, and it's not working.  Back when things were working, 
I think I had:

NetworkManager 0.7.0-0.6.6.svn3030
linux 2.6.23.1-49

The attachment is the output I get from running nm-applet from a terminal (as 
root), trying to enter my wireless router's passkey twice, and then hitting 
cancel on the third try (if that makes any sense).

I'm guessing the line
** (nm-applet:4315): WARNING **: couldn't read 4 bytes from gnome-keyring 
socket: Connection reset by peer
is significant, but what do I know?  I hope that helps in some way.

By the way, I should probably note that I tried downgrading the 
NetworkManager-related packages to the svn3030 version and using the older 
kernel, but this didn't seem to have any effect - it still just kept 
repeatedly asking for my password.

Is this bug still open? As i remarked last week, it just concerns wpa, but not 
wpa2, which works fine (even if the bssid is hidden).

Roger

I haven't been able to get madwifi (or ath5k) working on my laptop with the
latest kernels, so I can't test this for now.

Ok, I've been able to get madwifi working again. Connecting with wpa-supplicant
works, but nm-applet keeps asking for my password

[ruben@localhost ~]$ uname -r
2.6.25-0.78.rc3.git1.fc9
[ruben@localhost ~]$ rpm -q NetworkManager
NetworkManager-0.7.0-0.8.svn3369.fc9.i386
[ruben@localhost ~]$ rpm -q madwifi
madwifi-0.9.4-1.lvn9.i386

Somehow everything works now on the latest kernel:

[ruben@localhost ~]$ rpm -q madwifi
madwifi-0.9.4-1.lvn9.i386
[ruben@localhost ~]$ rpm -q NetworkManager
NetworkManager-0.7.0-0.8.svn3370.fc9.i386
[ruben@localhost ~]$ uname -r
2.6.25-0.93.rc4.fc9
[ruben@localhost ~]$