From owner-freebsd-net@FreeBSD.ORG Tue Mar 28 17:24:47 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 894F316A400; Tue, 28 Mar 2006 17:24: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 360D944534; Tue, 28 Mar 2006 16:24:32 +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 k2SGOV0H012071; Tue, 28 Mar 2006 08:24:31 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k2SGOV5c012070; Tue, 28 Mar 2006 08:24:31 -0800 Date: Tue, 28 Mar 2006 08:24:31 -0800 From: Brooks Davis To: Max Laier Message-ID: <20060328162431.GA9637@odin.ac.hmc.edu> References: <200603281131.28240.max@love2party.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline In-Reply-To: <200603281131.28240.max@love2party.net> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-net@freebsd.org, Brooks Davis Subject: Re: Interface groups (from OpenBSD) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2006 17:24:48 -0000 --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 28, 2006 at 11:31:22AM +0200, Max Laier wrote: > Hi, >=20 > while porting OpenBSD 3.9 (soon to be released) pf I stumbled on interfac= e=20 > groups. This is a mechanism to group arbitrary interfaces into logical= =20 > groups. It is just naming (not functional change), but it helps to conve= y=20 > semantic information (e.g. group "LAN", "DMZ" ...) about your interface t= o=20 > supporting applications. This way you can write a policies for interface= =20 > group "LAN" and have it applied to all the VLAN interfaces that come and = go. =20 > Administration is done via ifconfig. We currently have "ifconfig name" w= hich=20 > does part of the job. >=20 > My question: Does that sound like something interesting for us and should= I go=20 > for importing it into FreeBSD proper, or is it not at all interesting and= we=20 > don't want it (in which case I'd hack something up for pf). Sounds like a reasonable feature. I think it's orthogional to renaming. > Technical reasoning: A proper import would add an additional TAILQ link = into=20 > struct ifnet (which is a great deal of ABI change and causes the usual=20 > headaches). The hack would use a single void *, but we'd have to pay for= the=20 > additional indirection. Also yet another config tool would be required t= o=20 > administer the interface <-> group binding. Adding a TAILQ to the end of struct ifnet would not be an ABI change in 6 because drivers don't know or care how big struct ifnet is anymore and I can't think of an implementation where the drive code would need to care. -- 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 --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEKWM+XY6L6fI4GtQRAhoQAJ41pqwaheC1iAd5jcmXk6nPTUQCpACfcYly wiFAsgULr9EQ9ldqSuWYXwg= =X5zs -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4--