All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evan Bigall <evan.bigall@scalent.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Problem with VLANs on tg3 NICs
Date: Thu, 18 Jan 2007 19:30:07 -0500	[thread overview]
Message-ID: <45B0110F.5010904@scalent.com> (raw)
In-Reply-To: <8A87A9A84C201449A0C56B728ACF491E04F1B6@liverpoolst.ad.cl.cam.ac.uk>


>I'm still a bit confused as to how the standard linux bridge can work
>with VLAN trunks. With a 'real' Ethernet switch you have to enable which
>VLANs you want to appear on a port. I'm not aware of the Linux bridge
>having such functionality -- I thought you had to set up a separate
>bridge for each VLAN then mux/demux them at the physical/virtual NICs.
>
>  
>
 I'm not expecting it to deliver packets based on vlan membership, I'm just expecting the normal bridging behavior, but leaving the VLAN tags intact.  This seems to work fine for the e1000 and bnx2 drivers.  I'm just speculating but my guess is that the tg3 driver is stripping the tag before it even hits the bridge.

Evan

  reply	other threads:[~2007-01-19  0:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 19:33 Problem with VLANs on tg3 NICs Evan Bigall
2007-01-18 20:37 ` Ian Pratt
2007-01-18 21:46   ` Evan Bigall
2007-01-18 22:35     ` Ian Pratt
2007-01-19  0:30       ` Evan Bigall [this message]
2007-01-19  6:04       ` Nate Carlson
2007-01-19  7:52         ` Ian Pratt
2007-01-19 13:09           ` Evan Bigall
2007-01-19 14:14             ` Ian Pratt
2007-01-19 14:17               ` Christopher G. Stach II

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=45B0110F.5010904@scalent.com \
    --to=evan.bigall@scalent.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.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 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.