From owner-freebsd-net@FreeBSD.ORG Fri Mar 26 09:00:47 2010 Return-Path: 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 06E0B106566C; Fri, 26 Mar 2010 09:00:47 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp1.dlr.de (smtp1.dlr.de [129.247.252.32]) by mx1.freebsd.org (Postfix) with ESMTP id 89DD88FC0C; Fri, 26 Mar 2010 09:00:46 +0000 (UTC) Received: from beagle.kn.op.dlr.de ([129.247.178.136]) by smtp1.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Mar 2010 10:00:45 +0100 Date: Fri, 26 Mar 2010 10:01:53 +0100 (CET) From: Hartmut Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: Vasily Samoylov In-Reply-To: <4BAC6FF3.7090304@vas.org.ua> Message-ID: <20100326095919.A46084@beagle.kn.op.dlr.de> References: <4BAB5A77.7050505@mts.com.ua> <61b573981003250659n1076fef1u7d15920c4d560fdf@mail.gmail.com> <20100326080816.X46084@beagle.kn.op.dlr.de> <4BAC6FF3.7090304@vas.org.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 26 Mar 2010 09:00:45.0520 (UTC) FILETIME=[D22A7500:01CACCC2] Cc: freebsd-net@freebsd.org, Shteryana Shopova , Harti Brandt , Ivan Voras Subject: Re: Poor situation with snmp support in FreeBSD X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Mar 2010 09:00:47 -0000 On Fri, 26 Mar 2010, Vasily Samoylov wrote: VS>On 26.03.2010 9:10, Harti Brandt wrote: VS>> SS>P.S. Back to the thread topic - so the only problem the author is VS>> SS>facing with bsnmp is that it lacks support for LLDP, do I understand VS>> SS>correctly? VS>> VS>> This is what I understood too. VS>> VS>> harti VS>> VS>I, probably, was to verbose, and didn't make myself clear enough. For now, VS>from network admin point of view, it's 3 problems: VS>1) No ARP support The ARP table should be there. It may be that it got 'lost' with the ARP changes last year. So this should be fixable. The ARP table is the old one, though. VS>2) Routing table not exported correctly (directly attached routes not VS>visible, maybe something else - at least it's nothing like netstat -rn gives) This may be the same problem. The routing table code just fetches the routing table from the kernel. If the directly attached routes are not in the routing table anymore, they will not show up. 3) No LLDP support Until two days ago I was not even aware what LLDP is :-) harti