From: Ben Greear <greearb@candelatech.com>
To: Thomas Pedersen <thomas@eero.com>, Javier Cardona <jcardona@fb.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Frames acknowledged and silently discarded in firmware
Date: Wed, 14 Mar 2018 09:47:43 -0700 [thread overview]
Message-ID: <1c4295b7-8d14-6637-e3b9-ece031d0936e@candelatech.com> (raw)
In-Reply-To: <CADjYELy+LnHd77X+9YPmHFMoeb3Vx0+JVDgmPd_H1eysUF-sNQ@mail.gmail.com>
On 03/13/2018 05:52 PM, Thomas Pedersen wrote:
> Javier,
>
> On Tue, Mar 13, 2018 at 4:42 PM, Javier Cardona <jcardona@fb.com> wrote:
>> Hi,
>>
>> We have resolved this issue. I'm sharing the details in case that might help others.
>>
>> The description of the problem was accurate EXCEPT that the acks that we observed on the sniffer were not being sent by the failed station (MAP2, in the context of my original e-mail) but by a third station MAP3. Those Acks were sent by MAP3 but with MAP2's address in the Transmitter Address field.
>>
>> These anomalous Block Acks were sent because the MAC-ADDRESS-FILTER was misconfigured at MAP3, which caused that station to respond to addresses different than its own. The reasons for this misconfiguration were:
>> (1) in mesh (and other) mode(s), the driver creates a hidden monitor vif along the mesh vif
>
> At least since some 10.4 firmware, the hidden monitor vdev is no longer
> required. See https://www.spinics.net/lists/linux-wireless/msg156475.html
I'd like to fix my firmware to support this same feature (in case it does not currently
support it) and add the pertinent firmware feature flags.
Can anyone share the filter flag name(s) that needs to be enabled in the firmware for mesh
mode so that monitor devices are not required?
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
next prev parent reply other threads:[~2018-03-14 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 22:15 Frames acknowledged and silently discarded in firmware Javier Cardona
2018-02-08 23:23 ` Adrian Chadd
2018-02-09 1:21 ` Javier Cardona
2018-02-09 1:27 ` Adrian Chadd
2018-03-13 23:42 ` Javier Cardona
2018-03-14 0:09 ` Ben Greear
2018-03-14 0:20 ` Adrian Chadd
2018-03-14 2:36 ` Javier Cardona
2018-03-14 0:52 ` Thomas Pedersen
2018-03-14 2:33 ` Javier Cardona
2018-03-14 16:47 ` Ben Greear [this message]
2018-03-14 17:00 ` Thomas Pedersen
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=1c4295b7-8d14-6637-e3b9-ece031d0936e@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=jcardona@fb.com \
--cc=thomas@eero.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox