This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RTOS/CC1352R: MAC layer Security

Part Number: CC1352R
Other Parts Discussed in Thread: CC1352P, CC1350, UNIFLASH, LAUNCHXL-CC1350, CC1310, CC1312R, LAUNCHXL-CC1312R1, , , LAUNCHXL-CC1352P1, LAUNCHXL-CC1310

Tool/software: TI-RTOS

Hi all,

i am using CC1352P _ FH mode- Collector - sensor 

i want to remove the security in the both side and do the communication and after that i have to see the data in the packetr sniffer,

because now security is enable and i can see the encrypted data but i can't see the actual data. so i need ot disable security and then i can check the details in the packet sniffer.

Anil.

  • Hello Anil,

    If you want to see de coded data on the sniffer, you will need to configure the security key on wireshark. This could be done on the advanced settings of the wireshark softeare.

    Regards,

    AB 

  • Hi AB,

    I searched on net and with wireshark software also, i am unable to get the advanced settings of wireshark.

    Can you please help me to get the advanced settings location and what changes i need to make there. so i can see the actual data on wireshark only.

    and here which key i need to put. So i am using example code for FH Collector mode. so where in coding i can get those keys so i can put here.

    Decrypted data i am getting like this, so can you please help me out to decrypt it properly.

    Thanks 

    Anil.

  • Try to use the following key.

    #define KEY_TABLE_DEFAULT_KEY {0x12, 0x34, 0x56, 0x78, 0x9a, 0xbc, 0xde, 0xf0, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00}

  • Hi YK,

    In the second window of previous thread only I can see the decrypted data?

    Because I kept that key with

    123456789abcdef00000000000000000

    123456789abcdef0

    123456789abcdef

    With that many keys I tried to catch data in actual format but I didn't get.

    What can I do now?

    Regards,

    Anil.

  • Can you try writing it in LSB format. That could be the problem.

  • Hi AB,

    12:34:56:78:9a:bc:de:f0:00:00:00:00:00:00:00:00

    00000000000000000fedcba987654321

    0fedcba987654321

    fedcba987654321

    0x123456789abcdef0

    0x123456789abcdef

    0x0fedcba987654321

    0xfedcba987654321

    That many keys i tried but still i am not getting data in normal format,

    what else i need to try?

     This also i did, like i know the short and extended address of collector and sensor. with this also i am not getting decrypted data. 

    What i have to do?

    Anil.

  • The process of setting up wireshark to be able to decrypt packets is described in the documentation of the packet sniffer 2. Make sure you have installed the latest version of the Packet Sniffer 2 and then go to 

    "<Install Directory>\Texas Instruments\SmartRF Tools\SmartRF Packet Sniffer 2\docs\SmartRF_Packet_Sniffer_2_User_Guide.html"

    Section: Decrypting SimpleLink 15.4 Data Packets using Security Key

  • hi Hector,

    can you see this,

    Because i am using REV A devices foe my applications. and now i can't change the rev of boards. so will it work that 1.7 version?

    link : http://dev.ti.com/tirex/content/simplelink_cc13x0_sdk_1_40_00_10/docs/ti154stack/ti154stack-users-guide/ti154stack/packet-sniffer.html

    this doc i used for doing all installation AND getting data. if i am wrong just send me new doc for installation and all.

    Anil.

  • You should be fine as long as you don't flash your Rev A sniffer device with the built firmware binaries from Packet Sniffer 2 v1.7.0 

  • Sorry for misunderstanding.

    But all things mentioned in that i already did it. 

    So now i tried with short address, PAN ID and Extended address also. 

    But still i am not able to get the decrypted data on wireshark. so i removed the security from the coding and connected the collector and sensor - then i got the results in the wireshark that what i am sending only i seen in the wireshark.

    So, But with wireshark and with security and with decryption key i would like to see the results.

    And i installed new version of wireshark and packet sniffer 2 tool for checking. so there i am unable to do Wireshark Dissector Setup its showing error to me.

    What i have to try again?

    Anil.

  • What version of the Packet sniffer 2 are you using? there is a bug in older versions which does not allow you to decrypt packets so if you want to be able to decrypt the packets you need to use the latest Packet sniffer 2 v1.7.0

  • Hi Hector ,

    I will explain you i detail what i have done.

    file:///C:/Program%20Files%20(x86)/Texas%20Instruments/SmartRF%20Tools/SmartRF%20Packet%20Sniffer%202/docs/user_guide/html/users_guide.html

    1) I refer this Document for installing all software. So according to this document i installed SmartRf Packet Sniffer 2 V1.7.0.

    - Problem is that i am unable to detect the CC1350 device as a pipe. But with TiWsPc2 software i can able to detect the CC1350 device and i can able to catch my data on wireshark, But not able to decrypt.  Here with Packet Sniffer i loaded the Sniffer_sw.hex file in the CC1350. and with TiWsPc2 Software i loaded the Sniffer_fw_gfsk_50kbps_868_915.hex file. 

    2) Then i already have uniflash so i did not installed again. 

    3) Wireshark i installed the version of V2.6.2 first i didn't get the results so i installed V3.0.2.

    Problem I am unable to do the Wireshark Dissector Setup because .dll files i coped from the  C:\ti\simplelink_cc13x0_sdk_1_40_00_xx\tools\ti154stack\tiwsds\plugins to C:\Program Files (x86)\Wireshark\plugins\3.0  in this location also i found 3 different files so that i copied inside that files also then also i unable to get the files in About wireshark - Plugins.

     

    so that i installed back the wireshark V2.2.7 and checking with that.

    but still i am not getting results. But meanwhile i got one more doubt is that correct or not i don't so that i posted on forum.

    Link :- https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/815050

    Regards,

    Anil. 

  • it sounds like you are mixing a lot of different versions of the packet sniffer and packet sniffer plugins here. I would recommend starting over and follow the instructions in  the users guide of the Packet sniffer 2 v1.7.0

    you do not need to use anything from C:\ti\simplelink_cc13x0_sdk_1_40_00_xx\tools\ti154stack\tiwsds\plugins in order for the sniffer to work.

    Also make sure you are using the right wireshark version which is specified in the packet sniffer 2 users guide

  • Hi,

    See i followed the procedure which is mentioned here in file:///C:/Program%20Files%20(x86)/Texas%20Instruments/SmartRF%20Tools/SmartRF%20Packet%20Sniffer%202/docs/user_guide/html/users_guide.html

    Now with this i am facing a problem is that 

    CC1350 LaunchPad (LAUNCHXL-CC1350 with chip revision B/2.1 or later).  

    this they mentioned but with me

    CC1350 Launchpad Rev:1.3.0 -  US  -  FW Rev: 1.0  -  1723  this hardware is available 

    may be because of this hardware and software changes i am unable to detect the device 

    Problem: 

    So this 2 problems i am facing. first sniffer problem may be because of hardware revision. 

    and second problem is because of no pipe(device ) found so its not opening a pipe.

    What i have to do now?

    Anil.

  • Hi,

    I just did a quick test flashing a CC1310 Launchpad Rev 1.3 using the firmware located at

    "C:/Program Files (x86)/Texas Instruments/SmartRF Tools/SmartRF Packet Sniffer 2/sniffer_fw/bin/cc13x0lp/sniffer_fw.hex"

    And my Packet sniffer 2 recognizes the device with no issues, so please re flash your CC1310 launchpad with the firmware provided in Packet sniffer 2 v1.7.0

  • Hi Hector,

    As mentioned in the document 

    For IEEE 802.15.4ge - sub 1 GHz (15.4 Stack), RF proprietary and EasyLink protocols:

    • CC1312R LaunchPad (LAUNCHXL-CC1312R1 with chip revision E/2.1) or,
    • CC1352R LaunchPad (LAUNCHXL-CC1352R1 with chip revision E/2.1) or,
    • CC1352P LaunchPad (LAUNCHXL-CC1352P1 or LAUNCHXL-CC1352P-2 with chip revision E/2.1) or,
    • CC1310 LaunchPad (LAUNCHXL-CC1310 with chip revision B/2.1 or later) or,
    • CC1350 LaunchPad (LAUNCHXL-CC1350 with chip revision B/2.1 or later).

    i don't have a Rev B device with me(CC1310) , i have CC1352R1 Rev C device/ CC1350 REV 1.3.0 device/ CC1352P Rev C Device 

    So i loaded the firmware in CC1350 and checked with Smart RF sniffer Agent - V1.7.0 but not detecting device.

    So same test i have done with TI Wireshark Packet converter 2 - v1.00.03 its detecting in this software.

    so what i need to try now?

    Anil.

  • Hi all,

    http://dev.ti.com/tirex/content/simplelink_cc13x0_sdk_1_40_00_10/docs/ti154stack/ti154stack-users-guide/ti154stack/packet-sniffer.html

    I followed this link, but 1 major think is not mentioned in this document 

    that is: - 

    In addition to setting this decryption key, you need to do one of the following in order to successfully decrypt SimpleLink 15.4 packets from a device:

    1. Capture the device’s association in Wireshark (this will capture and store the device’s Extended Address which is needed for decryption), r
    2. Enter the device’s short address, PAN ID and IEEE Address in Static Addresses:

    and this information is available in this link

    file:///C:/Program%20Files%20(x86)/Texas%20Instruments/SmartRF%20Tools/SmartRF%20Packet%20Sniffer%202/docs/user_guide/html/users_guide.html

    I got the results, you have to use 12:34:56:78:9a:bc:de:f0:00:00:00:00:00:00:00:00 this key for simplelink_cc13x2_sdk_2_20_00_71 this SDK.

    Because in this SDK there is no concept of security commissioning 

    http://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_3_10_01_11/docs/ti154stack/html/ti154stack/secure-commissioning.html 

    if its not security commissioning then it will not change the KEY after joining the NODE. 

    Finally i got the results.

    Thanks to everyone spl - Hector,AB,YK.

    Best Wishes,

    Anil.