Hi,while working with AgentX++ and net-snmp V5.5 I fount the following error:
The master agent set or expect the AGENTX_MSG_FLAG_NON_DEFAULT_CONTEXT bit set for response messages?
This is wrong!There is a comment at protocol.c which note this, but a view statements later, the flag is set?
#-------snip
/*
* Various PDU types don't include context information (RFC 2741,
p. 20).
*/
switch (pdu->command) {
case AGENTX_MSG_OPEN: // ok
case AGENTX_MSG_CLOSE: // ok
case AGENTX_MSG_RESPONSE: //FIXME! ck
case AGENTX_MSG_COMMITSET: //not tested
case AGENTX_MSG_UNDOSET: //not tested
case AGENTX_MSG_CLEANUPSET: //not tested
pdu->flags &= ~(AGENTX_MSG_FLAG_NON_DEFAULT_CONTEXT);
}
#-------end
If the subagent build the response according to the RFC, the agentx
session run into time-out and will be closed after get or getnext
requests!
To be able to communicate with AgentX++ subagents a non-default context, I changed the protocol.c. But this unfortunately breaks the net-snmp snmptrapd when started as subagent with -x localhost options set.
Has someone ever work with net-nsmp and a non net-snmp subagent?With default context, everything works fine, but with a non default context, registrations works, but no access!
agentx-context-error.diff
Description: Binary data
agentx-context-error.log
Description: Binary data
It would be nice if this can be fixed according to the RFC. //regards Claus
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ 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
