
Juergen Schoenwaelder wrote:
It is a problem with the netsnmp output driver. If you grab the latest version from CVS, you will notice that the generated API has already changed. I expect even more changes to this output driver in the future to make it really useful.
Just updated my local tree, and it looks 'better' now.
[snap]
Thanks for your explanation about the __foo and _clientData structures, it's all clear now :)
Note that we now have a student who is going to improve the netsnmp code generator. So changes will be likely - but things will also get much better designed and tested.
Great! I assume he's (she?) following this list as well?
By the way, it's probably known already, but just to mention it - it seems that when using the Counter64 type in a MIB, the output from the netsnmp libsmi driver creates something like
CASE FOO: /* add code here */
CASE BLAH: return &bar;
Obvously this results in the agent returning the value for the wrong object, which is IMHO worse than returning zero or something like that.
I'll keep my local tree in sync with the IBR tree and for the time being focus on other parts of my implementation and get everything synchronized again when the API is more or less stabilized again. If you want me to test things or so, please let me know.
cheers, Remco.
-- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.