ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: ath10k@lists.infradead.org, Ben Greear <greearb@candelatech.com>,
	Sebastian Gottschall <s.gottschall@dd-wrt.com>
Subject: Re: EAP AP/VLAN: multicast not send to client
Date: Tue, 02 Feb 2021 10:06:26 +0100	[thread overview]
Message-ID: <2354947.QRssEMCmQP@ripper> (raw)
In-Reply-To: <93607622-3fef-a203-6ca0-3daa54dff07c@dd-wrt.com>


[-- Attachment #1.1: Type: text/plain, Size: 1725 bytes --]

On Tuesday, 2 February 2021 09:58:45 CET Sebastian Gottschall wrote:
> 
> Am 02.02.2021 um 09:23 schrieb Sven Eckelmann:
> > On Tuesday, 2 February 2021 08:04:56 CET Sebastian Gottschall wrote:
> >> the standard ath10k firmware für qca988x chipsets does filter vlans.
> > Just to be sure that we are talking about the same thing: I am (or actually
> > hostapd is) using NL80211_IFTYPE_AP_VLAN here - not 802.1Q.

> then it might be something different. i'm not sure at that point. but 
> consider that AP_VLAN is also used for WDS STA/WDS AP implementations.
> so each wds station becomes a individual interface on ap side for 
> bridging. that might of course have a influence to broadcast/multicast 
> frames

Interestingly, the WDS "mode" works perfectly fine  on the same hardware. So I 
have not a real idea what the difference is between EAP AP_VLAN and WDS (PSK) 
AP_VLAN at the moment.

> in addition the 10.4 firmware series has a special wmi flag which is not 
> used by ath10k, but solved alot of problems for me (in my case with 
> reauthentication)
> WMI_VDEV_DISABLE_4_ADDR_SRC_LRN
> this might be unrelated to your issue. but this flag must be set anyway 
> for proper work. but it isnt by default in all 10.4 firmwares.

Good to know, thanks.

> > For Ben Greear's firmware, the only workaround which I found until now was to
> > set NL80211_ATTR_MULTICAST_TO_UNICAST_ENABLED to 1 to force mac80211 to send
> > multicast as unicast.
> so if its a pure multicast/unicast issue it could be also a basic rate 
> issue for ct firmwares.

Interesting idea. Btw. I've also switched to sw crypto for a test just to make 
sure that there is no HW key problem.

Kind regards,
	Sven

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

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

  reply	other threads:[~2021-02-02  9:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 20:54 EAP AP/VLAN: multicast not send to client Sven Eckelmann
2021-02-02  7:04 ` Sebastian Gottschall
2021-02-02  8:23   ` Sven Eckelmann
2021-02-02  8:58     ` Sebastian Gottschall
2021-02-02  9:06       ` Sven Eckelmann [this message]
2021-02-02  9:12         ` Sebastian Gottschall
2021-02-02 10:12           ` Sven Eckelmann
2021-02-02 13:27             ` Ben Greear
2021-02-02 13:57               ` Sven Eckelmann
2021-02-07 16:50                 ` Ben Greear
2021-02-07 17:13                   ` Sven Eckelmann
2021-02-07 17:42                     ` Ben Greear
2021-02-08 20:32                       ` Sven Eckelmann
2021-02-08 20:50                         ` 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=2354947.QRssEMCmQP@ripper \
    --to=sven@narfation.org \
    --cc=ath10k@lists.infradead.org \
    --cc=greearb@candelatech.com \
    --cc=s.gottschall@dd-wrt.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;
as well as URLs for NNTP newsgroup(s).