I just wrapped together a gsnmp test package:
ftp://ftp.ibr.cs.tu-bs.de/pub/local/gsnmp/gsnmp-0.1.0.tar.gz
This package requires glib2 and compilation generates three libraries:
libgsnmp snmp protocol engine libgsnmpiana stubs for all IANA maintained MIB modules libgsnmpietf stubs for all published IETF MIB modules
There are some very simple test programs in the tools directory. It would be nice to get feedback about this. There are many things that could be done, such as:
- support for SNMP version 3 and perhaps TCP transport - more compatibility with the glib way of doing things - more intensive usage of new glib2 features - stubs for notifications and such - reduce size of the stubs
At the moment, libgsnmpietf.a offers 7674 stub entry points with a total size of 3521906 bytes (gcc compiled with -O2), which means an average stub size of roughly 460 bytes. I have some ideas on how to cut this down a bit, but probably nothing really dramatic. The point really is that the number of functions that fall out of all the MIBs is so huge. What really is needed are MIB annotations which help to produce fewer but more meaningful stubs.
I am working on an scli version which uses these libraries. I am not sure how I deal with the vendor specific stubs or unpublished stubs that scli needs. Ideally, there would be libgsnmpcisco or libgsnmpnortel but since it is difficult to get an overview of the vendor MIBs, the approach is probably to add them slowly when needed (and if the copyright allows to do so).
Anyway, it would be nice if people can check this out. Feedback on this is more than welcome.
/js
participants (1)
-
Juergen Schoenwaelder