If there's interest, I have a patch that allows communities of the form "community@context" to be treated by the snmp agent as separate community and context values, eliminating the need to define each combination as a valid community, and use com2sec to do the mapping.
I hadn't upstreamed it previously because it would change the behavior for anyone who had an "@" in their community string. Obviously giving it a configuration file entry to turn this behavior on would probably address that concern. Bill On Thu, Apr 21, 2022 at 3:41 PM Wes Hardaker via Net-snmp-coders < net-snmp-coders@lists.sourceforge.net> wrote: > Paban Agarwalla <pabanagarwa...@gmail.com> writes: > > > We are using to Netsnmp to collect statistics from our device. > > > > We are registering multiple subagents with the same set of oids. > > > > can i get all sub agent statastics using the same oid with v2c/v1 snmp > > host? > > The only way to deal with problems like that is to use SNMPv3 contexts, > where each context can map to a different subagent with overlapping OID > registrations. You can make v1/v2c communities to v3 contexts using the > com2sec configuration tokens if you wish. > > -- > Wes Hardaker > Please mail all replies to net-snmp-coders@lists.sourceforge.net > > > _______________________________________________ > Net-snmp-coders mailing list > Net-snmp-coders@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders >
_______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
