<?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>How RPi3 could decrypt Mesh packets</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/24757/how-rpi3-could-decrypt-mesh-packets</link><description>I managed to sniff Nordic mesh sdk 0.9.2 packets on raspberry pi 3 using &amp;quot;hcidump --raw&amp;quot;, and I can read the raw hex data of mesh packets of light control demo, but since these packets are encrypted I can&amp;#39;t understand or get use of this data, as I&amp;#39;m building</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 31 Aug 2017 11:08:00 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/24757/how-rpi3-could-decrypt-mesh-packets" /><item><title>RE: How RPi3 could decrypt Mesh packets</title><link>https://devzone.nordicsemi.com/thread/97500?ContentTypeID=1</link><pubDate>Thu, 31 Aug 2017 11:08:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:408fef32-9574-49f0-96cb-e9a12dab255f</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;To sniff packets using the PyACI-interface you need to add relevant cryptographic keys and addresses. In the light control example you will find these in the folder &amp;quot;examples/light_control/client/include/provisioner.h&amp;quot;:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;#define APPKEY {0x5f, 0x11, 0x6e, 0x6f, 0x72, 0x64, 0x69, 0x63, 0x5f, 0x5f, 0x73, 0x65, 0x6d, 0x69, 0x5f, 0x5f}
#define NETKEY {0x5f, 0x5f, 0x6e, 0x6f, 0x72, 0x64, 0x69, 0x63, 0x5f, 0x5f, 0x73, 0x65, 0x6d, 0x69, 0x5f, 0x5f}
#define APPKEY_INDEX (0)
#define NETKEY_INDEX (0)

#define GROUP_ADDRESS (0xCAFE)
#define PROVISIONER_ADDRESS  (0x0001)
#define UNPROV_START_ADDRESS (0x0010)
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;To use the build in BLE chip to sniff mesh activity you will have to implement the decryption yourself. It is unfortunately not possible to use mesh without encryption.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>