In addition to the SNMPv2->SNMPv1 error code mapping issues idenified by
another posting, it is also true that the readOnly SNMPv1 code should
*NEVER* be generated. A read-only object is not visible in the MIB view
for a SET request and so noSuchName is the correct response. The readOnly
error code was initially intended to handle this case, but I think the
development of the access control/MIB view mechanisms made it redundant
even before the first V1 documents became standardized. I am sure that the
V1 documents identify and explain this.
Hope this helps,
Robin
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.