From owner-freebsd-net@FreeBSD.ORG Tue Jan 14 10:15:50 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1751B8A7 for ; Tue, 14 Jan 2014 10:15:50 +0000 (UTC) Received: from quix.smartspb.net (quix.smartspb.net [217.119.16.133]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C55101531 for ; Tue, 14 Jan 2014 10:15:49 +0000 (UTC) Received: from dyr.smartspb.net ([217.119.16.26] helo=[127.0.0.1]) by quix.smartspb.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.61 (FreeBSD)) (envelope-from ) id 1W312B-0006EL-NT for freebsd-net@freebsd.org; Tue, 14 Jan 2014 14:15:47 +0400 Message-ID: <52D50E53.7000405@smartspb.net> Date: Tue, 14 Jan 2014 14:15:47 +0400 From: Dennis Yusupoff User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: Showing CDP info in ifconfig? References: <52D50065.8060907@fsn.hu> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 140114-0, 14.01.2014), Outbound message X-Antivirus-Status: Clean X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jan 2014 10:15:50 -0000 May be implement that functionality in ndp utility, as far it named after Neighbor Discovery Protocol? 14.01.2014 13:31, Bjoern A. Zeeb пишет: > No. Neither would lldp or other protocols. That’s what a higher level > management user interface is for. I’d be happy to finally see someone > do this in an abstracted way so it could be a cli, a Web interface, or > some xml-rpc thingy or whatever is the standard of the day. ifconfig > is not the place, especially since it would have to query a daemon > running somewhere else anyway. Otherwise we’ll end up with ndp, ospf, > isis, bgp, ipsec, and the apache, varnish, and squid status there as > well. Just my 2cts. -- Best regards, Dennis Yusupoff, network engineer of Smart-Telecom ISP Russia, Saint-Petersburg