From: Michael Buesch <mb@bu3sch.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: No ProbeResp - assume out of range
Date: Sun, 2 Nov 2008 23:03:54 +0100 [thread overview]
Message-ID: <200811022303.54476.mb@bu3sch.de> (raw)
In-Reply-To: <43e72e890811021305k19e9a314i6400cd1a759b3d00@mail.gmail.com>
On Sunday 02 November 2008 22:05:56 Luis R. Rodriguez wrote:
> I'm curious if others are getting this frequently as I am:
>
> No ProbeResp from current AP 00:DE:AD:BE:EE:FF - assume out of range
>
> I get this with ath5k and ath9k, can be triggered easily in ath5k by
> doing a lot of consecutive:
>
> iwlist wlan0 scan
>
> I have to check if I can trigger this with ath9k by scanning too. We
> were seeing this with ath9k but were thinking it was ath9k related as
> it can be triggered on it after doing a large TX. Wondering if this is
> more of a generic and mac80211 issue.
IMO this is a mac80211 issue.
mac80211 immediately assumes the connection is broken, if one probe-resp
to a keekalife-proberequest is lost.
So if you scan just after the request got sent, you'll never receive the response
and mac80211 will terminate the connection.
It should try a few times, instead, before blowing up things.
--
Greetings Michael.
next prev parent reply other threads:[~2008-11-02 22:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 21:05 No ProbeResp - assume out of range Luis R. Rodriguez
2008-11-02 22:03 ` Michael Buesch [this message]
2008-11-02 22:29 ` Luis R. Rodriguez
2008-11-02 22:52 ` Michael Buesch
2008-11-02 22:42 ` Tomas Winkler
2008-11-02 22:58 ` Luis R. Rodriguez
2008-11-03 0:25 ` Luis R. Rodriguez
2008-11-03 16:48 ` Felix Fietkau
2008-11-03 17:50 ` Johannes Berg
2008-11-04 5:32 ` Bharat Bhushan
2008-11-04 7:05 ` Kalle Valo
2008-11-04 6:58 ` Kalle Valo
2008-11-04 11:17 ` Michael Buesch
2008-11-04 12:43 ` Bob Copeland
2008-11-03 7:19 ` Kalle Valo
2008-11-02 22:33 ` Davide Pesavento
2008-11-04 18:19 ` Christoph Hellwig
2008-11-04 19:15 ` Luis R. Rodriguez
2008-11-05 10:30 ` Kalle Valo
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=200811022303.54476.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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).