From: Ben Greear <greearb@candelatech.com>
To: Ethan Sommer <sommere@gac.edu>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] RFC: [PATCH] bridge vlan integration
Date: Mon, 11 Sep 2006 12:14:23 -0700 [thread overview]
Message-ID: <4505B58F.8000905@candelatech.com> (raw)
In-Reply-To: <4505B312.4030606@gac.edu>
Ethan Sommer wrote:
> Have you tested this in a real world scenario?
>
> I attempted to use a linux bridge to bridge a few vlans and found that
> it didn't work as expected. At first I thought it was a performance
> problem relating to the linux bridge code because it was dropping
> packets, but I believe the problem is inherent in using a bridge in a
> vlan environment.
>
> The problem lies in the fact that the switch connected to the bridge
> (which has the vlans tagged) gets confused as to which port that
> particular mac address is out of. Take the following scenario: (based on
> my understanding of how things should work)
Cisco switches have this bug, though it can be worked around on some
switches. The Netgear switches I've used do not have any problem with
the same MAC on different vlans.
Either way, you can change the MAC of the Linux VLAN device using the
standard ifconfig or ip tool commands.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2006-09-11 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 17:49 [Bridge] RFC: [PATCH] bridge vlan integration David Kimdon
2006-09-11 17:57 ` David Kimdon
2006-09-11 18:55 ` Andy Gospodarek
2006-09-11 19:11 ` Ben Greear
2006-09-11 19:26 ` Andy Gospodarek
2006-09-11 19:59 ` David Kimdon
2006-09-11 19:53 ` David Kimdon
2006-09-11 19:03 ` Ethan Sommer
2006-09-11 19:14 ` Ben Greear [this message]
2006-09-11 22:04 ` Benny Amorsen
-- strict thread matches above, loose matches on Subject: below --
2006-09-12 20:46 Simon Barber
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=4505B58F.8000905@candelatech.com \
--to=greearb@candelatech.com \
--cc=bridge@lists.osdl.org \
--cc=sommere@gac.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.