From owner-freebsd-net@FreeBSD.ORG Wed Jan 18 22:17:11 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E54E616A41F; Wed, 18 Jan 2006 22:17:11 +0000 (GMT) (envelope-from dave@raven.za.net) Received: from elektra.opteqint.net (elektra.opteqint.net [209.25.178.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26B4743D46; Wed, 18 Jan 2006 22:17:10 +0000 (GMT) (envelope-from dave@raven.za.net) Received: from [165.165.205.92] (helo=LUCY) by elektra.opteqint.net with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.52 (FreeBSD)) id 1EzLZo-0002i2-TX; Wed, 18 Jan 2006 14:14:50 -0800 From: "Dave Raven" To: "'Doug Ambrisko'" Date: Thu, 19 Jan 2006 00:16:50 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <200601182004.k0IK4OV8071638@ambrisko.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 thread-index: AcYcag75HMpitKKaTrCMWr3osZV3WQAEr6AA X-Spam-Score: -101.4 (---------------------------------------------------) X-Spam-Report: Spam detection software, running on the system "elektra.opteqint.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: 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 Content analysis details: (-101.4 points, 4.5 required) pts rule name description ---- ---------------------- -------------------------------------------------- -100 USER_IN_WHITELIST From: address is in the user's white-list -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.1 TW_FX BODY: Odd Letter Triples with FX Message-Id: <20060118221710.26B4743D46@mx1.FreeBSD.org> Cc: freebsd-net@freebsd.org Subject: RE: em driver + VLAN's X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2006 22:17:12 -0000 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.