Hi,
don't know if it's a negotiation but I think need to have the engineID set
in the inform message
I have appended a tarball with messages, conf,logs and pcap from where I
did run a similar test with snmpd and snmptrapd.
The conf files includes a bunch of other stuff not needed for this case,
Hi Anders.
Thank you for answering.
Is the engineID actually ever *negotiated*?
I had the understanding this was unilaterally configured, either
statically or automatically.
Is my understanding of this mechanism incorrect?
My reasoning for using informs in the first place was that the receiver
Hi Dag,
try to not set the engineID in the snmptrapd.conf and let snmptrapd and
Junos negotiate the engineID
createUser -e 0x80001234 authpriv2 SHA xyzzy188 AES xazzza18
->
createUser authpriv2 SHA xyzzy188 AES xazzza18
Looking at the pcap file snmptrapd sends the engineid = 80001f88., but
Hi.
I am trying to convince snmptrapd to receive snmp v3 informs from Junos
(Juniper Networks' BSD-variant on switches and firewalls). The idea was
to use informs rather than traps, so I could :
- have encryption in place.
- avoid having to update the snmptrapd config for every new device
