Hi dave Thanks for clarification. It works perfectly when I access the proxy with v3 and the remote agent with v3 aswell.
As I have an agent which only understands v2 with a specific community string I tried the following: (Just for testing proxy everything to the remote device) proxy -Cn context1 -v2c -c public remotehost .1.3 (the cstring 'public' is set up on the remote host) without any setup of com2sec, as - how I understand it - this is not needed here. Howewer calling the proxy with snmpget -n context1 -v3 -u user proxyhost sysContact.0 results in a timeout. calling the remotehost directly with snmpget -v2c -c public remotehost sysContact.0 works. Anybody nows what I do wrong? Thanks a lot Boris 2011/3/28 Dave Shield <[email protected]> > On 27 March 2011 13:29, Boris Zweimueller <[email protected]> > wrote: > > Instead of using an snmp v2 context (-c) > > The '-c' flag is used to specify the SNMPv2 (or SNMPv1) community string, > not the context. The concept of contexts was only introduced with SNMPv3. > > A community name can be mapped into a (non-default) context via the > com2sec field. This is not needed with SNMPv3, which includes the > context information automatically. > > > > Can the two 'remotehosts' be accessed independently with: > > snmpget -v 3 -n ctx_remotehost1 proxyhost sysContact.0 > > and > > snmpget -v 3 -n ctx_remotehost2 proxyhost sysContact.0 > > That should work - yes. > > Dave >
------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
