From mboxrd@z Thu Jan 1 00:00:00 1970 From: Evan Bigall Subject: Re: Problem with VLANs on tg3 NICs Date: Thu, 18 Jan 2007 19:30:07 -0500 Message-ID: <45B0110F.5010904@scalent.com> References: <45AFCB74.4030909@scalent.com> <8A87A9A84C201449A0C56B728ACF491E04F1AA@liverpoolst.ad.cl.cam.ac.uk> <45AFEAC8.7050904@scalent.com> <8A87A9A84C201449A0C56B728ACF491E04F1B6@liverpoolst.ad.cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <8A87A9A84C201449A0C56B728ACF491E04F1B6@liverpoolst.ad.cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >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