On 16 June 2011 13:05, Jordi Lopez <[email protected]> wrote: > When you send your trap you do itĀ from a random port to port 162 in the > receiver. > And the receiver sends back the ack from port 162 to the same random port ....
The receiver *should* use port 162 as the source for the response - yes. That's why I suggested this as a possible solution to Dattaram's problem. But that relies on sensible behaviour by the trap receiver. I've got a vague recollection of complaints that at some point, snmptrapd didn't work this way, and we had to fix it. Which is why I asked what version of snmptrapd Dattaram was using. (Andif it's someone else's trap receiver software, then that's something to check with the relevant vendor) Dave ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
