From owner-freebsd-arch@FreeBSD.ORG Thu Apr 6 19:14:16 2006 Return-Path: X-Original-To: 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 78CB216A403; Thu, 6 Apr 2006 19:14:16 +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 2E03943D46; Thu, 6 Apr 2006 19:14:16 +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 k36JEF74026095; Thu, 6 Apr 2006 12:14:15 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k36JEFjA026094; Thu, 6 Apr 2006 12:14:15 -0700 Date: Thu, 6 Apr 2006 12:14:15 -0700 From: Brooks Davis To: Dima Dorfman Message-ID: <20060406191415.GA1578@odin.ac.hmc.edu> References: <20060406080644.GE843@trit.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZPt4rx8FFjLCG7dd" Content-Disposition: inline In-Reply-To: <20060406080644.GE843@trit.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new Cc: arch@freebsd.org Subject: Re: Using ifconfig(8) to configure netgraph interfaces 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: Thu, 06 Apr 2006 19:14:16 -0000 --ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 06, 2006 at 08:06:44AM +0000, Dima Dorfman wrote: > What are people's thoughts on extending ifconfig(8) to configure > netgraph-based interfaces, such as ng_fec(4)? The recent trend has > been to allow all kinds of different network interfaces to be > configured uniformly through ifconfig. Is there any reason > functionality based on netgraph nodes should be excluded? The netgraph configuration processes differs significantly enought that it would seem like you'd have to a lot of special cases for it. For instance the create option would have to grow a lot of specificic knowledge about the nodes that must be created via netgraph and how to create them. Thus far, ifconfig functions have been pretty generic in implementation except when they are specific a partifular interface (e.g. if_bridge) or class of interfaces (e.g. wireless interfaces). > On a related note, is there any reason to not to use netgraph to > implement things like FEC for production use? Are there any advantages > to using a normal pseudo device (like NetBSD's agr(4)) instead of > improving the netgraph node? Performance concerns, anything like that? ng_fec isn't really much of a netgraph node. It uses netgraph for configuration, but actually directly hijacks the interface's input functions rather than using the netgraph interfaces. I'd personally prefer to see it replaced with a pseudo interface that was a bit better integrated into the overall system -- 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 --ZPt4rx8FFjLCG7dd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFENWiGXY6L6fI4GtQRArVqAKCh9DRhPHNqxyGhg0zjsEzCGif80wCgmtYl eYckIVdcBTn2VfhevBPc9CI= =3FFM -----END PGP SIGNATURE----- --ZPt4rx8FFjLCG7dd--