On 14 August 2012 21:06, Sorrell, Al <[email protected]> wrote:
> Anyone seen anything like this before using snmptrap? I have an app running on
> Solaris8 NET-SNMP 5.4.2.1 (I know it's old - that system is going away) which 
> seems to
> work correctly, but under Solaris 10/NET-SNMP V5.6.1rc2 it fails. It appears 
> that snmptrap
> is using the destination as the source and leaving the destination blank 
> according
> to the -d packet dump.


I don't think that this is the problem - I've had a quick look at the 5.6.x code
that displays the source/destination addresses, and this appears to be
hardcoded to be    "remote -> local"   (i.e. the correct order for dumping
*received* traffic, but the wrong order for sending).

The thing that springs out in your dump is the port number being used.

The 5.4.x version is fine:
> Sending 110 bytes to UDP: [0.0.0.0]->[172.22.227.66]:162

but the 5.6.x version is using the 'query' port of 161
> Sending 111 bytes to UDP: [172.22.227.66]:161->[0.0.0.0]:0

It's possibly worth specifying the port explicitly (i.e. $trap_dest:162)
[Though that doesn't explain why this should be necessary]


Give that a go, and let us know if it makes a difference

Dave

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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

Reply via email to