From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: markh@compro.net, linux-wireless@vger.kernel.org
Subject: Re: Wireless network problem with Access Point selection using ifup
Date: Fri, 07 Dec 2012 05:12:19 -0500 [thread overview]
Message-ID: <50C1C103.1000803@cfl.rr.com> (raw)
In-Reply-To: <1354806200.18211.1.camel@jlt4.sipsolutions.net>
On 12/06/2012 10:03 AM, Johannes Berg wrote:
> On Thu, 2012-12-06 at 09:10 -0500, Mark Hounschell wrote:
>> I'm using
>> traditional ifup with static configurations.
>
> You should at least run wpa_supplicant, which will pick a better network
> and reconnect if the connection drops etc. Almost no device does that by
> itself any more.
wpa_supplicant is running.
#ps ax | grep wpa
wpa_supplicant -iwlan0 -c/var/run/wpa_supplicant-wlan0.conf -Dnl80211,wext
-P/var/run/wpa_supplicant/wlan0.pid -B
When the router in the middle of the house is chosen, as opposed to the
range extender in the very same room, the network works for a time but
eventually disassociates, usually reason 7, and never reconnects to
anything.
Mark
next prev parent reply other threads:[~2012-12-07 10:12 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 [this message]
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
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=50C1C103.1000803@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=johannes@sipsolutions.net \
--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).