Per https://tools.ietf.org/html/rfc3416#section-4.2.6, "The first two
variable bindings ... are sysUpTime.0 and snmpTrapOID.0". Your trap
contains sysUpTime.0 and snmpTrapEnterprise (with no instance ID, making it
invalid anyway). So, snmptrapd is probably just discarding it because it
is malform
Hi Marian,
I do not have an answer, though two minor things I wanted to note:
* You are sending packets from a “privileged” port 162 rather than an ephemeral
one
* Well-formed TRAP message should include a bunch of well-known OIDs at fixed
positions of the PDU (refer to SNMP RFCs for details)
We have a small device that send a trap on events I have configured
anmptrapd to pass traps generated manually but snmptrapd doesn't pass
the events generated by our devices the event doesn't show up when run
with -d so I'm guessing it's some thing fundamental. The following is
the wireshark trace
