["Martin Regner" <martin.regner@xxxxxxxxx>]

Wes Hardaker wrote:
> >>>>> On Tue, 14 Dec 2004 11:41:46 -0600, Gerald Combs <gerald@xxxxxxxxxxxx> said:
>
> Gerald> BTW, the "snmpcmd" man page on the Net-SNMP web site specifies
>
> Gerald> SNMPv2-TC:SNMPv2-MIB:IF-MIB:IP-MIB:TCP-MIB:UDP-MIB:SNMP-VACM-MIB
>
> Gerald> as the default list of MIBs to load.  Should we update
> Gerald> packet-snmp.c to match this?
>
> NNOOOOOO!!!!!
>
> The Net-SNMP package builds its list of default MIBs based on the
> version, the ones it is going to install, the ones configured by the
> user for the package, ...  you should not override this default in
> your application (IMHO, of course).  If the user wants to, that is
> fine of course.  But there is no reason that ethereal itself should be
> specifying the default list of MIBs.
>

I think the reason why we are actually specifying the MIBs to load is that previously there was a lot of complaints
that Ethereal was hanging on startup on Windows for people that had installed ucsdsnmp and defined the environment
variables in such a way that netsnmp was using the catalogues with MIBs that was used by ucdsnmp.
Certain malformed MIBs could get Ethereal to hang when using Net-SNMP.
I don't know if you still get the hanging still with the newest version of Net-SNMP.

It was especially a software package form Enterasys (NetSight Element Manager) that many of these people had installed.
At installation it set the environment variables (e.g. MIBDIRS) and pointed to a directory where it had installed some
MIBs that
was a bit malformed.
When you installed Ethereal on the same computer it couldn't start-up.

http://www.ethereal.com/lists/ethereal-users/200304/msg00086.html
http://www.ethereal.com/lists/ethereal-users/200304/msg00083.html
http://www.ethereal.com/lists/ethereal-users/200307/msg00061.html
http://www.ethereal.com/lists/ethereal-users/200309/msg00024.html