From owner-freebsd-questions@FreeBSD.ORG Thu Jun 18 16:41:55 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FEC4106566C for ; Thu, 18 Jun 2009 16:41:55 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id AE8B78FC21 for ; Thu, 18 Jun 2009 16:41:54 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3) with ESMTP id n5IGfd9L042420; Thu, 18 Jun 2009 18:41:39 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3/Submit) with ESMTP id n5IGfc8u042417; Thu, 18 Jun 2009 18:41:38 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Thu, 18 Jun 2009 18:41:38 +0200 (CEST) From: Wojciech Puchar To: Geoff Roberts In-Reply-To: <200906182345.43828.geoff@apro.com.au> Message-ID: References: <200906182345.43828.geoff@apro.com.au> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-questions@freebsd.org Subject: Re: Configuring VLANs - Why is IP address require on NIC connected to Trunk? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jun 2009 16:41:55 -0000 > done using ifconfig_em0_name="ext0" in rc.conf. > > I find I have to give the ext0 interface an IP address in order for routing > and packet filtering to work on the attached VLANs. You have to set up IP address to vlans, not main interface. It's the way vlan's work. Having 2 vlan's is like having 2 ethernet cards, while physically having one. switch is responsible to segregate your traffic and connect one "virtual ethernet" to right clients, and second to other clients - exactly how you configured switch.