From owner-freebsd-arch@FreeBSD.ORG Mon Jul 10 16:04:47 2006 Return-Path: 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 664BB16A4DD; Mon, 10 Jul 2006 16:04:47 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 087B443D6D; Mon, 10 Jul 2006 16:04:44 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k6AG4fR4025518; Mon, 10 Jul 2006 09:04:41 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k6AG4fL9025517; Mon, 10 Jul 2006 09:04:41 -0700 Date: Mon, 10 Jul 2006 09:04:41 -0700 From: Brooks Davis To: Andre Oppermann Message-ID: <20060710160441.GB31026@odin.ac.hmc.edu> References: <44B15511.206@errno.com> <44B21551.5050002@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ftEhullJWpWg/VHq" Content-Disposition: inline In-Reply-To: <44B21551.5050002@freebsd.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 16:04:47 -0000 --ftEhullJWpWg/VHq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 10, 2006 at 10:52:33AM +0200, 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 >=20 > /me wants to do: >=20 > "ifconfig em0.1 inet 192.168.2.2/24" >=20 > 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. Unless cause ifconfig to autoload all if_ modules when cloning fails, it's impossiable to support this without having if_vlan loaded. That said the current plan it to eliminate if_vlan and integrate vlan support directly into if_ethersubr.c to allow use to correctly handle the default vlan case among otherthings. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --ftEhullJWpWg/VHq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEsnqZXY6L6fI4GtQRAgUvAKC80nx6ScoGYLnWeOW0x6WtT+VpowCgxEfO QJWEgh5z8xdKyEpBgoEsb/E= =A+bK -----END PGP SIGNATURE----- --ftEhullJWpWg/VHq--