From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "open list:BROADCOM BRCM80211 IEEE802.11n WIRELESS DRIVER"
<brcm80211-dev-list.pdl@broadcom.com>,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Network Development <netdev@vger.kernel.org>,
Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
bridge@lists.linux-foundation.org,
linux-wireless@vger.kernel.org,
Hante Meuleman <hante.meuleman@broadcom.com>,
Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>,
Wright Feng <wright.feng@cypress.com>,
Felix Fietkau <nbd@nbd.name>,
brcm80211-dev-list@cypress.com,
Franky Lin <franky.lin@broadcom.com>
Subject: Re: [Bridge] Problem with bridge (mcast-to-ucast + hairpin) and Broadcom's 802.11f in their FullMAC fw
Date: Mon, 12 Mar 2018 12:48:15 +0100 [thread overview]
Message-ID: <20180312114815.GN2470@otheros> (raw)
In-Reply-To: <20180312110856.GL2470@otheros>
On Mon, Mar 12, 2018 at 12:08:56PM +0100, Linus Lüssing wrote:
> On Tue, Feb 27, 2018 at 11:08:20AM +0100, Rafał Miłecki wrote:
> > I've problem when using OpenWrt/LEDE on a home router with Broadcom's
> > FullMAC WiFi chipset.
>
> Hi Rafał,
>
> Thanks for reporting this issue!
>
> > Can you see any solution for this problem? Is that an option to stop
> > multicast-to-unicast from touching 802.11f packets? Some other ideas?
> > Obviously I can't modify Broadcom's firmware and drop that obsoleted
> > standard.
>
> Just to avoid some potential confusion: This is more an issue of
> hairpinning than it is an issue of multicast-to-unicast per se,
> right?
>
> That is, if you set this to 0 manually:
> /sys/class/net/<ap-iface>/brport/multicast_to_unicast
> Then the issue still occurs, right?
Btw., if in OpenWRT/LEDE you set 'option multicast_to_unicast 0'
in /etc/config/network for the bridge (and not bridge port)
then netifd should refrain from setting the bridge hairpinning and
AP isolation on wireless devices, too, if I remember correctly.
Can you confirm that the issue disappears for you then?
next prev parent reply other threads:[~2018-03-12 11:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 10:08 [Bridge] Problem with bridge (mcast-to-ucast + hairpin) and Broadcom's 802.11f in their FullMAC fw Rafał Miłecki
2018-02-27 10:14 ` Rafał Miłecki
2018-02-28 11:31 ` Arend van Spriel
2018-03-12 9:49 ` Rafał Miłecki
2018-02-27 17:05 ` Stephen Hemminger
2018-03-12 9:46 ` Rafał Miłecki
2018-03-12 11:40 ` Linus Lüssing
2018-03-12 11:08 ` Linus Lüssing
2018-03-12 11:48 ` Linus Lüssing [this message]
2018-03-12 21:52 ` Rafał Miłecki
2018-03-12 21:49 ` Rafał Miłecki
2018-03-12 22:42 ` Rafał Miłecki
2018-03-12 23:01 ` Stephen Hemminger
2018-03-13 6:23 ` Rafał Miłecki
2018-03-13 7:17 ` Felix Fietkau
2018-03-13 7:20 ` Felix Fietkau
2018-03-13 9:18 ` Arend van Spriel
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=20180312114815.GN2470@otheros \
--to=linus.luessing@c0d3.blue \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=bridge@lists.linux-foundation.org \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pieter-paul.giesberts@broadcom.com \
--cc=wright.feng@cypress.com \
--cc=zajec5@gmail.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