Based on earlier questions and feedback about building snmp++/agent++ with SNMPv3 support, I’ve rebuilt them to include SNMPv3 support (removed the --disable-snmpv3 flag). I still wish to instantiate my agent as an SNMPv2c agent, therefore configuring community strings. Currently, I get a build failure because the related functions setting the read/write stings are #ifdef’d out when SNMPv3 support is included.
Is it expected that building the libraries with SNMPv3 enabled that therefore you can ONLY create an an SNMPv3 agent?
No, the is a misunderstanding. If you “normally” build SNMP++/AGENT++, you can a multilingual SNMP agent that supports v1,v2c, and v3 simultaneously.
However, the methods to configure SNMPv1/v2c with the --disable-snmpv3 flag enabled, are not available. Instead, use the SNMP-COMMUNITY-MIB and the methods of RFC3584 to define you communities for v1/v2c.
Ah ok thank you for correcting my misunderstanding. I’ve used the example ‘multiagent’ as a basis. I am currently not getting any response when making a v2c GET using the correct community string. The log is below - would really appreciate any help! (P.S. I am running AgentX if that makes a difference)