Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Marco" <marco@tampabay.rr.com>
To: "Johannes Berg" <johannes@sipsolutions.net>,
	<linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi: 8265: unexpected LLC packets TX'ed in monitor mode
Date: Thu, 28 May 2020 10:26:04 -0400	[thread overview]
Message-ID: <C32FKI01HMGA.U0TCA9AIO8BX@b1> (raw)
In-Reply-To: <ca2b26a87d49284a07b24c71046993814c4fe821.camel@sipsolutions.net>

On Mon May 25, 2020 at 7:23 AM EDT, Johannes Berg wrote:
> On Wed, 2020-05-13 at 13:48 -0400, Marco Fonseca wrote:
> > Hello,
> > 
> > While in monitor mode, the 8265 will periodically transmit gratuitous
> > LLC packets.  In this mode, I would expect the wifi chipset to not
> > transmit any packets at all (unless packet injection is being used).
> > 
> > This behavior can be observed by a second wifi device in monitor mode.
> > A display filter on wireshark/tshark of 'llc' makes these easy to spot.
> > 
> > It seems these packets only get produced in presence of a few APs
> > and/or STAs but I'm not sure of the exact cause.  I don't see the LLC
> > packets on very quiet channels.
>
> I think these are somehow related to calibrations in the device.
>
> johannes

Are you perhaps implying that I can alter calibration settings to fix
this problem?  If you have any pointers to this it would be
appreciative.

Regardless though, I would still expect the default behavior to not
emit packets when in monitor mode, unless the user directs it to;
similar to what I've seen from other wifi chipsets.

Marco

  reply	other threads:[~2020-05-28 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 17:48 iwlwifi: 8265: unexpected LLC packets TX'ed in monitor mode Marco Fonseca
2020-05-25  9:23 ` Johannes Berg
2020-05-28 14:26   ` Marco [this message]
2020-05-28 14:53     ` Johannes Berg

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=C32FKI01HMGA.U0TCA9AIO8BX@b1 \
    --to=marco@tampabay.rr.com \
    --cc=johannes@sipsolutions.net \
    --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