* problem connecting to AP on new kernel (disassociating continuously after associating ) . Can some one please comment on the issue I am facing
@ 2013-03-15 13:29 vishnu
2013-03-16 16:44 ` Jussi Kivilinna
0 siblings, 1 reply; 8+ messages in thread
From: vishnu @ 2013-03-15 13:29 UTC (permalink / raw)
To: linux-wireless
Hello all,
driver used : rtl8192cu
When I tested with my linux kernel 3.0 , I didn't have any problems connecting
to AP. But with kernel 3.6.8 , I had a problem . When I tested with 3.7.8 also I
am facing the same problem. This is the latest kernel used by latest release of
buildroot , so I didn't test any kernels after that version.
The authentication and association are fine but from some reason it is
disassociating after that and it keeps repeating it and it never connects to the
AP.
Mar 15 11:23:04 kernel: [ 1943.421615] cfg80211: Calling CRDA to update world
regulatory domain
Mar 15 11:23:04 kernel: [ 1943.512963] cfg80211: World regulatory domain
updated:
Mar 15 11:23:04 kernel: [ 1943.513013] cfg80211: (start_freq - end_freq @
bandwidth), (max_antenna_gain, max_eirp)
Mar 15 11:23:04 kernel: [ 1943.513058] cfg80211: (2402000 KHz - 2472000 KHz @
40000 KHz), (300 mBi, 2000 mBm)
Mar 15 11:23:04 kernel: [ 1943.513102] cfg80211: (2457000 KHz - 2482000 KHz @
20000 KHz), (300 mBi, 2000 mBm)
Mar 15 11:23:04 kernel: [ 1943.513143] cfg80211: (2474000 KHz - 2494000 KHz @
20000 KHz), (300 mBi, 2000 mBm)
Mar 15 11:23:04 kernel: [ 1943.513183] cfg80211: (5170000 KHz - 5250000 KHz @
40000 KHz), (300 mBi, 2000 mBm)
Mar 15 11:23:04 kernel: [ 1943.513221] cfg80211: (5735000 KHz - 5835000 KHz @
40000 KHz), (300 mBi, 2000 mBm)
Mar 15 11:23:05 kernel: [ 1943.557338] rtl8192cu: Chip version 0x11
Mar 15 11:23:07 kernel: [ 1946.035267] rtl8192cu: MAC address:
00:34:f1:81:00:29
Mar 15 11:23:07 kernel: [ 1946.035283] rtl8192cu: Board Type 0
Mar 15 11:23:07 kernel: [ 1946.042320] rtlwifi: rx_max_size 15360, rx_urb_num
8, in_ep 1
Mar 15 11:23:07 kernel: [ 1946.042569] rtl8192cu: Loading firmware
rtlwifi/rtl8192cufw.bin
Mar 15 11:23:07 kernel: [ 1946.043055] ieee80211 phy0: Selected rate control
algorithm 'rtl_rc'
Mar 15 11:23:07 kernel: [ 1946.052242] usbcore: registered new interface driver
rtl8192cu
Mar 15 11:23:07 kernel: [ 1946.056275] rtlwifi: wireless switch is on
Mar 15 11:23:07 kernel: [ 1946.140211] rtl8192cu: MAC auto ON okay!
Mar 15 11:23:08 kernel: [ 1947.229454] rtl8192cu: Tx queue select: 0x05
Mar 15 11:23:10 kernel: [ 1949.153683] IPv6: ADDRCONF(NETDEV_UP): wlan0: link
is not ready
Mar 15 11:25:32 kernel: [ 2091.089686] wlan0: authenticate with
00:17:3f:15:8f:55
Mar 15 11:25:32 kernel: [ 2091.292720] wlan0: send auth to 00:17:3f:15:8f:55
(try 1/3)
Mar 15 11:25:32 kernel: [ 2091.317107] wlan0: authenticated
Mar 15 11:25:32 kernel: [ 2091.317845] rtl8192cu 1-2:1.0 wlan0: disabling HT as
WMM/QoS is not supported by the AP
Mar 15 11:25:32 kernel: [ 2091.317848] rtl8192cu 1-2:1.0 wlan0: disabling VHT
as WMM/QoS is not supported by the AP
Mar 15 11:25:32 kernel: [ 2091.321307] wlan0: associate with 00:17:3f:15:8f:55
(try 1/3)
Mar 15 11:25:32 kernel: [ 2091.342314] wlan0: RX AssocResp from
00:17:3f:15:8f:55 (capab=0x411 status=0 aid=2)
Mar 15 11:25:32 kernel: [ 2091.345594] wlan0: associated
Mar 15 11:25:32 kernel: [ 2091.346092] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0:
link becomes ready
Mar 15 11:25:42 kernel: [ 2101.346864] wlan0: disassociating from
00:17:3f:15:8f:55 by local choice (reason=3)
Mar 15 11:25:42 kernel: [ 2101.397208] cfg80211: Calling CRDA to update world
regulatory domain
Mar 15 11:25:42 kernel: [ 2101.399994] wlan0: deauthenticating from
00:17:3f:15:8f:55 by local choice (reason=3)
Mar 15 11:25:42 kernel: [ 2101.475451] cfg80211: World regulatory domain
updated:
Mar 15 11:25:42 kernel: [ 2101.475457] cfg80211: (start_freq - end_freq @
bandwidth), (max_antenna_gain, max_eirp)
Mar 15 11:25:42 kernel: [ 2101.475460] cfg80211: (2402000 KHz - 2472000 KHz @
40000 KHz), (300 mBi, 2000 mBm)
Mar 15 11:25:42 kernel: [ 2101.475462] cfg80211: (2457000 KHz - 2482000 KHz @
20000 KHz), (300 mBi, 2000 mBm)
Mar 15 11:25:42 kernel: [ 2101.475464] cfg80211: (2474000 KHz - 2494000 KHz @
20000 KHz), (300 mBi, 2000 mBm)
Mar 15 11:25:42 kernel: [ 2101.475467] cfg80211: (5170000 KHz - 5250000 KHz @
40000 KHz), (300 mBi, 2000 mBm)
Mar 15 11:25:42 kernel: [ 2101.475469] cfg80211: (5735000 KHz - 5835000 KHz @
40000 KHz), (300 mBi, 2000 mBm)
Mar 15 11:25:44 kernel: [ 2102.720500] wlan0: authenticate with
00:17:3f:15:8f:55
Mar 15 11:25:44 kernel: [ 2102.862351] wlan0: send auth to 00:17:3f:15:8f:55
(try 1/3)
Mar 15 11:25:44 kernel: [ 2102.869904] wlan0: authenticated
Mar 15 11:25:44 kernel: [ 2102.870255] rtl8192cu 1-2:1.0 wlan0: disabling HT as
WMM/QoS is not supported by the AP
Mar 15 11:25:44 kernel: [ 2102.870260] rtl8192cu 1-2:1.0 wlan0: disabling VHT
as WMM/QoS is not supported by the AP
Mar 15 11:25:44 kernel: [ 2102.872049] wlan0: associate with 00:17:3f:15:8f:55
(try 1/3)
Mar 15 11:25:44 kernel: [ 2102.875984] wlan0: RX AssocResp from
00:17:3f:15:8f:55 (capab=0x411 status=0 aid=2)
Mar 15 11:25:44 kernel: [ 2102.879009] wlan0: associated
Mar 15 11:25:54 kernel: [ 2112.881414] wlan0: disassociating from
00:17:3f:15:8f:55 by local choice (reason=3)
Configuration of wifi client:
modprobe rtl8192cu
wpa_supplicant -g/var/run/wpa_supplicant-global -B
wpa_cli -g/var/run/wpa_supplicant-global interface_add wlan0 "" nl80211
/var/run/wpa_supplicant
wpa_cli -iwlan0 -a/usr/bin/wifi-action -B
sleep 1
wpa_cli -iwlan0 add_network
wpa_cli -iwlan0 set_network 0 ssid '"belkin54g"'
wpa_cli -iwlan0 set_network 0 key_mgmt WPA-PSK
wpa_cli -iwlan0 set_network 0 proto WPA
wpa_cli -iwlan0 set_network 0 pairwise TKIP
wpa_cli -iwlan0 set_network 0 group TKIP
wpa_cli -iwlan0 set_network 0 psk '"Test123456"'
sleep 1
wpa_cli -iwlan0 enable_network 0
If you need more information , I will be happy to provide. thanks.
Regards,
Vishnu.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: problem connecting to AP on new kernel (disassociating continuously after associating ) . Can some one please comment on the issue I am facing
2013-03-15 13:29 problem connecting to AP on new kernel (disassociating continuously after associating ) . Can some one please comment on the issue I am facing vishnu
@ 2013-03-16 16:44 ` Jussi Kivilinna
2013-03-18 18:20 ` vishnu
0 siblings, 1 reply; 8+ messages in thread
From: Jussi Kivilinna @ 2013-03-16 16:44 UTC (permalink / raw)
To: vishnu; +Cc: linux-wireless
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
On 15.03.2013 15:29, vishnu wrote:
> Hello all,
>
> driver used : rtl8192cu
>
> When I tested with my linux kernel 3.0 , I didn't have any problems connecting
> to AP. But with kernel 3.6.8 , I had a problem . When I tested with 3.7.8 also I
> am facing the same problem. This is the latest kernel used by latest release of
> buildroot , so I didn't test any kernels after that version.
>
> The authentication and association are fine but from some reason it is
> disassociating after that and it keeps repeating it and it never connects to the
> AP.
>
Have you tested this patch: http://marc.info/?l=linux-wireless&m=136318849815054&w=2
It solves re-association issues that rtl8192cu had.
-Jussi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 730 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: problem connecting to AP on new kernel (disassociating continuously after associating ) . Can some one please comment on the issue I am facing
2013-03-16 16:44 ` Jussi Kivilinna
@ 2013-03-18 18:20 ` vishnu
2013-03-18 18:29 ` Larry Finger
0 siblings, 1 reply; 8+ messages in thread
From: vishnu @ 2013-03-18 18:20 UTC (permalink / raw)
To: linux-wireless
Jussi Kivilinna <jussi.kivilinna@...> writes:
>
> On 15.03.2013 15:29, vishnu wrote:
> > Hello all,
> >
> > driver used : rtl8192cu
> >
> > When I tested with my linux kernel 3.0 , I didn't have any problems
connecting
> > to AP. But with kernel 3.6.8 , I had a problem . When I tested with 3.7.8
also I
> > am facing the same problem. This is the latest kernel used by latest release
of
> > buildroot , so I didn't test any kernels after that version.
> >
> > The authentication and association are fine but from some reason it is
> > disassociating after that and it keeps repeating it and it never connects to
the
> > AP.
> >
>
> Have you tested this patch: http://marc.info/?l=linux-
wireless&m=136318849815054&w=2
>
> It solves re-association issues that rtl8192cu had.
>
> -Jussi
>
>
Hello Jussi,
I have applied the patch to kernel 3.7.8 and it doesn't fix my issue. I have
started testing the latest 3.9.0-rc2 version. I will let you know once I have
tested.
Thanks,
Vishnu.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: problem connecting to AP on new kernel (disassociating continuously after associating ) . Can some one please comment on the issue I am facing
2013-03-18 18:20 ` vishnu
@ 2013-03-18 18:29 ` Larry Finger
2013-03-18 18:44 ` vishnu
2013-03-19 15:40 ` vishnu
0 siblings, 2 replies; 8+ messages in thread
From: Larry Finger @ 2013-03-18 18:29 UTC (permalink / raw)
To: vishnu; +Cc: linux-wireless
On 03/18/2013 01:20 PM, vishnu wrote:
>
> Hello Jussi,
>
> I have applied the patch to kernel 3.7.8 and it doesn't fix my issue. I have
> started testing the latest 3.9.0-rc2 version. I will let you know once I have
> tested.
Please be aware that the patch is not in 3.9-rc2 from Linus's git tree (yet),
but it is in the wireless-testing git repo.
Larry
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: problem connecting to AP on new kernel (disassociating continuously after associating ) . Can some one please comment on the issue I am facing
2013-03-18 18:29 ` Larry Finger
@ 2013-03-18 18:44 ` vishnu
2013-03-19 15:40 ` vishnu
1 sibling, 0 replies; 8+ messages in thread
From: vishnu @ 2013-03-18 18:44 UTC (permalink / raw)
To: linux-wireless
Larry Finger <Larry.Finger@...> writes:
>
> On 03/18/2013 01:20 PM, vishnu wrote:
> >
> > Hello Jussi,
> >
> > I have applied the patch to kernel 3.7.8 and it doesn't fix my issue. I have
> > started testing the latest 3.9.0-rc2 version. I will let you know once I
have
> > tested.
>
> Please be aware that the patch is not in 3.9-rc2 from Linus's git tree (yet),
> but it is in the wireless-testing git repo.
>
> Larry
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@...
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
Hello Larry,
I have pulled it from wireless-testing git repository only. Will update once I
have done the testing.
Regards,
Vishnu
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: problem connecting to AP on new kernel (disassociating continuously after associating ) . Can some one please comment on the issue I am facing
2013-03-18 18:29 ` Larry Finger
2013-03-18 18:44 ` vishnu
@ 2013-03-19 15:40 ` vishnu
2013-03-19 18:14 ` Larry Finger
1 sibling, 1 reply; 8+ messages in thread
From: vishnu @ 2013-03-19 15:40 UTC (permalink / raw)
To: linux-wireless
Larry Finger <Larry.Finger@...> writes:
>
> On 03/18/2013 01:20 PM, vishnu wrote:
> >
> > Hello Jussi,
> >
> > I have applied the patch to kernel 3.7.8 and it doesn't fix my issue. I have
> > started testing the latest 3.9.0-rc2 version. I will let you know once I
have
> > tested.
>
> Please be aware that the patch is not in 3.9-rc2 from Linus's git tree (yet),
> but it is in the wireless-testing git repo.
>
> Larry
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@...
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
Hello Larry,
I have tried with 3.9-rc2 wireless-testing kernel and it is working fine . But
it is taking around 10 to 15 minutes , until which it is continuously
disassociating after association. Is this behaviour expected? Please find the
log if it is useful (Please discard the dates). This continuous for about 10 to
15 minutes and finally it doesn't disassociate with the AP.
Feb 25 05:20:06 buildroot kern.info kernel: wlan0: RX AssocResp from
00:17:3f:15:8f:55 (capab=0x411 status=0 aid=3)^M
wlan0: associated^M
Feb 25 05:20:06 buildroot kern.info kernel: wlan0: associated^M
wlan0: deauthenticating from 00:17:3f:15:8f:55 by local choice (reason=3)^M
Feb 25 05:20:16 buildroot kern.info kernel: wlan0: deauthenticating from
00:17:3f:15:8f:55 by local choice (reason=3)^M
cfg80211: Calling CRDA to update world regulatory domain^M
Feb 25 05:20:16 buildroot kern.debug kernel: cfg80211: All devices are
disconnected, going to restore regulatory settings^M
Feb 25 05:20:16 buildroot kern.debug kernel: cfg80211: Restoring regulatory
settings^M
Feb 25 05:20:16 buildroot kern.debug kernel: cfg80211: Kicking the queue^M
Feb 25 05:20:16 buildroot kern.info kernel: cfg80211: Calling CRDA to update
world regulatory domain^M
wlan0: authenticate with 00:17:3f:15:8f:55^M
Feb 25 05:21:18 buildroot kern.info kernel: wlan0: authenticate with
00:17:3f:15:8f:55^M
wlan0: send auth to 00:17:3f:15:8f:55 (try 1/3)^M
Feb 25 05:21:18 buildroot kern.info kerwlan0: authenticated^M
nel: wlan0: send auth to 00:17:3f:15:8f:55 (try 1/3)^M
Feb 25 05:21:18 buildroot kern.info kernel: wlan0: authenticated^M
rtl8192cu 1-1:1.0 wlan0: disabling HT/VHT due to WEP/TKIP use^M
rtl8192cu 1-1:1.0 wlan0: disabling HT as WMM/QoS is not supported by the AP^M
Feb 25 05:21:18 buildroot kern.info kernel: rtl8192cu 1-1:1.0 wlan0: disabling
HT/VHT due to WEP/TKIP use^M
rtl8192cu 1-1:1.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP^M
Feb 25 05:21:18 buildroot kern.info kernel: rtl8192cu 1-1:1.0 wlan0: disabling
HT as WMM/QoS is not supported by the AP^M
wlan0: associate with 00:17:3f:15:8f:55 (try 1/3)^M
Feb 25 05:21:18 buildroot kern.info kernel: wlan0: associate with
00:17:3f:15:8f:55 (try 1/3)^M
wlan0: RX AssocResp from 00:17:3f:15:8f:55 (capab=0x411 status=0 aid=3)^M
Feb 25 05:21:18 buildroot kern.info kernel: wlan0: RX AssocResp from
00:17:3f:15:8f:55 (capab=0x411 status=0 aidwlan0: associated^M
=3)^M
Feb 25 05:21:18 buildroot kern.info kernel: wlan0: associated^M
wlan0: deauthenticating from 00:17:3f:15:8f:55 by local choice (reason=3)^M
Feb 25 05:21:28 buildroot kern.info kernel: wlan0: deauthenticating from
00:17:3f:15:8f:55 by local choice (reason=3)^M
cfg80211: Calling CRDA to update world regulatory domain^M
Feb 25 05:21:28 buildroot kern.debug kernel: cfg80211: All devices are
disconnected, going to restore regulatory settings^M
Feb 25 05:21:28 buildroot kern.debug kernel: cfg80211: Restoring regulatory
settings^M
Feb 25 05:21:28 buildroot kern.debug kernel: cfg80211: Kicking the queue^M
Feb 25 05:21:28 buildroot kern.info kernel: cfg80211: Calling CRDA to update
world regulatory domain^M
wlan0: authenticate with 00:17:3f:15:8f:55^M
Feb 25 05:22:30 buildroot kern.info kernel: wlan0: authenticate with
00:17:3f:15:8f:55^M
wlan0: send auth to 00:17:3f:15:8f:55 (try 1/3)^M
Feb 25 05:22:30 buildroot kern.info kernel: wlan0: send auth to
00:17:3f:15:8f:55 (trwlan0: authenticated^M
y 1/3)^M
Feb 25 05:22:30 buildroot kern.info kernel:rtl8192cu 1-1:1.0 wlan0: disabling
HT/VHT due to WEP/TKIP use^M
wlan0: authenticated^M
Feb 25 05:22:31 buildroot kern.info kernel: rtl8192cu 1-1:1.0 wlan0: disabling
HT/VHT due to WEP/TKIP use^M
rtl8192cu 1-1:1.0 wlan0: disabling HT as WMM/QoS is not supported by the AP^M
Feb 25 05:22:31 buildroot kern.info kernel: rtl8192cu 1-1:1.0 wlan0rtl8192cu 1-
1:1.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP^M
: disabling HT as WMM/QoS is not supported by the AP^M
Feb 25 05wlan0: associate with 00:17:3f:15:8f:55 (try 1/3)^M
:22:31 buildroot kern.info kernwlan0: RX AssocResp from 00:17:3f:15:8f:55
(capab=0x411 status=0 aid=3)^M
el: rtl8192cu 1-1:1.0 wlan0: disabling VHT as WMM/QoS is not supported by the
AP^M
Feb 25 05:22:31 buildroot kern.info kernel: wlan0: associate with 00:1wlan0:
associated^M
Regards,
Vishnu.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: problem connecting to AP on new kernel (disassociating continuously after associating ) . Can some one please comment on the issue I am facing
2013-03-19 15:40 ` vishnu
@ 2013-03-19 18:14 ` Larry Finger
2013-03-20 12:56 ` vishnu
0 siblings, 1 reply; 8+ messages in thread
From: Larry Finger @ 2013-03-19 18:14 UTC (permalink / raw)
To: vishnu; +Cc: linux-wireless
On 03/19/2013 10:40 AM, vishnu wrote:
> Larry Finger <Larry.Finger@...> writes:
>
>>
>> On 03/18/2013 01:20 PM, vishnu wrote:
>>>
>>> Hello Jussi,
>>>
>>> I have applied the patch to kernel 3.7.8 and it doesn't fix my issue. I have
>>> started testing the latest 3.9.0-rc2 version. I will let you know once I
> have
>>> tested.
>>
>> Please be aware that the patch is not in 3.9-rc2 from Linus's git tree (yet),
>> but it is in the wireless-testing git repo.
>>
>> Larry
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@...
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>
>
> Hello Larry,
>
> I have tried with 3.9-rc2 wireless-testing kernel and it is working fine . But
> it is taking around 10 to 15 minutes , until which it is continuously
> disassociating after association. Is this behaviour expected? Please find the
> log if it is useful (Please discard the dates). This continuous for about 10 to
> 15 minutes and finally it doesn't disassociate with the AP.
>
>
> Feb 25 05:20:06 buildroot kern.info kernel: wlan0: RX AssocResp from
> 00:17:3f:15:8f:55 (capab=0x411 status=0 aid=3)^M
> wlan0: associated^M
> Feb 25 05:20:06 buildroot kern.info kernel: wlan0: associated^M
> wlan0: deauthenticating from 00:17:3f:15:8f:55 by local choice (reason=3)^M
> Feb 25 05:20:16 buildroot kern.info kernel: wlan0: deauthenticating from
> 00:17:3f:15:8f:55 by local choice (reason=3)^M
> cfg80211: Calling CRDA to update world regulatory domain^M
> Feb 25 05:20:16 buildroot kern.debug kernel: cfg80211: All devices are
> disconnected, going to restore regulatory settings^M
> Feb 25 05:20:16 buildroot kern.debug kernel: cfg80211: Restoring regulatory
> settings^M
> Feb 25 05:20:16 buildroot kern.debug kernel: cfg80211: Kicking the queue^M
> Feb 25 05:20:16 buildroot kern.info kernel: cfg80211: Calling CRDA to update
> world regulatory domain^M
> wlan0: authenticate with 00:17:3f:15:8f:55^M
> Feb 25 05:21:18 buildroot kern.info kernel: wlan0: authenticate with
> 00:17:3f:15:8f:55^M
> wlan0: send auth to 00:17:3f:15:8f:55 (try 1/3)^M
> Feb 25 05:21:18 buildroot kern.info kerwlan0: authenticated^M
> nel: wlan0: send auth to 00:17:3f:15:8f:55 (try 1/3)^M
> Feb 25 05:21:18 buildroot kern.info kernel: wlan0: authenticated^M
> rtl8192cu 1-1:1.0 wlan0: disabling HT/VHT due to WEP/TKIP use^M
> rtl8192cu 1-1:1.0 wlan0: disabling HT as WMM/QoS is not supported by the AP^M
> Feb 25 05:21:18 buildroot kern.info kernel: rtl8192cu 1-1:1.0 wlan0: disabling
> HT/VHT due to WEP/TKIP use^M
> rtl8192cu 1-1:1.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP^M
> Feb 25 05:21:18 buildroot kern.info kernel: rtl8192cu 1-1:1.0 wlan0: disabling
> HT as WMM/QoS is not supported by the AP^M
> wlan0: associate with 00:17:3f:15:8f:55 (try 1/3)^M
> Feb 25 05:21:18 buildroot kern.info kernel: wlan0: associate with
> 00:17:3f:15:8f:55 (try 1/3)^M
> wlan0: RX AssocResp from 00:17:3f:15:8f:55 (capab=0x411 status=0 aid=3)^M
> Feb 25 05:21:18 buildroot kern.info kernel: wlan0: RX AssocResp from
> 00:17:3f:15:8f:55 (capab=0x411 status=0 aidwlan0: associated^M
> =3)^M
> Feb 25 05:21:18 buildroot kern.info kernel: wlan0: associated^M
> wlan0: deauthenticating from 00:17:3f:15:8f:55 by local choice (reason=3)^M
> Feb 25 05:21:28 buildroot kern.info kernel: wlan0: deauthenticating from
> 00:17:3f:15:8f:55 by local choice (reason=3)^M
> cfg80211: Calling CRDA to update world regulatory domain^M
> Feb 25 05:21:28 buildroot kern.debug kernel: cfg80211: All devices are
> disconnected, going to restore regulatory settings^M
> Feb 25 05:21:28 buildroot kern.debug kernel: cfg80211: Restoring regulatory
> settings^M
> Feb 25 05:21:28 buildroot kern.debug kernel: cfg80211: Kicking the queue^M
> Feb 25 05:21:28 buildroot kern.info kernel: cfg80211: Calling CRDA to update
> world regulatory domain^M
> wlan0: authenticate with 00:17:3f:15:8f:55^M
> Feb 25 05:22:30 buildroot kern.info kernel: wlan0: authenticate with
> 00:17:3f:15:8f:55^M
> wlan0: send auth to 00:17:3f:15:8f:55 (try 1/3)^M
> Feb 25 05:22:30 buildroot kern.info kernel: wlan0: send auth to
> 00:17:3f:15:8f:55 (trwlan0: authenticated^M
> y 1/3)^M
> Feb 25 05:22:30 buildroot kern.info kernel:rtl8192cu 1-1:1.0 wlan0: disabling
> HT/VHT due to WEP/TKIP use^M
> wlan0: authenticated^M
> Feb 25 05:22:31 buildroot kern.info kernel: rtl8192cu 1-1:1.0 wlan0: disabling
> HT/VHT due to WEP/TKIP use^M
> rtl8192cu 1-1:1.0 wlan0: disabling HT as WMM/QoS is not supported by the AP^M
> Feb 25 05:22:31 buildroot kern.info kernel: rtl8192cu 1-1:1.0 wlan0rtl8192cu 1-
> 1:1.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP^M
> : disabling HT as WMM/QoS is not supported by the AP^M
> Feb 25 05wlan0: associate with 00:17:3f:15:8f:55 (try 1/3)^M
> :22:31 buildroot kern.info kernwlan0: RX AssocResp from 00:17:3f:15:8f:55
> (capab=0x411 status=0 aid=3)^M
> el: rtl8192cu 1-1:1.0 wlan0: disabling VHT as WMM/QoS is not supported by the
> AP^M
> Feb 25 05:22:31 buildroot kern.info kernel: wlan0: associate with 00:1wlan0:
> associated^M
That does not match my system. From the time I plug in my rtl8192cu device which
is shown by lsusb to be "Bus 001 Device 003: ID 7392:7811 Edimax Technology Co.,
Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]", the dmesg output
is as follows:
[47975.929602] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin
[47975.930889] usbcore: registered new interface driver rtl8192cu
[47975.977981] cfg80211: Ignoring regulatory request Set by core since the
driver uses its own custom regulatory domain
[47975.979893] ieee80211 phy1: Selected rate control algorithm 'rtl_rc'
[47975.986236] rtlwifi: wireless switch is on
[47976.821468] rtl8192cu: MAC auto ON okay!
[47976.899584] rtl8192cu: Tx queue select: 0x05
[47977.359377] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[47991.649505] wlan1: authenticate with 20:e5:2a:01:f7:ea
[47991.678097] wlan1: send auth to 20:e5:2a:01:f7:ea (try 1/3)
[47991.698862] wlan1: authenticated
[47991.700496] wlan1: associate with 20:e5:2a:01:f7:ea (try 1/3)
[47991.722112] wlan1: RX AssocResp from 20:e5:2a:01:f7:ea (capab=0x411 status=0
aid=2)
[47991.724125] wlan1: associated
[47991.724270] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[47991.732272] wlan1: dropped frame to 20:e5:2a:01:f7:ea (unauthorized port)
As I write this, the system is at 48246.72, and no drops. My AP is a Netgear
WNDR3400 running 802.11n with WPA2. What are the details for your AP?
Larry
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: problem connecting to AP on new kernel (disassociating continuously after associating ) . Can some one please comment on the issue I am facing
2013-03-19 18:14 ` Larry Finger
@ 2013-03-20 12:56 ` vishnu
0 siblings, 0 replies; 8+ messages in thread
From: vishnu @ 2013-03-20 12:56 UTC (permalink / raw)
To: linux-wireless
> That does not match my system. From the time I plug in my rtl8192cu device
which
> is shown by lsusb to be "Bus 001 Device 003: ID 7392:7811 Edimax Technology
Co.,
> Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]", the dmesg output
> is as follows:
>
> [47975.929602] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin
> [47975.930889] usbcore: registered new interface driver rtl8192cu
> [47975.977981] cfg80211: Ignoring regulatory request Set by core since the
> driver uses its own custom regulatory domain
> [47975.979893] ieee80211 phy1: Selected rate control algorithm 'rtl_rc'
> [47975.986236] rtlwifi: wireless switch is on
> [47976.821468] rtl8192cu: MAC auto ON okay!
> [47976.899584] rtl8192cu: Tx queue select: 0x05
> [47977.359377] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [47991.649505] wlan1: authenticate with 20:e5:2a:01:f7:ea
> [47991.678097] wlan1: send auth to 20:e5:2a:01:f7:ea (try 1/3)
> [47991.698862] wlan1: authenticated
> [47991.700496] wlan1: associate with 20:e5:2a:01:f7:ea (try 1/3)
> [47991.722112] wlan1: RX AssocResp from 20:e5:2a:01:f7:ea (capab=0x411
status=0
> aid=2)
> [47991.724125] wlan1: associated
> [47991.724270] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
> [47991.732272] wlan1: dropped frame to 20:e5:2a:01:f7:ea (unauthorized port)
>
> As I write this, the system is at 48246.72, and no drops. My AP is a Netgear
> WNDR3400 running 802.11n with WPA2. What are the details for your AP?
>
> Larry
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@...
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
Hello Larry,
I am using Belkin BELKIN F5D7633-4 as AP. It is configured as below
Security Mode - WPA/WPA2-Personal(PSK)
Authentication - WPA-PSK + WPA2-PSK
Encryption - TKIP
Configuration to start wifi client :
modprobe rtl8192cu
wpa_supplicant -g/var/run/wpa_supplicant-global -B
wpa_cli -g/var/run/wpa_supplicant-global interface_add wlan0 "" nl80211
/var/run/wpa_supplicant
wpa_cli -iwlan0 -a/usr/bin/wifi-action -B
wpa_cli -iwlan0 add_network
wpa_cli -iwlan0 set_network 0 ssid '"belkin54g"'
wpa_cli -iwlan0 set_network 0 key_mgmt WPA-PSK
wpa_cli -iwlan0 set_network 0 proto WPA
wpa_cli -iwlan0 set_network 0 pairwise TKIP
wpa_cli -iwlan0 set_network 0 group TKIP
wpa_cli -iwlan0 set_network 0 psk '"Test123456"'
wpa_cli -iwlan0 enable_network 0
Do you see any reason, why it is behaving differently on my system.
Regards,
Vishnu.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2013-03-20 12:56 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-03-15 13:29 problem connecting to AP on new kernel (disassociating continuously after associating ) . Can some one please comment on the issue I am facing vishnu
2013-03-16 16:44 ` Jussi Kivilinna
2013-03-18 18:20 ` vishnu
2013-03-18 18:29 ` Larry Finger
2013-03-18 18:44 ` vishnu
2013-03-19 15:40 ` vishnu
2013-03-19 18:14 ` Larry Finger
2013-03-20 12:56 ` vishnu
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.