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]

Message-ID: <49AC5534.2090102@trash.net>
Date:	Mon, 02 Mar 2009 22:52:52 +0100
From:	Patrick McHardy <kaber@...sh.net>
To:	Jarek Poplawski <jarkao2@...il.com>
CC:	Ben Greear <greearb@...delatech.com>,
	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	Stephen Hemminger <shemminger@...tta.com>,
	netdev@...r.kernel.org
Subject: Re: Vlan interface nuisance

Jarek Poplawski wrote:
> Ben Greear wrote, On 03/02/2009 07:56 PM:
> 
>> 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...
> 
> To make it clear: I don't say vlan0 is better; but IMHO it doesn't
> have to be silly or nothing useful either.

Admittedly, this part of the rtnl_link interface could be improved.
The names are allocated centrally when unspecified, which imposes
this fixed naming scheme. A simple callback to choose a better
name than just incrementally counting up interfaces types would
allow to at least choose a default name of ethX.xyz or something
similar. I refuse to introduce the selectable naming schemes to
this interface though, this can easily be done in userspace.


--
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