From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Richard Weinberger Date: Mon, 01 Oct 2018 20:16:22 +0200 Message-ID: <3581745.3NPUBHfd8z@blindfold> In-Reply-To: <9331d9d8-fb4b-36f3-9484-fc80f579e617@gmail.com> References: <1420505776-26827-1-git-send-email-bernhard.thaler@wvnet.at> <9331d9d8-fb4b-36f3-9484-fc80f579e617@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [Bridge] [PATCH 1/1] bridge: remove BR_GROUPFWD_RESTRICTED for arbitrary forwarding of reserved addresses List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Florian Fainelli Cc: David Gstir , Richard Weinberger , netdev@vger.kernel.org, bridge@lists.linux-foundation.org, bernhard.thaler@wvnet.at, "David S. Miller" Florian, Am Montag, 1. Oktober 2018, 18:24:25 CEST schrieb Florian Fainelli: > If all you are doing is forwarding anything, one thing I experimented > with before is the following: > > # tc qdisc add dev eth1 handle ffff: ingress > # tc qdisc add dev eth3 handle ffff: ingress > # tc filter add dev eth3 parent ffff: u32 \ > > match u32 0 0 \ > > action mirred egress redirect dev eth1 > # tc filter add dev eth1 parent ffff: u32 \ > > match u32 0 0 \ > > action mirred egress redirect dev eth3 > # ifconfig eth3 promisc > # ifconfig eth1 promisc > > and this works just fine actually, bypassing the bridge layer entirely. Yeah, mirred is a powerful knife. :-) In my case it is too low level since I utilize the netfilter functionality of the bridge layer. Thanks, //richard