Ethernet Bridge development
 help / color / mirror / Atom feed
From: Zoilo Gomez <zoilo@xs4all.nl>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] using bridges to connect vlans and untagged data
Date: Mon, 22 Feb 2010 00:24:06 +0100	[thread overview]
Message-ID: <4B81C096.9090106@xs4all.nl> (raw)

I have the following interfaces:
=> vlan22 and vlan2 on eth0
=> vlan23 and untagged traffic on eth1

The essence is that:
=> vlan22@eth0 and vlan23@eth1 need to be bridged, and
=> vlan2@eth0 and the untagged traffic on eth1 need to be bridged.

Software:
=> Gentoo 10.1
=> linux 2.6.32.7 vanilla
=> vconfig 1.9
=> bridge-utils 1.4

===== My implementation:

vconfig add eth0 2
vconfig add eth0 22

vconfig add eth1 23

brctl addbr br0
brctl addif br0 vlan2
brctl addif br0 eth1

brctl addbr br1
brctl addif br1 vlan22
brctl addif br1 vlan23

ebtables -P FORWARD DROP

ebtables -A FORWARD -j ACCEPT -p ! 802_1Q -i eth1 -o vlan2
ebtables -A FORWARD -j ACCEPT -p ! 802_1Q -i vlan2 -o eth1

ebtables -A FORWARD -j ACCEPT -i vlan23 -o vlan22
ebtables -A FORWARD -j ACCEPT -i vlan22 -o vlan23

Unfortunately, the vlan23 interface stops receiving data as soon as eth1 
is connected to br0. It seems that the bridge sucks all data from eth1, 
effectively disabling vlan23; why is this?

How can I get access to the untagged data on eth1, while simultaneously 
using vlan23@eth1 ?

Or should I use a different approach?

Z.


             reply	other threads:[~2010-02-21 23:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-21 23:24 Zoilo Gomez [this message]
2010-02-22  0:47 ` [Bridge] using bridges to connect vlans and untagged data richardvoigt
2010-02-22  1:12   ` Zoilo Gomez
2010-02-22 16:04   ` [Bridge] Slow receive side on bridge james.card

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=4B81C096.9090106@xs4all.nl \
    --to=zoilo@xs4all.nl \
    --cc=bridge@lists.linux-foundation.org \
    /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