Hi all, There is a network forum meeting today 4 Aug at 8AM PDT / 17.00 CET. Agenda: - Making the new TCP stack the default. See https://github.com/zephyrproject-rtos/zephyr/pull/27208 for details. -

I was not able to connect to net using Boron, it is probably some minor thing, but you need at least my PR to try it. I have used SIM808 modem which works fine with generic GSM modem. Cheers, Jukka

#gsm_modem

Hi Ricardo, having a secure connection to AWS over the generic GSM modem should work just fine. Do you have a working setup for generic GSM modem with Particle Boron board? I am asking because I had s

#gsm_modem

Hi Brenton, you can follow the instructions at https://docs.zephyrproject.org/latest/guides/networking/qemu_eth_setup.html#networking-with-eth-qemu LWM2M and most of the networking samples will work f

Hi Kenth, there has not been such plans so far. Patches are welcome of course. What kind of hw you had in mind that has multiple Ethernet sockets? Cheers, Jukka

#networking

Hi Bo, some comments inline below: Can you try what you are doing using upstream master branch, it might have issues fixed regarding what you are trying to do? Where do you see a recommendation to use

#ppp #gsm_modem #mbedtls #networking

Hi all, There is a network forum meeting tomorrow 5 May at 8AM PDT / 17.00 CET. We will be using Teams instead of Zoom: ________________________________________________________________ Join Microsoft

Hi all, There is a network forum meeting tomorrow 7 Apr at 8AM PDT / 17.00 CET https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#networking-forum Preliminar

Hi Darryl, I think it is more of a historical relic than a purpose design. There has not been any reports that this have caused issues. Patches are welcome of course. Cheers, Jukka

Hi, some comments inline below: Use IP address here instead of hostname. You could print the IP address you are trying to connect in order to verify that it is set correctly. Cheers, Jukka

Hi Immo, the networking unit tests under tests/net directory should be self contained i.e., they should not need SLIP to be able to run. The sanitychecker also compiles samples/net/ programs and those

Hi Immo, for networking tests to run, I think you need to say - netif:eth in board yaml file (instead of just "- net") Cheers, Jukka

Hi Holger, one option is use the generic GSM modem, which uses PPP to connect to modem, instead of offloading the IP stack to the modem. In that case one can send DTLS data via the modem. Unfortunatel

Hi Guillaume, it sounds like sara modem driver has a regression. Could you create a bug report for this at https://github.com/zephyrproject-rtos/zephyr/issues/new?assignees=&labels=bug&template=bug_re

Hi Giri, currently we have multicast group support only implemented for IPv6. It would not be a big task to implement mcast listener support for IPv4 if you want to do that. As always, patches are wel

#networking #samples

Hi Alessandro, could you create github issue about the slowness of the networking stack, we can then discuss more about the issue there. Cheers, Jukka wrote:

Hi Giri, can you create an issue in github for this. Trying to resolve your issue in mailing list is not very effective. https://github.com/zephyrproject-rtos/zephyr/issues/new/choose Cheers, Jukka

#nrf52840 #samples

The changes that you do there basically turn off ARP, the end result is that the IPv4 connectivity cannot work properly after this. Cheers, Jukka

#nrf52840 #samples

Hi Giri, yes, that is definitely a problem. The destination MAC address should be a valid unicast address. Does you ethernet board have a proper MAC address set to it? You can see the MAC address usin

#nrf52840 #samples

Hi Giri, You could also verify from wireshark that the MAC addresses are correctly set in the packets. If zephyr sends a packet using wrong destination MAC address, then your ubuntu would not receive

#nrf52840 #samples