On 5 February 2010 00:50, Mike Ayers <mike_ay...@tvworks.com> wrote: > > Does your firewall have port 162 open? > Have you tried sending to 127.0.0.1 > (Same machine for send and receive, correct?)?
But surely this would only affect whether the trap was *received* by snmptrapd? Mike(B) has said that turning on debugging on the client side indicates that the notification was never actually sent in the first place. I'm inclined to agree that this points the finger at a problem with the snmptrap command itself. Dave ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ 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/listinfo/net-snmp-users
