Additionally to requesting a delegated prefix via DHCPv6 this also
enables to ask for a temporary (non-permanent) address on the 6lbr. If
the upstream DHCP server provides one, this can be used to establish
end-to-end connectivity from the 6lbr towards an Internet host directly.
This adds the new `nanocoap_server_observe` module that implements the
server side of the CoAP Observe option. It does require cooperation
from the resource handler to work, though.
Co-Authored-By: mguetschow <mikolai.guetschow@tu-dresden.de>
Co-authored-by: benpicco <benpicco@googlemail.com>
This allows sending a separate response with CoAP Options and adds a
helper to detect duplicate requests, so that resource handlers can
repeat their empty ACK on duplicates.
For convenience, it would be nice to have DNS resolution enabled by
default in the examples. Hence, this patch configures a default DNS
resolver on the 6lbr example and propagates its via RDNSS option in RAs
to the nodes.
When RFC 8974 support (module `nanocoap_token_ext`) is in use, the
request token may be longer than the buffer in the separate response
context is large. This adds a check to not overflow the buffer.
Sadly, this is an API change: Preparing the separate response context
can actually fail, so we need to report this with a return value.
The example application has been adapted to only proceed if the separate
reply context could have been prepared, and rather directly emit a
reset message if the token exceeds the static buffer.
Co-authored-by: benpicco <benpicco@googlemail.com>
examples/readme: fix SAUL spelling mistake
examples/readme: Link to README.md instead of folder
examples/readme: increase title size
examples/readme: make networking category name a bit clearer
examples/readme: move nimble to own category within BLE
examples/readme: move dtls to own category
examples/readme: move heart rate sensor to nimble category
examples/readme: move arduino sketch to languages
examples/timer_periodic: fix file name issue
examples/readme: change level wording about nanocoap
This changes the API of xfa from
XFA(array_name, prio) type element_name = INITIALIZER;
to
XFA(type, array_name, prio) element_name = INITIALIZER;
this allows forcing natural alignment of the type, fixing failing tests
on `native64`.
Before, handlers writing blockwise transfer assumed that the response
header length will match the request header length. This is true for
UDP, but not for TCP: The CoAP over TCP header contains a Len field,
that gets extended for larger messages. Since the reply often is indeed
larger than the request, this is indeed often the case for CoAP over
TCP.
Note: Right now, no CoAP over TCP implementation is upstream. However,
getting rid of incorrect assumptions now will make life easier
later on.
