[ First - *please* don't mail me privately, without copying
any responses to the mailing list. I don't have the time
or inclination to offer private, unpaid, SNMP consultancy.
Keep discussions to the list, where others can both learn
and offer advice. Thanks. ]
On 23 February 2011 12:56, Oleg Litvinov <o...@gomelpromstroy.by> wrote:
> #snmpset -v 2c -c private 172.22.0.1
> 1.3.6.1.4.1.8072.1.5.3.1.2.1.3.6.1.2.1.2.2 i 1
> Error in packet.
> Reason: noAccess
Which shows that this *is* an access control problem.
> rocommunity private 172.22.0.0/16
> rwcommunity private 172.22.0.0/16
You've got the same community string set as both read-only, and read-write.
Why?
read-write allows reading and writing, so allows everything covered by
read-only.
But the "rocommunity" setting gets picked up first, and this
explicitly disallows
SET requests.
Use one or the other - not both,
It's also a bad idea to use "rwcommunity" with a well-known community
string such as "private" or "public". That might be just about OK on a
completely isolated private network, but anything connected to the internet
should use a secret community string, or (better) use SNMPv3
Dave
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
