ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: ath10k@lists.infradead.org,
	Sebastian Gottschall <s.gottschall@dd-wrt.com>,
	Ben Greear <greearb@candelatech.com>
Subject: Re: EAP AP/VLAN: multicast not send to client
Date: Tue, 02 Feb 2021 09:23:31 +0100	[thread overview]
Message-ID: <6253766.kEHZKgWlQx@ripper> (raw)
In-Reply-To: <7759ef6a-2853-5c13-12d9-5cc966b10833@dd-wrt.com>


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

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.

> the only option for you is using the CT firmware by candelatech, which 
> does not suffer from this issue.

Thanks for the interesting hint - but there is a twist :)

I've initially tried ath10k-ct with the candelatech firmware. 
5.4.93+2021-01-11-9fe1df7d-1 with 10.4b-ct-4019-fW-13-5ae337bb1 to be more 
precise. And later also switched to the ath10k backport from 5.8.18(-1-5).
Sorry for forgetting to mention such details in the first mail.

And I've just noticed that I was always testing with the ath10k-ct firmware 
(which is the default in OpenWrt but never with the official one from Kalle's 
ath10k-firmware tree. So I've just switched to QCA4019 hw1.0 10.4-3.6-00140 
from the official tree and the problem went away. 

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.

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  8:24 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 [this message]
2021-02-02  8:58     ` Sebastian Gottschall
2021-02-02  9:06       ` Sven Eckelmann
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=6253766.kEHZKgWlQx@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).