or something like this... I suspect #LwIP is smart enough to just forward lora0 > lora1 on the same device. else just test with 3 devices.

was sich so alles fast acht Jahre lang in open Source Code unbemerkt verstecken kann.

https://github.com/SmingHub/Sming/issues/2936

#bug #lwip

possible division by zero in lwip/core/ipv4/igmp.c · Issue #2936 · SmingHub/Sming

A user reported that his controllers were regularly restarting. Some troubleshooting revealed the following: A WiFi access point in his network regularly sends the following query: [Arch/Esp8266/Co...

GitHub

Uvoks daily struggle.

"Huh?? Why does the LwIP stack send an ACK for a second incoming TCP connection?? I only accept one at a time!?!?"

Apparently, that's a "backlog", and it's suffering you can't turn off completely.
If I really want to only work with one client at a time, I probably have to accept and close the other sockets immediately?

(No, setting backlog to 0 on listen doesn't help)

#esp32 #lwip #networking

Accessing #lwip directly seems to work pretty ok already.

Now I'm trying to see how far I can implement rudimentary #Arduino framework compatibility (before losing interest in the tedium).

After some hours, the EthernetClient finally behaved enough for a simple TCP echo test :D

#WCH #CH32 #CH32V208

Progress of the night: Getting the essentials of the #lwip stack running on the #CH32V208.

Still need to clean it up _a lot_ and build the wrapping library, so it's actually useful.
But seeing lwip run at all is amazing.
(So I don't need to depend on the proprietary, closed source #WCHNET library)

Good night :D

#WCH #CH32

It's still got some issues, but looks like UDP/IP works for the most part. I've done a couple #CoAP requests, so that's cool.

There's a bit of into in the repo but this will need more detail and a larger writeup of the whole project(s), covering
#ESP32 #NetIF <> #ESPNow,
#LwIP over ESPNow
#Linux #TUNTAP <> #ESPNow

And that's all just been groundwork for what I really want to do (recap: CoAP like serverless #MQTT)

https://git.oit.cloud/morgan/ifnow.git

ifnow

Userland driver to bind a TUN interface to ESP-Now on a monitor mode WiFi interface.

Oit Cloud Consulting Services
holy heck! I got #CoAP over #LoRa working! I had expected more issues with packet management, waiting for TX to complete specifically but one again it's 'just worked'. Admittedly with only two devices in a tame environment but still super cool. In addition I found the 223.0.blah broad address wasn't going to work without additional work but turns out CoAP with #LwIP will respond to requests on, 255.255.255.255.

I did a write up on my recent work with #ESP32 #ESP-NETIF #ESPNow #LwIP and #CoAP

CoAP over Everything:
https://oit.cloud/posts/2023-12-30-coap-over-everything/

This is going to be a bit of a living post, serving as my memory and progress report on this exploration.

CoAP over Everything

This research deep dive was inspired from using my Dust Collector Remote. It works great, but after a year using it I’ve found the delay to connect pretty annoying. On bad days with a router misbehaving the 4 or 5 second delay while I’m waiting to turn a tool on can get frustrating. This started getting me thinking about how it could be handled faster. I’ve used ESP-Now a handful of times and have appreciated it’s quick boot to ‘do something useful’ time.

oit blarg!

And why not another #ESP32 component...
`esp_ifnet_lora` #LwIP binding for #LoRa again using ESP-IFNET.

https://git.oit.cloud/morgan/esp_netif_lora

esp_netif_lora

esp_netif_lora

Oit Cloud Consulting Services
oh hai #LwIP over #LoRa