All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@nokia.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: "Michael Buesch" <mb@bu3sch.de>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>
Subject: Re: No ProbeResp - assume out of range
Date: Mon, 03 Nov 2008 09:19:32 +0200	[thread overview]
Message-ID: <87prldb7jv.fsf@nokia.com> (raw)
In-Reply-To: <1ba2fa240811021442o178c98a1pa920b863b60d9293@mail.gmail.com> (ext Tomas Winkler's message of "Mon\, 3 Nov 2008 00\:42\:48 +0200")

Tomas Winkler <tomasw@gmail.com> writes:

>> 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.
>
> I've seen this happening  in high traffic with some APs but it can be
> also NIC issue. It needs to really investigate the sniffer capture I
> wouldn't assume its only mac80211 issue.  Probe is issued only when RX
> is not received for some time so there is some problem, nevertheless
> monitoring beacons is a better approach from my experience.

I agree, monitoring received beacons and the number of failed
transmissions would be better. But on the other hand some broken APs
might work better if we periodically send frames to them.

-- 
Kalle Valo

  parent reply	other threads:[~2008-11-03  7:19 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
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 [this message]
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=87prldb7jv.fsf@nokia.com \
    --to=kalle.valo@nokia.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=mcgrof@gmail.com \
    --cc=tomasw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.