From: Jouni Malinen <j@w1.fi>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/2] mac80211: ignore probe response from adjacent channels
Date: Wed, 5 Mar 2014 12:51:23 +0200 [thread overview]
Message-ID: <20140305105123.GA32093@w1.fi> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB303D786F6@HASMSX103.ger.corp.intel.com>
On Wed, Mar 05, 2014 at 09:16:44AM +0000, Grumbach, Emmanuel wrote:
> >
> > On Tue, Mar 04, 2014 at 04:50:14PM +0200, Emmanuel Grumbach wrote:
> > > This logic is already implemented in ieee80211_rx_mgmt_beacon.
> > > The purpose is to ignore probe responses that are received on adjacent
> > > channels. This can happen in 2.4GHz since channels overlap.
> >
> > Why would this be done? I can understand not updating signal information,
> > but dropping Probe Response frames completely sounds quite undesirable.
> > These can be used to help optimize partial scans and any additional
> > information that can be used without having to change channels sounds
> > helpful to me.
> So I guess you want me to revert the code we currently have in ieee80211_rx_mgmt_beacon ;)
I'm not sure about Beacon frames, but possibly. Anyway, I was more
thinking about use of active scanning on 2.4 GHz band and that would be
more applicable for Probe Response frames.
> Don't know really... If you are associated to an AP and hear its beacons / probe responses on another channel you really have a big problem in your radio?
Is this only for the case of Beacon/Probe Response frames from the AP
with which the device is associated? The commit log seemed to imply that
this is for all Probe Response frames. I have no problems with the Probe
Response from the current AP being ignored from other channels; it is
the case of finding other APs that I'm much more interested in in this
context.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2014-03-05 10:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 14:50 [PATCH 1/2] cfg80211/mac80211: ignore signal if the frame was heard on wrong channel Emmanuel Grumbach
2014-03-04 14:50 ` [PATCH 2/2] mac80211: ignore probe response from adjacent channels Emmanuel Grumbach
2014-03-05 9:08 ` Jouni Malinen
2014-03-05 9:16 ` Grumbach, Emmanuel
2014-03-05 10:51 ` Jouni Malinen [this message]
2014-03-05 9:20 ` Grumbach, Emmanuel
2014-03-05 10:54 ` Jouni Malinen
2014-03-05 11:00 ` Grumbach, Emmanuel
2014-03-05 11:20 ` Grumbach, Emmanuel
2014-03-19 14:15 ` [PATCH 1/2] cfg80211/mac80211: ignore signal if the frame was heard on wrong channel Johannes Berg
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=20140305105123.GA32093@w1.fi \
--to=j@w1.fi \
--cc=emmanuel.grumbach@intel.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 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.