From owner-freebsd-current@FreeBSD.ORG Wed Jan 25 07:57:03 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 992B016A41F for ; Wed, 25 Jan 2006 07:57:03 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D93B243D48 for ; Wed, 25 Jan 2006 07:56:58 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 99693 invoked from network); 25 Jan 2006 07:57:08 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 25 Jan 2006 07:57:08 -0000 Message-ID: <43D72F49.8080304@freebsd.org> Date: Wed, 25 Jan 2006 08:56:57 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: sthaug@nethelp.no References: <20060124075437.B67285@xorpc.icir.org> <43D67C6E.7020403@errno.com> <43D6811D.9070309@elischer.org> <20060124.231504.74682748.sthaug@nethelp.no> In-Reply-To: <20060124.231504.74682748.sthaug@nethelp.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: rizzo@icir.org, julian@elischer.org, current@freebsd.org Subject: Re: if_flags usage etc. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2006 07:57:03 -0000 sthaug@nethelp.no wrote: >>We should probably better document the interface "interface". if we are >>going to (as Sam suggests) >>do some cleanups we might as well consider what other changes should be >>put in at the same time. > > A couple of other suggestions: > > - For software routers (quagga, zebra etc.) it would be very nice to > have "link up" / "link down" notifications to the routing process(es). We have that already since 5.3 I think. You have various options for receiving notifications on this event, routing socket, kqueue, netgraph and devctl. > - One feature sorely missed (which I use a lot in my daily work with > hardware based routers) is the ability to associate a "description" > field with each interface. Note that this should be available both > for physical interfaces (Ethernet etc.) and for logical interfaces > (e.g. vlan). Struct ifnet is the same for all kinds of interfaces, so any change would make it available for everyone. And yes, this looks like a useful addition. -- Andre