From: vishnu <vishnu.kopparapu@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: problem connecting to AP on new kernel (disassociating continuously after associating ) . Can some one please comment on the issue I am facing
Date: Wed, 20 Mar 2013 12:56:09 +0000 (UTC) [thread overview]
Message-ID: <loom.20130320T134142-168@post.gmane.org> (raw)
In-Reply-To: 5148AB04.2070003@lwfinger.net
> 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.
prev parent reply other threads:[~2013-03-20 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20130320T134142-168@post.gmane.org \
--to=vishnu.kopparapu@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).