Re: [meta-networking][PATCH:V3] vlan: Add vlan recipe

From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: Paul Barker <paul@paulbarker.me.uk>, <lei.yang@windriver.com>
Cc: Openembedded Discussion <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH:V3] vlan: Add vlan recipe
Date: Thu, 27 Jun 2013 08:38:59 -0400	[thread overview]
Message-ID: <20130627123859.GA3812@windriver.com> (raw)
In-Reply-To: <CANyK_8cc7LLLDJssgeWhRHkBy4AshZsGByvjUdwJUZPeBzprgw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1993 bytes --]

[Re: [oe] [meta-networking][PATCH:V3] vlan: Add vlan recipe] On 13.06.27 (Thu 12:00) Paul Barker wrote:

> On 27 June 2013 10:51,  <lei.yang@windriver.com> wrote:
> > From: Lei Yang <lei.yang@windriver.com>
> >
> > A 802.1q vlan support program,which can be used by virt-test
> >
> > Signed-off-by: Lei Yang <lei.yang@windriver.com>
> 
> Just took a quick look at this out of interest. What's using the
> vconfig program once it's installed on the target?
> 
> vlan-1.9 was released in 2005 and there hasn't been an update since.
> The ArchWiki suggests that the modern 'ip' command can do what vconfig
> used to do (https://wiki.archlinux.org/index.php/VLAN).
> 
> If we can avoid a dependency on such legacy code that would probably
> be good. Though I may be missing something as I haven't followed all
> the discussion around this patch and I don't know your use case.

That's a good point.  Seeing something like this hasn't changed since
2005 is a little concerning, but frankly I'm not completely shocked when
I find out some piece of networking infrastructure has stabilized to the
point where it isn't undergoing much development anymore.  Particularly
if it's something not everyone uses (and sometimes even if it is:
http://comments.gmane.org/gmane.linux.network/238858).

That said, I remember vconfig coming up a bit when I was working with
the CGL workgroup and at the time we'd thought that ip was able to do
everything vconfig was doing, but we were looking at it in the more
narrow context of the requirements definition.

So I guess my question is the same, is there even a use-case for vlan
now that cannot be addressed by existing, already integrated tools?
Lei?  Your comment is specifically saying "can be used by virt-test",
does that mean that virt-test (or something else in meta-virtualization)
requires vconfig to do 802.1q testing or simply that it hasn't been
ported to use other tools (like ip)?

-- 
-Joe MacDonald.
:wq

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]