Hi,
I am working on a VTP ( extend Net-SNMP support for IEEE 802.11 MIB)
. The Approch document is given below .
************************************************************************
************************************************************************
***************************************************
I. Purpose:
This document provides an overview of the WLAN interface management
using SNMP. It is intended to capture the functionalities involved in
the management of a few objects in the IEEE 802.11 MIB.
II. Scope of the document:
The document gives a brief description about each of the functional
modules involved in the development and testing of the SNMP manager and
the extended agent for the IEEE 802.11 MIB.
III. Project Description:
The project mainly focuses on familiarization of the management of
network interfaces using SNMP. Here the management framework is being
built for a wireless LAN access point. The SNMP based opensource tool,
Net-SNMP, is used to realize the agent/manager model. Net-SNMP does not
support the wireless MIB (802.11 MIB) in opensource. This project
extends SNMP support for 802.11 MIB.
System Specification:
Hardware:
* Netgear WG311T using Atheros AR5212
Software:
* Ubuntu 6.10 (Edgy Eft). Linux Kernel version is 2.6.17.
* MADWiFi tools 0.9.2
* Net-SNMP 5.2.2
The main activities/modules involved in this VTP are as follows:
1. Installation of Net-SNMP:
The activity involves downloading of Net-SNMP on a Linux platform,
installing it and configuring it for restricted access. Testing of the
installed tool can be done using standard SNMP commands like SET, GET,
and GETNEXT.
2. Understanding the 802.11 MIB:
The MIB definition file for 802.11 has been provided by the IEEE. It is
required to understand the MIB tree structure so as to divide the MIB
tree for implementation of the extension agent. The MIB tree consists
of scalar as well as table objects.
3. Creating the extension agent/extending the MIB:
Implementation of the extended agent is done by treating separate scalar
objects as different implementation modules. A table is handled in a
single implementation module by considering the objects as related
scalar objects in the same subtree. The actual implementation is done
using the mib2c tool as well as hand coding. C files are generated along
with header files on using the mib2c. The core work of implementing the
module is done in the C code file. Currently, the 802.11 MIB contains
198 objects. We are extending the support to only a few of these
objects.
4. Creating the wireless API:
The actual fetching of the device parameters are done using the ioctl()
calls. We are implementing a separate C module which interacts with the
device driver in retrieving all the required information.
5. Testing :
Testing of the extended agent would be done using the standard SNMP
commands like GET, SET and GETNEXT. Tools like GetIf and OIDview would
be used for the same.
************************************************************************
*****************************************
Actually we are struck now . We have that IEEE 802.11 MIB with
us . But our doubt is , which configuration file should be used
with mib2c. ??? I mean among 'mib2c.raw-table.conf' , -
'table_data', 'container' and
'tdata','iterate_access','mib2c.mfd.conf' which one should we use
with mib2c .
Did anyone try to extend the IEEE 802.11 MIB support for Net-SNNMP
...?? please respond .
Thanks & Regards,
Dhannya Chandran.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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
