From owner-freebsd-arch@FreeBSD.ORG Sun Nov 30 11:23:33 2003 Return-Path: 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 BF6F016A4CE; Sun, 30 Nov 2003 11:23:33 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BDF543FE0; Sun, 30 Nov 2003 11:23:30 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9p2/8.12.9) with ESMTP id hAUJKpMg067769; Sun, 30 Nov 2003 14:20:51 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)hAUJKoET067766; Sun, 30 Nov 2003 14:20:51 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 30 Nov 2003 14:20:50 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Bruce M Simpson In-Reply-To: <20031130135805.GA80639@saboteur.dek.spc.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: sam@freebsd.org cc: Andre Oppermann cc: freebsd-arch@freebsd.org Subject: Re: ifconfig(8) refactoring -- YACC grammar now online X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2003 19:23:33 -0000 On Sun, 30 Nov 2003, Bruce M Simpson wrote: > On Sun, Nov 30, 2003 at 01:12:42PM +0100, Andre Oppermann wrote: > > What I've thinking about a lot is to make the networking system and > > ifconfig sort of class-based like newbus and geom. > > Look at: http://people.freebsd.org/~bms/dump/nifconfig/nifconfig-design.txt > > There is a pending change to if_gre to enable it to be easily classified > in this way; ifconfig would simply query the interface for its if_type. > This is one way to do it without having to change struct ifnet. We could > add a new field, but avoiding changing the ABI is a Good Thing. if_type seems like it will work for high level classes of interfaces, but something more fine-grained will be required for interfaces that implement multiple classes or subclasses (i.e., 802 generally, and also 802.11b). Or likewise, tap interfaces might implement 802 generally, but also if_tap-specific primitives. Do we need to probe by-name for capabilities using interface ioctls, or return a "list" of implemented interfaces/classes to allow things to be a bit more multidimensional? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research