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: <49ABAA97.4060103@trash.net>
Date:	Mon, 02 Mar 2009 10:44:55 +0100
From:	Patrick McHardy <kaber@...sh.net>
To:	David Miller <davem@...emloft.net>
CC:	shemminger@...tta.com, netdev@...r.kernel.org
Subject: Re: Vlan interface nuisance

David Miller wrote:
> From: Stephen Hemminger <shemminger@...tta.com>
> Date: Sun, 1 Mar 2009 21:05:41 -0800
> 
>> On Sun, 01 Mar 2009 20:57:02 -0800 (PST)
>> David Miller <davem@...emloft.net> wrote:
>>
>>> From: Stephen Hemminger <shemminger@...tta.com>
>>> Date: Sun, 1 Mar 2009 20:47:31 -0800
>>>
>>>> Why is interface created through netlink named 'vlan0' and
>>>> interface created through old vconfig called 'ethX.YY'.
>>>> Seems like the interface should be consistent.
>>> I think the netlink scheme is saner, and the idea is to
>>> transition people over to that.
>>>
>>> We can't change what vconfig uses, so what Patrick decided
>>> to do is pretty sane if you ask me.
>> This is missing:
> 
> You can just say you don't think the behavior is
> intentional.... :-/

Indeed, it was intentional not to have these IMO useless naming
schemes when you can simply supply the name of your choice when
creating the interface.

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