• State Not Answered
  • Replies 6 replies
  • Subscribers 63 subscribers
  • Views 1353 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 249176
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

google string in sniffed BLE packet

gschelotto

Hi,

I've launched wireshark + nRF52 Dongle successfully and I'm also able to select my device (named EWAT AI-No) from the list to sniff. However there's something I don't understand. Where does the Google_08:8f:63 string come from?

The device is a EYSHSNZWZ based on nRF52832 with UART BLE application example.

Here's the screenshot.

gaston

Parents
  • 0

    Hi gaston

    I'm sorry, I misunderstood this as well. It seems like it is Wireshark that is storing some manufacturer IDs in the "Wireshark manufacturer database", found here. Here you can see that Google, amongst others, is present. Nordic Thread and Zigbee devices are also stored here.

    The reason only the Google address is identified by name is likely because that is the only device in your vicinity using a public address instead of a private resolvable one. I don't see why this matters whether it says a company name or just the full address though.

    Best regards,

    Simon

Reply
  • 0

    Hi gaston

    I'm sorry, I misunderstood this as well. It seems like it is Wireshark that is storing some manufacturer IDs in the "Wireshark manufacturer database", found here. Here you can see that Google, amongst others, is present. Nordic Thread and Zigbee devices are also stored here.

    The reason only the Google address is identified by name is likely because that is the only device in your vicinity using a public address instead of a private resolvable one. I don't see why this matters whether it says a company name or just the full address though.

    Best regards,

    Simon

Children
Related

core_v2_widget.Hide()