cannot do SNMPv3 set

[Frank Fock]

Hi Lukasz,

It seems that problems is the same as in one of the latest positings
to this list. You did not specify a context engine ID. That's why request
will fail. I just did a SET with MD5 and DES and it worked fine when
specifying the context engine ID.

May be the snmpSet example has to be improved for better report
handling...

Best regards,
Frank

Lukasz Szczepankowski wrote:

> Ever since I upgraded to snmp++v3.1.4a and agent++v3.5h I have been unable
> to perform set operations.  Gets work just fine, and I can also walk the
> mib, but I am not able to change any values (even though snmpSet returns
> SUCCESS as status on the set).  I am using SNMPv3 with both authentication
> and privacy.
>
> When I try to use the snmpSet (from consoleExamples, and having snmp
> compiled with debugging), I get a number of error messages.
>
> Here are some of these messages (generated by the agent):
> ErrorCode is 0
> Parsing contextEngineID with length = 0x0
> Parsing contextName with length = 0xa
> mp: received request message with zero length contextEngineID ->
> unknownPduHandlers.
> mpAddToCache: adding entry[0], msgID = 0xe0003, reqID = 0x3eb
> mpSendReport: Sending report message.
> ASN parse error (asn length too long)
> mpParseScopedPDU: bad header in scopedPDU.
> mp: Error while trying to parse  scopedPDU!
> pdu->reqid = 0x3eb
> ErrorCode was -1415 in mpSnmpParse
>
> And what is generated by snmpSet:
> ErrorCode is 0
> Parsing contextEngineID with length = 0x0
> Parsing contextName with length = 0x0
> mpGetFromCache: searching for msgID 0xe0003.
> mpGetFromCache: msgID found at entry[0].
> ***Receiving a ReportPDU ***
> mp finished (OK)
> receive_snmp_response:
> engine_id: (<data>), security_name: (<name>),
>  security_model: (3), security_level (1)
>  addtoengineidtable: (127.0.0.1)
>  Addr (127.0.0.1/1161), port (1161)
> receive_snmp_response requestID = 1003
> receive_snmp_response (uxsnmp.cpp) return SUCCESS
> received oid: 1.3.6.1.6.3.11.2.1.2.0 with value: 4
> SNMPv3: Invalid Message
> Set Status = Success
>
> This agent used to work just fine before I recompiled it with the new
> libraries (it compiled without any problems).  What could be the problem?
>
> Best Regards,
>
> Lukasz Szczepankowski