WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
1–10 of 51 posts
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#2[deleted]
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#3It would be interesting to know why you would choose this over something like the Contiki uIP or lwIP that everything seems to use.
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#4It would be interesting to know why you would choose this over something like the Contiki uIP or lwIP that everything seems to use.
Not sure if they do for _this_ package, but the Wolf* people's model is usually selling certification packages so you can put their things in stuff that need certifications and you offload liability. You also get people that wrote it and that you can pay for support. I kind of like them, had a short project where I had to call on them for getting their WolfSSL to work with a ATECC508 device and it was pretty good support from them.
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#5It would be interesting to know why you would choose this over something like the Contiki uIP or lwIP that everything seems to use.
Not sure if they do for _this_ package, but the Wolf* people's model is usually selling certification packages so you can put their things in stuff that need certifications and you offload liability. You also get people that wrote it and that you can pay for support. I kind of like them, had a short project where I had to call on them for getting their WolfSSL to work with a ATECC508 device and it was pretty good sup…
As the project is GPL’ed I guess they sell a commercial version. GPL is toxic for embedded commercial software. But it can be good marketing to sell the commercial version.
Edit: I meant commercial license
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#6Earlier quoted context omitted.
Not sure if they do for _this_ package, but the Wolf* people's model is usually selling certification packages so you can put their things in stuff that need certifications and you offload liability. You also get people that wrote it and that you can pay for support. I kind of like them, had a short project where I had to call on them for getting their WolfSSL to work with a ATECC508 device and it was pretty good sup…
As the project is GPL’ed I guess they sell a commercial version. GPL is toxic for embedded commercial software. But it can be good marketing to sell the commercial version. Edit: I meant commercial license
You don't need a commercial version, many projects get away with selling just a commercial license to the same version. As long as they have the rights to relicense this works fine.
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#7Earlier quoted context omitted.
Not sure if they do for _this_ package, but the Wolf* people's model is usually selling certification packages so you can put their things in stuff that need certifications and you offload liability. You also get people that wrote it and that you can pay for support. I kind of like them, had a short project where I had to call on them for getting their WolfSSL to work with a ATECC508 device and it was pretty good sup…
As the project is GPL’ed I guess they sell a commercial version. GPL is toxic for embedded commercial software. But it can be good marketing to sell the commercial version. Edit: I meant commercial license
I think they might sell a commercial version as well. It makes sense with the GPL. But I can't really recall that well.
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#8passt (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
#9It only implements IPv4 which explains to a degree that why IPv6 isn't ubiquitous: it's costly to implement.
Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations
#10It 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'.