From: Stephen Hemminger <shemminger@linux-foundation.org>
To: krunal patel <krunal.raj@gmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Bridge between switch and router + VLAN issue
Date: Wed, 6 Oct 2010 15:17:48 -0700 [thread overview]
Message-ID: <20101006151748.603b0636@nehalam> (raw)
In-Reply-To: <AANLkTi=Ze5M=So8kAzM_SDBqjkpFrMw_NhxvymXjNmHa@mail.gmail.com>
On Tue, 5 Oct 2010 13:46:31 +0530
krunal patel <krunal.raj@gmail.com> wrote:
> Hi,
>
> There is one setup i am not able to complete.
>
> I am putting bridge between a VLAN aware switch and a router with VLAN's.
>
> All hosts are behind VLAN switch and their gateway is router.
> All works well when there are no VLANs.
>
> br0
> |--------eth0
> |--------eth1
>
> When VLAN tags are added and passed to bridge, for forwarded traffic
> it works well.
>
> Now, if i want to do transparent proxy i have to create vlan devices
> for eth0, eth1 and add them to bridge
>
> br0
> |--------eth0
> |--------eth1
> |--------eth0.2
> |--------eth1.2
>
> Problem here is, on one side of bridge router is there which gives
> same mac for different tagged and untagged traffic. So bridge only
> learns one mac. So some tagged frame entered into bridge and if we do
> transparent proxy on it. Frames generated by proxy to router goes
> untagged or with different tag.
> To do proxy and handle vlan tag i have to add vlan interfaces into
> same bridge but vlan tags are not same.
This isn't going to work because it creates a loop. eth0 sees
both tagged and untagged frames and eth0.2 sees tagged frames
In recent kernels vlan 0 is supposed to work as way to manage
untagged frames. Maybe using:
br0
|--------eth0.0
|--------eth1.0
|--------eth0.2
|--------eth1.2
--
prev parent reply other threads:[~2010-10-06 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 8:16 [Bridge] Bridge between switch and router + VLAN issue krunal patel
2010-10-05 13:17 ` Jonathan Thibault
2010-10-06 22:17 ` Stephen Hemminger [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=20101006151748.603b0636@nehalam \
--to=shemminger@linux-foundation.org \
--cc=bridge@lists.linux-foundation.org \
--cc=krunal.raj@gmail.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