From owner-freebsd-current@FreeBSD.ORG Sat Nov 13 18:21:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C49D16A4CE; Sat, 13 Nov 2004 18:21:09 +0000 (GMT) Received: from mail.netroad.ru (mail.netroad.ru [213.24.172.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id A96FD43D41; Sat, 13 Nov 2004 18:21:08 +0000 (GMT) (envelope-from devel@proxy.netroad.ru) Received: by mail.netroad.ru (Postfix, from userid 65534) id 108261484ED; Sat, 13 Nov 2004 21:19:29 +0300 (MSK) Received: from mail.netroad.ru (localhost [127.0.0.1]) by mail.netroad.ru (Postfix) with ESMTP id D8D551484EB; Sat, 13 Nov 2004 21:19:28 +0300 (MSK) Received: from proxy.netroad.ru (proxy.netroad.ru [213.24.172.2]) by mail.netroad.ru (Postfix) with ESMTP id B43E5148431; Sat, 13 Nov 2004 21:19:28 +0300 (MSK) Received: by proxy.netroad.ru (Postfix, from userid 999) id D89E3256217; Sat, 13 Nov 2004 21:21:03 +0300 (MSK) Date: Sat, 13 Nov 2004 21:21:03 +0300 From: "Lenar D. Tukhvatullin" To: Mike Tancsa Message-ID: <20041113182103.GA43222@proxy.netroad.ru> Mail-Followup-To: Mike Tancsa , Robert Watson , freebsd-current@freebsd.org References: <6.1.2.0.0.20041113113942.10365d88@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.1.2.0.0.20041113113942.10365d88@64.7.153.2> User-Agent: Mutt/1.5.5.1i X-AntiVirus: ClamAV at mail.netroad.ru cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: Yes it did the trick - Re[3]: Re[2]: em0, VLAN and bpf(?) trouble w/RELENG_5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Nov 2004 18:21:09 -0000 On Sat, Nov 13, 2004 at 12:05:30PM -0500, Mike Tancsa wrote: > I am able to create and use VLANS and putting the nic or the vlan interface > into promisc mode does not break the passing of packets. And what about bridging? Can you test bridging beetween vlan and another physical interface, for example: em1 - another physical interface, not connected to wire 172.16.0.0/24 - network in vlan (tag 100) 172.16.0.1 - remote host in this vlan # ifconfig em0 up # ifconfig vlan0 create # ifconfig vlan0 vlan 100 vlandev em0 # ifconfig vlan0 up # ifconfig em1 172.16.0.2 netmask 255.255.255.0 # kldload bridge # sysctl net.link.ether.bridge.config="vlan0 em1" # sysctl net.link.ether.bridge.enable=1 Pinging remote host: $ ping 172.16.0.1 -- Lenar D. Tukhvatullin