OoO En ce début d'après-midi ensoleillé du mercredi 20 avril 2011, vers 15:25, Hemant Dewnarain <hemant_dewnar...@hotmail.com> disait :
> After Enabling OID resolution in Wireshark Preferences -->Name > Resolution we started seeing this error in Wireshark: > Stopped processing module SNMPv2-SMI due to error(s) to prevent > potential crash in libsmi. > Module’s conformance level:1. > See details at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug= > 560325 > We use WireShark ( Version 1.4.0 (S ) ). > In Vista C:\Program Files\Wireshark\snmp\mibs directory we have all > posible MIBS available ( 309 items) including SNMPv2-SMI, > RFC1155-SMI, > SNMP-COMMUNITY-MIB , SNMP-MPD-MIB, SNMP-PROXY-MIB etecetera > However when looking closely in Wireshark SMI(MIB and PIB) modules to > check which modules are loaded we see only a few. > We don’t see here SNMPv2-SMI, RFC1155-SMI, SNMP-COMMUNITY-MIB , > SNMP-MPD-MIB, SNMP-PROXY-MIB etecetera. See attachment. > This in contrast to the number of MIB files present in the C:\Program > Files\Wireshark\snmp\mibs directory. > What do we need to configure to sidetrack abovementioned error? On Linux, you would run smilint against your MIB to check what the problem is. On Windows, I don't really know how you would check this. -- I WILL NOT SELL MIRACLE CURES I WILL NOT SELL MIRACLE CURES I WILL NOT SELL MIRACLE CURES -+- Bart Simpson on chalkboard in episode 9F16
pgp9QBl0tgLid.pgp
Description: PGP signature
