From owner-freebsd-arch@FreeBSD.ORG  Mon Jul 10 15:25: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 0738D16A4DE;
	Mon, 10 Jul 2006 15:25:30 +0000 (UTC) (envelope-from sam@errno.com)
Received: from ebb.errno.com (ebb.errno.com [69.12.149.25])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AB97343D5F;
	Mon, 10 Jul 2006 15:25:28 +0000 (GMT) (envelope-from sam@errno.com)
Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248])
	(authenticated bits=0)
	by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k6AFPRo7087365
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 10 Jul 2006 08:25:28 -0700 (PDT) (envelope-from sam@errno.com)
Message-ID: <44B27167.8090406@errno.com>
Date: Mon, 10 Jul 2006 08:25:27 -0700
From: Sam Leffler <sam@errno.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060508)
MIME-Version: 1.0
To: Andre Oppermann <andre@freebsd.org>
References: <44B15511.206@errno.com> <44B21551.5050002@freebsd.org>
In-Reply-To: <44B21551.5050002@freebsd.org>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
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 15:25:30 -0000

Andre Oppermann wrote:
> 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"

That can still be done and is just different syntax to ifconfig.

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