Replying to my earlier message I hadn't noticed this: In each case, only one directive should be specified for a given SNMPv3 user, or community string. It is not appropriate to specify both rouser and rwuser directives referring to the same SNMPv3 user (or equivalent community settings). The rwuser directive provides all the access of rouser (as well as allowing SET support). The same holds true for the community-based directives.
In the snmpd.conf documentation. I think that answers my question, setting both rwcommunity and rocommunity to the same thing is "not appropriate". Thanks for the help. Phil -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dave Shield Sent: 30 January 2009 11:03 To: Philip Mason Cc: [email protected] Subject: Re: FW: Unable to set the object from the scalar_int example 2009/1/30 Philip Mason <[email protected]>: > If I try to set it I get the following message: > > $ snmpset -c public -v 2c 10.0.0.27 1.3.6.1.4.1.8072.2.1.1.0 i 19 > Error in packet. > Reason: notWritable (That object does not support modification) How is the agent configured? In particular - what access control setting do you have? Note that the community 'public' is normally configured for read-only access, so wouldn't support SET requests. See the FAQ for more details. Dave -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
