<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nRF Mesh Reply Attack Problem</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/108797/nrf-mesh-reply-attack-problem</link><description>Hi, 
 I am developing a vendor specific Mesh Model, I have already integrated the mesh model sucessfully to my network and is able to send data from each node by multiple hops. I am facing some issues from the mesh model. 
 
 1. During data transmission</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 05 Mar 2024 17:52:41 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/108797/nrf-mesh-reply-attack-problem" /><item><title>RE: nRF Mesh Reply Attack Problem</title><link>https://devzone.nordicsemi.com/thread/472314?ContentTypeID=1</link><pubDate>Tue, 05 Mar 2024 17:52:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7d0aae3c-094a-41b6-89d0-4e1750a89870</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Sorry for the delay. It took time for your answers.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regarding the first question: I can&amp;#39;t seem to reproduce their problem using the supplied config file. Is this the config you use on both ends? I tried resetting both the sender and receiver (both using the config supplied) several times (including resetting after the message sending but before RPL was stored in settings), but RPL functionality worked as expected. If you use a different config or firmware on one of the sides, this would be interesting to know. As of now, I can&amp;#39;t reproduce this issue with the information I have.&lt;/p&gt;
[quote user=""]My most vexing issue is even with 0 hops sending 240 bytes payload in a single send, I am facing a delay of &lt;span style="color:rgba(255, 0, 0, 1);"&gt;2 seconds&lt;/span&gt;[/quote]
&lt;p&gt;&lt;span&gt;&lt;span dir="ltr"&gt;The two seconds taken is expected with the default network transmit configuration.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The default number of time each Network PDU is sent: 3, &lt;span&gt;configured by&amp;nbsp;&lt;/span&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.2/kconfig/index.html#CONFIG_BT_MESH_NETWORK_TRANSMIT_COUNT"&gt;CONFIG_BT_MESH_NETWORK_TRANSMIT_COUNT&lt;/a&gt;&lt;span&gt;. Its default value is 2, meaning each segment is transmitted 3 times.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The default interval between network PDUs (&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.2/kconfig/index.html#CONFIG_BT_MESH_NETWORK_TRANSMIT_INTERVAL"&gt;CONFIG_BT_MESH_NETWORK_TRANSMIT_INTERVAL&lt;/a&gt;) : 20 (ms)&lt;/p&gt;
&lt;p&gt;Time spent sending each Network PDU: 60ms + advertisement delays&lt;/p&gt;
&lt;p&gt;&lt;span&gt;At the Lower Transport Layer, it will be broken into 20 Lower Transport PDUs (240/12=20, &lt;em&gt;segment buffer is&amp;nbsp;&lt;span dir="ltr"&gt;12 bytes long&lt;/span&gt;&lt;/em&gt;)&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Time spent sending 20 PDUs: 60ms * 20 PDUs + advertisement delays == 1200ms + advertisement delays&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span dir="ltr"&gt;With the default configuration, around 1,5 or so seconds (with no packet loss) is expected. To decrease this time, the easiest is to lower the network transmit count or the network transmit interval, keeping in mind the tradeoffs (lower transmit count could make things less reliable, and lower interval could cause more collisions)&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span dir="ltr"&gt;Regards,&lt;br /&gt;Amanda H.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Mesh Reply Attack Problem</title><link>https://devzone.nordicsemi.com/thread/471937?ContentTypeID=1</link><pubDate>Mon, 04 Mar 2024 05:49:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bf256f4e-0daf-4b9e-9f98-9d8ccd4f8245</guid><dc:creator>Rajeev K R</dc:creator><description>&lt;p&gt;Hi, &lt;a href="https://devzone.nordicsemi.com/members/amanda"&gt;Amanda Hsieh&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Please let me know if are there any solution to this&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Mesh Reply Attack Problem</title><link>https://devzone.nordicsemi.com/thread/471587?ContentTypeID=1</link><pubDate>Thu, 29 Feb 2024 14:45:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:74658781-9e74-41ab-b2df-dffe870c1961</guid><dc:creator>Rajeev K R</dc:creator><description>&lt;p&gt;I am using ncs version 2.4.2&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Mesh Reply Attack Problem</title><link>https://devzone.nordicsemi.com/thread/471562?ContentTypeID=1</link><pubDate>Thu, 29 Feb 2024 14:03:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3691b480-95e4-4741-bcfb-abafadbb662c</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Which NCS version are you using?&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Amanda H.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>