[ 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 06/03/07, Ricardo Marin Vinuesa <[EMAIL PROTECTED]> wrote:
> If I run snmpd -f -Le -d I see this:
>
> Sending 216 bytes to UDP: [192.168.175.247]:161
Aha!
The agent is sending the notification to port 161
(SNMP queries), rather than port 162 (traps).
That may well explain why snmtrapd isn't seeing anything.
Try using a snmpd.conf directive of the form:
trapsess ..... localhost:162
i.e. specifying the port explicitly.
I thought that this particular bug had been fixed with the
latest code, but apparently not.
Dave
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
