Date: Thu, 19 Jan 2006 00:16:50 +0200 From: "Dave Raven" <dave@raven.za.net> To: "'Doug Ambrisko'" <ambrisko@ambrisko.com> Cc: freebsd-net@freebsd.org Subject: RE: em driver + VLAN's Message-ID: <20060118221710.26B4743D46@mx1.FreeBSD.org> In-Reply-To: <200601182004.k0IK4OV8071638@ambrisko.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the reply - I went down to the office to do exactly what you are suggesting and it worked fine - removed "em_enable_vlans(adapter);" Thanks all Dave -----Original Message----- From: Doug Ambrisko [mailto:ambrisko@ambrisko.com] Sent: 18 January 2006 10:04 PM To: Dave Raven Cc: 'Gleb Smirnoff'; freebsd-net@freebsd.org Subject: Re: em driver + VLAN's Dave Raven writes: | FreeBSD 4.9 - char em_driver_version[] = "1.7.16"; | | I've tried multiple bridge configurations - from bridging just em0,em1 | to bridging two vlan's attached to each card. Unfortunately I don't | have access to the box at the moment - if its still necessary I will | fetch the information tomorrow (ifconfig etc) | | To sum up its something like the following | net.inet.ether.bridge_config=em0,em1 | net.inet.ether.bridge=1 | | Or vlan0,vlan1 with: | ifconfig vlan0 create | ifconfig vlan1 create | ifconfig vlan0 vlan 100 vlandev em0 | ifconfig vlan1 vlan 100 vlandev em1 | | | If I change to using fxp it immediately works.. I think you will find you are bridging in promiscous mode and the HW VLAN stuff isn't there. You should try to bridge the vlan devices or disable the VLAN HW (driver hack). It works with the fxp0 since you are using SW VLAN so the HW part isn't grabing it. I've done the driver hack for some things I needed to do. Doug A.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060118221710.26B4743D46>