FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 11-07-2009, 01:20 AM
Mike Edenfield
 
Default Strange iwl3945 behavior (possibly wpa_supplicant related?)

Thanks to some good advice from here, I've narrowed down my wireless
problems to one specific configuration. Unfortunately it's the one I
really need to work (of course).

My laptop has an Intel 3954, using the iwlwifi driver, which I am trying
to get working with NetworkManager. At home and on the few public AP's
I've connected to, everything works fine. At work, if I run
wpa_supplicant via Gentoo's init script, or if wicd runs it, everything
works there as well.

When using NetworkManager on my work network, however, things go
horribly wrong. I get tons of this in my kernel logs:

wlan0: authenticate with AP 00:1e:58:04:1e:ec
wlan0: authenticated
wlan0: associate with AP 00:1e:58:04:1e:ec
wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1)
wlan0: AP denied association (code=12)
wlan0: associate with AP 00:1e:58:04:1e:ec
wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1)
wlan0: AP denied association (code=12)
wlan0: associate with AP 00:1e:58:04:1e:ec
wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1)
wlan0: AP denied association (code=12)
wlan0: association with AP 00:1e:58:04:1e:ec timed out
wlan0: authenticate with AP 00:1e:58:04:1e:ec
wlan0: authenticated
wlan0: associate with AP 00:1e:58:04:1e:ec
wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=0 aid=1)
wlan0: associated

Once associated, it stays connected for about a minute, then :

wlan0: disassociated (Reason: 14)
wlan0: deauthenticated (Reason: 6)

and the cycle starts again. Does anyone recognize those error codes or
what they're trying to tell me is wrong with the network?

So far, the only notable difference between nm and the working
configurations is wpa_supplicant. Both Gentoo's init script and wicd
run wpa_supplicant directly on the interface, passing a configuration
file. NetworkManager launches wpa_supplicant with a -u parameter, which
makes it run in the background and accept configuration data from DBus.
Should this really make that much difference?

--Mike
 
Old 11-07-2009, 09:09 AM
Alan McKinnon
 
Default Strange iwl3945 behavior (possibly wpa_supplicant related?)

On Saturday 07 November 2009 04:20:09 Mike Edenfield wrote:
> Thanks to some good advice from here, I've narrowed down my wireless
> problems to one specific configuration. Unfortunately it's the one I
> really need to work (of course).
>
> My laptop has an Intel 3954, using the iwlwifi driver, which I am trying
> to get working with NetworkManager. At home and on the few public AP's
> I've connected to, everything works fine. At work, if I run
> wpa_supplicant via Gentoo's init script, or if wicd runs it, everything
> works there as well.
>
> When using NetworkManager on my work network, however, things go
> horribly wrong. I get tons of this in my kernel logs:
>
> wlan0: authenticate with AP 00:1e:58:04:1e:ec
> wlan0: authenticated
> wlan0: associate with AP 00:1e:58:04:1e:ec
> wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1)
> wlan0: AP denied association (code=12)
> wlan0: associate with AP 00:1e:58:04:1e:ec
> wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1)
> wlan0: AP denied association (code=12)
> wlan0: associate with AP 00:1e:58:04:1e:ec
> wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1)
> wlan0: AP denied association (code=12)
> wlan0: association with AP 00:1e:58:04:1e:ec timed out
> wlan0: authenticate with AP 00:1e:58:04:1e:ec
> wlan0: authenticated
> wlan0: associate with AP 00:1e:58:04:1e:ec
> wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=0 aid=1)
> wlan0: associated
>
> Once associated, it stays connected for about a minute, then :
>
> wlan0: disassociated (Reason: 14)
> wlan0: deauthenticated (Reason: 6)
>
> and the cycle starts again. Does anyone recognize those error codes or
> what they're trying to tell me is wrong with the network?
>
> So far, the only notable difference between nm and the working
> configurations is wpa_supplicant. Both Gentoo's init script and wicd
> run wpa_supplicant directly on the interface, passing a configuration
> file. NetworkManager launches wpa_supplicant with a -u parameter, which
> makes it run in the background and accept configuration data from DBus.
> Should this really make that much difference?

If it works everywhere else and not at home, the difference is obviously with
your home router.

What config does it have and how does it differ from what everywhere else has?

--
alan dot mckinnon at gmail dot com
 
Old 11-07-2009, 03:11 PM
Mike Edenfield
 
Default Strange iwl3945 behavior (possibly wpa_supplicant related?)

On Sat, 2009-11-07 at 12:09 +0200, Alan McKinnon wrote:
> On Saturday 07 November 2009 04:20:09 Mike Edenfield wrote:

> > When using NetworkManager on my work network, however, things go
> > horribly wrong. I get tons of this in my kernel logs:
> >
> > wlan0: authenticate with AP 00:1e:58:04:1e:ec
> > wlan0: authenticated
> > wlan0: associate with AP 00:1e:58:04:1e:ec
> > wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1)
> > wlan0: AP denied association (code=12)
> > wlan0: associate with AP 00:1e:58:04:1e:ec
> > wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1)
> > wlan0: AP denied association (code=12)
> > wlan0: associate with AP 00:1e:58:04:1e:ec
> > wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=12 aid=1)
> > wlan0: AP denied association (code=12)
> > wlan0: association with AP 00:1e:58:04:1e:ec timed out
> > wlan0: authenticate with AP 00:1e:58:04:1e:ec
> > wlan0: authenticated
> > wlan0: associate with AP 00:1e:58:04:1e:ec
> > wlan0: RX AssocResp from 00:1e:58:04:1e:ec (capab=0x411 status=0 aid=1)
> > wlan0: associated

> If it works everywhere else and not at home, the difference is obviously with
> your home router.
>
> What config does it have and how does it differ from what everywhere else has?

Well, it works at home but not at work, so I don't have much information
beyond what they can tell me. I'll try to find someone who knows more,
but as far as I can tell it's nearly identical to what I have at home: a
single WAP with a broadcast SSID using WPA Personal, even using the same
(cheap) Linksys hardware.

What really confuses me is that the NIC works fine at work *if* I run
wpa_supplicant manually; it only seems to fail when NetworkManager is
controlling the NIC. So, yeah, it seems like the difference is with
NetworkManager and/or wpa_supplicant, but I have no idea what that
difference is.

(Also, to head off the upcoming "just don't use NetworkManager": this
laptop is eventually going to someone who'll be roaming a lot more than
I do, for whom constantly editing wpa_supplicant.conf isn't really an
option. Wicd doesn't support VPN connections, so NetworkManager seems
to be my only option

--Mike
 
Old 11-08-2009, 06:11 AM
Alan McKinnon
 
Default Strange iwl3945 behavior (possibly wpa_supplicant related?)

On Saturday 07 November 2009 18:11:05 Mike Edenfield wrote:
> controlling the NIC. So, yeah, it seems like the difference is with
> NetworkManager and/or wpa_supplicant, but I have no idea what that
> difference is.
>
> (Also, to head off the upcoming "just don't use NetworkManager": this
> laptop is eventually going to someone who'll be roaming a lot more than
> I do, for whom constantly editing wpa_supplicant.conf isn't really an
> option. Wicd doesn't support VPN connections, so NetworkManager seems
> to be my only option
>

That's a pity. Using wicd instead of nm was going to be my next suggestion :-)

--
alan dot mckinnon at gmail dot com
 

Thread Tools




All times are GMT. The time now is 07:12 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org