From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 09:34:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9F7F106564A for ; Tue, 18 Nov 2008 09:34:27 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by mx1.freebsd.org (Postfix) with SMTP id 031E08FC1A for ; Tue, 18 Nov 2008 09:34:26 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: (qmail 44310 invoked from network); 18 Nov 2008 09:34:24 -0000 Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 18 Nov 2008 09:34:24 -0000 Date: Tue, 18 Nov 2008 10:34:24 +0100 (CET) Message-Id: <20081118.103424.74710091.sthaug@nethelp.no> To: peterjeremy@optushome.com.au From: sthaug@nethelp.no In-Reply-To: <20081118081153.GQ51761@server.vk2pj.dyndns.org> References: <5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk> <20081117.233619.85395429.sthaug@nethelp.no> <20081118081153.GQ51761@server.vk2pj.dyndns.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Possible regression in ifconfig under7.0 - removes validdefault route X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Nov 2008 09:34:27 -0000 > >Oh yeah, since we're in wishful thinking mode, I want interface > >descriptions too... > > Have you looked at the 'name' and 'group' keywords in ifconfig(8)? > If this isn't what you want, please expand on your wish. It is not what I want. On routers, switches and lots of other boxes from most vendors you can associate a description string with each interface - where interface can be a physical port, or for instance a VLAN based interface. This description string is useful to document things like - what is the box at the other end of the cable connected to this port - what is the port at the other end of the cable connected to this port - what is the circuit id for the circuit this port is connected to - what is this port used for etc. Typical example, from one of our switches (Cisco syntax): interface GigabitEthernet0/12 description TO: fs1.td ID: BTN-11510092 TXT: gi1/0/7 EoSDH 50 Mbps switchport trunk allowed vlan 123,770,1024,1500,1504,1528,1536 showing the first three points I mentioned above. Such a description string is can normally be retrieved using SNMP. Steinar Haug, Nethelp consulting, sthaug@nethelp.no