Skip to main content
DavePfz
Senior
Nov 13, 2026 4:39 PM UTC
Question

BLE Sniffer doesn't follow connection with Wireshark 4.6.9

I’m using an STM32WB6MM-DK as a BLE sniffer and all works well until I try to “follow” a connection as described in https://wiki.st.com/stm32mcu/wiki/Connectivity:STM32_Sniffer_for_BLE_User_guide#Following_a_connection

After carefully following the instructions, I get nothing. When I try to paste the original 00:00:00:00:00:00 back into the target window and starting a capture, the window or save or not pops up and when I select discard, it seems to start, but no data is captured. On hitting stop, an error window pops up to the extent of “attempting to use a port that is not open.”

Am I doing something wrong or have the Wireshark plugin scripts changed recently?

2 replies

Dominique FOLLEZOUR
ST Employee
Nov 16, 2026 9:42 AM UTC

Hello

 

As you are able to sniff and see device advertising i guess you have required plug-in.

 

If i understand when you submit for a specific ble address xx:xx:xx:xx:xx:xx in the Target BD address window you do not see the connection ?

 

Of course this might required several trials. The sniffer is capable to sniff only one channel so 37,38,39 (adv channels) , when client try to connect to peripheral the connection might occured over one of the 3 channels. In short connection might be done on channel 37,  while sniffer is looking for 38.

This is maybe the concern.

 

Br

Dom

DavePfz
DavePfzAuthor
Senior
Nov 18, 2026 4:32 PM UTC

What I find is that if I stop Wireshark, change the address, and restart, nothing is captured. (See below for trying to start again.)

However, if I change the target address while Wireshark is running, then only those advertising packets are captured. That’s OK. Also, while Wireshark is running, I can change the scanning channel and it continues after a pause. In other words, it seems as though the device is advertising on all three channels as expected.

However, after I have changed the target address, if I stop the scan and try to restart, I get the following:

Wireshark Capture

The only way to get operational again is to quite Wireshark and start over again.

At this point after many trials, I have not yet been able to “follow” a connection.