On Tue, Mar 19, 2013 at 12:12 PM, Joan Landry <joan.lan...@overturenetworks.com> wrote: > The Silvercreek test fails on a getnext of the following oid: > > 1.3.111.2.802.1.1.13.1.3.8.1.3.1.4294967295.2.3.4.5 > > Netsnmp is converting 4294967295 which is the string length of the ip address > to 0, which makes the get next return > > 1.3.111.2.802.1.1.13.1.3.8.1.3.1.4.2.3.4.5 > > Which is not lexicographic greater than the request oid. > > Any info on how to resolve this would be greatly appreciated.
There are a whole bunch of places where net-snmp uses a signed integer for oid storage and integer comparisons. We fixed some of them locally (not that one, since we don't use net-snmp's ipAddrTable) but didn't really think anyone else cared. https://github.com/aristanetworks/net-snmp/commit/47003a2498c8333a0d4a35a3ccceb0a2206586c6 https://github.com/aristanetworks/net-snmp/commit/db96c8d110b53b088b7025f079641f5a32ed2243 https://github.com/aristanetworks/net-snmp/commit/aa4a6a96a41b0908c56a36ea2798784ef18779fb Especially if you look at the last one, it's fairly simple: make sure that you are treating oid elements as unsigned. Bill ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
