| 1 |
Thanks to some good advice from here, I've narrowed down my wireless |
| 2 |
problems to one specific configuration. Unfortunately it's the one I |
| 3 |
really need to work (of course). |
| 4 |
|
| 5 |
My laptop has an Intel 3954, using the iwlwifi driver, which I am trying |
| 6 |
to get working with NetworkManager. At home and on the few public AP's |
| 7 |
I've connected to, everything works fine. At work, if I run |
| 8 |
wpa_supplicant via Gentoo's init script, or if wicd runs it, everything |
| 9 |
works there as well. |
| 10 |
|
| 11 |
When using NetworkManager on my work network, however, things go |
| 12 |
horribly wrong. I get tons of this in my kernel logs: |
| 13 |
|
| 14 |
wlan0: authenticate with AP 00:1e:58:04:1e:ec |
| 15 |
wlan0: authenticated |
| 16 |
wlan0: associate with AP 00:1e:58:04:1e:ec |
| 17 |
wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1) |
| 18 |
wlan0: AP denied association (code=12) |
| 19 |
wlan0: associate with AP 00:1e:58:04:1e:ec |
| 20 |
wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1) |
| 21 |
wlan0: AP denied association (code=12) |
| 22 |
wlan0: associate with AP 00:1e:58:04:1e:ec |
| 23 |
wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1) |
| 24 |
wlan0: AP denied association (code=12) |
| 25 |
wlan0: association with AP 00:1e:58:04:1e:ec timed out |
| 26 |
wlan0: authenticate with AP 00:1e:58:04:1e:ec |
| 27 |
wlan0: authenticated |
| 28 |
wlan0: associate with AP 00:1e:58:04:1e:ec |
| 29 |
wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=0 aid=1) |
| 30 |
wlan0: associated |
| 31 |
|
| 32 |
Once associated, it stays connected for about a minute, then : |
| 33 |
|
| 34 |
wlan0: disassociated (Reason: 14) |
| 35 |
wlan0: deauthenticated (Reason: 6) |
| 36 |
|
| 37 |
and the cycle starts again. Does anyone recognize those error codes or |
| 38 |
what they're trying to tell me is wrong with the network? |
| 39 |
|
| 40 |
So far, the only notable difference between nm and the working |
| 41 |
configurations is wpa_supplicant. Both Gentoo's init script and wicd |
| 42 |
run wpa_supplicant directly on the interface, passing a configuration |
| 43 |
file. NetworkManager launches wpa_supplicant with a -u parameter, which |
| 44 |
makes it run in the background and accept configuration data from DBus. |
| 45 |
Should this really make that much difference? |
| 46 |
|
| 47 |
--Mike |
Archives