Closed hacperme closed 7 months ago
Thank you for looking into this. This however is not a libcoap issue, but a Wireshark issue where the Wireshark CoAP dissector does not support decoding RFC9175 information. See RFC9175 3.2. The Request-Tag Option for further information about the CoAP Request-Tag option.
You may find it useful to add the-v7
option when running the coap-client to see what is happening.
Thank you for looking into this. This however is not a libcoap issue, but a Wireshark issue where the Wireshark CoAP dissector does not support decoding RFC9175 information. See RFC9175 3.2. The Request-Tag Option for further information about the CoAP Request-Tag option.
You may find it useful to add the
-v7
option when running the coap-client to see what is happening.
Thank you for your help, it is indeed a wireshark issue.
Environment
libcoap Configuration Summary
If get_config,sh exists, please copy the output from (do in the top level libcoap directory) :-
Else if using ./configure, please copy the output from (do in the top level libcoap directory) :-
Else if using cmake, please copy the output from (do in the cmake build directory) :-
Else please copy the output from (do from within the libcoap directory) :-
Problem Description
Run coap-client.c exmaple, send get request to coap://coap.me/hello, then capture network packets with Wireshark. We find that there is an invalid option 292 in the packets.
Expected Behavior
Invalid option 292 should not appear in the packets.
Actual Behavior
// Describe what you are seeing.
Steps to reproduce
Code to reproduce this issue
We using examples/coap-client.c.
// If your code is longer than 30 lines, upload it as an attachment. Do not include code that is proprietary or sensitive for your project. Try to reduce your code as much as possible so that it only demonstrates the issue.
Debug Logs
Capture network packets with Wireshark, and find that there is an invalid option 292 in the packets.
coaptestlog.zip
Other items if possible