Unable to receive publish from server after unprovision and re-provision the same node

RE: Unable to receive publish from server after unprovision and re-provision the same node

Joakim Jakobsen — Fri, 20 Sep 2019 08:16:09 GMT

No problem.
Sorry about the confusion!

I'll close the case for now. If you have any further questions, you are welcome to create a new ticket.

Best regards,
Joakim

RE: Unable to receive publish from server after unprovision and re-provision the same node

Andrea Pieretti — Fri, 20 Sep 2019 06:14:43 GMT

Ok, Thank you for the feedback.

In my case, I will take the risk ;)

RE: Unable to receive publish from server after unprovision and re-provision the same node

Joakim Jakobsen — Fri, 20 Sep 2019 05:24:37 GMT

Hi again!

I might have misunderstood the feedback from our Mesh team.

[quote user="Joakim-Jakobsen"]Secondly, your suggestion of clearing of the replay list of the client after re-provisioning the server node is not valid. Because for a node which is provisioned, replay list should not be cleared manually.[/quote]

This was not quite correct from my side.

If your application is able to tolerate the risk of clearing the replay cache, you can clear the replay list manually. Note that this will have implications for the replay protection.

Best regards,
Joakim

RE: Unable to receive publish from server after unprovision and re-provision the same node

Andrea Pieretti — Wed, 04 Sep 2019 07:24:58 GMT

Thank you for the feedback.

I understand what happens, but waiting the correct sequence number from the server will cause the loss of many messagges.

If I can't clear the replay list, how can I fix this?

RE: Unable to receive publish from server after unprovision and re-provision the same node

Joakim Jakobsen — Wed, 04 Sep 2019 06:40:26 GMT

Got some feedback on this.

After you unprovision the server node, and reprovision it, this will cause sequence number on the server nodes to reset to zeros. Therefore all the messages sent by the server nodes will get filtered by the replay protection mechanism of the client node. This will continue to happen until the server node starts sending messages with a higher sequence number than the one stored in the client's replay list.

Secondly, your suggestion of clearing of the replay list of the client after re-provisioning the server node is not valid. Because for a node which is provisioned, replay list should not be cleared manually.

Best regards

RE: Unable to receive publish from server after unprovision and re-provision the same node

Andrea Pieretti — Tue, 06 Aug 2019 09:02:23 GMT

Ok,

please let me know when you've some news

RE: Unable to receive publish from server after unprovision and re-provision the same node

Joakim Jakobsen — Fri, 02 Aug 2019 12:27:10 GMT

Hi.

Sorry about the delay here.

Your question have been forwarded to our Mesh developers so that they can confirm this.
I'll get back to you when I have more information from them.

Best regards,
Joakim

RE: Unable to receive publish from server after unprovision and re-provision the same node

Andrea Pieretti — Wed, 31 Jul 2019 13:47:53 GMT

Any news?

RE: Unable to receive publish from server after unprovision and re-provision the same node

Andrea Pieretti — Thu, 25 Jul 2019 10:37:38 GMT

The Nordic app sets always a new address during provisioning.

However, I think that the problem is due by the m_replay_cache list, which is an 64 element array in my case.

Le me explain you:
in transport.c, the function transport_packet_in is called when e mesh network message is received.

Inside this function i''ve noted that replay_cache_has_elem returns false, because It find other element with the same source address and that not respect the Mesh Profile Specification below

/* According to Mesh Profile Specification v1.0 Section 3.8.8, we should discard packets
* coming IV indexes lower than a previous packet from the same source as well as
* packets on the same IV index with lower sequence numbers. */

The node reset cause the clear of the m_replay_cache list inside the function replay_cache_clear, called by the replay_cache_init function.

I think that a call of the replay_cache_clear function after a node provision can solve my problem

Am I correct?

Are there any hidden drawbacks?

RE: Unable to receive publish from server after unprovision and re-provision the same node

Joakim Jakobsen — Mon, 22 Jul 2019 14:28:27 GMT

Ok, I haven't been able to reproduce this using the Nordic nRF Mesh app. Are you seeing the same behavior if you use our app to "re-provision" the node?

RE: Unable to receive publish from server after unprovision and re-provision the same node

Andrea Pieretti — Mon, 22 Jul 2019 08:06:35 GMT

I'm provisioning the devices using the smartphone with our app, which is based on Nordic Libraries.

I see that this behaviour happens especially when I re-provision a node with the same address.

RE: Unable to receive publish from server after unprovision and re-provision the same node

Joakim Jakobsen — Wed, 17 Jul 2019 12:02:16 GMT

Hi.

I haven't seen this issue before. I wasn't able to reproduce it either.

How are you provisioning the devices? Are you using the nRF Mesh app or the static provisioning example in the SDK?

I can ask our Mesh team if they have seen something similar and if this is a known issue.

Best regards,
Joakim Jakobsen