Hi Peter,
The command responder is not setting the request-id correctly in the
REPORT PDU.
This is causing the issue on the SNMP4J side. Nevertheless, SNMP4J
should behave more
robust and should call the response listener after the request times out.
I will add a corresponding unit test for
Hi Ron,
There are two cases you have to differentiate:
1. You have already localized passphrases for your target:
Then use USM.addLocalizedUser(...)
2. You have plain text passphrases for your target:
Then use USM.addUser with a UsmUser that had been created with a
Hi,
I have read about localized keys and understand the concept. I don't yet
understand how to implement them and use them with SNMP4J.
If anyone has the time to briefly share how to do this I would greatly
appreciate it.
Ron
___
SNMP4J mailing list
Hi Peter,
Sorry, my statement in my previous message was wrong. Please ignore it,
because
setting the request-id field to 0 in a REPORT PDU is OK: If the request
was encrypted
the command responder would have no chance to decode the request-id field.
That's is why the command generator has
