quot;
If I try any other model other than 3 it succeeds. But according to man
pages we are not allowed to use any other value than 3 (snmp v3).
BR,
Nikos
- Original Message -
From: "Thomas Anders"
To: "Nikos Balkanas"
Cc:
Sent: Tuesday, December 23, 2008 12:29 AM
Nikos Balkanas wrote:
> Server2:~/work/.../snmp/tutorial-> snmpget -v 3 -u 127.0.0.1
> sysUpTime.0
> snmpget: Unknown user name (Sub-id not found: (top) -> sysUpTime)
>
> But I give user-name ()! snmpd is 5.4.1 and os is Solaris 10.5. I
> also specify noAuthNoPriv in snmp.conf
The *agen
Hi,
I don't seem to be able to make snmp v3 authentication work. Command line
messages snmpget are very cryptic and not helpful:
Server2:~/work/.../snmp/tutorial-> snmpget -v 2c -c 127.0.0.1 sysUpTime.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3467) 0:00:34.67
Server
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dave Shield
> Sent: Thursday, January 31, 2008 1:40 AM
> On 30/01/2008, Mike Ayers <[EMAIL PROTECTED]> wrote:
> > This much I can tell you - communities were never
> (OK - the SNMPv3 specs talk in terms of "entities" ra
On 30/01/2008, Mike Ayers <[EMAIL PROTECTED]> wrote:
> This much I can tell you - communities were never intended as an
> authentication mechanism. They are, and always were intended to be,
> more like SNMPv3's context than anything else,
I sort of agree - at least in part.
The main diff
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Dave Shield
> Sent: Wednesday, January 30, 2008 7:59 AM
> On 30/01/2008, Buchupalli, Sasidevi
> <[EMAIL PROTECTED]> wrote:
> > So, per RFC, can I summarize:
> >
> > For SNMPv1, if the community string is incorrect, the agent
On 30/01/2008, Buchupalli, Sasidevi <[EMAIL PROTECTED]> wrote:
> So, per RFC, can I summarize:
>
> For SNMPv1, if the community string is incorrect, the agent should send
> an authenticationFailure Trap.
> For SNMPv2c, if the community string is incorrect, the agent should send
> an authenticationF
: Re: SNMP v3 - Authentication - Report PDU/Trap
On 25/01/2008, Karthick Babu <[EMAIL PROTECTED]> wrote:
> RFC 3414, section 3.2 (Processing an Incoming SNMP Message),
> point no. 6 says as follows :
> If the authentication module returns failure, then ...
> . a
On 25/01/2008, Karthick Babu <[EMAIL PROTECTED]> wrote:
> RFC 3414, section 3.2 (Processing an Incoming SNMP Message),
> point no. 6 says as follows :
> If the authentication module returns failure, then ...
> . an error indication (authenticationFailure)
> together with the OID and value
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Karthick Babu
> Sent: Thursday, January 24, 2008 11:45 PM
> RFC 3414, section 3.2 (Processing an Incoming SNMP Message),
> point no. 6 says as follows :
>
>
>
>
> If the authentication module returns failure, then
hi,
RFC 3414, section 3.2 (Processing an Incoming SNMP Message), point no. 6
says as follows :
If the authentication module returns failure, then the message
cannot be trusted, so the usmStatsWrongDigests counter is
incremented and an error indication (authenticationFailu
On 18/07/06, Tripathi Anoop-A18046 <[EMAIL PROTECTED]> wrote:
> I have a doubt regarding how net-snmp implements encryption and
> authentication (snmp v3 security) using SSL.
That's easy - it doesn't.
SNMPv3 does not use SSL - they are different security mechanisms.
The Net-SNMP library can
Hi
I have a doubt regarding
how net-snmp implements encryption and authentication (snmp v3 security)
using SSL.
The keys used for encryption and
authentication in SSL are derived from a pre-master secret, which is distributed
from client to server using RSA certificates, or Di
13 matches
Mail list logo
