On 14/08/07, 하영훈 <[EMAIL PROTECTED]> wrote:
> case b)
> # this configuration file doesn't work for snmp SET request
> rocommunity ssul97
> rwcommunity ssul97
> When I use second snmpd.conf file, snmp agent returns "No access"
> response to my SET request.
>
> Are there any problems in my snmpd.conf file?
Yes.
From the snmpd.conf(5) man page:
In each case, only one directive should be specified for a given...
... community string. It is not appropriate to specify both
rocommunity and rwcommunity directives referring to the same ....
... community settings. The rwcommunity directive provides all the
access of rocommunity (as well as allowing SET support).
You've said that "ssul97" should have read-only access.
So that is what the agent is applying.
Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
