From owner-freebsd-net@FreeBSD.ORG  Thu Aug 13 11:34:26 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 772B41065673
	for <freebsd-net@freebsd.org>; Thu, 13 Aug 2009 11:34:26 +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 BCF988FC65
	for <freebsd-net@freebsd.org>; Thu, 13 Aug 2009 11:34:25 +0000 (UTC)
Received: (qmail 76684 invoked from network); 13 Aug 2009 11:34:24 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33)
	by bizet.nethelp.no with SMTP; 13 Aug 2009 11:34:24 -0000
Date: Thu, 13 Aug 2009 13:34:24 +0200 (CEST)
Message-Id: <20090813.133424.41729466.sthaug@nethelp.no>
To: d@delphij.net, delphij@delphij.net
From: sthaug@nethelp.no
In-Reply-To: <4A83EEA8.5080202@delphij.net>
References: <4A83EEA8.5080202@delphij.net>
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-net@freebsd.org
Subject: Re: RFC: interface description
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Aug 2009 11:34:26 -0000

> While playing with some OpenBSD installation I found that they have an
> interesting feature - adding description to a NIC.  This is useful for
> system administrators to "tag" the interface, also, the ladvd program
> has a feature to use the SIOCSIFDESCR ioctl to document the remote CDP
> peer like:

Yes please! This is an "obvious" feature to those of us who are router
geeks, and I've been wishing for this to show up in FreeBSD for years.

Now if I could have "sticky" static routes also I would be even happier
(as in: Next hop disappears -> route disappears. Next hop available
again -> route shows up in routing table again).

Steinar Haug, Nethelp consulting, sthaug@nethelp.no