On Tuesday 03 November 2015 16:19:01 pierre.rust at orange.com wrote: > First, I've missed some packaet during my capture with wireshark : I > was only capturing on eth0 and it seems that for some reasons some > packets are only visible when capturing on 'any'.
They were probably sent on "lo" (localhost). > On 11/03/2015 02:42 PM, Thiago Macieira wrote: > >> * the examples work but wireshark displays these errors : > >> "coap[Malformed Packet]" > > > > Can you expand the packet in Wireshark and see what it is complaining > > about? We may have introduced a bug in our copy of libcoap. > > > > I hope it's only complaining about the format of the body. Since we use > > CBOR, wireshark probably won't understand it. > > When starting the simpleclient, I see > * 4 "coap[Malformed Packet]" errors, which are multicast > non-confirmable GET and are probably part of the discovery phase. For > these packets, wireshark does not give me any indication on what is > wrong (or maybe I just don't know how to do it) > * Some other (unicast) packets, wireshark give a bit more info with > these error messages : > > [Dissector bug, protocol CoAP: proto.c:2541: failed assertion > "hfinfo->type == FT_STRING || hfinfo->type == FT_STRINGZ"] > > I'm afraid I don't know how to check what might be wrong with these packets. Nor I. That looks like an internal wireshark bug. > > 5.00 is "Internal server error". You said that you didn't see the packet > > on > > wireshark, but coap-client is showing a reply. So either wireshark failed > > to show something or coap-client didn't send anything. I can't go from > > here, I need more information. > > OK, when capturing on 'any', I see the packets and I can now confirm > that the simplesever is indeed returning an "Internal server error". > Unfortunately, that still doesn't give me any clue on that is happening > here. But it does tell us that the server did receive the packet but was unable to process it. All indications point to CoAP code having a packet format bug and it's failing to properly parse the requests and properly send replies. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
