Eddystone URL malformed packet

RE: Eddystone URL malformed packet

FormerMember — Thu, 30 Jun 2016 13:20:16 GMT

In the nRF Master Control Panel, what does the raw advertising/broadcasting data look like for the two cases, the one that work and the one that doesn't?

RE: Eddystone URL malformed packet

jefcap — Tue, 28 Jun 2016 18:39:16 GMT

Yes, in nRF Master Control Panel, the website address is shown correct. That's why I felt surprise about the "Malformed Packet". Shall I ignore this kind of error? Could you reproduce it with wireshark 1.12.12?

RE: Eddystone URL malformed packet

FormerMember — Mon, 27 Jun 2016 06:25:24 GMT

The recommended version for wireshark to be used with the sniffer is wireshark v.1.10.x. When I test examples that you describe here (wireshark v.1.10.14), there is hardly any malformed packets.

When you see the malformed packets in wireshark, does nRF Master Control panel still show the correct address?

RE: Eddystone URL malformed packet

jefcap — Fri, 24 Jun 2016 12:57:38 GMT

Hi Kristin I'm using wireshark Version 1.12.12 (v1.12.12-0-g2f634e8 from master-1.12).

I noticed the problem happen when I try to use the "Eddystone-URL HTTP URL encoding" in the middle of the URL string. For example:

#define APP_EDDYSTONE_URL_URL           't', 'e', 's', 't',0x07,'.','x','x'

If I change the address to the one below, there's no more "Malformed Packet".

#define APP_EDDYSTONE_URL_URL           't', 'e', 's', 't','.','c','o','m','.','x','x'

The URL encoding is just to use at the first and last byte of the URL address?

RE: Eddystone URL malformed packet

FormerMember — Fri, 24 Jun 2016 09:15:48 GMT

I just tested here with www.nordicsemi.com.xx, and wireshark is not showing "Malformed Packet". Which version of wireshark do you use?