https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7580
--- Comment #6 from DeCount <aatrade@xxxxxxxxx> 2012-11-21 08:35:12 PST ---
(In reply to comment #4)
> (In reply to comment #3)
> > After an analysis the problem seem related to the "libsmi-2.dll" library
> > delivered. The library doesn't process the user MIB files.
> Then there's probably a problem with the MIBs not beeing compliant
> libsmi is very touchy about that. I think this arcive
> http://anonsvn.wireshark.org/viewvc/trunk/packages/libsmi-svn-40773-win32ws.zip?view=markup&revision=358&root=Wireshark-win32-libs
> contains tools you can use to
> check the MIBs.
I have checked the MIB files and no error or warning are reported by the
smilint command (version used 0.4.6).
I think that the libsmi-2 library read and process the "user" MIB files because
the "name" of the OID is correctly decoded. See on the screenshot the "name"
that come from for the related OID:
OMSTRAP-MIB::omsTrapContentsManagedObjectId.0
(1.3.6.1.4.1.193.167.2.1.2.2.5.0)
What is going wrong is the data contained on the objects that are not more
"decoded". For example instead of "TUG:Slot=0;Port=1;dcbklm ....." report
"5455473a536 ...".
This not happens with the previous 1.6.x releases of Wireshark.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.