From owner-freebsd-net@FreeBSD.ORG Thu Mar 25 16:25:07 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 98E73106567C for ; Thu, 25 Mar 2010 16:25:07 +0000 (UTC) (envelope-from mail@vas.org.ua) Received: from relay.electro.ua (electro.ua [213.186.192.234]) by mx1.freebsd.org (Postfix) with ESMTP id 386A08FC1F for ; Thu, 25 Mar 2010 16:25:07 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by relay.electro.ua (Postfix) with ESMTP id B448C170BA for ; Thu, 25 Mar 2010 18:07:49 +0200 (EET) X-Virus-Scanned: amavisd-new at http.org.ua Received: from relay.electro.ua ([127.0.0.1]) by localhost (http.org.ua [127.0.0.1]) (amavisd-new, port 10024) with LMTP id AoNSPzw0CGn0 for ; Thu, 25 Mar 2010 18:07:49 +0200 (EET) Received: from [192.168.168.161] (41-224-132-95.pool.ukrtel.net [95.132.224.41]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by relay.electro.ua (Postfix) with ESMTPSA id 5C061170B7 for ; Thu, 25 Mar 2010 18:07:49 +0200 (EET) Message-ID: <4BAB8A36.5010702@vas.org.ua> Date: Thu, 25 Mar 2010 18:07:18 +0200 From: Vasyl Samoilov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; uk; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <4BAB5A77.7050505@mts.com.ua> <61b573981003250659n1076fef1u7d15920c4d560fdf@mail.gmail.com> In-Reply-To: <61b573981003250659n1076fef1u7d15920c4d560fdf@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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: Thu, 25 Mar 2010 16:25:07 -0000 25.03.2010 15:59, Shteryana Shopova написав(ла): > > We already have BSNMP listed on the SoC project ideas page :) The > problem is we still need a developer to review and test the code > before it can be imported. :) > > cheers, > Shteryana > > P.S. Back to the thread topic - so the only problem the author is > facing with bsnmp is that it lacks support for LLDP, do I understand > correctly? > It's 3 problems: 1) No ARP support 2) Routing table not exported correctly (directly attached routes not visible, maybe something else - at least it's nothing like netstat -rn gives) 3) No LLDP support for the future (I understand how hard it is to complete with limited resources): *Complete etherlike-mib for interface duplex information * vlan information for interfaces / per-vlan mac address table for bridge - freebsd as managed layer 2 device (I didn't dig deep into this yet, considering the first 3 showstoppers)