I just downloaded the latest release (net-snmp-5.2.tag.gz), and am
running on RedHat 9 (with current up2date support). The problem
with the MFD helper remains unresolved. The appropriate excerpt
from my command line is:
===================================
Excerpt Begin
===================================
[EMAIL PROTECTED] dot11]# mib2c ieee802dot11
writing to -
mib2c has multiple configuration files depending on the type of
code you need to write. You must pick one depending on your need.
You requested mib2c to be run on the following part of the MIB tree:
OID: ieee802dot11
numeric translation: .1.2.840.10036
number of scalars within: 1
number of tables within: 23
number of notifications within: 1
First, do you want to generate code that is compatible with the
ucd-snmp 4.X line of code, or code for the newer Net-SNMP 5.X code
base (which provides a much greater choice of APIs to pick from):
1) ucd-snmp style code
2) Net-SNMP style code
Select your choice : 2
**********************************************************************
GENERATING CODE FOR SCALAR OBJECTS:
**********************************************************************
It looks like you have some scalars in the mib you requested, so I
will now generate code for them if you wish. You have two choices
for scalar API styles currently. Pick between them, or choose not
to generate any code for the scalars:
1) If you're writing code for some generic scalars
(by hand use: "mib2c -c mib2c.scalar.conf ieee802dot11")
2) If you want to magically "tie" integer variables to integer
scalars
(by hand use: "mib2c -c mib2c.int_watch.conf ieee802dot11")
3) Don't generate any code for the scalars
Select your choice: 2
using the mib2c.int_watch.conf configuration file to generate your code.
*** Warning: only generating code for nodes of MIB type INTEGER
writing to ieee802dot11.h
writing to ieee802dot11.c
**********************************************************************
GENERATING CODE FOR TABLES:
**********************************************************************
Your tables will likely either fall into one of two categories:
1) tables where the list of rows is external to the agent.
This is suited to MIBs which monitor or manipulate external
data (perhaps extracted from the operating system kernel
or other system interfaces), and where rows are typically
created or destroyed independently of the SNMP agent.
2) tables where the list of rows is held by the agent itself.
This is particularly suited to tables that are primarily
manipulated via SNMP, or where the rows of the table are
relatively static.
3) Do not generate code for the tables.
Select the option that best fits you: 1
This style of table tends to use the iterator helper to instrument
the external data, so it can be represented by an SNMP table.
The main characteristic of this helper is the use of a pair
of "iteration hook" routines to loop through the rows in turn
(in the most natural order for the underlying data).
There are a couple of different template configurations that
can be used as a framework for this:
1) One based around a single handler, that includes code to handle
both GET and SET requests, as well as row creation and deletion.
This template defines a suitable data structure, and implements
the table as an internally-held linked list, but both of these
are mainly for illustration, and could reasonably be replaced by
code more appropriate for the table being implemented.
The same template can be generated using
mib2c -c mib2c.iterate.conf ieee802dot11
2) An alternative framework, designed as an API wrapper on top of
the basic iterator helper, that seeks to separate the standard
processing of the syntax of a MIB table (which can be generated
automaticall), from the semantics of a given table (which cannot).
It generates a number of separate code files, but typically
only one or two of these will need to be edited. These contain
separate 'get_column()' and 'set_column()' functions for each
column in the table, plus some other routines for manipulating
rows (plus the standard iterator hook routines).
The same templates can be generated using
mib2c -c mib2c.iterate_access.conf ieee802dot11
(See the agent/mibgroup/example/netSnmpHostsTable.c file for example)
3) An API layer (not based on the iterator helper) that attempts
to reduce the amount of SNMP specific knowledge required to
implement a module. It provides more APIs than 2, which are
(hopefully) smaller and more specific, with less SNMP terminology.
This API is also known as "MIBs for Dummies". Numerous tables
in the Net-SNMP agent have been re-written to use this API.
The same templates can be generated using
mib2c -c mib2c.mfd.conf ieee802dot11
(See the agent/mibgroup/if-mib/ifTable/ifTable*.c files for examples)
4) Do not generate code for the tables.
If you are unsure which option to pick, choices 2) or 3) are perhaps
more suited for those less familiar with the concepts behind the SNMP
protocol operations, while choice 1) gives more control over exactly
what is done.
Select the API style you wish to use: 3
using the mib2c.mfd.conf configuration file to
generate your code.
| +-> Processing table dot11StationConfigTable
writing to default-table-dot11StationConfigTable.m2d
writing to default-node-dot11StationID.m2d
writing to default-node-dot11MediumOccupancyLimit.m2d
writing to default-node-dot11CFPollable.m2d
writing to default-node-dot11CFPPeriod.m2d
writing to default-node-dot11CFPMaxDuration.m2d
writing to default-node-dot11AuthenticationResponseTimeOut.m2d
writing to default-node-dot11PrivacyOptionImplemented.m2d
writing to default-node-dot11PowerManagementMode.m2d
writing to default-node-dot11DesiredSSID.m2d
writing to default-node-dot11DesiredBSSType.m2d
writing to default-node-dot11OperationalRateSet.m2d
writing to default-node-dot11BeaconPeriod.m2d
writing to default-node-dot11DTIMPeriod.m2d
writing to default-node-dot11AssociationResponseTimeOut.m2d
writing to default-node-dot11DisassociateReason.m2d
writing to default-node-dot11DisassociateStation.m2d
writing to default-node-dot11DeauthenticateReason.m2d
writing to default-node-dot11DeauthenticateStation.m2d
writing to default-node-dot11AuthenticateFailStatus.m2d
writing to default-node-dot11AuthenticateFailStation.m2d
writing to default-node-dot11MultiDomainCapabilityImplemented.m2d
writing to default-node-dot11MultiDomainCapabilityEnabled.m2d
writing to default-node-dot11CountryString.m2d
writing to default-node-ifIndex.m2d
| +-> Processing table dot11AuthenticationAlgorithmsTable
Can't find a configuration file called
default-table-dot11AuthenticationAlgorithmsTable.m2d
(referenced at /usr/local/share/snmp/mib2c-data/m2c_setup_table.m2i:54)
I looked in:
.
/usr/local/share/snmp/
/usr/local/share/snmp/mib2c-data
./mib2c-conf.d
[EMAIL PROTECTED] dot11]#
===================================
Excerpt End
===================================
Of course, the problem is that only the first table of the 802dot11
MIB was compiled.
So, what is the problem, and what is the solution?
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Net-snmp-users mailing list
[EMAIL PROTECTED]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
