From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Erik Schweigert <ejschweigert@gmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] VLAN traffic through an Ethernet Bridge
Date: Wed, 20 Oct 2010 08:38:07 -0700 [thread overview]
Message-ID: <20101020083807.449c9ae5@nehalam> (raw)
In-Reply-To: <AANLkTinBfvrkb6Oe832h8QFO8B7i4bzdYo9YzsimCrY+@mail.gmail.com>
On Tue, 19 Oct 2010 10:46:38 -0700
Erik Schweigert <ejschweigert@gmail.com> wrote:
> Hello all,
>
> I have configured a transparent ethernet bridge containing two network
> interfaces: eth0, eth1 in br0. IP forwarding is enabled i.e. cat
> /proc/sys/net/ipv4/ip_forward = 1.
This is irrelevant for bridging.
> All traffic destined through my Linux machine has the 802.1Q tag
> (VLAN). However, only ARP with the VLAN tags passes through the
> machine correctly (100% of the time) and broadcast and multicast
> appears to work. It 'seems' IP layer and above is being dropped if it
> is unicast, or intermittently works ( +/- 1 of 10 ICMP passes
> through).
>
> All non-VLAN'd traffic passes through my machine flawlessly.
>
> arptables, ebtables, and IPtables are all flushed, so there is no
> possibility of any traffic being blocked.
>
> Is there a caveat with ethernet bridging that does not permit VLAN'd traffic?
>
> Any help or suggestions is greatly appreciated!
>
> Thanks,
>
> Erik
Missing bits:
1. Kernel version?
2. Did you configure vlans on eth0 and eth1?
3. Is it an MTU issue? do small packets get through but
not largere ones.
4. What is overall configuration of bridging and ethernets?
Did you assign IP address to bridge or the ethernet devices.
prev parent reply other threads:[~2010-10-20 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 17:46 [Bridge] VLAN traffic through an Ethernet Bridge Erik Schweigert
2010-10-20 15:38 ` 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=20101020083807.449c9ae5@nehalam \
--to=shemminger@linux-foundation.org \
--cc=bridge@lists.linux-foundation.org \
--cc=ejschweigert@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