When i am sending data packet from node a to node b why is b node relaying the message back and forth.It shudnt do that .

[Brijesh]

When i am sending data packet from node a to node b why is b node  relaying the message back and forth.It shudnt do that .

 I just have 2 nodes in the current setup. Node b is recieving the message but still its relaying

why is that.how to fix that. If u suggest i change ttl thats fine but once the message reaches the destination it shudnt relay forward. 

I am using latest sdk fr mesh with nrf52840 and 842 boards.

3431880>, network.c, 322, ----- Relaying Packet 30 -----
<t: 3447167>, network.c, 322, ----- Relaying Packet 30 -----
<t: 3447925>, network.c, 322, ----- Relaying Packet 30 -----
<t: 3463387>, network.c, 322, ----- Relaying Packet 30 -----
<t: 3464265>, network.c, 322, ----- Relaying Packet 30 -----
<t: 3480288>, network.c, 322, ----- Relaying Packet 30 -----
<t: 3480944>, network.c, 322, ----- Relaying Packet 30 -----
<t: 3496175>, network.c, 322, ----- Relaying Packet 30 -----
<t: 3497079>, network.c, 322, ----- Relaying Packet 30 -----
<t: 3583988>, network.c, 322, ----- Relaying Packet 30 -----

[Bjørn Kvaale]

Are you sending a unicast or group message from node A to node B? From your logging, it seems that you may be sending a group message from the client to the server & then the server relays the message back to the client. How many times does the message get relayed from the server every time you send a message from the client?

An easy solution would be to send a unicast message from the client to the server. That way, the server will not relay the message further if the unicast message is intended for itself. You can easily do this in the nRF Mesh app by setting the publication address of the client to the unicast address of the server. Remember to bind the same app key to the client & the server. This Youtube video could be helpful.