All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: CT firmware beta-15 now has better monitor mode.
Date: Wed, 19 Aug 2015 19:16:29 -0700	[thread overview]
Message-ID: <55D5387D.9000509@candelatech.com> (raw)

Here is the changelog note.  This particular improvement does not require
any driver patches as far as I know.  I tested this on my 4.0.4+ kernel.

Should be useful for anyone doing sniffing with ath10k.

   *  Allow monitor mode to receive 'Association Request', block-ack action frames,
      nodata frames, TYPE-CTL frames.  Previously, these were not delivered to
      the WMI interface, and the kernel driver is configured to drop mgmt frames in
      the normal RX htt datapath, so host never saw them.

      This makes sniffing with ath10k a lot more useful.  When no monitor devices are
      active, the firmware reverts to the previous behaviour.  I guess the idea is that
      this is an optimization and keeps some un-needed frames off the host.

http://www.candelatech.com/ath10k.php

I'd be curious to know if anyone finds any bugs with this.  It is possible
that my changes could cause duplicate frames to be received in monitor mode,
so please keep an eye out for that.

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

WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: CT firmware beta-15 now has better monitor mode.
Date: Wed, 19 Aug 2015 19:16:29 -0700	[thread overview]
Message-ID: <55D5387D.9000509@candelatech.com> (raw)

Here is the changelog note.  This particular improvement does not require
any driver patches as far as I know.  I tested this on my 4.0.4+ kernel.

Should be useful for anyone doing sniffing with ath10k.

   *  Allow monitor mode to receive 'Association Request', block-ack action frames,
      nodata frames, TYPE-CTL frames.  Previously, these were not delivered to
      the WMI interface, and the kernel driver is configured to drop mgmt frames in
      the normal RX htt datapath, so host never saw them.

      This makes sniffing with ath10k a lot more useful.  When no monitor devices are
      active, the firmware reverts to the previous behaviour.  I guess the idea is that
      this is an optimization and keeps some un-needed frames off the host.

http://www.candelatech.com/ath10k.php

I'd be curious to know if anyone finds any bugs with this.  It is possible
that my changes could cause duplicate frames to be received in monitor mode,
so please keep an eye out for that.

Thanks,
Ben

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


             reply	other threads:[~2015-08-20  2:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20  2:16 Ben Greear [this message]
2015-08-20  2:16 ` CT firmware beta-15 now has better monitor mode 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=55D5387D.9000509@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --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 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.