netdev - Re: Vlan interface nuisance

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 02 Mar 2009 22:49:18 +0100
From:	Patrick McHardy <kaber@...sh.net>
To:	Jarek Poplawski <jarkao2@...il.com>
CC:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	Stephen Hemminger <shemminger@...tta.com>,
	netdev@...r.kernel.org
Subject: Re: Vlan interface nuisance

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?

The binding is displayed when listing interfaces. This hole
argument is silly, if you want a particular name, just specify
it. The current naming schemes are entirely based on information
that you have to specify anyways.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html