RE: EXTERNAL: Re: 5.7.3 | snmptrap not populating EngineBoots or EngineTime for snmp v3 traps

Denis Hainsworth wrote:
> #2899 - snmptrap bug
> #2900 - snmptrapd bug
> 
> -denis

Denis,

Sorry for the delayed response.  I haven't had time to look at this until recently.
 
Regarding the snmptrapd bug you created (#2900): I think this is working as expected.
I compiled and tested v5.7.3 from git source, and snmptrapd is certainly validating the
msgAuthoritativeEngineBoots value.  Whenever I send a trap with a boot value that is
the same or greater than the last, the trap is received.  If I send a trap with a
boot value that is less than a previous trap, I get the following error from snmptrapd:
 
usm: USM processing begun...
usm: match on user testuser
usm: Verification succeeded.
usm: Remote boot count invalid.


As for the msgAuthoritativeEngineTime values, if the delta from the previous trap
is large enough, the trap is also rejected by snmptrapd.  Here's the message you
will see (with -Dusm):

usm: USM processing begun...
usm: match on user testuser
usm: Verification succeeded.
usm: Message too old.

I haven't dug into the code deep enough to find the threshold, but I suspect it's
following the RFC.

The end result is that I think that bug #2900 should be closed as invalid.

Please let me know your thoughts.


-Drew