Re: Failed sending V3 traps with auth using snmpNotifyTable

On 25/01/07, Michael Kirkham <mikek@muonics.com> wrote:
> > [SNMP_FLAGS_DONT_PROBE] 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.

Ummm...
One possibility would certainly be to have two session fields in the
snmpNotify{Mumble} structure.
An alternative might be to explicitly set the pdu->securityEngineID
in the PDU template when sending a trap.

[Again, without looking at the code. Not sure how practical that would
be in reality]

Dave

PS: Note this will probably be my last contribution for a while.
My better half's natal anniversary needs to take priority!

-------------------------------------------------------------------------
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