From: Boris Dores <babal@via.ecp.fr>
To: Lv Zheng <lv.zheng@soliton.com.cn>
Cc: Bridge Linux <bridge@lists.linux-foundation.org>
Subject: Re: [Bridge] vlan and bond integration in bridge
Date: Thu, 8 Jan 2009 13:45:25 +0100 [thread overview]
Message-ID: <20090108124525.GV10913@via.ecp.fr> (raw)
In-Reply-To: <2E0FC4E549A74D6A836D12FCC08A3E59@lzheng>
On Thu, Jan 08, 2009 at 06:13:07PM (GMT+0800), Lv Zheng wrote:
> >+---------------------------+-----------------+
> >| br0 | br1 |
> >+------------------+--------+--------+--------+
> >| bond0 | eth2 | eth3 | eth4 |
> >+---------+--------+ | | |
> >| eth0 | eth1 | | | |
> >+---------+--------+--------+--------+--------+
> >
> > without the VLAN layer, otherwise packets will be tagged.
>
> Do you mean BPDU will also be tagged and no longer a BPDU
> on the wire?
Well, I'm not sure about BPDU packets, although I don't see why they
would be treated differently (but someone else on this list must have a
definite answer).
I was talking about regular data packets. Usually, when refering to
"port based" VLAN, we mean that the host (or the hosts) connected to
that port has no knowledge whatsoever of what a VLAN is.
If (and only if) this is what you want, then br0 should be directly
connected to the physical port (bond or eth), and not on top of a vlan
layer which will filter out untagged incoming packets, and tag outgoing
packets.
--
Boris Dorès
next prev parent reply other threads:[~2009-01-08 12:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 9:53 [Bridge] vlan and bond integration in bridge Lv Zheng
2009-01-06 17:19 ` Ben Greear
2009-01-06 21:35 ` richardvoigt
2009-01-07 1:56 ` Lv Zheng
2009-01-07 1:53 ` Lv Zheng
2009-01-07 2:07 ` Ben Greear
2009-01-08 1:47 ` Lv Zheng
2009-01-08 7:58 ` Boris Dores
2009-01-08 10:13 ` Lv Zheng
2009-01-08 12:45 ` Boris Dores [this message]
2009-01-12 4:41 ` Lv Zheng
2009-01-12 8:13 ` Simon Barber
2009-01-13 14:32 ` Benny Amorsen
2009-01-14 7:59 ` Lv Zheng
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=20090108124525.GV10913@via.ecp.fr \
--to=babal@via.ecp.fr \
--cc=bridge@lists.linux-foundation.org \
--cc=lv.zheng@soliton.com.cn \
/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