On 17.02.21 15:48, Wes Hardaker wrote:
Harald Krammer writes:
If an SNMPv3 node is missing, the function is blocked.
What function is getting blocked? Anything in our library should return
with a timeout error just like v1/v2. Yes, the engineID won't be
retrievable but it shouldn't cause
Harald Krammer writes:
> If an SNMPv3 node is missing, the function is blocked.
What function is getting blocked? Anything in our library should return
with a timeout error just like v1/v2. Yes, the engineID won't be
retrievable but it shouldn't cause anything to hang indefinitely.
--
Wes
Hello !
I use the SNMP client on a small embedded system to generate a summary
message for around 150 SNMP-Server nodes (only SNMPv1/v2). This works
flawlessly and only requires one thread through the traditional API.
Now I should also support snmpv3. That works too, but...
If an SNMPv3
