From owner-freebsd-net@FreeBSD.ORG Wed Dec 14 07:10:24 2005 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 3FD1F16A420 for ; Wed, 14 Dec 2005 07:10:24 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received: from dbmail-mx1.orcon.net.nz (loadbalancer1.orcon.net.nz [219.88.242.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CCD043D4C for ; Wed, 14 Dec 2005 07:10:23 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received-SPF: none Received: from heff.fud.org.nz (60-234-149-201.bitstream.orcon.net.nz [60.234.149.201]) by dbmail-mx1.orcon.net.nz (8.13.2/8.13.2/Debian-1) with ESMTP id jBE7B2Rg012671; Wed, 14 Dec 2005 20:11:02 +1300 Received: by heff.fud.org.nz (Postfix, from userid 1001) id 27B0328432; Wed, 14 Dec 2005 20:10:20 +1300 (NZDT) Date: Wed, 14 Dec 2005 20:10:20 +1300 From: Andrew Thompson To: Dave Raven Message-ID: <20051214071020.GC5248@heff.fud.org.nz> References: <20051214054114.058C243D60@mx1.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051214054114.058C243D60@mx1.FreeBSD.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on dbmail-mx1.orcon.net.nz X-Virus-Status: Clean Cc: freebsd-net@freebsd.org Subject: Re: Bridging 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, 14 Dec 2005 07:10:24 -0000 On Wed, Dec 14, 2005 at 07:41:07AM +0200, Dave Raven wrote: > Hi all, > I've done some research on bridging vlans and can't get it right > with FreeBSD bridge. What I want to do is bridge an undefined number of > vlans through a BSD machine. For example. Vlan 10 from em0 out em1. > > Now I can't create each vlan and bridge those, because you can't have a > vlan10 bound to em0 and to em1, if you create different ones and bridge them > the packet comes in on the right vlan but leaves tagged for the wrong one. > Well actually you can. Dont be fooled by the interface name, vlan10 doesnt have to have the tag of 10. A nice way to do it is use the vlan automatic creation, create the interfaces em0.1, em0.2, em0.3, [...] em1.1, em1.2, em1.3, [...] and the tag and parent will get set up for you. ifconfig em0.1 create ifconfig em0.2 create ifconfig em0.3 create and so on. cheers, Andrew