Re: Sending traps with dynamic destinations

2007-02-12 Thread Dave Shield
On 12/02/07, jin zhou [EMAIL PROTECTED] wrote: But I am afraid simply using : snmp_send( ss1, pdu ); snmp_send( ss2, pdu ); snmp_send( ss3, pdu ); can't send a trap with content pdu to different destinations ,because the routine snmp_send will free pdu automaticlly if succeed. Good point.

Re: Sending traps with dynamic destinations

2007-02-12 Thread jin zhou
Yes, it is a good idea of using snmp_clone_pdu to improve the efficiency of the codes.And because the num of trap receivers is not certain, so I use struct netsnmp_session *ss_head as a head of linked list,which is built before sending a series of traps and free at last.It seems like that

Re: Sending traps with dynamic destinations

2007-02-11 Thread jin zhou
Dear Dave, Thank you for your suggestions.But I am afraid simply using : snmp_send( ss1, pdu ); snmp_send( ss2, pdu ); snmp_send( ss3, pdu ); can't send a trap with content pdu to different destinations ,because the routine snmp_send will free pdu automaticlly if succeed.I have

Re: Sending traps with dynamic destinations

2007-02-09 Thread Dave Shield
[ First - *please* don't mail me privately, without copying any responses to the mailing list. I don't have the time or inclination to offer private, unpaid, SNMP consultancy. Keep discussions to the list, where others can both learn and offer advice. Thanks. ] On

Re: Sending traps with dynamic destinations

2007-02-08 Thread Thomas Anders
jin zhou wrote: I choose using API routines snmp_pdu_create(SNMP_MSG_TRAP2) and snmp_send(ss,pdu) to send traps,while the session peername and port can be specified.But i meet the troulbe:it always send traps on port 161,even through i use the codesession.remote_port= SNMP_TRAP_PORT;,while

Re: Sending traps with dynamic destinations

2007-02-08 Thread jin zhou
net-snmp 5.2.3 ,working on Linux,thank you! Thomas Anders [EMAIL PROTECTED] 写道: jin zhou wrote: I choose using API routines snmp_pdu_create(SNMP_MSG_TRAP2) and snmp_send(ss,pdu) to send traps,while the session peername and port can be specified.But i meet the troulbe:it always send traps

Re: Sending traps with dynamic destinations

2007-02-08 Thread Dave Shield
On 08/02/07, jin zhou [EMAIL PROTECTED] wrote: I choose using API routines snmp_pdu_create(SNMP_MSG_TRAP2) and snmp_send(ss,pdu) to send traps,while the session peername and port can be specified.But i meet the troulbe:it always send traps on port 161 Specify the destination as

Re: Sending traps with dynamic destinations

2007-02-08 Thread jin zhou
Cleared~! OMG,it is so easy to you,but i can't think about it,thank you very much! And is the method I use the best way of resolving the problem of dynamic trap receiver?If I meet these questiones of API using angain,how can I find out the error quickly by myself? Dave Shield [EMAIL

Re: Sending traps with dynamic destinations

2007-02-08 Thread Dave Shield
On 08/02/07, jin zhou [EMAIL PROTECTED] wrote: And is the method I use the best way of resolving the problem of dynamic trap receiver? Probably, yes. The alternative would be to manipulate the contents of the snmpNotifyTable and snmpTargetTable - but that would affect *all* traps sent by the

Sending traps with dynamic destinations

2007-02-07 Thread jin zhou
Dear Dave and all, Hi,I am sorry to interrupt you again becuase I have another trouble.I need to send traps to dynamic destinations which only can be determined when sending traps on IPV4,so the trap API routines 'send_easy_trap()' or 'send_v2trap' are not so effective because I am not