All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>,
	Zefir Kurtisi <zefir.kurtisi@neratec.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Christian Lamparter <chunkeey@googlemail.com>
Subject: Re: Using ath5k/ath9k radio for constant-tx noise source.
Date: Fri, 11 Aug 2017 15:56:37 -0700	[thread overview]
Message-ID: <ecbebbde-bc34-d51e-99be-6c629dc8629c@candelatech.com> (raw)
In-Reply-To: <c7ead258-5a88-5c76-b65e-3286d5b5b4ff@dd-wrt.com>


On 10/22/2016 07:49 AM, Sebastian Gottschall wrote:
> atheros has a continues transmission mode which is used for power calibration in factory using the ART utility. its available on ath9k cards as well.
> once enabled no wifi connection is possible on the same frequency since it will break up all CSMA handling also with neighbor networks. its a nice
> feature for disconnecting all wifi networks in your area
> look for the called atheros / qca TESTMODE. its a simple register setting (enable, disable)

Hello,

I noticed recently that the carl9170 based system I was using can do a minimum
burst width of about 17us, which is not good enough for most RADAR emulation
settings (which often need 1us, 11us, etc).

So, I am back to thinking about trying this for ath9k, in hopes it can cycle
TX on/off faster.

So far, I have not found any useful info searching for TESTMODE in ath9k and madwifi code.

Do you have any more specific details about where I can find documents or source
code that uses the TX100 mode for ath9k?

Thanks,
Ben

>
> Am 15.09.2016 um 17:28 schrieb Zefir Kurtisi:
>> Hi Ben,
>>
>> On 09/15/2016 02:22 AM, Ben Greear wrote:
>>> On 08/20/2015 08:11 AM, Zefir Kurtisi wrote:
>>>> On 08/19/2015 09:07 PM, Ben Greear wrote:
>>>>> I have a commercial AP that is using a CM9 ath5k radio (evidently, I could be
>>>>> wrong)
>>>>> and it has the ability to do a constant transmit of raw noise (RF probe shows
>>>>> noise, but a monitor-port sniffer does not see any frames from the CM9).
>>>>>
>>>>> I don't know the low-level details of how it is doing this, but I suspect
>>>>> it is using something like madwifi for a driver.
>>>>>
>>>>> Does anyone know how this can be done with modern software and
>>>>> ath5k or ath9k NICs?
>>>>>
>>>>> Thanks,
>>>>> Ben
>>>>>
>>>> Maybe slightly related: some years ago when DFS became a topic and it was hard to
>>>> get hands on radar pattern generators, Christian Lamparter wrote a variant of the
>>>> carl9170 fw [1] which can generate radar pulses to test ath9k and other DFS radar
>>>> detectors. Pulses are generated by enabling txout at defined sampling intervals.
>>>>
>>>> It should be doable to mimic what you are looking for by generating a _very_ long
>>>> pulse.
>>> Sorry to revive such an old thread..but I'm back poking at this.
>>>
>> Whew, that year went by so incredibly fast ;)
>>
>>> I've used the modified carl9170 firmware to generate pulses, with
>>> the control being 'pulse-width' and 'pulse-interval'.
>>>
>>> This sort of works, and sometimes our ath10k in an isolation chamber reports
>>> a radar event.
>>>
>>> But, after some reading, I am thinking I need more control to better mimic
>>> a radar.
>>>
>>> If I understand things properly, I need something like this:
>>>
>>> A pulse event being:  pulse width, pulse period:  For instance 1us, 200us
>>> Then, I need to configure an amount of pulse events, maybe 10-30 consecutive pulse
>>> events.
>>> Then, I need a quiet period to mimic the radar sweeping full circle (15 seconds
>>> perhaps)
>>>
>>>  From what I can tell, the carl9170 modified firmware is missing the features
>>> to do this, though it should not be too difficult to add.
>>>
>> Yes, that's essentially it - the last step is even not needed if your goal is to
>> estimate DFS detection probabilities, since in the certification lab they usually
>> just repeatedly fire the radar pattern and count detection events.
>>
>> When I played with the modified carl9170 FW, I estimated that developing an solid
>> and reliable radar pattern pulse scheduler would take me 2-4 weeks, so being in a
>> hurry I ended up using an SDR (Ettus USRP N200, see [1]). I developed a pulse
>> scheduler to feed arbitrary patterns (covering those for DFS testing), which is
>> available in [2]. It has not been maintained ever since, but might help you as
>> starting point if you decide to go that route.
>>
>>> If someone has an idea whether the control above is appropriate, I'd
>>> appreciate feedback before I start hacking...
>>>
>>> This document seemed useful, for instance:
>>>
>>> https://dl.cdn-anritsu.com/en-en/test-measurement/files/Product-Introductions/Product-Introduction/mx370073a-el1200.pdf
>>>
>> We use the R&S SMBV100A [3], which we know is also used in some certification
>> labs. Unfortunately it is not exactly cheap - if you are not going to prepare your
>> product for certification, the SDR approach is affordable and good enough.
>>
>>> Thanks,
>>> Ben
>>>
>> Good luck,
>> Zefir
>>
>> [1] https://www.ettus.com/product/details/UN200-KIT
>> [2] https://github.com/zefir-kurtisi/USRP-Radar-Relay
>> [3]
>> https://www.rohde-schwarz.com/us/product/smbv100a-productstartpage_63493-10220.html
>>
>>
>
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2017-08-11 22:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 19:07 Using ath5k/ath9k radio for constant-tx noise source Ben Greear
2015-08-20 15:11 ` Zefir Kurtisi
2016-09-15  0:22   ` Ben Greear
2016-09-15 13:26     ` Bob Copeland
2016-09-15 16:03       ` Ben Greear
2016-09-15 15:28     ` Zefir Kurtisi
2016-09-15 15:59       ` Ben Greear
2016-10-22 14:49       ` Sebastian Gottschall
2017-08-11 22:56         ` Ben Greear [this message]
2015-09-08  9:21 ` Nick Kossifidis
2016-09-18 22:14 ` Bob Copeland

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=ecbebbde-bc34-d51e-99be-6c629dc8629c@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=s.gottschall@dd-wrt.com \
    --cc=zefir.kurtisi@neratec.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.