From: Ross Vandegrift <ross@kallisti.us>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: bridge@lists.linux-foundation.org,
Benny Amorsen <benny+usenet@amorsen.dk>
Subject: Re: [Bridge] [PATCH] [bridge] Add split horizon
Date: Sat, 13 Jun 2009 19:04:53 -0400 [thread overview]
Message-ID: <20090613230453.GA17161@kallisti.us> (raw)
In-Reply-To: <OFA105ED6C.F40466BF-ONC12575D4.00656544-C12575D4.0065DA78@transmode.se>
On Sat, Jun 13, 2009 at 08:32:31PM +0200, Joakim Tjernlund wrote:
> Ross Vandegrift <ross@kallisti.us> wrote on 13/06/2009 18:56:40:
> >
> > On Sat, Jun 13, 2009 at 05:45:47PM +0200, Joakim Tjernlund wrote:
> > > I would really like to read up on the claim that each VLAN is also a physical port.
> > > Any pointers?
> >
> > Note that you added the VLAN tagged subinterface to the bridge. Using
> > brctl's functions, you'll be able to see the port numbers assigned to
> > each port. You'll be able to display the MACs learned on each port,
> > along with each port's ID.
>
> And ...? Sorry, but I don't see anything about VLAN==physical interface.
> I suppose the MACs learned will be different, but how does that matter?
Let me put it another way. What distinguishes eth0, eth1, and eth0.10
when you bridge them together?
Nothing - one gets untagged frames from the interface associated with
eth0. One gets untagged frames from the interface associated with
eth1. The last gets tagged frames from the interface associated with
eth0. I don't see how there's any distinction between these roles.
Each is just a source & sink for frames. Some end up using the same
cable, but who cares?
--
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
next prev parent reply other threads:[~2009-06-13 23:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 21:26 [Bridge] [PATCH] [bridge] Add split horizon Joakim Tjernlund
2009-06-12 23:58 ` Benny Amorsen
2009-06-13 15:03 ` Joakim Tjernlund
2009-06-13 15:12 ` Benny Amorsen
2009-06-13 15:45 ` Joakim Tjernlund
2009-06-13 16:56 ` Ross Vandegrift
2009-06-13 18:32 ` Joakim Tjernlund
2009-06-13 23:04 ` Ross Vandegrift [this message]
2009-06-14 8:44 ` Joakim Tjernlund
2009-06-13 16:57 ` Benny Amorsen
2009-06-13 17:06 ` Benny Amorsen
2009-06-13 18:37 ` Joakim Tjernlund
2009-06-13 18:51 ` Benny Amorsen
2009-06-13 15:57 ` richardvoigt
2009-06-13 16:30 ` Joakim Tjernlund
2009-06-14 2:18 ` richardvoigt
2009-06-14 2:36 ` richardvoigt
2009-06-13 4:39 ` richardvoigt
2009-06-13 13:07 ` Jonathan Thibault
2009-06-13 16: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=20090613230453.GA17161@kallisti.us \
--to=ross@kallisti.us \
--cc=benny+usenet@amorsen.dk \
--cc=bridge@lists.linux-foundation.org \
--cc=joakim.tjernlund@transmode.se \
/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