From owner-freebsd-net@FreeBSD.ORG Tue Mar 18 13:05:53 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 67D7ABE4 for ; Tue, 18 Mar 2014 13:05:53 +0000 (UTC) Received: from mail.egr.msu.edu (dauterive.egr.msu.edu [35.9.37.168]) by mx1.freebsd.org (Postfix) with ESMTP id 3CA35DB4 for ; Tue, 18 Mar 2014 13:05:52 +0000 (UTC) Received: from dauterive (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 59922293B5 for ; Tue, 18 Mar 2014 09:05:45 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by dauterive (dauterive.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1nSHxv_Q6BjB for ; Tue, 18 Mar 2014 09:05:45 -0400 (EDT) Received: from EGR authenticated sender Message-ID: <532844A9.3020100@egr.msu.edu> Date: Tue, 18 Mar 2014 09:05:45 -0400 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: vlanXXX vs ifXX.YY notation References: <20140318074246.8519@smtp.new-ukraine.org> In-Reply-To: <20140318074246.8519@smtp.new-ukraine.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Mar 2014 13:05:53 -0000 On 03/18/2014 01:42, Zeus Panchenko wrote: > hi, > > is there any advantage of using vlanXXX vs ifXX.YY notation? > > I mean > >> ifconfig em0 > vlan777: flags=8843 metric 0 mtu 1500 > ether 00:1b:b9:8b:ca:33 > ... > vlan: 777 parent interface: em0 > > vs > > em0.555: flags=8843 metric 0 mtu 1500 > ether 00:1b:b9:8b:ca:33 > ... > vlan: 555 parent interface: em0 > > - -- > Zeus V. Panchenko jid:zeus@im.ibs.dn.ua > IT Dpt., I.B.S. LLC GMT+2 (EET) It would seem to have an advantage on a bridge where you are passing a vlan through multiple interfaces since 'vlan777' cannot represent both the incoming and outgoing vlan interfaces, but em0.555 and em1.555 seem quite logical. It gives an easy way to differentiate the same vlan on more than one parent interface. Additionally the native names are shorter which often helps in status reporting utilities that truncate the name for display.