From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC] ath9k: validate for non-zero BSSID
Date: Wed, 30 Nov 2011 10:51:58 +0530 [thread overview]
Message-ID: <4ED5BD76.7020204@qca.qualcomm.com> (raw)
In-Reply-To: <20111130023650.19520.qmail@stuge.se>
Hi Peter,
On Wednesday 30 November 2011 08:06 AM, Peter Stuge wrote:
> Mohammed Shafi Shajakhan wrote:
>> before concluding that the recieved beacon is for us, let us make sure
>> that the BSSID is non-zero.
>
> Under what circumstances would the BSSID be zero?
>
>
> //Peter
unassociated state for station.
but I observed this when i tested ad-hoc mode. I just started an ad-hoc
mode creator and left it for some time with no one joining. i observed
there are few frames in rx_tasklet of ath9k driver which seem to be
beacons and their BSSID is '0', as our curbssid is also '0' they seem to
be wrongly identified as 'my_beacons'. let me also verify it in STA mode
and find the effect of this before sending it as a PATCH.
let me also check if it has any effect in ath9k_process_rssi and ath_rx_ps.
--
thanks,
shafi
WARNING: multiple messages have this Message-ID (diff)
From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: "John W. Linville" <linville@tuxdriver.com>,
Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>,
Jouni Malinen <jouni@qca.qualcomm.com>,
<ath9k-devel@lists.ath9k.org>, <linux-wireless@vger.kernel.org>,
Rodriguez Luis <rodrigue@qca.qualcomm.com>,
Vivek Natarajan <nataraja@qualcomm.com>,
Balasubramanian senthilkumar <senthilb@qca.qualcomm.com>,
Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Subject: Re: [ath9k-devel] [RFC] ath9k: validate for non-zero BSSID
Date: Wed, 30 Nov 2011 10:51:58 +0530 [thread overview]
Message-ID: <4ED5BD76.7020204@qca.qualcomm.com> (raw)
In-Reply-To: <20111130023650.19520.qmail@stuge.se>
Hi Peter,
On Wednesday 30 November 2011 08:06 AM, Peter Stuge wrote:
> Mohammed Shafi Shajakhan wrote:
>> before concluding that the recieved beacon is for us, let us make sure
>> that the BSSID is non-zero.
>
> Under what circumstances would the BSSID be zero?
>
>
> //Peter
unassociated state for station.
but I observed this when i tested ad-hoc mode. I just started an ad-hoc
mode creator and left it for some time with no one joining. i observed
there are few frames in rx_tasklet of ath9k driver which seem to be
beacons and their BSSID is '0', as our curbssid is also '0' they seem to
be wrongly identified as 'my_beacons'. let me also verify it in STA mode
and find the effect of this before sending it as a PATCH.
let me also check if it has any effect in ath9k_process_rssi and ath_rx_ps.
--
thanks,
shafi
next prev parent reply other threads:[~2011-11-30 5:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 14:22 [ath9k-devel] [RFC] ath9k: validate for non-zero BSSID Mohammed Shafi Shajakhan
2011-11-29 14:22 ` Mohammed Shafi Shajakhan
2011-11-30 2:36 ` [ath9k-devel] " Peter Stuge
2011-11-30 2:36 ` Peter Stuge
2011-11-30 5:21 ` Mohammed Shafi Shajakhan [this message]
2011-11-30 5:21 ` Mohammed Shafi Shajakhan
2011-11-30 6:47 ` Kalle Valo
2011-11-30 6:47 ` Kalle Valo
2011-11-30 7:11 ` Mohammed Shafi Shajakhan
2011-11-30 7:11 ` Mohammed Shafi Shajakhan
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=4ED5BD76.7020204@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.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.