All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Sending frames on monitor interface?
Date: Fri, 20 Feb 2015 09:27:49 -0800	[thread overview]
Message-ID: <54E76E95.6070003@candelatech.com> (raw)
In-Reply-To: <CA+BoTQn=oZ6g4J4gDNs2pnNYg4ifkhNh5S1iYS35VurnZzMTDQ@mail.gmail.com>

On 02/19/2015 10:43 PM, Michal Kazior wrote:
> On 19 February 2015 at 22:38, Ben Greear <greearb@candelatech.com> wrote:
>> Do any of the firmware versions support sending (raw) frames on
>> the monitor interface?
>>
>> It seems 10.1 just asserts if someone tries this.  I can fix at least
>> some of this, but firmware seems to want a peer in order to transmit
>> any packets...maybe adding self-peer to the monitor interface is
>> a way to get around this?
> 
> Just an idea: Once upon a time we had to create temporary DA peer for
> offchannel tx (the code is still in ath10k). 10.1 might want something
> like that as well for data frames.

I hacked my CT firwmare to allow transmit on monitor interfaces, including
logic to allow setting up a (fake) peer and rate-ctrl structures.

I tweaked ath10k to create a peer when starting the monitor interface,
using the local radio's MAC as the peer address (this could easily be part
of the problem).  I hacked the firmware to always use this peer object when
transmitting on a monitor interface.

Packets now appear to be accepted for transmit, but I do not see anything on
the air.  I'll dig into it more if I find time...but not sure exactly how useful
the feature is anyway.

I see the code for off-channel work that you are talking about.  That seems like
a pretty awful hack if you wanted to do any realistic throughput, but I bet that
whatever issue this works around is the same issue that I am having trying to
get monitor TX to work.

Thanks,
Ben

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


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2015-02-20 17:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 21:38 Sending frames on monitor interface? Ben Greear
2015-02-20  6:43 ` Michal Kazior
2015-02-20 17:27   ` Ben Greear [this message]
2015-02-23  6:37     ` Michal Kazior
2015-02-23 17:16       ` Ben Greear

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=54E76E95.6070003@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=michal.kazior@tieto.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.