On Thu, 23 Dec 2004 12:49:20 -0800 [EMAIL PROTECTED] wrote:
WC> >WRB> Would you be more supportive of one of the handlers, or of an
WC> >extension WRB> of the if-mib implementation code?
WC> >
WC> >An extension of the if-mib code is only appropriate if the interface is to
WC> >appear in the ifTable and ifXTables. What are you trying to do with the
WC> >device driver? What MIB are you implementing?
WC>
WC> That information was presented in the email that Wes clipped. Yes, the
WC> interface, I expect, will show up in the if-mib. After all, it is a
WC> wireless ethernet adapter. I am implementing the 802.11 MIB.
Ok. The if-mib gets all its data from the kernel. So if your driver does the
right thing with the kernel, it should show up in the if-mib tables.
WC> In any case, I need addess to the device driver, for how else am I to get
WC> management information into and out of the device in response to an SNMP
WC> get or set request?
WC>
WC> The answers to my questions regarding the specific means to interface with
WC> a device via SNMP are sure to be more generally valuable to other users
WC> of the toolkit.
WC>
On Thu, 23 Dec 2004 13:02:33 -0800 [EMAIL PROTECTED] wrote:
WC> interface is a NIC (the hardware part of 802.11), it will show up in the
WC> if-tables. The if-tables don't support the 802.11 MIB, so the if-mib code
WC> is not the place to provide for 802.11 MIB management information support
WC> via SNMP requests. Yet, the if-mib code does present a tantilizing option
WC> for 802.11 MIB support.
I think it'd be best to keep the two separate. Leave the existing if-mib to
kernel (well, /proc + ioctl) interface as is, and add a separate module (or
modules) for the 802.11 support.
WC> I will give great consideration to this option, iff (in the mathematical
WC> sense) I can get from you a little bit of hand-holding in the use of the
WC> code thereby generated.
That's the idea. In the process, we might be able to polish up the
documentation to reduce (or eliminate) the handholding.
This tutorial is a good place to start:
http://www.net-snmp.org/tutorial/tutorial-5/toolkit/mfd/index.html
I would also recommend grabbing 5.2.1.pre1, as there have been a few fixes to
the mfd templates.
And To get a pseudo-todo list, try this command in directory with the
generated code:
grep -n "TODO:" *.[ch] | sed 's/\([^ ]*\) \(.*\)TODO\(.*\)/\3 (\1)/' | sort -n
Key:
:o: Optional
:r: Recommended
:M: Mandatory
:A: Advanced users
--
Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users>
You are lost in a twisty maze of little standards, all different.
-------------------------------------------------------
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
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
