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

Sniffing Extended advertisement using NRF Sniffer 4.0

I am using NRF5240 board and and the latest Sniffer Software 4.0 (which claims Extended Advertising support).

Able to sniff all 3 advertisement channels (37, 38, 39) and Could see ADV_EXT_IND PDU.

Could you please help thow to see the Extended Packet Information which are sent over the data channels.

Log Snippet:

3 0.000 Anonymous LE 1M LE LL 7 72µs 0 ADV_EXT_IND
1 0.000 Anonymous LE 1M LE LL 7 0 ADV_EXT_IND
2 0.000 Anonymous LE 1M LE LL 7 67µs 0 ADV_EXT_IND

Wireshark has Adv Hop [37, 38, 39] accepts only the 3 values. 

Parents
  • hi,

    I believe NRF Sniffer is now able to sniff the extended Advertising.
    in wireshark i see ADV_EXT_IND and AUD_ADV_IND.
    However I have another problem ... I don't read the address for three legacy channels 37, 38, 39, but only Anonymous, while for AUX_ADV_IND I have the MAC address on board. (this for the eddystone firmware). Can the MAC address also be broadcast in Legacy Channel Advertising?

    In the example of running speed and cadence, I have the opposite situation. I only read the MAC address for AUX_ADV_IND packets.

    would you have any suggestions for me?

    best regard, 

    Marco

Reply
  • hi,

    I believe NRF Sniffer is now able to sniff the extended Advertising.
    in wireshark i see ADV_EXT_IND and AUD_ADV_IND.
    However I have another problem ... I don't read the address for three legacy channels 37, 38, 39, but only Anonymous, while for AUX_ADV_IND I have the MAC address on board. (this for the eddystone firmware). Can the MAC address also be broadcast in Legacy Channel Advertising?

    In the example of running speed and cadence, I have the opposite situation. I only read the MAC address for AUX_ADV_IND packets.

    would you have any suggestions for me?

    best regard, 

    Marco

Children
  • Hi

    This is not direcly related to the Snfifer it seems, as it depends on where your advertising device puts the MAC address in the advertising packet, and not on the sniffer. I would recommend trying to add the MAC address in the primary advertising packet instead of the scan response or secondary packet, as that should make the MAC address visible on the legacy channels as well. 

    If you still have trouble, please create a new ticket on DevZone instead, as I don't see how this is related to the nRF Sniffer.

    Best regards,

    Simon

Related