From: Ben Greear <greearb@candelatech.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] VLAN translation + PVST+
Date: Thu, 18 May 2006 08:30:59 -0700 [thread overview]
Message-ID: <446C9333.90608@candelatech.com> (raw)
In-Reply-To: <20060518143959.GB21325@tuxdriver.com>
John W. Linville wrote:
> On Wed, May 17, 2006 at 06:09:37PM -0700, Ian Schwimmer wrote:
>
>>Hello, I am creating a configuration where a Redhat server running
>>bridge-tools 0.9.5 will be bridging between different VLANs on the same
>>physical interface (for example: a bridge consisting of eth1.100 and
>>eth1.110). This physical interface is being connected to modern Cisco
>>switches running PVST+.
>
>
> I'm curious as to how this is useful? What is the point of having
> two VLANs on the same segment if you are just going to bridge them
> together? Is this useful for something beyond some sort of migration?
You can add a bridge group for 10 vlans, and route them to another bridge
group of 10 VLANs. You can also enforce firewall rules on particular
VLANs (ie, could put each customer on individual VLAN, and backhaul them
all to one linux box to bridge/firewall/bill/etc them...)
Ben
>
> Curious,
>
> John
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/bridge
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2006-05-18 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 1:09 [Bridge] VLAN translation + PVST+ Ian Schwimmer
2006-05-18 6:40 ` Gergely Madarasz
2006-05-18 14:40 ` John W. Linville
2006-05-18 15:02 ` Ian Schwimmer
2006-05-18 15:35 ` Vivek Kuncham
2006-05-18 17:45 ` [Bridge] getting off list Stephen Hemminger
2006-05-18 15:30 ` Ben Greear [this message]
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=446C9333.90608@candelatech.com \
--to=greearb@candelatech.com \
--cc=bridge@lists.osdl.org \
--cc=linville@tuxdriver.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