From: Johannes Berg <johannes@sipsolutions.net>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
linville <linville@tuxdriver.com>,
Reinette Chatre <reinette.chatre@intel.com>
Subject: Re: [PATCH 001/002] [MAC80211] Retry probe request few times
Date: Wed, 05 Aug 2009 07:33:36 +0200 [thread overview]
Message-ID: <1249450416.4168.22.camel@johannes.local> (raw)
In-Reply-To: <1249450153.6083.4.camel@maxim-laptop>
[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]
On Wed, 2009-08-05 at 08:29 +0300, Maxim Levitsky wrote:
> > [54632.657912] No probe response from AP 00:1c:f0:xx:xx:xx after 500ms, try 1
> > [54633.154560] No probe response from AP 00:1c:f0:xx:xx:xx after 500ms, try 2
> > [54873.231210] No probe response from AP 00:1c:f0:xx:xx:xx after 500ms, try 1
> > [55113.467840] No probe response from AP 00:1c:f0:xx:xx:xx after 500ms, try 1
> > [55113.964510] No probe response from AP 00:1c:f0:xx:xx:xx after 500ms, try 2
> > [55114.464516] No probe response from AP 00:1c:f0:xx:xx:xx after 500ms, try 3
> > [55114.967868] No probe response from AP 00:1c:f0:xx:xx:xx after 500ms, try 4
> > [55115.464511] No probe response from AP 00:1c:f0:xx:xx:xx after 500ms, disconnecting.
> >
> > Should we increase the value to 8 or something? Or just accept that
> > sometimes we get a disconnect?
> >
> I think a disconnect or two aren't a problem, they are always handled
> automatically, and can be caused by natural events.
>
> Even without these patches (I have WPA2, and disconnects were every 4
> five seconds), and still it was possible to use network.
>
> One disconnect in a day is really nothing to worry about (I have seen
> such here as well)
>
> You can increase try count, probably won't hurt much (each try is 0.5
> seconds, so even 10 tries gives total of 5 seconds, before disconnect on
> a really unaccessible AP, anyway)
Mind you, each try will end up sending a LOT of probe request frames,
iwlwifi sends like 12 frames for every try and never gets a response for
some reason, so I wouldn't really increase it much further since you'd
be spamming around a lot.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-08-05 5:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 16:13 [PATCH 000/002] Fix frequent reconnects caused by new conection monitor Maxim Levitsky
2009-07-31 16:14 ` [PATCH 001/002] [MAC80211] Retry probe request few times Maxim Levitsky
2009-07-31 16:21 ` Johannes Berg
2009-08-05 2:22 ` Marcel Holtmann
2009-08-05 5:29 ` Maxim Levitsky
2009-08-05 5:33 ` Johannes Berg [this message]
2009-08-05 5:50 ` Gábor Stefanik
2009-08-05 5:51 ` Johannes Berg
2009-08-05 5:53 ` Gábor Stefanik
2009-08-05 5:58 ` Johannes Berg
2009-08-05 15:45 ` Marcel Holtmann
2009-07-31 16:17 ` [PATCH 002/002] [MAC80211] Increase timeouts for station polling Maxim Levitsky
2009-07-31 16:21 ` Johannes Berg
2009-07-31 18:52 ` [PATCH 000/002] Fix frequent reconnects caused by new conection monitor reinette chatre
2009-07-31 19:08 ` Maxim Levitsky
2009-07-31 19:27 ` Marcel Holtmann
2009-07-31 20:05 ` Maxim Levitsky
2009-08-01 15:25 ` Marcel Holtmann
2009-08-03 22:33 ` Maxim Levitsky
2009-08-03 23:58 ` Marcel Holtmann
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=1249450416.4168.22.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcel@holtmann.org \
--cc=maximlevitsky@gmail.com \
--cc=reinette.chatre@intel.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).