WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
789c789c789c
114 points
14 comments
March 12, 2026
Related Discussions
Found 5 related stories in 54.6ms across 3,663 title embeddings via pgvector HNSW
- Show HN: WolfStack – Proxmox-like server management in a single Rust binary wolfsoftware · 23 pts · March 08, 2026 · 51% similar
- WolfGuard: WireGuard with FIPS 140-3 cryptography 789c789c789c · 84 pts · March 24, 2026 · 50% similar
- The inner workings of TCP zero-copy mfrw · 49 pts · March 02, 2026 · 49% similar
- Show HN: I built Wool, a lightweight distributed Python runtime bzurak · 13 pts · March 14, 2026 · 47% similar
- Wisp: WebAssembly Lisp DavidCanHelp · 15 pts · March 30, 2026 · 46% similar
Discussion Highlights (4 comments)
rpcope1
It would be interesting to know why you would choose this over something like the Contiki uIP or lwIP that everything seems to use.
rwmj
passt (the network stack that you might be using if you're running qemu, or podman containers) also has no dynamic memory allocations. I always thought it's quite an interesting achievement. https://blog.vmsplice.net/2021/10/a-new-approach-to-usermode... https://passt.top/passt/about/#security
sedatk
It only implements IPv4 which explains to a degree that why IPv6 isn't ubiquitous: it's costly to implement.
CyberDildonics
Are there TCP/IP stacks out there in common use that are allocating memory all the time?