On Sun, 29 Apr 2018 12:10:12 -0400 Bill wrote:
BF> BF> It's plausible that a workaround as simple as
BF> > BF>
BF> > BF> + /*
BF> > BF> + * We lie about being SNMPv3, because ...
BF> > BF> + */
BF> > BF> if (add_trap_session(main_session,
BF> > BF> AGENTX_MSG_NOTIFY, 1,
BF> > BF> - AGENTX_VERSION_1)) {
BF> > BF> + SNMP_VERSION_3)) {
BF> > BF>
BF> > BF> would work. (I picked V3 because you can't disable it,
BF> > BF> unlike v2c.) I also didn't feel like writing the rest of
BF> > BF> the comment :-)
BF> >
BF> > Hmm.. I'm not a fan of lying if it's avoidable... The fix
BF> > should be to recognize the agentx sessions properly...
BF>
BF> Well, the rest of the system doesn't know anything about
BF> agentx, it's all encapsulated inside of mibgroup/agentx. That
BF> certainly makes lying the easier solution.
I'd rather move the definition of AGENTX versions up into library
headers so we can test for it.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
