From owner-freebsd-arch@FreeBSD.ORG Wed Oct 4 02:47:00 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 7F6DA16A403; Wed, 4 Oct 2006 02:47:00 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1238343D4C; Wed, 4 Oct 2006 02:46:59 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k942kxof035445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Oct 2006 19:46:59 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <452320A2.9070103@errno.com> Date: Tue, 03 Oct 2006 19:46:58 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5.0.4 (X11/20060724) MIME-Version: 1.0 To: Andrew Thompson References: <20061003232716.GJ21444@heff.fud.org.nz> In-Reply-To: <20061003232716.GJ21444@heff.fud.org.nz> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: arch@freebsd.org Subject: Re: where to put extra RSTP info 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: Wed, 04 Oct 2006 02:47:00 -0000 Andrew Thompson wrote: > Hi, > > > The new RSTP code I have been working on has more info that can be shown > and tweaked by the network admin when setting up the layer2 topo. I now > have the problem of what utility to stuff it into. > > a) ifconfig > b) netstat > c) some new util like bridgestat > > I realise that ifconfig is for setting the interface config and should > not be abused. I am tempted to add a new util, here is an example of > what I need to show. > > Spanning Tree Parameters for bridge0 > Protocol : IEEE 802.1W (Rapid STP), > Priority : 32768 (0x8000), > Bridge ID : 8000-00:d0:95:8e:56:7e, > Designated Root : 8000-00:04:75:d1:f8:98, > Cost to Root Bridge : 0, > Root Port : None, > Next Best Root Cost : 100, > Next Best Root Port : 8000-00:d0:95:aa:bb:cc, > Hold Time : 1, > Topology Changes : 98, > Topology age : 5:02:36 > > Interface 1 > Role : Designated > Link type : Point to Point > ... > > Interface 2 > Role : Alternate > Link type : Shared > ... > > > Any suggestions? Tweaking parameters definitely belongs in ifconfig. If the information to report falls into the area of "status" then it too belongs in ifconfig. Other stuff is a hard call. I stuck a bunch of 802.11-related status display that could also go someplace like netstat into ifconfig and noone's complained so I guess it's been acceptable. I've been working to unify network interface-related manipulation work under a single application (ifconfig) so people don't need to search for the appropriate program. I did this after getting frustrated with tool sets in other os's (e.g. linux's iw* apps). However dynamic status reporting kinda feels like it belongs elsewhere (e.g. netstat). Some things like "list stations" and "list scan" that are present in ifconfig may not belong but were stuck there because it's a natural spot for folks coming from linux and the structure minimized code duplication. Sam