From owner-freebsd-arch@FreeBSD.ORG  Mon Jul 10 08:52:30 2006
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
X-Original-To: freebsd-arch@freebsd.org
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6E3C716A4DD
	for <freebsd-arch@freebsd.org>; Mon, 10 Jul 2006 08:52:30 +0000 (UTC)
	(envelope-from andre@freebsd.org)
Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B37EE43D45
	for <freebsd-arch@freebsd.org>; Mon, 10 Jul 2006 08:52:29 +0000 (GMT)
	(envelope-from andre@freebsd.org)
Received: (qmail 11116 invoked from network); 10 Jul 2006 08:48:20 -0000
Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2])
	(envelope-sender <andre@freebsd.org>)
	by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP
	for <sam@errno.com>; 10 Jul 2006 08:48:20 -0000
Message-ID: <44B21551.5050002@freebsd.org>
Date: Mon, 10 Jul 2006 10:52:33 +0200
From: Andre Oppermann <andre@freebsd.org>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Sam Leffler <sam@errno.com>
References: <44B15511.206@errno.com>
In-Reply-To: <44B15511.206@errno.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-arch@freebsd.org
Subject: Re: vlans and cloning
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2006 08:52:30 -0000

Sam Leffler wrote:
> I committed the revised netif cloning api so you can now specify
> parameters when cloning.  I also modified the vlan code to use this
> mechanism so doing something like:
> 
> ifconfig vlan create vlan 1 vlandev em0
> 
> causes a single request to clone a vlan together with the tag+parent
> device parameters (i.e. and no subsequent SIOCSETVLAN request).
> 
> Given the above do we still need to support setting vlan tag+device
> separately or can we just require everything be specified when doing the
> clone operation?  This would change the user api but otherwise I can see
> no reason for continuing to support the old mechanism where you do:
> 
> ifconfig vlan create
> ifconfig vlan0 vlan 1 vlandev em0

/me wants to do:

"ifconfig em0.1 inet 192.168.2.2/24"

Even simpler.  And yes, this works already but only if if_vlan.ko
was loaded before or compiled into the kernel.  It doesn't do auto-
load.

-- 
Andre