On Thu, 4 Mar 2010 00:50:04 -0500
Robert Story <[email protected]> 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.
The documentation for snmp.conf (not snmpd.conf) says:
clientaddr [<transport-specifier>:]<transport-address>
specifies the source address to be used by command-line applica‐
tions when sending SNMP requests. See snmpcmd(1) for more infor‐
mation about the format of addresses.
This value is also used by snmpd when generating notifications.
I expect that if clientaddr is set in snmp.conf it will be used for
sending trap source address.
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
