From: Johannes Berg <johannes@sipsolutions.net>
To: dmarkh@cfl.rr.com
Cc: markh@compro.net, linux-wireless@vger.kernel.org
Subject: Re: Wireless network problem with Access Point selection using ifup
Date: Mon, 10 Dec 2012 12:29:19 +0100 [thread overview]
Message-ID: <1355138959.9857.13.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <50C5C321.1090501@cfl.rr.com>
On Mon, 2012-12-10 at 06:10 -0500, Mark Hounschell wrote:
> The driver is use has was identified in the original email. So I guess this
> is the right place to report this issue?
Yeah, I guess Larry should take a look.
> In each of the wpa log files I See
> in the beginning, a section like this:
>
> nl80211: Received scan results (4 BSSes)
> wlan0: BSS: Start scan result update 1
> wlan0: BSS: Add new id 0 BSSID c8:d7:19:7a:ab:1e SSID 'hounschell-1'
> wlan0: BSS: Add new id 1 BSSID 20:aa:4b:b2:dd:79 SSID 'hounschell-1'
> wlan0: BSS: Add new id 2 BSSID 00:18:f8:ff:72:d5 SSID 'hounschell-1'
> wlan0: BSS: Add new id 3 BSSID 00:1a:70:6d:99:50 SSID 'MACDONALD'
>
> Every time the first one listed is the one actually selected and each time
> is different and usually NOT the closest.
That's expected, the order is random by the order in which it was found
in scanning etc. There's no inherent order here.
> It is a Desktop in a fixed location. The AP is within 15ft of the ASUS USB
> adapter and in direct line of sight. There may be more than one problem
> here. I think one of the problems is right here. Above 20:aa:4b:b2:dd:79 is
> the closest AP. Why is it not first in the list?
See above.
> Why, when it selects one
> of the others and it can't figure out it selected the wrong one and
> reselect the right one seems like a different problem. After all when it
> does select the correct one, all is good but the actual bandwidth.
Well so I suspect the driver is also not reporting useful signal
strength so that wpa_s doesn't know which one to select. And then when
the connection fails, the driver is refusing scanning so it can't even
reconnect to a better AP ...
IOW, all driver problems, and I'm not familiar enough with that driver
to tell you what's going on.
johannes
next prev parent reply other threads:[~2012-12-10 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 14:10 Wireless network problem with Access Point selection using ifup Mark Hounschell
2012-12-06 15:03 ` Johannes Berg
2012-12-07 10:12 ` Mark Hounschell
2012-12-07 20:50 ` Mark Hounschell
2012-12-07 20:54 ` Johannes Berg
2012-12-07 21:06 ` Mark Hounschell
[not found] ` <50C5B65F.4040104@cfl.rr.com>
2012-12-10 10:26 ` Johannes Berg
2012-12-10 11:10 ` Mark Hounschell
2012-12-10 11:29 ` Johannes Berg [this message]
2012-12-10 12:00 ` Mark Hounschell
2012-12-10 12:46 ` rtl8192cu problem - " Johannes Berg
2012-12-10 16:24 ` Larry Finger
2012-12-10 17:38 ` Mark Hounschell
2013-01-03 12:52 ` Mark Hounschell
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=1355138959.9857.13.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dmarkh@cfl.rr.com \
--cc=linux-wireless@vger.kernel.org \
--cc=markh@compro.net \
/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).