The set_value function used to process SNMPSET requests with integer data ignores the data value on the request and always uses a NULL value. This only impacts custom MIBs since all integer fields on the base MIBs are read-only.
The following change appears to correct this. src/core/snmp/msg_in.c src/core/snmp/msg_in.c.old 594,595c594 + en->set_value_a(request_id, &msg_ps->ext_object_def, + msg_ps->vb_ptr->value_len,msg_ps->vb_ptr->value); - en->set_value_a(request_id, &msg_ps->ext_object_def, 0, NULL); This was posted as bug #25636 on http://savannah.nongnu.org/bugs/?group=lwip _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
