Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 03 Oct 2006 19:46:58 -0700
From:      Sam Leffler <sam@errno.com>
To:        Andrew Thompson <thompsa@freebsd.org>
Cc:        arch@freebsd.org
Subject:   Re: where to put extra RSTP info
Message-ID:  <452320A2.9070103@errno.com>
In-Reply-To: <20061003232716.GJ21444@heff.fud.org.nz>
References:  <20061003232716.GJ21444@heff.fud.org.nz>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?452320A2.9070103>