fabian18
fabian18
Just a reminder. I think this is only stalling because the `fixup` commit must be squashed.
Although it is probably within the bounds of some `static` buffer where `buf` points to, I just saw a couple of lines below for the NON case technically we might...
I dropped the static IP configuration in the Makefiles I used for testing and adjusted the README.
Thank you
I think this needs an update. The `rtc_setter_callback` is no longer compiled in to our app, because when the module is enabled, the build system complains about an unknown feature....
What about `ethos`? `stdio.c` is not being compiled when using `stdio_ethos`. `stdio.inc.mk` ```Makefile STDIO_LEGACY_MODULES = \ ethos_stdio \ stdio_ethos \ stdio_native # requires #19002 \ # # select stdio_uart if...
So the client is not broken, just the test had to be adapted?
Of course the Observe notification must be sent from the same address as well ... I am at it to add it here. https://github.com/RIOT-OS/RIOT/blob/230df5fe3b2deb69353c8f09c86b2654bd1852c6/sys/net/application_layer/gcoap/gcoap.c#L1824-L1837
Depends on #20711 now due to aux tx local supply in `_handle_req()`
for better testing I added an `/rtc` resource to the gcoap example. Use our `tapsetup.sh` and observe the notifications in wireshark for two `native` instances.