Re: Failed sending V3 traps with auth using snmpNotifyTable

This is a discussion on Re: Failed sending V3 traps with auth using snmpNotifyTable within the SNMP Users forums, part of the Networking and Network Related category; On Thu, 25 Jan 2007, Dave Shield wrote: > On 25/01/07, Michael Kirkham <mikek@muonics.com> ...


Go Back   Usenet Forums > Networking and Network Related > SNMP Users

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 01-25-2007
Michael Kirkham
 
Posts: n/a
Default Re: Failed sending V3 traps with auth using snmpNotifyTable


On Thu, 25 Jan 2007, Dave Shield wrote:

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


Sure, I think one of my suggestions for fixing it was to do that in
send_trap_to_sess(), since that's where the template pdu gets duplicated
prior to doing session-specific stuff to it. Maybe I should just submit a
patch that does that as a suggested solution. Only reason I didn't do so
is there are a bunch of feasible approaches to fixing it and I'm not sure
what would be most acceptable. :)

But, ah, what the heck: patch # 1644280 submitted. Works for me.

--
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
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 05:04 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0