From: Ido Schimmel <idosch@idosch.org>
To: Richard Weinberger <richard@nod.at>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Richard Weinberger <richard.weinberger@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>,
bernhard.thaler@wvnet.at, "David S. Miller" <davem@davemloft.net>,
bridge@lists.linux-foundation.org, netdev@vger.kernel.org,
David Gstir <david@sigma-star.at>
Subject: Re: [PATCH 1/1] bridge: remove BR_GROUPFWD_RESTRICTED for arbitrary forwarding of reserved addresses
Date: Mon, 1 Oct 2018 21:25:26 +0300 [thread overview]
Message-ID: <20181001182526.GA28369@splinter> (raw)
In-Reply-To: <3581745.3NPUBHfd8z@blindfold>
On Mon, Oct 01, 2018 at 08:16:22PM +0200, Richard Weinberger wrote:
> 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.
You can use mirred only for the specific packets you care about and let
the rest continue to the bridge.
next prev parent reply other threads:[~2018-10-02 1:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 0:56 [PATCH 1/1] bridge: remove BR_GROUPFWD_RESTRICTED for arbitrary forwarding of reserved addresses Bernhard Thaler
2015-01-06 6:10 ` Stephen Hemminger
2018-10-01 14:28 ` Richard Weinberger
2018-10-01 16:24 ` Florian Fainelli
2018-10-01 18:16 ` Richard Weinberger
2018-10-01 18:25 ` Ido Schimmel [this message]
2018-10-01 18:32 ` Richard Weinberger
2018-10-01 18:48 ` Ido Schimmel
2018-10-01 18:54 ` Richard Weinberger
2018-10-01 19:04 ` Ido Schimmel
2018-10-01 19:10 ` Richard Weinberger
2018-10-02 14:59 ` Nikolay Aleksandrov
2018-10-02 15:56 ` Richard Weinberger
2018-10-02 16:10 ` Nikolay Aleksandrov
2018-10-02 19:30 ` Richard Weinberger
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=20181001182526.GA28369@splinter \
--to=idosch@idosch.org \
--cc=bernhard.thaler@wvnet.at \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=david@sigma-star.at \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
--cc=stephen@networkplumber.org \
/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).