Re: Failed sending V3 traps with auth using snmpNotifyTable

On Wed, 24 Jan 2007, Michael Kirkham wrote:

> On Wed, 24 Jan 2007, Dave Shield wrote:
>
>> Well, there is already a flag 'SNMP_FLAGS_DONT_PROBE'
>> to disable SNMPv3 engine probing. So the simplest approach
>> should be to set this in the prototype session structure, before
>> calling snmp_sess_add_ex.
>>
>> [That's without having looked at the code closely, mind - so
>> it might not be quite as easy as that]
>>
>> Dave
>>
>
> That should work to prevent probing a trap-only target and postpone probing
> of inform targets until an inform is sent. It wouldn't (alone) completely
> fix the issue of the traps being sent with the wrong Engine ID. If the target
> has a TagList whose tags indicate both informs and traps are to be sent, then
> it would still probe later and then use the Engine ID from the probe, cached
> in the session, to send the trap.

FYI - added some debugging output, and snmpv3_build() is indeed where the
Engine ID of the trap is getting set to that of the management station,
from the session, because it is not yet assigned in pdu->securityEngineID.

--
Michael Kirkham
President & CEO
Muonics, Inc.
http://www.muonics.com/

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?p...rge&CID=DEVDEV
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/...net-snmp-users