Date: Fri, 26 Mar 2010 11:31:54 +0200 From: Vasily Samoylov <mail@vas.org.ua> To: Hartmut Brandt <hartmut.brandt@dlr.de> Cc: freebsd-net@freebsd.org, Shteryana Shopova <shteryana@gmail.com>, Harti Brandt <harti@freebsd.org>, Ivan Voras <ivoras@freebsd.org> Subject: Re: Poor situation with snmp support in FreeBSD Message-ID: <4BAC7F0A.1070905@vas.org.ua> In-Reply-To: <20100326095919.A46084@beagle.kn.op.dlr.de> References: <4BAB5A77.7050505@mts.com.ua> <hofp7m$r06$1@dough.gmane.org> <61b573981003250659n1076fef1u7d15920c4d560fdf@mail.gmail.com> <20100326080816.X46084@beagle.kn.op.dlr.de> <4BAC6FF3.7090304@vas.org.ua> <20100326095919.A46084@beagle.kn.op.dlr.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26.03.2010 11:01, Hartmut Brandt wrote: > 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. > I was looking for something like ipNetToPhysicalTable (ipv6 compatible) or ipNetToMedia (depreciated, ip4 only) - both are not there. A bug, I suppose. net-snmp under freebsd got ipNetToMedia. If there is anything I can do to help with testing new bsnmpd or patches - I am ready. :) > 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. > Routes are in the routing table. netstat -rn show everything correctly, and, againg, net-snmp ipCidrRoute contains all routes, but consider all them "local". bsnmp, in the other hand, got only some of the routes. This is obviously a bug and should be fixed. > 3) No LLDP support > > Until two days ago I was not even aware what LLDP is :-) > You never what that is link-layer discovery protocol until it comes to large network and you need to automate link discovery and build a topology. LLDP daemon by itself is good, but there must be a way to query it by snmp - otherwise it is useless. So far the best lldp daemon for bsd systems is ladvd, link advertising daemon, but bsnmp got no means of reading info from it, so I'm kinda stuck here. http://www.blinkenlights.nl/software/ladvd/ ladvd uses cdp / lldp frames to inform switches about connected hosts, which simplifies ethernet switch management. It does this by creating a raw socket at startup, and then switching to a non-privileged user for the remaining runtime. Every 30 seconds it will transmit CDP/LLDP packets reflecting the current system state. Interfaces (bridge, bonding, wireless), capabilities (bridging, forwarding, wireless) and addresses (IPv4, IPv6) are detected dynamically. > harti > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BAC7F0A.1070905>