Been poking at #tuntap in #Linux todayβ¦ trying to figure out how to dissect Ethernet framesβ¦
This is something I wrote some time back, but now I've got some time, I've circled back and expanded it a little. Somewhere, I wrote a tool that basically piped frames to/from stdio, so that it could run privileged under `sudo` from a Python subprocess.
I'll have to dig that code out. At least now though, I have some better idea how to pick things apart.
How can I read from a TAP device (via posix::stream_descriptor) simultaneously with Boost.Asio?
https://stackoverflow.com/questions/78143322/how-can-i-read-from-a-tap-device-via-posixstream-descriptor-simultaneously-w
https://codeberg.org/mark22k/cpp_tap_device
My program should simultaneously read packets from a generated TAP device and process them. For this I use the tuntap library from LaKabane together with Boost.Asio's posix::stream_descriptor. Howe...
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)
Anything can be a message queue if you use it wrongly enough
"Anything can be a message queue if you use it wrongly enough"
Funny, geeky, and quite technical. So jelly
"Anything can be a message queue if you use it wrongly enough"
Eek - this is wonderful (as they say: don't do this!)
Anything can be a message queue if you use it wrongly enough
Anything can be a message queue if you use it wrongly enough
Anything can be a message queue if you use it wrongly enough
Stuart Longland (VK4MSL)
Marek
morgan
Mugurel Tudor
jay
Alec 
π¦πΊ π¨βπ»
Tibs
Martin Peck
Colin Dean
Jean de Barochez