Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#1411 Docu. snmpd.conf proxy for snmpv1

proxy-override-etc
closed
Thomas Anders
3
2013-01-25
2005-08-01
schbach
No

net-snmp-5.2.1
Windows NT4
see snmpd.conf.html
proxy [-Cn CONTEXTNAME] [SNMPCMD ARGS] HOST
OID [REMOTEOID]
...
Then you can use "snmpwalk -n contextname1" to
walk one
remote proxied agent and "snmpwalk -n
contextname2" to walk another, assuming you
are using SNMPv3 to talk to the proxy (snmpv1 and
snmpv2c context mappings aren't
currently supported but might be in the future).
...

Please change the text to:
snmpv1 is possible, with com2Sec mapping.

(I thing snmpv2c is possible too, but I have not tested
this)

My test ist running with this snmpd.conf:
createUser v1AdminHost2 MD5 authadmin
proxy -Cn ContextHost2 -v 1 -c public localhost:161 .1.3
com2sec -Cn ContextHost2 v1AdminHost2 default
PublicHost2
group RWgroup v1 v1AdminHost2
view all included .1
access RWgroup ContextHost2 any noauth exact all
all none

I have start snmpd.exe with:
snmpd.exe -d -c snmpd.conf udp:1161

The request is:
snmpwalk.exe -v 1 -c PublicHost2 -r 0 -t 3
127.0.0.1:1161 .1.3.6.1.2.1.1.1

The result is the object from the original SNMP agent
under windows on port 161.

Discussion

  • Thomas Anders
    Thomas Anders
    2005-08-19

    Logged In: YES
    user_id=848638

    Thanks for the report. Are you willing to supply a patch for
    man/snmpd.conf.5.def against current CVS?

     
  • Dave Shield
    Dave Shield
    2005-12-01

    Logged In: YES
    user_id=88893

    The 'snmpd.conf(5)' man page in the upcoming 5.3 release
    will correctly describe the use of non-default contexts
    with community-based SNMP requests