April 2010 - Libsmi - lists.ibr.cs.tu-bs.de

libsmi/smidump 0.4.8 problem: SYSAPPL-MIB::sysApplPastRunMaxRows SYNTAX Upper Bound
by Jens Engel 18 Mar '11

18 Mar '11

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. Ciao, Jens Engel Jens Engel mailto:jens_engel@t-online.de mailto:jens.engel

2 1

smidump -f svg and problem with wrong mixed scalar and table group?
by Claus Klein 21 Apr '10

21 Apr '10

Hi, If have worked with LLDP-MIB (IEEE) and saw, that some scalars are wrongly shown as members of a Table Entry? The same can be found with the IF-MIB (only the ifNumber is ok) and NOTIFICATION-LOG-MIB. Is this a bug or what is the reason for this strange grouping? I used smidump V0.4.8. Regards Claus

1 0

Building 0.4.8 on fresh install of Solaris 10 10/09
by Root, Paul 13 Apr '10

13 Apr '10

I'm trying to build libsmi-0.4.8 to use with wireshark 1.0.8 on Solaris 10 10/09 The machine is a fresh install, with packages from sunfreeware.com The library configures and builds without complaint, but when I run "gmake check", I get 7 failed tests. I'm trying to figure out what fails, but am not getting too far. If the failure is do to a compare of output, the only differences are trailing blank characters on a number test output files. I installed the libs, and moved on to build wireshark. Which builds fine. Try to run it however, and I get a core dump, when its trying to open ~/.wireshark/smi_paths. Has anybody gone through anything like this? Google searches have lead to nothing useful. Thanks, Paul. Paul Root Lead Internet Systems Eng Network Services This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.

1 0

+Hi+
by Patty Ackermann 09 Apr '10

09 Apr '10

http://sites.google.com/site/asdf32rweft/oblk3c

2 1