From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Aleksandar Milivojevic <alex@milivojevic.org>
Cc: Wolfgang Kufner <wolfgang.kufner@gmail.com>,
Luis Correia <buga@loide.net>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"users@rt2x00.serialmonkey.com" <users@rt2x00.serialmonkey.com>,
Helmut Schaa <helmut.schaa@googlemail.com>
Subject: Re: [rt2x00-users] Linksys WUSB600N v1 disconnecting from AP
Date: Thu, 6 Jan 2011 18:44:32 -0800 [thread overview]
Message-ID: <20110107024432.GC20431@tux> (raw)
In-Reply-To: <AANLkTin8JO4UHUYLufSmPhRw0ZndDdjTpueSOHNQbDiZ@mail.gmail.com>
On Thu, Jan 06, 2011 at 08:31:22AM -0800, Aleksandar Milivojevic wrote:
> Playing with it a bit more this morning. Looks like the connection
> from wireless adapter to my AP drops periodically. Sometimes it
> recovers (sometimes after several attempts), sometimes it does not.
> Seems to be very random:
>
> # egrep 'authent|associat' /var/log/debug
> Jan 6 08:00:54 toporko kernel: [ 47.570810] wlan0: authenticate
> with 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:00:54 toporko kernel: [ 47.571321] wlan0: authenticated
> Jan 6 08:00:56 toporko kernel: [ 49.174175] wlan0: associate with
> 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:00:56 toporko kernel: [ 49.175536] wlan0: associated
> Jan 6 08:06:01 toporko kernel: [ 354.230874] wlan0: authenticate
> with 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:06:01 toporko kernel: [ 354.231364] wlan0: authenticated
> Jan 6 08:06:01 toporko kernel: [ 354.236066] wlan0: associate with
> 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:06:01 toporko kernel: [ 354.236865] wlan0: associated
> Jan 6 08:09:36 toporko kernel: [ 569.868923] wlan0: authenticate
> with 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:09:36 toporko kernel: [ 569.869416] wlan0: authenticated
> Jan 6 08:09:36 toporko kernel: [ 569.873736] wlan0: associate with
> 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:09:36 toporko kernel: [ 569.874507] wlan0: associated
> Jan 6 08:09:46 toporko kernel: [ 579.233563] wlan0: authenticate
> with 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:09:46 toporko kernel: [ 579.235574] wlan0: authenticated
> Jan 6 08:09:46 toporko kernel: [ 579.240737] wlan0: associate with
> 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:09:46 toporko kernel: [ 579.241518] wlan0: associated
> Jan 6 08:09:57 toporko kernel: [ 590.830933] wlan0: authenticate
> with 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:09:57 toporko kernel: [ 590.831435] wlan0: authenticated
> Jan 6 08:09:57 toporko kernel: [ 590.839102] wlan0: associate with
> 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:09:57 toporko kernel: [ 590.839881] wlan0: associated
> Jan 6 08:21:29 toporko kernel: [ 1282.823289] wlan0: authenticate
> with 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:21:29 toporko kernel: [ 1282.823783] wlan0: authenticated
> Jan 6 08:21:29 toporko kernel: [ 1282.828990] wlan0: associate with
> 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:21:29 toporko kernel: [ 1282.830132] wlan0: associated
> Jan 6 08:25:30 toporko kernel: [ 1523.433931] wlan0: authenticate
> with 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:25:30 toporko kernel: [ 1523.434930] wlan0: authenticated
> Jan 6 08:25:30 toporko kernel: [ 1523.439868] wlan0: associate with
> 00:1e:52:79:e9:ff (try 1)
> Jan 6 08:25:30 toporko kernel: [ 1523.440652] wlan0: associated
>
> So far, it managed to re-connect every time. Though, I'm rather sure
> if I leave it long enough, the last night's case of connection dropped
> completely would repeat sooner or later (even last night, there were
> some connect/disconnect events before connection was dropped
> permanently).
>
> The AP reports signal from wireless card between -70 and -75dB, noise
> at -96dB, and speed at 120mbps (with occasional drop to 45mbps).
> These numbers sound about OK for the location (on the other side of my
> apartment, few walls in between). For comparison, if I position my
> MacBook at same location (right next to my Linux box), AP reports
> signal from its AirPort card at about -60dB and speed in about 100mbps
> range and no drops.
The Linux regulatory code only relies on the Country IE from the AP you
decide to associate to, that's it. Then, as for all the regulatory stuff
popping out once you are associated, its happening because as I see it
you are being disconnected from the AP. The Linux regulatory code will
reset the regulatory settings after you disconnect from an AP.
The disconnect issues should not be regularory related from what I see.
Seems like a general disconnect issue with your driver.
Luis
next prev parent reply other threads:[~2011-01-07 2:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTim0AM3=T=TMu79ZQi79+CKANamBcz620n2xm8bW@mail.gmail.com>
2011-01-04 18:46 ` [rt2x00-users] Linksys WUSB600N v1 disconnecting from AP Helmut Schaa
2011-01-04 19:01 ` Luis Correia
[not found] ` <AANLkTi=KFG-7GPw2=6VTZqEceEcJM6OdWoTQaN_83NqP@mail.gmail.com>
[not found] ` <AANLkTikREOFV+WGWgo9yh9bTrz346kF0muKE8gs5N+km@mail.gmail.com>
2011-01-04 21:53 ` Aleksandar Milivojevic
2011-01-04 22:31 ` Wolfgang Kufner
2011-01-05 6:57 ` Aleksandar Milivojevic
2011-01-05 10:32 ` Wolfgang Kufner
2011-01-06 4:11 ` Aleksandar Milivojevic
2011-01-06 7:09 ` Aleksandar Milivojevic
2011-01-06 16:31 ` Aleksandar Milivojevic
2011-01-07 2:44 ` Luis R. Rodriguez [this message]
2011-01-07 10:11 ` Helmut Schaa
2011-01-07 19:46 ` Aleksandar Milivojevic
2011-01-07 20:22 ` Luis R. Rodriguez
2011-01-07 22:13 ` Peter Stuge
2011-01-07 22:18 ` Luis R. Rodriguez
2011-01-07 23:00 ` Peter Stuge
2011-01-07 23:26 ` Jouni Malinen
2011-01-07 22:54 ` Aleksandar Milivojevic
2011-01-08 6:14 ` Aleksandar Milivojevic
2011-01-08 9:47 ` Helmut Schaa
2011-01-10 7:12 ` Aleksandar Milivojevic
2011-01-10 7:30 ` Gertjan van Wingerde
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=20110107024432.GC20431@tux \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=alex@milivojevic.org \
--cc=buga@loide.net \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.com \
--cc=wolfgang.kufner@gmail.com \
/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).