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

Understanding Wireshark logs

Hi,

I am trying to understand Wireshark logs when sniffing packets. Please check the attachment. I have been reading about the description of advertising packets. Can you please check my logs and explain me which are the actual data packets? These logs were captured for BLE_UART example.uart_log.pcapng

  • bscdb said:
    One more question where are you checking the values or changes in values?

     That is a pretty open question. Do you mean in the sniffer log? That would be the read requests. Do you mean in the source code? Are you talking about the peripheral or the central? 

  • How do we check values in the sniffer logs? In the previous reply, you mentioned that you noticed change in the values from 0x00 to 0x01 from my logs so if you could point out where exactly can I view that in my sniffer log.

    I did not change anything in the ble blinky example code and I'm using SDK 15.2.

  • bscdb said:
    How do we check values in the sniffer logs? In the previous reply, you mentioned that you noticed change in the values from 0x00 to 0x01 from my logs so if you could point out where exactly can I view that in my sniffer log.

     Oh. Sorry. I see.

    From the log that you sent, take e.g. pack number 13333, where the master sends a write request with value 0x01. If you click the packet, it is displayed in raw data at the bottom. I don't know how to interpret this data directly, but right above the raw data there is a field that describes the packet for you. Initially, the fields are hidden, but if you expand the field called "Bluetooth Attribute Protocol" you will get some more information about the packet. There it says Value: 01. If you click this, it will also highlight in the raw data what bytes that is the value field of this packet. Check out this screenshot:

    Best regards,

    Edvin

Related