Hi Mike, You need to increase “CONFIG_WEBSOCKET_MAX_CONTEXTS” in order to create more websocket connections, this config defaults to 1. I’m not sure if you open any other sockets in your application,

Hi, Yes, socket API is thread safe. Regards, Robert

#networking

Hi all, There is a networking forum tomorrow Tue 3 August at 8AM PST / 17.00 CEST. The current agenda is empty, please let me know if there are any topics you’d like to discuss. Otherwise, I’ll cancel

Hi all, There is a networking forum tomorrow Tue 6 July at 8AM PST / 17.00 CEST. Currently there are no major topics on the agenda. We’re going to briefly discuss networking stack maintenance transiti

Hi Nagesh, USB device re-enumeration is a known issue for RCP and OTBR. The topic is still quite fresh in terms of Zephyr, as we do not implement “software” reset OTBR required so far. There’ve been s

#nrf52480

I just meant that OpenThread uses mbedTLS as it’s crypto library, for instance: https://github.com/openthread/openthread/blob/master/src/core/crypto/sha256.cpp#L41 Regards, Robert

#nrf52840 #networking

Hi Nikos, Contributions are always welcome, would be also good to contribute the overlay-ot.conf to the lwm2m_client sample, once you have configuration that is proven to work. We even have an outstan

#nrf52840 #networking

Hi Nikos, If you use CONF_FILE option, you need to specify both, prj.conf and the overlay: “-- -DCONF_FILE="prj.conf overlay-usb-nrf-br.conf"”. There’s also an OVERLAY_CONFIG option, where you can spe

#nrf52840 #networking

Hi, I’ve just checked current master, and building with "overlay-usb-nrf-br.conf" worked fine for me. Perhaps you need to clear your build directory? Anyway, unless I miss something, it should be ok t

#nrf52840 #networking

Hi Nikos, The project file selection depends on whether you want to use USB CDC or UART for the communication, by default UART is used, applying ` overlay-usb-nrf-br.conf` will switch to USB (you’ll n

#nrf52840 #networking

Hi Nikos, Unfortunately, we don’t have a step-by-step guide for the scenario you describe, but I can provide you with some guidelines. OpenThread has a reference implementation of border router, which

#nrf52840 #networking

Hi Axel, I've found the following configuration to be the minimal needed to use the Zephyr ieee802154 radio driver w/o the networking stack: CONFIG_IEEE802154=y CONFIG_NETWORKING=y CONFIG_IEEE802154_R

Yes, applying `overlay-802154.conf` will make the sample use Zephyr’s native 6lowpan stack. Applying ` overlay-ot.conf` will make the sample use OpenThread, which implements it’s own 6lowpan layer. Yo

Nikos, CoAP over DTLS is supported, we just don’t have a straightforward sample of this functionality. For instance, the `lwm2m_client` sample uses CoAP protocol over DLTS (LWM2M uses CoAP internally)

Hi Nikos, The samples you mention were likely removed/modified during our transition from net_app API to socket API. CoAP samples we have now does not seem to feature DTLS at this point. There are a f

Hi Erin, It is be possible to have both, TCP and TLS sockets when CONFIG_NET_SOCKETS_SOCKOPT_TLS option is enabled. Just to be sure, I’ve verified this functionality with current master and echo_serve

Hi Karthik, In order to use cryptography you need a cryptographic library. Our networking applications use mbedTLS, therefore I don’t see a way to disable it, while still using cryptographic features.

Hello Karthik, MQTT event callback will run in the same thread from which you call `mqtt_input` function. So in case you call it from ISR (not recommended), the event callback will also run from ISR.

#mqtt

Hello, I’ll try address unanswered questions: Thread Group has recently released Thread Commissioning App. How we can use it for exploring further things? I think Border router will be required in tha

#nrf52840