Ethernet Bridge development
 help / color / mirror / Atom feed
From: Ross Vandegrift <ross@kallisti.us>
To: "richardvoigt@gmail.com" <richardvoigt@gmail.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
	bridge@lists.linux-foundation.org,
	Joakim Tjernlund <joakim.tjernlund@transmode.se>
Subject: Re: [Bridge] brigde does not relay BPDU multicast pkgs
Date: Tue, 12 May 2009 09:52:33 -0400	[thread overview]
Message-ID: <20090512135233.GD20371@kallisti.us> (raw)
In-Reply-To: <2e59e6970905120644t71674e2cl8e565912f17e6c79@mail.gmail.com>

On Tue, May 12, 2009 at 08:44:44AM -0500, richardvoigt@gmail.com wrote:
> > If you're implementing that, it should only forward the STP address.
> >
> > 802.1X and LACP will be very suprised (and very broken) when their
> > PDUs start being forwarded to entities on other bridges...
> 
> They break when there's a simple hub on the network?

Correct.  Both technologies depend on being run over point-to-point
ethernet links - they are communications between entities that manage
individual bridge port roles.

-- 
Ross Vandegrift
ross@kallisti.us

"If the fight gets hot, the songs get hotter.  If the going gets tough,
the songs get tougher."
	--Woody Guthrie

  reply	other threads:[~2009-05-12 13:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08  8:33 [Bridge] brigde does not relay BPDU multicast pkgs Joakim Tjernlund
2009-05-08 12:14 ` Ross Vandegrift
2009-05-08 12:27   ` Joakim Tjernlund
2009-05-08 16:02 ` Stephen Hemminger
2009-05-08 16:43   ` richardvoigt
2009-05-10 17:47   ` Joakim Tjernlund
     [not found]   ` <OFD8A6DCB5.C299BC0C-ONC12575B2.006169DD-C12575B2.0061B705@LocalDomain>
2009-05-12  9:43     ` Joakim Tjernlund
2009-05-12 13:06       ` Ross Vandegrift
2009-05-12 13:44         ` richardvoigt
2009-05-12 13:52           ` Ross Vandegrift [this message]
2009-05-12 14:03         ` Joakim Tjernlund

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=20090512135233.GD20371@kallisti.us \
    --to=ross@kallisti.us \
    --cc=bridge@lists.linux-foundation.org \
    --cc=joakim.tjernlund@transmode.se \
    --cc=richardvoigt@gmail.com \
    --cc=shemminger@vyatta.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