[ath9k-devel] Does DWA-642 AR5008 support 80211n?

[ath9k-devel] Does DWA-642 AR5008 support 80211n?

[hong zhang]

List,

I bought my second card for ath9k but looks like failed again.
DWA-642 has AR5008 and failed to associate to 80211n AP.
There are many wrong information on the ath9k list for which card supports ath9k.

16:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)


---henry


      

[ath9k-devel] Does DWA-642 AR5008 support 80211n?

[Luis R. Rodriguez]

On Tue, Jun 02, 2009 at 09:05:20AM -0700, hong zhang wrote:
> 
> List,
> 
> I bought my second card for ath9k but looks like failed again.

Describe failed again.

> DWA-642 has AR5008 and failed to associate to 80211n AP.

What AP do you have? Can you provide more information like for AP
configuration.

> There are many wrong information on the ath9k list for which card supports ath9k.
> 
> 16:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)

The device should work, are you trying wireless-testing? If not what kernel?

  Luis

[ath9k-devel] Does DWA-642 AR5008 support 80211n?

[hong zhang]

I am using CISCO 1250 AP that is 802.11n.
It works fine with Intel chip.
Actually, DWA642 can associate wit 802.11g.

Here is dmesg:
[59021.835466] wlan3: associate with AP 00:17:df:a6:e7:30
[59021.849286] wlan3: RX ReassocResp from 00:17:df:a6:e7:30 (capab=0x421 status=0 aid=1)
[59021.849293] wlan3: associated
[59021.855104] wlan3: disassociating by local choice (reason=3)
[59022.677330] wlan3: authenticate with AP 00:17:df:a6:e7:30
[59022.878101] wlan3: authenticate with AP 00:17:df:a6:e7:30
[59022.880030] wlan3: authenticated
[59022.880037] wlan3: associate with AP 00:17:df:a6:e7:30
[59022.892490] wlan3: RX ReassocResp from 00:17:df:a6:e7:30 (capab=0x421 status=0 aid=3)
[59022.892497] wlan3: associated
[59022.898604] wlan3: disassociating by local choice (reason=3)

wpa_supplicant message:

Setting scan request: 5 sec 0 usec
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added

Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
BSSID 00:17:df:a6:e7:30 blacklist count incremented to 2
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0




--- On Tue, 6/2/09, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:

> From: Luis R. Rodriguez <lrodriguez@atheros.com>
> Subject: Re: [ath9k-devel] Does DWA-642 AR5008 support 80211n?
> To: "hong zhang" <henryzhang62@yahoo.com>
> Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Date: Tuesday, June 2, 2009, 11:45 AM
> On Tue, Jun 02, 2009 at 09:05:20AM
> -0700, hong zhang wrote:
> > 
> > List,
> > 
> > I bought my second card for ath9k but looks like
> failed again.
> 
> Describe failed again.
> 
> > DWA-642 has AR5008 and failed to associate to 80211n
> AP.
> 
> What AP do you have? Can you provide more information like
> for AP
> configuration.
> 
> > There are many wrong information on the ath9k list for
> which card supports ath9k.
> > 
> > 16:00.0 Network controller: Atheros Communications
> Inc. AR5008 Wireless Network Adapter (rev 01)
> 
> The device should work, are you trying wireless-testing? If
> not what kernel?
> 
> ? Luis
> 


      

[ath9k-devel] Does DWA-642 AR5008 support 80211n?

[Luis R. Rodriguez]

On Tue, Jun 02, 2009 at 11:06:50AM -0700, hong zhang wrote:
> 
> I am using CISCO 1250 AP that is 802.11n.
> It works fine with Intel chip.
> Actually, DWA642 can associate wit 802.11g.

You mean the same card can associate to the same AP if
11n is disabled?

> Here is dmesg:

I take it this is the log with 11n enabled?

> [59021.835466] wlan3: associate with AP 00:17:df:a6:e7:30
> [59021.849286] wlan3: RX ReassocResp from 00:17:df:a6:e7:30 (capab=0x421 status=0 aid=1)
> [59021.849293] wlan3: associated
> [59021.855104] wlan3: disassociating by local choice (reason=3)
> [59022.677330] wlan3: authenticate with AP 00:17:df:a6:e7:30
> [59022.878101] wlan3: authenticate with AP 00:17:df:a6:e7:30
> [59022.880030] wlan3: authenticated
> [59022.880037] wlan3: associate with AP 00:17:df:a6:e7:30
> [59022.892490] wlan3: RX ReassocResp from 00:17:df:a6:e7:30 (capab=0x421 status=0 aid=3)
> [59022.892497] wlan3: associated
> [59022.898604] wlan3: disassociating by local choice (reason=3)
> 
> wpa_supplicant message:
> 
> Setting scan request: 5 sec 0 usec
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
> 
> Cancelling scan request
> WPA: clearing own WPA/RSN IE
> Automatic auth_alg selection: 0x1
> WPA: clearing AP WPA IE
> WPA: clearing AP RSN IE
> WPA: clearing own WPA/RSN IE
> No keys have been configured - skip key clearing

And encryption is disabled?

  Luis

[ath9k-devel] Does DWA-642 AR5008 support 80211n?

[hong zhang]

wpa_config
network={

	ssid="Linux11n-2.4-40"

	key_mgmt=NONE

	}


Here is wpa_supplicant:

Associate but disconnect then do cycle.
33: 00:17:df:a6:e7:30 ssid='Linux11n-2.4-40' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   selected non-WPA AP 00:17:df:a6:e7:30 ssid='Linux11n-2.4-40'
Trying to associate with 00:17:df:a6:e7:30 (SSID='Linux11n-2.4-40' freq=2437 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
Wireless event: cmd=0x8c02 len=208
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:17:df:a6:e7:30
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated with 00:00:00:00:00:00
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state S_FORCE_AUTH
EAPOL: SUPP_BE entering state IDLE
Cancelling authentication timeout
State: ASSOCIATED -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed (reauth) [id=0 id_str=]
wpa_driver_wext_set_operstate: operstate 0->1 (UP)
WEXT: Operstate: linkmode=-1, operstate=6
Cancelling scan request
RTM_NEWLINK: operstate=1 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
BSSID 00:17:df:a6:e7:30 blacklist count incremented to 2
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
State: COMPLETED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 1->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
State: DISCONNECTED -> SCANNING


--- On Tue, 6/2/09, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:

> From: Luis R. Rodriguez <lrodriguez@atheros.com>
> Subject: Re: [ath9k-devel] Does DWA-642 AR5008 support 80211n?
> To: "hong zhang" <henryzhang62@yahoo.com>
> Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Date: Tuesday, June 2, 2009, 11:45 AM
> On Tue, Jun 02, 2009 at 09:05:20AM
> -0700, hong zhang wrote:
> > 
> > List,
> > 
> > I bought my second card for ath9k but looks like
> failed again.
> 
> Describe failed again.
> 
> > DWA-642 has AR5008 and failed to associate to 80211n
> AP.
> 
> What AP do you have? Can you provide more information like
> for AP
> configuration.
> 
> > There are many wrong information on the ath9k list for
> which card supports ath9k.
> > 
> > 16:00.0 Network controller: Atheros Communications
> Inc. AR5008 Wireless Network Adapter (rev 01)
> 
> The device should work, are you trying wireless-testing? If
> not what kernel?
> 
> ? Luis
> 


      

[ath9k-devel] Does DWA-642 AR5008 support 80211n?

[Jouni Malinen]

On Tue, 2009-06-02 at 11:15 -0700, hong zhang wrote:
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:17:df:a6:e7:30
> State: ASSOCIATING -> ASSOCIATED
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> Associated with 00:00:00:00:00:00

That looks odd.. The wireless event seems to indicate a valid MAC
address that does even match with the scan results, but this all zeroes
address is odd.. Which version of wpa_supplicant are you using? Are you
by any chance using 64-bit kernel with 32-bit user space?

> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:00:00:00:00:00
> Setting scan request: 0 sec 100000 usec
> BSSID 00:17:df:a6:e7:30 blacklist count incremented to 2
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> State: COMPLETED -> DISCONNECTED

The AP did not seem to like something (or based on the dmesg output,
something local did not like it).. Are you running NetworkManager, too,
when running wpa_supplicant manually? That would likely result in this
type of behavior with NM requesting disconnection immediately after the
manually started wpa_supplicant process managed to connect.

- Jouni

[ath9k-devel] Does DWA-642 AR5008 support 80211n?

[hong zhang]

--- On Tue, 6/2/09, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:

> From: Luis R. Rodriguez <lrodriguez@atheros.com>
> Subject: Re: [ath9k-devel] Does DWA-642 AR5008 support 80211n?
> To: "hong zhang" <henryzhang62@yahoo.com>
> Cc: "Luis Rodriguez" <Luis.Rodriguez@Atheros.com>, "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Date: Tuesday, June 2, 2009, 1:15 PM
> On Tue, Jun 02, 2009 at 11:06:50AM
> -0700, hong zhang wrote:
> > 
> > I am using CISCO 1250 AP that is 802.11n.
> > It works fine with Intel chip.
> > Actually, DWA642 can associate wit 802.11g.
> 
> You mean the same card can associate to the same AP if
> 11n is disabled?

I use different 802.11g AP and assoicates.

> > Here is dmesg:
> 
> I take it this is the log with 11n enabled?

Yes, use CISCO 1250 AP. I tried Intel card and it works.
Do you have AR5008 on your hand now?

> > [59021.835466] wlan3: associate with AP
> 00:17:df:a6:e7:30
> > [59021.849286] wlan3: RX ReassocResp from
> 00:17:df:a6:e7:30 (capab=0x421 status=0 aid=1)
> > [59021.849293] wlan3: associated
> > [59021.855104] wlan3: disassociating by local choice
> (reason=3)
> > [59022.677330] wlan3: authenticate with AP
> 00:17:df:a6:e7:30
> > [59022.878101] wlan3: authenticate with AP
> 00:17:df:a6:e7:30
> > [59022.880030] wlan3: authenticated
> > [59022.880037] wlan3: associate with AP
> 00:17:df:a6:e7:30
> > [59022.892490] wlan3: RX ReassocResp from
> 00:17:df:a6:e7:30 (capab=0x421 status=0 aid=3)
> > [59022.892497] wlan3: associated
> > [59022.898604] wlan3: disassociating by local choice
> (reason=3)
> > 
> > wpa_supplicant message:
> > 
> > Setting scan request: 5 sec 0 usec
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan3' added
> > 
> > Cancelling scan request
> > WPA: clearing own WPA/RSN IE
> > Automatic auth_alg selection: 0x1
> > WPA: clearing AP WPA IE
> > WPA: clearing AP RSN IE
> > WPA: clearing own WPA/RSN IE
> > No keys have been configured - skip key clearing
> 
> And encryption is disabled?
Yes, it is open. 
> ? Luis
> 


      

[ath9k-devel] Does DWA-642 AR5008 support 80211n?

[hong zhang]

--- On Tue, 6/2/09, Jouni Malinen <jouni.malinen@atheros.com> wrote:

> From: Jouni Malinen <jouni.malinen@atheros.com>
> Subject: Re: [ath9k-devel] Does DWA-642 AR5008 support 80211n?
> To: "hong zhang" <henryzhang62@yahoo.com>
> Cc: "Luis Rodriguez" <Luis.Rodriguez@Atheros.com>, "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Date: Tuesday, June 2, 2009, 1:24 PM
> On Tue, 2009-06-02 at 11:15 -0700,
> hong zhang wrote:
> > Wireless event: cmd=0x8b15 len=20
> > Wireless event: new AP: 00:17:df:a6:e7:30
> > State: ASSOCIATING -> ASSOCIATED
> > wpa_driver_wext_set_operstate: operstate 0->0
> (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > Associated with 00:00:00:00:00:00
> 
> That looks odd.. The wireless event seems to indicate a
> valid MAC
> address that does even match with the scan results, but
> this all zeroes
> address is odd.. Which version of wpa_supplicant are you
> using? Are you
> by any chance using 64-bit kernel with 32-bit user space?

wpa_supplicant version is wpa_supplicant v0.6.4
and run wpa_supplicant -d -Dwext -i wlan3 -c 11n-2.4-40.conf
on Lenovo T61 laptop with Ubuntu.

No problem with Intel card.

> > Wireless event: cmd=0x8b15 len=20
> > Wireless event: new AP: 00:00:00:00:00:00
> > Setting scan request: 0 sec 100000 usec
> > BSSID 00:17:df:a6:e7:30 blacklist count incremented to
> 2
> > CTRL-EVENT-DISCONNECTED - Disconnect event - remove
> keys
> > State: COMPLETED -> DISCONNECTED
> 
> The AP did not seem to like something (or based on the
> dmesg output,
> something local did not like it).. Are you running
> NetworkManager, too,
> when running wpa_supplicant manually? That would likely
> result in this
> type of behavior with NM requesting disconnection
> immediately after the
> manually started wpa_supplicant process managed to
> connect.
I have killall NetwrokManager and nm-applet 
 
> - Jouni
> 
> 
> 


      

[ath9k-devel] Does DWA-642 AR5008 support 80211n?

[Luis R. Rodriguez]

On Tue, Jun 2, 2009 at 11:31 AM, hong zhang <henryzhang62@yahoo.com> wrote:
>
>
>
> --- On Tue, 6/2/09, Jouni Malinen <jouni.malinen@atheros.com> wrote:
>
>> From: Jouni Malinen <jouni.malinen@atheros.com>
>> Subject: Re: [ath9k-devel] Does DWA-642 AR5008 support 80211n?
>> To: "hong zhang" <henryzhang62@yahoo.com>
>> Cc: "Luis Rodriguez" <Luis.Rodriguez@Atheros.com>, "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
>> Date: Tuesday, June 2, 2009, 1:24 PM
>> On Tue, 2009-06-02 at 11:15 -0700,
>> hong zhang wrote:
>> > Wireless event: cmd=0x8b15 len=20
>> > Wireless event: new AP: 00:17:df:a6:e7:30
>> > State: ASSOCIATING -> ASSOCIATED
>> > wpa_driver_wext_set_operstate: operstate 0->0
>> (DORMANT)
>> > WEXT: Operstate: linkmode=-1, operstate=5
>> > Associated with 00:00:00:00:00:00
>>
>> That looks odd.. The wireless event seems to indicate a
>> valid MAC
>> address that does even match with the scan results, but
>> this all zeroes
>> address is odd.. Which version of wpa_supplicant are you
>> using? Are you
>> by any chance using 64-bit kernel with 32-bit user space?
>
> wpa_supplicant version is wpa_supplicant v0.6.4
> and run wpa_supplicant -d -Dwext -i wlan3 -c 11n-2.4-40.conf
> on Lenovo T61 laptop with Ubuntu.
>
> No problem with Intel card.
>
>> > Wireless event: cmd=0x8b15 len=20
>> > Wireless event: new AP: 00:00:00:00:00:00
>> > Setting scan request: 0 sec 100000 usec
>> > BSSID 00:17:df:a6:e7:30 blacklist count incremented to
>> 2
>> > CTRL-EVENT-DISCONNECTED - Disconnect event - remove
>> keys
>> > State: COMPLETED -> DISCONNECTED
>>
>> The AP did not seem to like something (or based on the
>> dmesg output,
>> something local did not like it).. Are you running
>> NetworkManager, too,
>> when running wpa_supplicant manually? That would likely
>> result in this
>> type of behavior with NM requesting disconnection
>> immediately after the
>> manually started wpa_supplicant process managed to
>> connect.
> I have killall NetwrokManager and nm-applet

Don't forget about the wpa_supplicant Network Manager leaves lingering.

sudo killall -TERM wpa_supplicant

  Luis

[ath9k-devel] Does DWA-642 AR5008 support 80211n?

[hong zhang]

After reboot. It works in 2.6.30-rc7 and rc4.
Thanks.

--- On Tue, 6/2/09, Luis R. Rodriguez <mcgrof@gmail.com> wrote:

> From: Luis R. Rodriguez <mcgrof@gmail.com>
> Subject: Re: [ath9k-devel] Does DWA-642 AR5008 support 80211n?
> To: "hong zhang" <henryzhang62@yahoo.com>
> Cc: "Jouni Malinen" <jouni.malinen@atheros.com>, "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>, "Luis Rodriguez" <Luis.Rodriguez@atheros.com>
> Date: Tuesday, June 2, 2009, 1:34 PM
> On Tue, Jun 2, 2009 at 11:31 AM, hong
> zhang <henryzhang62@yahoo.com>
> wrote:
> >
> >
> >
> > --- On Tue, 6/2/09, Jouni Malinen <jouni.malinen@atheros.com>
> wrote:
> >
> >> From: Jouni Malinen <jouni.malinen@atheros.com>
> >> Subject: Re: [ath9k-devel] Does DWA-642 AR5008
> support 80211n?
> >> To: "hong zhang" <henryzhang62@yahoo.com>
> >> Cc: "Luis Rodriguez" <Luis.Rodriguez@Atheros.com>,
> "ath9k-devel at lists.ath9k.org"
> <ath9k-devel@lists.ath9k.org>
> >> Date: Tuesday, June 2, 2009, 1:24 PM
> >> On Tue, 2009-06-02 at 11:15 -0700,
> >> hong zhang wrote:
> >> > Wireless event: cmd=0x8b15 len=20
> >> > Wireless event: new AP: 00:17:df:a6:e7:30
> >> > State: ASSOCIATING -> ASSOCIATED
> >> > wpa_driver_wext_set_operstate: operstate
> 0->0
> >> (DORMANT)
> >> > WEXT: Operstate: linkmode=-1, operstate=5
> >> > Associated with 00:00:00:00:00:00
> >>
> >> That looks odd.. The wireless event seems to
> indicate a
> >> valid MAC
> >> address that does even match with the scan
> results, but
> >> this all zeroes
> >> address is odd.. Which version of wpa_supplicant
> are you
> >> using? Are you
> >> by any chance using 64-bit kernel with 32-bit user
> space?
> >
> > wpa_supplicant version is wpa_supplicant v0.6.4
> > and run wpa_supplicant -d -Dwext -i wlan3 -c
> 11n-2.4-40.conf
> > on Lenovo T61 laptop with Ubuntu.
> >
> > No problem with Intel card.
> >
> >> > Wireless event: cmd=0x8b15 len=20
> >> > Wireless event: new AP: 00:00:00:00:00:00
> >> > Setting scan request: 0 sec 100000 usec
> >> > BSSID 00:17:df:a6:e7:30 blacklist count
> incremented to
> >> 2
> >> > CTRL-EVENT-DISCONNECTED - Disconnect event -
> remove
> >> keys
> >> > State: COMPLETED -> DISCONNECTED
> >>
> >> The AP did not seem to like something (or based on
> the
> >> dmesg output,
> >> something local did not like it).. Are you
> running
> >> NetworkManager, too,
> >> when running wpa_supplicant manually? That would
> likely
> >> result in this
> >> type of behavior with NM requesting disconnection
> >> immediately after the
> >> manually started wpa_supplicant process managed
> to
> >> connect.
> > I have killall NetwrokManager and nm-applet
> 
> Don't forget about the wpa_supplicant Network Manager
> leaves lingering.
> 
> sudo killall -TERM wpa_supplicant
> 
> ? Luis
>