Hi All ,
I am using MG Soft mib browser and in my enterprise mib i have
taken the Mac Address as a index (Entries based on mac addess ) and in mib the
SYNTAX of Mac Address as MacAddress .
I Imports the mib file SNMPV2-TC in my enterprise mib .where the MacAddress is
defined as
I would like to add the attached patch to all branches in order to work
around 1976772 where long DEFVAL's cause a failure in loading the mib.
The patch eats all the data but fails to store it properly so it is not
good enough for mib2c but solves the immediate problem of not beeing
able to parse
I have thought some more on config_version_require and ended up with the
conclusion that I need to use double parentheses since it takes a
variable number of arguments and ... is unsupported prior to C99.
Thus the attached patch is what I will go with.
/MF
Index: clean/configure.in
==
> On Wed, 11 Jun 2008 10:39:48 -0700, "Nathan Schrenk" <[EMAIL PROTECTED]>
> said:
NS> There appears to be an error in the 5.4.1.1 tarball distribution that
NS> causes problems for me when I attempt to build the perl module:
NS> snmplib/snmp_version.c still contains a version string of "5
There appears to be an error in the 5.4.1.1 tarball distribution that
causes problems for me when I attempt to build the perl module:
snmplib/snmp_version.c still contains a version string of "5.4.1" and
that's where the configure script extracts VERSION from. So
net-snmp-config --version reports
2008/6/11 ntwrkd <[EMAIL PROTECTED]>:
> i am more interested in the different options for extending the agent.
> would i use mib2c?
That's the easiest way to produce suitable template code
for implementing a new MIB module, yes.
But it's not compulsory.
It is perfectly possible to generate equi
2008/6/10 <[EMAIL PROTECTED]>:
> Could it be possible for creating a different log file for subagent
> and manage the log level and type of log messages to be logged.
If your subagent understands the standard command-line arguments,
then you can use the -Lf option to specify the appropriate log f
