I'm happy to share the changes I made to the library, but they were
minimal. Really just:
(a) adding this hook to snmp_api.c to allow response packets to be
fed back in...
// add hook to allow this to be called from outside
void snmp_sess_receive_packet(void *sessp, u_char *packet, int
Neil Mckee writes:
> You are very welcome. Let me know if you want to discuss any of the
> particulars.
Well, the biggest question in my mind is: are you willing to contribute
the patches back?
It's unclear if any of them break backwards compatability (which we
always strive for), but
You are very welcome. Let me know if you want to discuss any of the
particulars. For example, it seems like snmpusm.c is also trying to
please the SNMPv3 user MIB by getting everything in the right order
for GETNEXT there. So my use of a hash-table breaks that, but that's
OK for me because I am
Neil Mckee writes:
> This may have been covered many times before, but just in case it
> helps someone, here is a summary of my experience with using net-snmp
> in a large network.
Thank you for the very useful list of changes.
--
Wes Hardaker
Please mail all replies to
This may have been covered many times before, but just in case it
helps someone, here is a summary of my experience with using net-snmp
in a large network. Specifically, I use it to talk to thousands of
SNMPv2 and SNMPv3 agents using just one UDP socket in a process that
runs continuously.
The
