[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] SNMPv2 failed SetRequest response

From: Dirk Ziegelmeier
Subject: Re: [lwip-users] SNMPv2 failed SetRequest response
Date: Mon, 12 Sep 2016 12:32:22 +0200

Hello Marco,

I cannot check this at the moment, and the guy who actually wrote the code at my company is on vacation for more than one week...


Dirk Ziegelmeier * address@hidden * http://www.ziegelmeier.net

On Thu, Sep 8, 2016 at 4:17 PM, Marco Veeneman <address@hidden> wrote:


I'm facing a problem with SNMP again and I would like to hear your thoughts about it.

In <sometable>_get_instance, if no valid instance oid for a row is found, it returns SNMP_ERR_NOSUCHINSTANCE.

If a user requests to set an invalid table oid using SNMPv1, the SNMP agent responds with 'error-status: noSuchName (2)'.

This is OK.

If a user requests to set an invalid table oid using SNMPv2, the SNMP agent doesn't respond at all. It just drops the packet. 

This happens because of the following code in snmp_complete_outbound_frame() (at line 1366 in snmp_msg.c):

    if (request->error_status >= SNMP_VARBIND_EXCEPTION_OFFSET) {

        return ERR_ARG;


which stops further processing of the request.

It would be better if the SNMP agent would respond with a message with error-status set to some value. What would be the best solution here?


lwip-users mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]