We have written our own AgentX C++ subagent library and are testing it against net-snmp snmpd.
We found the following:
If we try to send an agentx Notify-PDU containing the varbinds snmpTrapOid.0 = anyOid
.2.1 = [OctetString: "test" ]
and have the include bit cleared in all Oids then the response from net-snmp snmpd has the include bit set in the anyOid.
RFC 2741 (and 2257) states, in section 5.1, that the include
bit is used only in SearchRanges, so why is it toggled in this case?
We had to relax the check on the response in our library to make it work with net-snmp snmpd... but we still are a bit curious why the bit is tampered with at all.
/Andreas
(This question has been sent to the net-snmp-coders list 2004-06-08 without any answers posted to the list... we are still curious...)
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Net-snmp-users mailing list [EMAIL PROTECTED] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
