On tor, 2007-03-08 at 08:23 +0100, Magnus Fromreide wrote: > On ons, 2007-03-07 at 09:13 +0000, Dave Shield wrote: > > > > 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. > > I thought the bug you are thinking of, and the one Thomas referred to in > his mail, was that snmptrap sends to port 161. > > When I tries with snmpd from HEAD this seems to work, but I can't access > eventual config in earlier messages in this thread since the SF mail > list server gives me 'Internal Error', but I am very interested in why > your trap got sent to port 161.
Ok, the problem was that I had missed the snmp_open in the trapsess directive so it used the wrong application and thus got the wrong port. I have now updated patch 1620424 to correct that snmp_open as well. /MF ------------------------------------------------------------------------- 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
