From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 12 Mar 2018 12:08:56 +0100 From: Linus =?utf-8?Q?L=C3=BCssing?= Message-ID: <20180312110856.GL2470@otheros> References: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Subject: Re: [Bridge] Problem with bridge (mcast-to-ucast + hairpin) and Broadcom's 802.11f in their FullMAC fw List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= Cc: "open list:BROADCOM BRCM80211 IEEE802.11n WIRELESS DRIVER" , Arend van Spriel , Network Development , Chi-Hsien Lin , bridge@lists.linux-foundation.org, linux-wireless@vger.kernel.org, Hante Meuleman , Pieter-Paul Giesberts , Wright Feng , Felix Fietkau , brcm80211-dev-list@cypress.com, Franky Lin 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//brport/multicast_to_unicast Then the issue still occurs, right? Regards, Linus