> "Password"
>This really belongs in the /var/net-snmp/snmpd.conf file
Actually I am running server as
#/usr/local/sbin/snmpd -C -c "/root/snmpd.conf" -fV
/var/net-snmp/snmpd.conf says don't edit the file
>The one thing that I'd suggest would be to have this *as well* as the origin
On 19 July 2012 15:55, wrote:
> I am using VACM approach
> My snmpd.conf file without contextname
> createUser V3User MD5 "Password"
This really belongs in the /var/net-snmp/snmpd.conf file
> com2sec V3User default community
This is not relevant for SNMPv3
It's concerned with
>> How can I properly configure the context name on the server side?
>See the section covering "rouser" and "rwuser" in the snmpd.conf(5) man page -
>this comes in the section headed "Traditional Access Control"
>(or the description of "access" in the section "VACM Configuration"
>if you're usi
On 19 July 2012 11:08, wrote:
> I have an application which worked perfectly in SNMpv3 in AuthnoPriv mode.
> There is a requirement like a “context name” is to be added to the snmp
> requests which is sent by the application.
> I have only one snmpd server which sends responses back to this appl
Hi,
I have an application which worked perfectly in SNMpv3 in AuthnoPriv mode.
There is a requirement like a "context name" is to be added to the snmp
requests which is sent by the application.
So I have filled the contextName and contextNameLen in netsnmp_pdu with the
proper values.
Then copied
