From owner-freebsd-net@FreeBSD.ORG Thu Jan 12 10:16:08 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 39B4216A425 for ; Thu, 12 Jan 2006 10:16:08 +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 AD58743D48 for ; Thu, 12 Jan 2006 10:16:07 +0000 (GMT) (envelope-from thompsa@freebsd.org) 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 k0CAG5Zq008215; Thu, 12 Jan 2006 23:16:05 +1300 Received: by heff.fud.org.nz (Postfix, from userid 1001) id 5119F2843B; Thu, 12 Jan 2006 23:16:16 +1300 (NZDT) Date: Thu, 12 Jan 2006 23:16:16 +1300 From: Andrew Thompson To: Marcin Jessa Message-ID: <20060112101616.GG2332@heff.fud.org.nz> References: <170970070.20060112144241@kr.ru> <20060112105808.0ec94f40.lists@yazzy.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060112105808.0ec94f40.lists@yazzy.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: Automatic VLANS 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: Thu, 12 Jan 2006 10:16:08 -0000 On Thu, Jan 12, 2006 at 10:58:08AM +0100, Marcin Jessa wrote: > On Thu, 12 Jan 2006 14:42:41 +0700 > Vitaliy Ovsyannikov wrote: > > Does Automatic VLANS works? > > It is was described in > > http://people.freebsd.org/~andre/FreeBSD-5.3-Networking.pdf > > > > # ifconfig em0.1 inet 10.90.90.200/24 > > ifconfig: interface em0.1 does not exist > > Run > ifconfig vlan0 create > ifconfig vlan0 destroy > to create or remove vlan0 interface. > > You can also rename your vlan0 interface so it will be more descriptive > with ifconfig vlan0 name vlan_to_somewhere > > If you want it to be renamed at boot something like this should work: > ifconfig_vlan0="name vlan_to_somewhere inet 10.90.90.200 vlan 123 > vlandev em0" While what you have posted is correct, the automatic vlans the original poster referred to do exist. 'ifconfig em0.1 create' will create a vlan and also set the parent to em0 and tag as 1. Andrew