linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Ben Greear <greearb@candelatech.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: Thu, 20 Aug 2015 17:11:10 +0200	[thread overview]
Message-ID: <55D5EE0E.3020408@neratec.com> (raw)
In-Reply-To: <55D4D406.5000603@candelatech.com>

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.


Good Luck,
Zefir


[1] https://github.com/chunkeey/carl9170fw/tree/radar

  reply	other threads:[~2015-08-20 15:16 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 [this message]
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
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=55D5EE0E.3020408@neratec.com \
    --to=zefir.kurtisi@neratec.com \
    --cc=chunkeey@googlemail.com \
    --cc=greearb@candelatech.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).