USB-KW41Z BLE sniffer does not decode Ethernet II "data" on wireshark.
It is like the "kinetis adapter information" plug in does not work.
Set up: Windows 10 + wireshark 2.6.1 + Kinetis protocol analyser adapter 184.108.40.206 installed
Are you trying to use it with BLE? If you are trying to do so, could you please make sure that you are using the correct interface?
Sometimes, depending on the computer the sniffer it's not set by default on the Ethernet II and you might be seeing other types of packets.
Yes, I am trying to use it with BLE.
I am pretty sure that I am using the correct interface. It is the only one available from the Protocol Analyzer adapter and I only get traffic when I select all the BLE channels.
If you look at my previous screenshot, data is passing through the wireshark interface but it is not decoded.
I guess that the 45 bytes of data you can see there should match with a NXP protocol to wrap the BLE device information.
I have done the installation on another windows pc and I get the same result.
I install Wireshark and the Protocol Analyzer adapter from here: USB-KW41Z|Bluetooth Low Energy/IEEE® 802.15.4 Wireless Packet Sniffer|NXP
Is there a chance you could share with me the capture? Also, could you please attach a screenshot of both the device manager and the adapter settings on the computer?
Also, by any chance, do you have a firewall active? Sometimes the firewall causes some problems while working with the protocol analyzer and Wireshark?
I do not understand, you can find the screenshot in my first post.
Anyway here there is another one with the Protocol Analyzer Adapter.
I have disabled the firewall.
I have exactly the same problem. Please downgrade wireshark to 2.4.7.
Hello. I'm getting the same issue. Any clue how to fix dissector?
I am dealing with the same issue...
I have tested with Wireshark v2.4.7, v2.4.8, and v3.2.4 and Protocol Analyzer Adapter v220.127.116.11
Here is a screenshot of my wireshark and adapter. Any feedback would be appreciated.
Thank you very much se7ensong. It worked!
Please Estephania Martinez correct either the "bug" or the link in the getting started web page :-)
Retrieving data ...