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

BLE 4.2 sniffer

I am hoping to get solid verification that nordic offers a solution for sniffing BLE 4.2 packets.

The application I need to sniff is maxing out the MTU (250B payload) so I need support for long packets.

The blogs and googling haven't provided me with a solid answer.

Thanks

Parents
  • I'm in the very same situation. I have MTU sizes > 200 bytes and I'm blind to what happens over the air. In addition, I have the problem, that I'm using a Mac to work with. If I got the NRF Sniffer architecture right: There is a firmware on an evaluation board, sending the received data via a serial connection, which is then reformated by some python scripts, which send sends the data to wireshark for interpretation.

    I would be happy to help to port the windows-only part to OS/X and to help to improve the eval board firmware, if Nordic want's to release this as open source.

    I mean, yes, I could write a firmware for an eval board that does the same and write an adapter for wireshark, but this would likely take me some weeks and the NRF Sniffer is already there.

  • My recollection is it puts a handy header in yellow telling you DLT157 isn't registered and helpfully suggesting you go to Preferences->Protocols->DLT_USER. Which the guy in this thread followed, worked out the only hard bit, that the decoder is called 'nordic_ble' and .. due to wireshark integrating the decoder 2 years ago, it works. And you all the new BLE stuff, and a ton of bug fixes.

    he also gives some handy tips in there for capturing from a pipe which won't work because the OSX pipes aren't in the same place, I believe it's on-screen somewhere in the app and you could probably set it up for a live capture, but I can't imagine it's fun.

Reply
  • My recollection is it puts a handy header in yellow telling you DLT157 isn't registered and helpfully suggesting you go to Preferences->Protocols->DLT_USER. Which the guy in this thread followed, worked out the only hard bit, that the decoder is called 'nordic_ble' and .. due to wireshark integrating the decoder 2 years ago, it works. And you all the new BLE stuff, and a ton of bug fixes.

    he also gives some handy tips in there for capturing from a pipe which won't work because the OSX pipes aren't in the same place, I believe it's on-screen somewhere in the app and you could probably set it up for a live capture, but I can't imagine it's fun.

Children
No Data
Related