I have read a few other postings from the archives, and noted
comments just a few weeks ago that relate to the issue of
using mib2c.scalar.conf on a MIB having no scalar objects,
and the result being no stubs for any OIDs. This is a significant
departure from past behavior, and while initially con
> The documentation says that I must select a .conf file
> and pass this to mib2c, along with the suitable root OID.
> I have attached the .txt file of my MIB, for 802.11 support.
It doesn't look as if you did attach that MIB file,
but I presume you're working with the standard IEEE802dot11-MIB
(
I am having some issues with mib2c, using the net-snmp-5.0.9
distribution under RedHat 9. I have read the various documents
for the release in question, the FAQ, the descriptions for agent
construction, and the like. I followed the instructions for perl
installation (BTW, they differ in two place
