From: Mark Hounschell <markh@compro.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: dmarkh@cfl.rr.com, linux-wireless@vger.kernel.org
Subject: Re: Wireless network problem with Access Point selection using ifup
Date: Fri, 07 Dec 2012 16:06:19 -0500 [thread overview]
Message-ID: <50C25A4B.8030302@compro.net> (raw)
In-Reply-To: <1354913688.9124.2.camel@jlt4.sipsolutions.net>
On 12/07/2012 03:54 PM, Johannes Berg wrote:
>
>> Thanks for responding. Do you think my problem is a wpa_supplicant
>> issue, a kernel issue, or a Dist issue?
>
> I'd say it's a wpa_s issue, but I can't remember any time that it didn't
> reconnect after getting disconnected, so maybe there's an issue with
> your driver/device that causes it to need a reset or something ... hard
> to tell more without at least the supplicant log.
>
I am wpa_supplicant stupid. I'll investigate and see if I can provide
more info. I have 4 of these devices scattered about the house on Linux
boxes. They all do the same thing. I also have 3 TV's and a windows
laptop my wife uses that all connect properly to it's closest AP. As you
can see this is a project to make the whole house wireless.
Also, personally I'm more concerned as to why the Linux boxes don't just
pick the closest AP to begin with. If it did, and it actually has, it
never disconnects and will be reliable until a reboot.
Thanks
Mark
next prev parent reply other threads:[~2012-12-07 21:06 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 [this message]
[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
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=50C25A4B.8030302@compro.net \
--to=markh@compro.net \
--cc=dmarkh@cfl.rr.com \
--cc=johannes@sipsolutions.net \
--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).