Lucien Zürcher

As @MatthewPennock points out, the issue is connected by using a newer autoconf-archive version. I installed an older version as follows, this helped me fix the issue on ubuntu 20.04,...

Any chance that that will be fixed?

Same issue on windows, this is unwanted behavior due to the example case of forgetting to stop pomatz for an unexpected meeting.

~Same issue here, this still seems to be broken~ Should be working, be sure that the port `config` is set to the correct port: _jest-puppeteer.config.js_ ```js module.exports = { server:...

Thank you, the newer version by long tabbing works fine. It might be the launcher. Tell me if i should test something specific.

Installing the correct googledriver and chrome version from [google chrome labs](https://googlechromelabs.github.io/chrome-for-testing/#stable) will fix this. I will leave this issue open, as I believe two things would improve user friendliness: 1....

Updated the Dockerfile to install the correct chromedriver and chrome version, which then allows running: `wasm-pack test --chrome --chromedriver "$(which chromedriver)" --headless`. New Dockerfile ```dockerfile ARG VARIANT="16" ARG RUSTUP_VERSION="1.26.0" ARG...

@EskoDijk Do you see any CoAP rfc compliance issues with the proposed approaches?

@mrdeep1 thank you for the fast response. Thanks for the hint just realized the mixup. I also found the multicast binding `coap_join_mcast_group_intf` opens a new socket so I am happy...

The use case; I have multiple servers listening on the same multicast address + port and sending to the same multicast address + port. A very basic event based system...