if(req) {
removeFromTree(snmp->timeoutTree, req);
snmp_sess_receive_packet(req->target->sessp, msg->buf,
msg->len, (struct sockaddr *)&msg->peer, msg->peer_len);
}
}
On Fri, Oct 22, 2021 at 9:07 AM Wes Hardaker
wrote:
>
> Neil Mckee writes:
>
&g
lti-threaded then it seems like your hands are tied? I
certainly won't object if nothing changes.
On Mon, Oct 18, 2021 at 10:30 AM Wes Hardaker
wrote:
>
> Neil Mckee writes:
>
> > This may have been covered many times before, but just in case it
> > helps someone, here is
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 n
Hello All,
Sorry if this has been discussed already. I just thought I would share my
experience with trying to use just one client UDP socket for many SNMPv3
sessions.
Using just one socket was easy enough for SNMP v1 and v2 because I could use
the single-session API and multiplex all reques
