Analysis of several open-source TCP/IP protocol stacks

1:bsd TCP/IP stack, BSD stack historically is the starting point of other commercial stacks, most professional TCP/IP stacks (vxworks embedded TCP/IP stacks) are BSD stack derived. This is because the BSD stack provides the prototype of these professional stacks under the BSD License agreement, which allows the BSD stack to combine the code of these professional stacks in a modified or unmodified form without paying royalties to the creator. At the same time, BSD is also the starting point for innovations in many TCP/IP protocols, such as hungry congestion control and avoidance in WAN.
Ftp://ftp.FreeBSD.org/pub/FreeBSD-stable/src/sys.netinet

2:UC/IP is a set of Uc/os-based, open-source TCP/IP stacks, written by Guy Lancaster, and can be ported to other operating systems, a completely free, research-ready TCP/IP stack, uc/ IP most of the source code is from the open source BSD publishing site and Ka9q (a DOS single-task-based environment running TCP/IP protocol stack) ported over. UC/IP has the following features: PPP protocol with authentication and header compression support, optimized single request/reply interaction, support for IP/TCP/UDP protocol, more powerful network functions, and can be cut. The UCIP protocol stack is designed as a network module with a minimized user interface and an applied serial link. Based on the number of protocols required to implement the CPU, compiler, and system, the code capacity required for the protocol stack is between 30-60kb.
Http://ucip.sourceforge.net

3. lwIP is a set of open source TCP/IP stacks for embedded systems developed by the Swiss Computer Science Institute (Swedish Institute of computer Sciences), Adam Dunkels. The meaning of lwIP is light Weight (lightweight) IP protocol, relative to UIP. lwIP can be ported to the operating system or run independently without an operating system. The focus of LwIP TCP/IP implementation is to reduce the use of RAM on the basis of maintaining the main functions of the TCP protocol, generally it requires only dozens of K of RAM and about 40K ROM to run, which makes the LwIP protocol stack suitable for low-end embedded systems. The features of the LWIP are: support for IP forwarding under multiple network interfaces, support for the ICMP protocol, including the experimental extended UDP (User Datagram protocol), including congestion control, RTT estimation and fast recovery, and fast forwarding of TCP (the Transmission Control Protocol), providing a dedicated internal callback interface (RAW API) is used to improve application performance and provides an optional Berkeley interface API.
http://sics.se/~sdam/lwip/

4. uIP is a very small TCP/IP stack specifically designed for 8-bit and 16-bit controllers. Written entirely in C, so it can be ported to a variety of different architectures and operating systems, and a compiled stack can run in a few KB rom or hundreds of bytes of RAM. The UIP also includes an HTTP server as the service content. License: BSD Permit http://dunkels.com/adam/uip/

5, Tinytcp Stack is a very small and simple implementation of TCP/IP, it includes an FTP client. The TINYTCP is designed to burn into ROM and now begins to seem useful to the big-endian structure (the initial target is 68000 chips). The TINYTCP also includes a simple Ethernet driver for 3COM multi-Bus cards http://ftp.ecs.soton.ac.uk/pub/elks/utils/tiny-tcp.txt

Analysis of several open-source TCP/IP protocol stacks