Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Gui Iribarren <gui@altermundi.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Realtime plot of Spectral Scan in ath9k
Date: Sun, 28 Jul 2013 04:29:54 -0300	[thread overview]
Message-ID: <51F4C872.3070703@altermundi.net> (raw)
In-Reply-To: <CAJ-Vmom_WWwzjkAhYL3X9thnwP22jwCUQLYQzBB-NSMnKM9Y6Q@mail.gmail.com>

On 07/26/2013 06:18 PM, Adrian Chadd wrote:
> Right. Adjacent channels can decode some CCK frames, but OFDM should
> look like garbage.
>
> Now, the $50 question - can we (ab)use the signal sizing / threshold
> parameters (like what ANI does) to make the OFDM/CCK receiver
> effectively deaf to wireless frames, so they appear as spectral
> samples? Hm!

He-he ;)
well, i actually did try the opposite: i wanted to generate/visualize 
recognizable spectral patterns, like a 5mhz bw communication, which 
would definitely appear and stand out clear, so i set a couple of 
routers with wireless.radio0.chanbw=5 ... sadly it didn't work.

/sys/kernel/debug/ieee80211/phy0/ath9k/chanbw was correctly set to 0x5
but communication used 20mhz as usual. didn't dug into it, maybe i was 
missing some other option.. who knows, didn't care much, it was just a test.

Yet, I must admit I didn't think about setting the *scanning* radio to a 
narrower bandwidth, that would definitely make the trick!
Hm, there's no code yet for sampling anything else than HT20,
But in any case, I think we would need a "spectral scan" mode, distinct 
from "normal" scan (which is currently overloaded with sampling), to be 
able to:
a) Use a narrower bandwidth like you say,
b) not send any beacon request, or wait for any beacon (which is what i 
suspect happens in "passive" scans) which would speed up the hopping

i don't know what are the implications of modifying the bw size, is it 
something that can be done just for a single scan? i.e. radio is 
operating normally on 20/40mhz, talking to peers, and for an instant 
(100ms?) makes a quick scan with 5mhz bw over 14 channels in 2.4ghz, 
then goes back to normal 20/40mhz?
maybe a reset is needed between those bw changes?
[I have *absolutely* no idea of what i'm talking about]

Thanks a lot for the feedback Adrian!

Gui

>
>
> -adrian
>

  reply	other threads:[~2013-07-28  7:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 15:50 [ath9k-devel] Spectral Scan in ath9k Saulo Queiroz
2012-03-24 22:53 ` Adrian Chadd
2012-05-30 10:25   ` Alex Hacker
2012-05-31 10:58     ` Saulo Queiroz
2012-05-31 13:27       ` Alex Hacker
2012-05-31 14:48     ` abhinav narain
2012-05-31 19:19       ` Adrian Chadd
2012-06-01  3:01         ` Peizhao Hu
2012-06-01 14:10           ` Adrian Chadd
2012-06-01  8:57         ` Alex Hacker
2013-05-08 16:15           ` Claudio
2013-05-08 17:50             ` Oleksij Rempel
2013-06-10 15:15               ` Gui Iribarren
2013-07-25 13:43                 ` [ath9k-devel] Realtime plot of " Gui Iribarren
2013-07-25 19:54                   ` Adrian Chadd
2013-07-26 16:18                     ` Gui Iribarren
2013-07-26 18:26                       ` Gui Iribarren
2013-07-26 21:18                         ` Adrian Chadd
2013-07-28  7:29                           ` Gui Iribarren [this message]
2013-07-28 17:52                             ` Adrian Chadd
2013-07-30 12:12                   ` Michal Kazior
2013-07-25 20:24                 ` [ath9k-devel] Measurements with " Gabriel Tolón

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=51F4C872.3070703@altermundi.net \
    --to=gui@altermundi.net \
    --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