On Thu, 4 Mar 2010 00:50:04 -0500 Robert Story <rst...@freesnmp.com> wrote:
> On Tue, 2 Mar 2010 09:13:29 -0800 Stephen wrote: > SH> > I suspect you're putting clientaddr in snmpd.conf instead of snmp.conf. > If you > SH> > want to do that, you have to prefix it for it to be recognized as a > snmp.conf > SH> > token.. e.g. > SH> > > SH> > [snmp] clientaddr 192.168.1.99 > SH> > > SH> > If that's not the case, further debugging is needed... > SH> > SH> I put it in snmp.conf. It is a bug, see the patch. Please apply. > > I see the patch. It allows clientaddr to be in snmpd.conf without the [snmp] > prefix. But clientaddr is a snmp token, and does work in snmpd.conf when > properly prefixed. Have you tried putting address (source address) in snmp.conf and generating a trap. It didn't work with 5.4.2.1. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
