From owner-freebsd-net@FreeBSD.ORG Tue Mar 28 09:32:34 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 5682E16A400; Tue, 28 Mar 2006 09:32:34 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4ACE43D48; Tue, 28 Mar 2006 09:32:33 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.180.83] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis), id 0MKxQS-1FOAYv2ri9-0005dS; Tue, 28 Mar 2006 11:32:29 +0200 From: Max Laier Organization: FreeBSD To: freebsd-net@freebsd.org Date: Tue, 28 Mar 2006 11:31:22 +0200 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart6535353.WdSbsXgMfN"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200603281131.28240.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Brooks Davis Subject: 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 09:32:34 -0000 --nextPart6535353.WdSbsXgMfN Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, while porting OpenBSD 3.9 (soon to be released) pf I stumbled on interface= =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 convey= =20 semantic information (e.g. group "LAN", "DMZ" ...) about your interface to= =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= =2E =20 Administration is done via ifconfig. We currently have "ifconfig name" whi= ch=20 does part of the job. 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 w= e=20 don't want it (in which case I'd hack something up for pf). Technical reasoning: A proper import would add an additional TAILQ link in= to=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 t= he=20 additional indirection. Also yet another config tool would be required to= =20 administer the interface <-> group binding. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart6535353.WdSbsXgMfN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEKQJwXyyEoT62BG0RApLBAJ9XCNZefXFhdoOe2ddvvmnw8aERwgCeIojM 4j/m5sU8Qm7OP4FGAKDGMys= =64hZ -----END PGP SIGNATURE----- --nextPart6535353.WdSbsXgMfN--