Re: Flaky association with ipw2200 and Linksys WRT54G

[Robert Hancock <hancockr shaw ca>]

At least some of the time it seems the problem starts at the point in 
the output below. It seems like what is happening is that the supplicant 
is inserting the keys and then removing them immediately (you can see 
this by viewing the output of "watch --interval=0.2 /sbin/iwconfig 
eth1"), and then wondering why the link times out (duhhh..) It seems 
that when the scan is performed it gets a disconnect event at some point 
which leads it to remove the keys. It seems to be just luck whether this 
happens before the keys were originally inserted or not, therefore 
meaning that the connection process depends on luck as well. Sometimes 
it also seems to go into an infinite loop because of this and the 
connection keeps bouncing up and down.

I would think either the driver should not report disconnect events from 
this or else wpa_supplicant should not be responding to it by 
immediately removing the keys..

wpa_supplicant(6335): CTRL_IFACE: ENABLE_NETWORK id=0
wpa_supplicant(6335): Setting scan request: 0 sec 0 usec
wpa_supplicant(6335): State: DISCONNECTED -> SCANNING
wpa_supplicant(6335): Starting AP scan (broadcast SSID)
wpa_supplicant(6335): RX ctrl_iface - hexdump_ascii(len=6):
wpa_supplicant(6335):    ATTACH
wpa_supplicant(6335): CTRL_IFACE monitor attached - hexdump(len=42): 2f 
76 61 72 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 
70 61 5f 63 74 72 6c 5f 35 33 30 36 2d 39 00 00 00
wpa_supplicant(6335): Wireless event: cmd=0x8b15 len=20
wpa_supplicant(6335): Wireless event: new AP: 00:00:00:00:00:00
wpa_supplicant(6335): Added BSSID 00:00:00:00:00:00 into blacklist
wpa_supplicant(6335): State: SCANNING -> DISCONNECTED
wpa_supplicant(6335): EAPOL: External notification - portEnabled=0
wpa_supplicant(6335): EAPOL: External notification - portValid=0
wpa_supplicant(6335): CTRL-EVENT-DISCONNECTED - Disconnect event - 
remove keys
wpa_supplicant(6335): CTRL_IFACE monitor send - hexdump(len=42): 2f 76 
61 72 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 
61 5f 63 74 72 6c 5f 35 33 30 36 2d 39 00 00 00
wpa_supplicant(6335): wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 
seq_len=0 key_len=0
wpa_supplicant(6335): wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 
seq_len=0 key_len=0
wpa_supplicant(6335): wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 
seq_len=0 key_len=0
wpa_supplicant(6335): wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 
seq_len=0 key_len=0
wpa_supplicant(6335): wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 
seq_len=0 key_len=0
eth1: link timed out.


Jens Lautenbacher wrote:
> On Mon, 2006-03-27 at 21:49 -0600, Robert Hancock wrote:
> > I'm using NetworkManager in Fedora Core 5 with an ipw2200 wireless card
> > and a Linksys WRT54G access point. The AP is set up for WPA2 Personal
> > security.
> >
> > Once in a while the connection just works the first time. Most of the
> > time, it usually just times out, or else it appears to connect but then
> > the connection goes down again. I'm not sure what to do to debug this
> > much further, maybe somebody can see something interesting from the
> > output. I'm attaching some /var/log/messages output that shows some of
> > these (zipped up, otherwise it's too big to post to this list).
>
> I can see the same behavior, only for me it's a FritzBox Wlan Fon 7050
> router/AP.
>
> 	jtl
>
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list