From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Greear Subject: Re: Vlan interface nuisance Date: Mon, 02 Mar 2009 10:56:17 -0800 Message-ID: <49AC2BD1.4070209@candelatech.com> References: <20090301204731.40ce346a@nehalam> <20090302172057.GA23247@csclub.uwaterloo.ca> <49AC2A9C.5090303@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Lennart Sorensen , Stephen Hemminger , Patrick McHardy , netdev@vger.kernel.org To: Jarek Poplawski Return-path: Received: from mail.candelatech.com ([208.74.158.172]:45635 "EHLO ns3.lanforge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753584AbZCBS4c (ORCPT ); Mon, 2 Mar 2009 13:56:32 -0500 In-Reply-To: <49AC2A9C.5090303@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: Jarek Poplawski wrote: > Lennart Sorensen wrote, On 03/02/2009 06:20 PM: > >> On Sun, Mar 01, 2009 at 08:47:31PM -0800, Stephen Hemminger wrote: >>> Why is interface created through netlink named 'vlan0' and >>> interface created through old vconfig called 'ethX.YY'. >>> Seems like the interface should be consistent. >> That does seem silly. >> >> ethX.YYYY told you which physical interface and which vlan number it was. >> >> vlan0 tells you nothing useful. > > > Even if you have only one ethX? Yes...the old way would tell you the vlan-id regardless of how many NICs you have, which is useful information for anyone actually trying to configure two boxes to talk to each other, or (god forbid), debug someone else's config. It's true you can specify the vlan-name on creation using 'ip', which is what I do, so I'm not going to argue Stephen's change either way..but I do like device names that give more info... Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com