Hello,
I have been looking for a way to use this module to enable snmpv3 only on some servers.
I found #56 which proposes a merged PR that prevents related entries in the VACM configuration.
I also found that one way to prevent the use of snmpv2 with cleartext community name is to remove these lines from Traditional Access Control
rocommunity public 127.0.0.1/32
rocommunity6 public ::1/128
This is however not done by the $snmpv2_enable => false parameter. And if the parameter ro_community is left undefined, it defaults to public. I have not found a way to not generate these lines with this module as it is, hence no way to disable snmp v1 and v2c.
Am I missing something obvious here?
Currently, my workaround is to use a huge random community string. I may try to provide a PR if I find the time for it.
Hello,
I have been looking for a way to use this module to enable snmpv3 only on some servers.
I found #56 which proposes a merged PR that prevents related entries in the VACM configuration.
I also found that one way to prevent the use of snmpv2 with cleartext community name is to remove these lines from Traditional Access Control
This is however not done by the
$snmpv2_enable => falseparameter. And if the parameterro_communityis left undefined, it defaults to public. I have not found a way to not generate these lines with this module as it is, hence no way to disable snmp v1 and v2c.Am I missing something obvious here?
Currently, my workaround is to use a huge random community string. I may try to provide a PR if I find the time for it.