This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Error when launching wireshark (1.8.3) in nRF Sniffer

Hello, I'm using:

nRF sniffer, win_1.0.1_1111_Sniffer,

under OS

win7 64bit

Per @endnode's advice, I installed old version of

wireshark 1.8.3

I'm running the sniff firmware on nrf51dk, manufactured in 2015.

After locking on to the target , I press w, and this 2 error messages appear:

image description image description

How should I proceed next? Shall I switch to a different version?

Parents
  • Wireshark 2.4.0 has better support it just require one manual configuration the first time you use it. (I think you shouldn't go with a version as old a 1.10.x)

    For the "simple user" with NRFsniffer1.0.1 here is a basic help on how to use wireshark 2.4.0 or more (note it could be simplified if Nordic does an update of it's nRFsniffer):

    • open the sniffer
    • press w as explained in docuementation

    For the first time only you open Wireshark:

    • go to edit->preferences->protocols->DLT_USER
    • edit the encapsulation table and add "user10 (DLT=157)" with "nordic_ble" in payload protocol field.
  • I see, sorry I thought it was our plugin. The reason started few years back when the native BLE protocol parsing on Wireshark was not very good compare to our plugin and we then suggested customer to continue using our. From that time until now, unfortunately we don't have enough staff to follow and update the sniffer. From my impression seems that the current native BLE protocol in wireshark now have same information as in our plugin. Will try to test more.

Reply
  • I see, sorry I thought it was our plugin. The reason started few years back when the native BLE protocol parsing on Wireshark was not very good compare to our plugin and we then suggested customer to continue using our. From that time until now, unfortunately we don't have enough staff to follow and update the sniffer. From my impression seems that the current native BLE protocol in wireshark now have same information as in our plugin. Will try to test more.

Children
No Data
Related