Ethernet Bridge development
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Ido Schimmel <idosch@idosch.org>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: David Gstir <david@sigma-star.at>,
	Florian Fainelli <f.fainelli@gmail.com>,
	netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
	bernhard.thaler@wvnet.at, "David S. Miller" <davem@davemloft.net>
Subject: Re: [Bridge] [PATCH 1/1] bridge: remove BR_GROUPFWD_RESTRICTED for arbitrary forwarding of reserved addresses
Date: Mon, 01 Oct 2018 20:54:08 +0200	[thread overview]
Message-ID: <2473404.DTJdS9eVm5@blindfold> (raw)
In-Reply-To: <20181001184821.GA29148@splinter>

Am Montag, 1. Oktober 2018, 20:48:21 CEST schrieb Ido Schimmel:
> > This is my plan b, having a u32 classifier that transports STP directly
> > to the other interface.
> > But IMHO this all is a bit hacky and a "forward anything" bridge mode
> > sounds more natural to me.
> 
> But "forwarding STP and PAUSE if the number of slaves is restricted to
> 2" is a hack. The Linux bridge (like other networking equipment) needs
> to conform to standards and to the best of my knowledge what you're
> requesting is explicitly forbidden by IEEE standards.
> 
> Also, if what you need is "forward anything", then Florian's suggestion
> should work for you.

Agreed, both variants are hacks. Depending on the point of view one might seem
less hacky than the other. :-)

As I said, netfilter is also part of the game. Unless I miss something, netfilter
won't see any packets if tc-mirred is used.
So the only option is having a bridge and transport STP via tc-mirred
or patching the bridge code (what we do right now).
 
Thanks,
//richard




  reply	other threads:[~2018-10-01 18:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06  0:56 [Bridge] [PATCH 1/1] bridge: remove BR_GROUPFWD_RESTRICTED for arbitrary forwarding of reserved addresses Bernhard Thaler
2015-01-06  6:10 ` Stephen Hemminger
     [not found] ` <CAFLxGvzVbWvQ5YA8NS-zcESguNNvJAbE_99SdFcAjbftCXzsdQ@mail.gmail.com>
     [not found]   ` <9331d9d8-fb4b-36f3-9484-fc80f579e617@gmail.com>
2018-10-01 18:16     ` Richard Weinberger
2018-10-01 18:25       ` Ido Schimmel
2018-10-01 18:32         ` Richard Weinberger
2018-10-01 18:48           ` Ido Schimmel
2018-10-01 18:54             ` Richard Weinberger [this message]
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=2473404.DTJdS9eVm5@blindfold \
    --to=richard@nod.at \
    --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=idosch@idosch.org \
    --cc=netdev@vger.kernel.org \
    --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