On Wed, 09 Mar 2005 12:25:01 -0500 Olsson, wrote: OS> RS> I'm also unclear on whether or not using tcp would create/tear-down a OS> RS> connection for each trap, or establish the connection once. OS> OS> Ok, I implemented a SNMP trap receiver (minimal version of snmptrapd) OS> and found that the connection does indeed get made and torn down each time OS> a trap is sent when using the forward directive in snmptrapd.conf. Anyone OS> know if there is a way to make the connection persist?
Probably not as is, but it would be a reasonable feature to add. OS> For now I'm using UDP over localhost which I guess should be suffice, OS> but TCP would be better since I wouldn't want a trap to show up in the OS> snmptrapd log, but not in my management application. Any thoughts on the OS> UDP approach over localhost? That should be fairly reliable. I think it would be a fairly extreme condition where a trap would be lost. Mainly, you'd have to make sure your application read the traps fast enough, so that the buffer doesn't get full. You would definitely want to look into the new socket buffer size options to try and maximize them, reducing the chances of packets being lost. -- Robert Story; NET-SNMP Junkie Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
