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'.
On 11/03/2015 02:42 PM, Thiago Macieira wrote:
> On Tuesday 03 November 2015 11:06:55 pierre.rust at orange.com wrote:
>> * When using simpleclient and simpleserver,
>> * The simpleclient displays the discovered server:
>>
>> DISCOVERED Resource:
>> URI of the resource: /a/light
>> Host address of the resource:
>> coap://[fe80::5265:f3ff:feb8:58e1]:42603
>>
>> * 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.
>> * I tried then to use the uri and address printed by the client with
>> coap-client (client from libcoap) :
>>
>> ./coap-client -m get
>> coap://[fe80::5265:f3ff:feb8:58e1]:42603/a/light
>> v:1 t:CON c:GET i:cbd5 {} [ ]
>> 5.00
>>
>> It fails and I don't see trace of the request in wireshark.
> 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.
>> let me know if I can give some more details (but as you have probably
>> seen, I'm not really comfortable with the ipv6 networking stuff).
--
Pierre Rust
Senior Software Developer
OLPS/SOFT/NEC
06 76 88 75 28
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
