It only implements IPv4 which explains to a degree that why IPv6 isn't ubiquitous: it's costly to implement.
It's just not worth it. the only thing keeping it alive is people being overly zealous over it. if the cost to implement is measured as '1', the cost to administer it is like '50'.
WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
11–20 of 51 posts
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#12It only implements IPv4 which explains to a degree that why IPv6 isn't ubiquitous: it's costly to implement.
It's just not worth it. the only thing keeping it alive is people being overly zealous over it. if the cost to implement is measured as '1', the cost to administer it is like '50'.
Is it my favorite? No. Is it well supported? Not everywhere. Is it going to win, eventually? Probably, but maybe IPv8 will happen, in which case maybe they learn and it it has a 10 years to 50% of traffic instead of 30 years to 50% of traffic.
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#13Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#14It only implements IPv4 which explains to a degree that why IPv6 isn't ubiquitous: it's costly to implement.
It's just not worth it. the only thing keeping it alive is people being overly zealous over it. if the cost to implement is measured as '1', the cost to administer it is like '50'.
Hard disagree. It turned out to be great for mobile connectivity and IoT (Matter + Thread).
> the cost to administer it is like '50'.
I'm not sure if that's true. It feels like less work to me because you don't need to worry about NAT or DHCP as much as you need with IPv4.
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#15Are there TCP/IP stacks out there in common use that are allocating memory all the time?
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#16Are there TCP/IP stacks out there in common use that are allocating memory all the time?
Packets and sockets have to be stored in memory somehow. If you have a fixed pool that you reuse it's basically a slab allocator.
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#17passt (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
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#18Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#19Are there TCP/IP stacks out there in common use that are allocating memory all the time?
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#20It only implements IPv4 which explains to a degree that why IPv6 isn't ubiquitous: it's costly to implement.
It's just not worth it. the only thing keeping it alive is people being overly zealous over it. if the cost to implement is measured as '1', the cost to administer it is like '50'.