net: lwm2m: Fix blockwise Ack NUM calculation
After the PR #85000 the calculation of NUM field of Block 1 option on CoAP Ack packet started to advance to next packet block. We should not update the ctx->current field because it is used for calculating the NUM field in response packet. It should point to beginning of the payload, so the response is correct. Leshan server don't seem to care about this, but Coiote does. Signed-off-by: Seppo Takalo <seppo.takalo@nordicsemi.no>
This commit is contained in:
parent
1a7642b291
commit
252f8fefe0
1 changed files with 0 additions and 3 deletions
|
@ -1057,9 +1057,6 @@ static int lwm2m_write_handler_opaque(struct lwm2m_engine_obj_inst *obj_inst,
|
||||||
return ret;
|
return ret;
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
if (msg->in.block_ctx && !last_pkt_block) {
|
|
||||||
msg->in.block_ctx->ctx.current += len;
|
|
||||||
}
|
|
||||||
opaque_ctx.offset += len;
|
opaque_ctx.offset += len;
|
||||||
written += len;
|
written += len;
|
||||||
}
|
}
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue