Unable to sniff CTE packets in wireshark with nRF52840

RE: Unable to sniff CTE packets in wireshark with nRF52840

Simonr — Tue, 10 Oct 2023 07:38:27 GMT

This would most likely be because the nRF52840 doesn't support AOA or CTE packets, and thus won't be able to read the CTE part of an advertising packet. You will need to have I.E. an nRF52833 on both ends of the communication to correctly transmit and receive CTE data correctly.

Best regards,

Simon

RE: Unable to sniff CTE packets in wireshark with nRF52840

piethan — Tue, 26 Sep 2023 23:05:14 GMT

Hello, on my machine I can read the CTE info field you picture with an NRF52840 and the NRF sniffer/wireshark software. I have almost the same setup, being NRF52833 transmitting CTE on periodic packet and NRF52840 receiving. I'm sure it doesn't actually read the CTE part of the packet, but I can confirm it for sure can read the CTE info in the extended headers.

RE: Unable to sniff CTE packets in wireshark with nRF52840

Simonr — Fri, 25 Aug 2023 12:53:02 GMT

Hi Lihua

I'll have to ask the team behind the nRF Sniffer internally about this as I'm not sure if this is supported (we don't mention this feature/support in the nRF Sniffer release notes at least), but my guess is that you will at least have to use a chipset that support Direction Finding and CTE to sniff CTE data.

Best regards,

Simon