On 09/04/2008, Joan Landry <[EMAIL PROTECTED]> wrote:
> >>If you are using "com2sec", then this relates to SNMPv1/2.
>
> What should I use for SNMPv3?
Take a step back.
Think about what the "com2sec" directive is doing.
It's taking the only administrative information that is available
in SNMPv1/
"context1" to the 2nd configuration. Also, the 2nd
configuration did not result in a new vacmContextName being added to the
vacmContextTable.
Thanks,
Joan
-Original Message-
From: Mike Ayers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 8:34 PM
To: Joan Landry; net-sn
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Joan Landry
> Sent: Wednesday, April 09, 2008 1:17 PM
> >>If you are using "com2sec", then this relates to SNMPv1/2.
>
> What should I use for SNMPv3?
>
> I created the following 2 users one has a context name
> defined the
esday, April 09, 2008 4:22 AM
To: Joan Landry
Cc: net-snmp-users@lists.sourceforge.net
Subject: Re: Configuring a new vacmContextName
On 08/04/2008, Joan Landry <[EMAIL PROTECTED]> wrote:
> I would like to know how to add a new vacmContextName to netsnmpd.
>
> I added the following user
&
On 08/04/2008, Joan Landry <[EMAIL PROTECTED]> wrote:
> I would like to know how to add a new vacmContextName to netsnmpd.
>
> I added the following user
> com2sec -Cn context1 v3user1 default v3user1
> access groupd context1 usm authPriv exact readview writeview notifyview
If you are usin
I would like to know how to add a new vacmContextName to netsnmpd.
I added the following user
com2sec -Cn context1 v3user1 default v3user1
access groupd context1 usm authPriv exact readview writeview
notifyview
This does not work as acces is denied when I do snmpwalk. If I remove
the co
