On Tue, May 05, 2009 at 08:28:12PM +0200, Jens Engel wrote:

smidump 0.4.8 (up to rev13631 and maybe never) have a problem with the following SMI construct:

-- FROM libsmi distributed SYSAPPL-MIB: sysApplPastRunMaxRows OBJECT-TYPE SYNTAX Unsigned32 (0..'ffffffff'h) ...

NOTE: 0xFFFFFFFF = 2^32-1 = 4 294 967 295

when you try to convert the provided MIB via:

smidump --format=smiv2 SYSAPPL-MIB ...

you get the following output for libsmi 0.4.7 and 0.4.8. NOTE: Upper syntax bound is wrong in both cases.

=== modified file 'IETF/mibs/SYSAPPL-MIB.mib' --- IETF/mibs/SYSAPPL-MIB.mib 2009-03-28 19:03:48 +0000 +++ IETF/mibs/SYSAPPL-MIB.mib 2009-05-04 16:57:29 +0000 @@ -1038,7 +1038,7 @@ ::= { sysApplElmtPastRunEntry 11 }

sysApplPastRunMaxRows OBJECT-TYPE

• SYNTAX Unsigned32 (0..1134880) -- smidump 0.4.7 output

• SYNTAX Unsigned32 (0..1134864) -- smidump 0.4.8

rev13631 (post-release)

NOTE: Output of SYNTAX upper bound varies. WEIRD: The conversion to format=python leads to the correct result. Without looking at the source code, I assume that the hex-string to integer conversion has a problem.

This problem seems to be fixed in trunk now.

/js