Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

David Edwin — Wed, 31 Jan 2018 10:43:42 GMT

@All , those who still have issues with the nRF Sniffer should post into the [support portal] (www.nordicsemi.com/.../Contact-Support-Team) directly or post a separate question in devzone so we can resolve the issue directly. It is getting hard to see the individual issues in the post, after you have posted send me a direct message on devzone so I can resolve it.

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

Panometric — Tue, 30 Jan 2018 19:37:27 GMT

I found that the 32 bit Wireshark did not work, but the 64 bit did. Note sure why, but my Python install is only 64 bit. Also had to :

Modify nrf_sniffer.py, add "from SnifferAPI " to "import Sniffer,myVersion..."
Force Python 27 using in bat: c:\python27\python "%~dp0nrf_sniffer.py" %*

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

MANGO — Tue, 30 Jan 2018 19:16:28 GMT

Hello, @Don Collier.

still no interface to select That is strange. I don't know what to say about that problem.

The devteam will ask you that whether you have connected your Nordic device to your PC directly, not to the USB hub. Also, can you see your COM x port from the Device Manager, if you are using Windows OS?

If you have prepared the correct setup, but having trouble that Wireshark 2 cannot find your COM x port, I'm sorry that I cannot help you with that issue.

-Regards, MANGO

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

MANGO — Tue, 30 Jan 2018 19:10:02 GMT

Hi, @SRA. I updated my original post. As you mentioned, I cannot see the discovery or characteristics.

Thanks for sharing and I hope the devteam to check this, too.

-Regards, MANGO

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

David Edwin — Tue, 30 Jan 2018 08:48:18 GMT

Need to use only Segger jlink 6.16c as mentioned in the nRF Sniffer v2 User guide. Other Jlink versions will not work with the nRF Sniffer beta 1.

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

David Edwin — Tue, 30 Jan 2018 08:45:36 GMT

Segger 6.16c is the only segger software supported with the Wireshark beta 1. You will need to downgrade the segger firmware on the jlink emulator, follow the troubleshooting guide to downgrade to segger jlink 6.16c.

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

SRA — Tue, 30 Jan 2018 03:20:48 GMT

The new entry in Wireshark does work, your python or pyserial isn’t right if that isn’t showing.

But in my experience that still won’t make the nrf52dk work as a sniffer so it doesn’t really matter.

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

Panometric — Tue, 30 Jan 2018 02:40:36 GMT

I would not call these minor issues... nRF52 is not recognized at all by Wireshark.
There is no new Wireshark menu, and the interface does not show on the interface list , even though this works:

c:\Program Files (x86)\Wireshark\extcap>nrf_sniffer.bat --extcap-interfaces

extcap {version=2.0.0}{display=nRF Sniffer}{help=www.nordicsemi.com/.../nRF-Sniffer interface {value=COM6}{display=nRF Sniffer COM6} control {number=0}{type=selector}{display=Device}{tooltip=Device list} control {number=1}{type=string}{display=Passkey / OOB key}{tooltip=6 digit temporary key or 16 byte Out-of-band (OOB) key in hexadecimal starting with '0x', big endian format. If the entered key is shorter than 16 bytes, it will be zero-padded in front'}{validation=\b^(([0-9]{6})|(0x[0-9a-fA-F]{1,32}))$\b} control {number=2}{type=string}{display=Adv Hop}{default=37,38,39}{tooltip=Advertising channel hop sequence. Change the order in which the siffer switches advertising channels. Valid channels are 37, 38 and 39 separated by comma.}{validation=^\s*((37|38|39)\s*,\s*){0,2}(37|38|39){1}\s*$}{required=true} control {number=3}{type=button}{role=help}{display=Help}{tooltip=Access user guide (launches browser)} control {number=4}{type=button}{role=restore}{display=Defaults}{tooltip=Resets the user interface and clears the log file} control {number=5}{type=button}{role=logger}{display=Log}{tooltip=Log per interface} value {control=0}{value= }{display=All advertising devices}{default=true}

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

SRA — Thu, 25 Jan 2018 18:16:34 GMT

I tried again, same issues. Maybe works 10% of the time with the 51-Dongle, never with the 52. When it works it doesn't show any logging if the packet has to do with characteristics.

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

dcollier8 — Thu, 25 Jan 2018 16:26:22 GMT

Thanks it worked I now see the interface toolbar, and selected the sniffer, see my answer here, which includes answers to most of the issues here: devzone.nordicsemi.com/.../ However I still do not see the characteristics, mostly get MIC or decryption errors when I am sniffing, even though I sniffed pairing OK.

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

MANGO — Thu, 25 Jan 2018 02:44:35 GMT

Hi, Don Collier. I had the same issue, too.

Main Reason: nrf_sniffer.bat (in Windows) / nrf_sniffer.py wasn't executed correctly.

Reason why: You can see the details in my previous question. Take a look and hope it helps.

After that is executed correctly, you can see the View - Interface Toolbars - nRF Sniffer from Wireshark 2.

-Regards, MANGO

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

dcollier8 — Thu, 25 Jan 2018 00:45:45 GMT

I have wireshark 2.4.4 installed, and dont see any interfaces toolbar option in the view dropdown menu. Anyone seeing this issue ?

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

SRA — Wed, 24 Jan 2018 06:32:04 GMT

Warm yes, hot no. But mine is only rarely working. I’ll be interested to know if you are getting characteristic data with the new sniffer.

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

MANGO — Wed, 24 Jan 2018 06:16:43 GMT

Thanks, @SRA. I used this webpage to convert video files to gif.

In the past, as shown here,

many users wanted the Wireshark 2 support.

Though we have waited quite long, the devteam is working on the thing we wanted. So I just want to appreciate their efforts, stay positive, and point out some issues from the beta version.

Come to think of it, I only tested the advertising/scan request packets. Didn't notice that the sniffer cannot log characteristics.

I will test that on my side, too.

By the way, does your nRF51 dongle (PCA10031) becomes hot, so hot that you let go of your fingers as soon as you touch the dongle?

I don't have an IR temperature measurement to show you the temperature, but my dongle goes quite hot while running the sniffer.

-Regards, MANGO

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

SRA — Tue, 23 Jan 2018 19:50:27 GMT

Great post the gifs are very helpful! (What did you use for that?)

Here are the things I learned...

pyserial - The guide is HORRIBLE at mentioning this, its in the required software but never mentions it again. pip install pyserial, but make sure you are using python 2.7.x to do this. I had to manually install pip because my 2.7 installer wouldn't do it.
Do almost everything as Admin. Right click and run Wireshark as admin, install py27 as admin, etc.
I'm using 6.22g of Segger and yea, exact same issues.
I've tried the nrf51 Dongle and nrf52DK. I at least have gotten partial results on the 51D, nothing on the 52.
The guide isn't clear at all about the EXTCAP folders, but it's fairly obvious where the files go.
If running python --version returns 3.x, try removing 3.x from your PATHS and making sure only 2.7 is in there. Whatever version comes up is the one the .bat file that wireshark loads will try and use.
When I DID get connections up and logging - albeit flaky - with the nrf51Dongle, I could log adv, con_req, and negotiation but it WOULD NOT show any discovery or characteristics. So even "working" it's really not working.

Short story is, I'm giving up for now. 2.0 Beta is CLEARLY not ready. I spent all morning on it and the best I got was still unusable. Waiting on next version.

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

MANGO — Wed, 17 Jan 2018 14:32:46 GMT

Hello, shibshab.

import serial

print serial.__version__

This showed 3.4. I'm using Python 2.7.14.

try to use the latest version of J-Link

Well, the user guide says that I should use J-Link v6.16c so I downgraded the J-Link.

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

shibshab — Tue, 16 Jan 2018 07:50:52 GMT

What version of pyserial do you use?

import pyserial print serial.version

Also, you could try to use the latest version of J-Link as I have seen (but not experienced myself) that it could work.

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

MANGO — Mon, 15 Jan 2018 18:29:05 GMT

I am not sure whether this is the cause but the second exception (logging.info("Unable to read UART: ...) was mainly observed when I tried to sniff Estimote's Virtual Beacon packets.

1.Re-open Wireshark 2.

2.Before opening COMx port with Wireshark, run the Virtual Beacon to advertise beacon packets.

(Estimote 2.35.1 Mobile app; Configuration ->Virtual Beacon, used iPhone 6 Plus iOS 11.2)

3.Now open COMx port and you might observe the second exception.

It is weird that I didn't notice the second exception when I was sniffing the NUS example.

I noticed that exception when sniffing this beacon.

Hope this can help while you are investigating.

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

MANGO — Mon, 15 Jan 2018 18:14:46 GMT

Hi, Hung Bui. I typed exec invalidatefw with the J-Link Commander v6.16c and downgraded the firmware.

As mentioned, I connected the dongle directly to the PC's USB ports.

After re-opening Wireshark 2, now I can see the COMx ports.

However, the aforementioned Python exception is thrown most of the time when I re-open the COMx port after re-opening Wireshark 2.

Can you check this Python exception, please?

Actually, two types of exceptions were observed.

Lastly, is it normal that PCA10031 becomes quite hot even though it was plugged in at a short time?

-Regards, MANGO

RE: Wireshark 2.4.3 & Sniffer 2.0 Beta - Minor issues

Hung Bui — Thu, 11 Jan 2018 10:26:03 GMT

I'm not so sure about the issue. On my computer I can re-open wireshark with out a problem. Have you made sure J-Link v6.16c is on the board ? (You can use Jlink Configurator, right click on the board and click Replace Firmware)

Please try to plug the dongle directly to the PC not via a hub.