netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	Stephen Hemminger <shemminger@vyatta.com>,
	Patrick McHardy <kaber@trash.net>,
	netdev@vger.kernel.org
Subject: Re: Vlan interface nuisance
Date: Mon, 02 Mar 2009 20:06:26 +0100	[thread overview]
Message-ID: <49AC2E32.2020403@gmail.com> (raw)
In-Reply-To: <49AC2BD1.4070209@candelatech.com>

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.

Jarek P.

  reply	other threads:[~2009-03-02 19:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02  4:47 Vlan interface nuisance Stephen Hemminger
2009-03-02  4:57 ` David Miller
2009-03-02  5:05   ` Stephen Hemminger
2009-03-02  5:28     ` David Miller
2009-03-02  9:44       ` Patrick McHardy
2009-03-02  6:50     ` Herbert Xu
2009-03-02  7:15       ` Stephen Hemminger
2009-03-02  7:39         ` Herbert Xu
2009-03-02  9:45           ` Patrick McHardy
2009-03-02  9:57             ` David Miller
2009-03-02 17:20 ` Lennart Sorensen
2009-03-02 18:51   ` Jarek Poplawski
2009-03-02 18:56     ` Ben Greear
2009-03-02 19:06       ` Jarek Poplawski [this message]
2009-03-02 19:23         ` Denys Fedoryschenko
2009-03-02 20:24           ` Jarek Poplawski
2009-03-02 21:52         ` Patrick McHardy
2009-03-02 19:36     ` Lennart Sorensen
2009-03-02 20:07       ` Jarek Poplawski
2009-03-02 21:49     ` Patrick McHardy
2009-03-02 21:51       ` Stephen Hemminger
2009-03-02 21:54         ` Patrick McHardy
2009-03-02 22:30       ` Jarek Poplawski
2009-03-02 23:35         ` Patrick McHardy
2009-03-03  6:41           ` Jarek Poplawski
2009-03-03  6:53             ` Ben Greear

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49AC2E32.2020403@gmail.com \
    --to=jarkao2@gmail.com \
    --cc=greearb@candelatech.com \
    --cc=kaber@trash.net \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).