On Tue, 2005-09-20 at 08:38 +0800, Ying Wang(CD) wrote:
> > With SNMPv1, a read-only community (not user) trying to
> > SET a value will result in a noSuchName error.
>
> I still think noSuchName is not a suitable error type for this case.
You are quite correct. It is not a particularly suitabl
TECTED]
Sent: 2005年9月19日 16:18
To: Ying Wang(CD)
Cc: net-snmp-users@lists.sourceforge.net
Subject: Re: the accurate description of the snmp error
On Mon, 2005-09-19 at 13:49 +0800, Ying Wang(CD) wrote:
> Where can I find the accurate description of the snmp error?
In the SNMP specification docume
On Mon, 2005-09-19 at 13:49 +0800, Ying Wang(CD) wrote:
> Where can I find the accurate description of the snmp error?
In the SNMP specification documents - RFC 1157 for SNMPv1,
RFC 1905 for SNMPv2c, RFCs 3414 and 3416 for SNMPv3/USM.
> Which error is right when a invalid user to acce
Where can I find the accurate
description of the snmp error?
Which error is right when a invalid
user to access mib, such as a SNMPv1 read-only user does a configuration, or a
unknown user read something?
Thanks very much for your help!
Errors definitions are extracted
Where can I find the accurate description
of the snmp error?
Which error is right when a invalid
user to access mib, such as a SNMPv1 read-only user does a configuration, or a
unknown user read something?
Errors definitions are extracted in
the file snmp.h for your reference
