| 1 |
On Sat, 2009-11-07 at 12:09 +0200, Alan McKinnon wrote: |
| 2 |
> On Saturday 07 November 2009 04:20:09 Mike Edenfield wrote: |
| 3 |
|
| 4 |
> > When using NetworkManager on my work network, however, things go |
| 5 |
> > horribly wrong. I get tons of this in my kernel logs: |
| 6 |
> > |
| 7 |
> > wlan0: authenticate with AP 00:1e:58:04:1e:ec |
| 8 |
> > wlan0: authenticated |
| 9 |
> > wlan0: associate with AP 00:1e:58:04:1e:ec |
| 10 |
> > wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1) |
| 11 |
> > wlan0: AP denied association (code=12) |
| 12 |
> > wlan0: associate with AP 00:1e:58:04:1e:ec |
| 13 |
> > wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1) |
| 14 |
> > wlan0: AP denied association (code=12) |
| 15 |
> > wlan0: associate with AP 00:1e:58:04:1e:ec |
| 16 |
> > wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1) |
| 17 |
> > wlan0: AP denied association (code=12) |
| 18 |
> > wlan0: association with AP 00:1e:58:04:1e:ec timed out |
| 19 |
> > wlan0: authenticate with AP 00:1e:58:04:1e:ec |
| 20 |
> > wlan0: authenticated |
| 21 |
> > wlan0: associate with AP 00:1e:58:04:1e:ec |
| 22 |
> > wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=0 aid=1) |
| 23 |
> > wlan0: associated |
| 24 |
|
| 25 |
> If it works everywhere else and not at home, the difference is obviously with |
| 26 |
> your home router. |
| 27 |
> |
| 28 |
> What config does it have and how does it differ from what everywhere else has? |
| 29 |
|
| 30 |
Well, it works at home but not at work, so I don't have much information |
| 31 |
beyond what they can tell me. I'll try to find someone who knows more, |
| 32 |
but as far as I can tell it's nearly identical to what I have at home: a |
| 33 |
single WAP with a broadcast SSID using WPA Personal, even using the same |
| 34 |
(cheap) Linksys hardware. |
| 35 |
|
| 36 |
What really confuses me is that the NIC works fine at work *if* I run |
| 37 |
wpa_supplicant manually; it only seems to fail when NetworkManager is |
| 38 |
controlling the NIC. So, yeah, it seems like the difference is with |
| 39 |
NetworkManager and/or wpa_supplicant, but I have no idea what that |
| 40 |
difference is. |
| 41 |
|
| 42 |
(Also, to head off the upcoming "just don't use NetworkManager": this |
| 43 |
laptop is eventually going to someone who'll be roaming a lot more than |
| 44 |
I do, for whom constantly editing wpa_supplicant.conf isn't really an |
| 45 |
option. Wicd doesn't support VPN connections, so NetworkManager seems |
| 46 |
to be my only option :\) |
| 47 |
|
| 48 |
--Mike |
Archives