Date: Thu, 11 Nov 2010 15:01:20 -0600 From: Brandon Gooch <jamesbrandongooch@gmail.com> 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>, Vasily Samoylov <mail@vas.org.ua> Subject: Re: Poor situation with snmp support in FreeBSD Message-ID: <AANLkTimigyQLSxJiVQCDuomtd2sSzv2i-4N2ZVRkQM6Y@mail.gmail.com> 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 Fri, Mar 26, 2010 at 4:01 AM, Hartmut Brandt <hartmut.brandt@dlr.de> 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. Old thread, but I just recently bumped into this problem... Does anyone CC'd in this exchange know how to go about fixing this? Perhaps a pointer to a document describing the changes in ARP that broke this? Seems that net-snmp manages to gather this info: # snmpwalk -v 1 -c public 192.168.1.1 ... IP-MIB::ipNetToMediaPhysAddress.1.192.168.0.105 = Hex-STRING: 00 21 E1 FB 25 2D IP-MIB::ipNetToMediaPhysAddress.1.192.168.0.0 = Hex-STRING: 00 13 20 2E 89 61 IP-MIB::ipNetToMediaPhysAddress.1.192.168.0.168 = Hex-STRING: 00 11 43 A3 1C 1F IP-MIB::ipNetToMediaPhysAddress.1.192.168.0.194 = Hex-STRING: 00 60 97 92 59 64 ... Thanks for any pointers... -Brandon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimigyQLSxJiVQCDuomtd2sSzv2i-4N2ZVRkQM6Y>