[#196] Documentation for snmp_auth to explain list emulation of "community"

This commit is contained in:
Oliver Gorwits
2015-02-04 21:58:36 +00:00
parent e99f5ee410
commit 67559e8d3f
2 changed files with 10 additions and 4 deletions

View File

@@ -417,7 +417,8 @@ configuration.
snmp_auth:
- community: public
- communtiy: mycommunity
- community: publictwo
- community: mycommunity
write: true
- community: mycommunity2
read: false
@@ -442,9 +443,13 @@ configuration.
only:
- 2001:db8::/32
For SNMPv1 and SNMPv2, only the C<community> key is required. You can add
C<read> and/or C<write> restrictions, and an IP restriction using C<only>.
Giving the stanza a C<tag> name is optional, but recommended.
For SNMPv1 and SNMPv2, only the C<community> key is required. Unlike the
global C<community>/C<community_rw> setting, this is not a list but a single
item. To emulate their list behaviour, have multiple entries at the top
C<snmp_auth> level, as in the example above.
You can add C<read> and/or C<write> restrictions, and an IP restriction using
C<only>. Giving the stanza a C<tag> name is optional, but recommended.
For SNMPv3 the C<tag> and C<user> keys are required. You can add C<read>
and/or C<write> restrictions, and an IP restriction using C<only>. Providing