Thank you for your reply. Another post on the users mailing list helped me fix my issue. To make a long story short, changing this line in "snmpd.conf",
rocommunity public to rocommunity public 0.0.0.0 fixed my problem. I'd like to update this in the wiki - how do I go about it? (No need to let anyone else waste a whole weekend...) Also, my snmpd.conf file was auto-generated by the "snmpconf" utility. Can this be classified as a bug? -Abraham Varricatt On Fri, Sep 3, 2010 at 7:04 PM, Wes Hardaker <[email protected]> wrote: > > I'd start by running both the agent and your tools with -d, which shows > when packets are received. Then you can see if the agent is actually > receiving something. > > It's also possible (likely) that agent is actually receiving the > requests but discarding them since they're not authorized (and running > the agent with -Dvacm will help you check that). > > I actually suspect that the 'sockstat' program is incorrectly marking > the port as closed. UDP doesn't operate in a "LISTEN" mode like TCP > does. I have this suspicion that sockstat is getting confused about the > port's status. > > -- > Wes Hardaker > Please mail all replies to [email protected] > ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
