Unable to use SAR for both request and response using loopback with SDK For Mesh v3.2.0

[JonasJ]

During testing of SDK for Mesh v3.2.0 I noticed that it's no longer possible to send a request and response using SAR where both models are on the same element. This was possible in v3.1.0 as the loopback handling was done at the Access layer instead of the bearer layer, i.e. SAR was never involved before.

Assume that there is a client model that sends a message that requires the use of SAR, the server model receiving this responds with a message that also requires SAR. When sending the response the transport layer will fail with NRF_ERROR_INVALID_STATE in segmented_packet_tx() as there is already an ongoing TX session between the two addresses (The same addresses in the this case).

As the message has been received the SAR session should be considered finished and allow for the response to use SAR again, right?

Thanks.

[Mttrinh]

Hi,

We will have a look at this issue. As a workaround, you can instantiate client and server models on the two separate elements. 

[JonasJ]

Thanks. I'm currently using that as a workaround for now.

[gsegment]

Hi, I have the same issue. And I can't use separate elements as workaround due to network structure. Please, fix it.