From: Lukasz <zmielony@poczta.onet.pl>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: signal level of rxed probe req.
Date: Sat, 23 Jun 2012 22:13:28 +0200 [thread overview]
Message-ID: <4FE62368.50105@poczta.onet.pl> (raw)
In-Reply-To: <CAOpc7mHNbuzNP5J-XjbZCEcjCm6SRg1ONC1FhGNUsKxDVNn=xA@mail.gmail.com>
On 06/22/2012 08:42 AM, Holger Schurig wrote:
>> Is there any way to filter out frames received on other channels (so I only
>> receive frames from channel on which my AP is configured)?
>
> No, there isn't. Suppose the probe request was sent on channel 10. And
> your AP is on channel 11. Then your AP actually really receives the
> probe request on channel 11. Those channels are overlapping, after
> all. Also, then "received channel" information in some wiretap header
> (available on some monitoring interface) would also indicate channel
> 11.
>
> You may use a heuristics: then you receive probe requests, record
> their mac, signal level and a time stamp. If you get another probe
> requets from the same MAC and the time is similar to what you already
> have, then use the higher signal. That will work because a probing
> client usually probes on different frequencies within a short timespan
> (around 100 ms per channel).
>
Actually I'm doing it this way now. The problem is that different devices use
different scan interval, also time of channel switch doesn't seem to be constant
(even for the same device). And it sometimes happens that not all frames are
being received by AP. So it's quite tricky to find out good filter timing.
Anyway, I think I will have to improve my current filtering implementation :)
Thank you for answers!
with regards,
Lukasz
prev parent reply other threads:[~2012-06-23 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 20:39 [ath9k-devel] ath9k: signal level of rxed probe req Lukasz
2012-06-21 22:15 ` Guido Iribarren
2012-06-22 6:42 ` Holger Schurig
2012-06-22 7:21 ` Guido Iribarren
2012-06-22 8:04 ` Holger Schurig
2012-06-22 9:57 ` Guido Iribarren
2012-06-23 20:13 ` Lukasz [this message]
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=4FE62368.50105@poczta.onet.pl \
--to=zmielony@poczta.onet.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox