Hi Frank,
I think it’s not a problem with engine ID because when the noAuthNoPriv SNMPv3
trap is sent then the engine ID is also used and when I set incorrect engine ID
then the noAuthNoPriv trap is not received.
I have to use trap messages in my project, not INFORM messages.
Best regard
Hi Michael,
I guess you need to check your SNMPv3 engine ID configuration (i.e. use unique
SNMPv3 engine IDs for all SNMPv3 entities) when you test using SNMP4J only.
In addition, when using the NET-SNMP snmptrap or any other notification sender
with the SNMP4J trap listener or any other notific
Michał Tarczyński writes:
> I have a problem with receiving SNMPv3 authPriv traps on my own Java
> trap receiver.
So I don't *know* what your particular problem might be; but I can
recommend a few things to look at:
1) try INFORMs instead of TRAPs and see if you get more interesting
results.
2
Hello,
I have a problem with receiving SNMPv3 authPriv traps on my own Java trap
receiver.
When using snmptrap command on the Linux terminal with authPriv option then
the trap is never received on my Java trap receiver regardless of which
authentication is used: MD5, SHA or SHA-256. Only if th
