TCP/IP Networking

A full-featured TCP/IP protocol stack with over a decade's worth of successful deployments.

IPv6 Support

Micrium's TCP/IP stack provides IPv6 support, a necessity for the next generation of IoT devices. The IPv6 implementation includes support for the Neighbor Discovery Protocol (NDP) and versatile multicasting capabilities. With Micrium's stack, which allows for simultaneous use of IPv4 and IPv6, taking advantage of the newer protocol is easy. The stack's intutitive API makes inititialization of practically any network application possible with just a handful of function calls.

GUI Features

Main Features

  • Support for multiple interfaces and multiple IP addresses per interface (multihoming)
  • Support for IPv4 and IPv6
  • A BSD socket API with most popular socket options
  • Scalable to contain only required features and minimize memory footprint
  • SSL/TLS support for secure sockets (sold separately).

IPv6 Support Features

  • IPv6 Node
  • SLAAC (IPv6 stateless address autoconfiguration )
  • IPv6 Multicast (MLD)
  • Neighbor Discovery Protocol (NDP)
  • ICMPv6 (echo request/response)

SSL Module (optional)

  • SSL/TLS protocols are the standard for network security
  • Ideal for IoT devices (medical equipment, industrial sensors, and smart meters)
  • Built for efficiency and high performance with support for TLS 1.2 and TLS certificate management
  • The memory footprint makes the module viable even for deeply embedded systems
  • This module is available as an option


Implementation and RFC Compliance

Highlights of Micrium's TCP/IP implementation include the following:

Related network applications - DHCP client, DNS client, HTTP client, HTTP server, FTP client, TFTP server, TFTP client, SMTP client, SNTP client, TELNET server.

Real-time kernel - Required. Micrium’s OS kernel suggested and supported.

Transport layer - TCP and/or UDP

Protocols supported - Multicast transmission and reception (IGMPv2), IPv6 Multicast (MLD), ICMPv6, ARP, Neighbor Discovery Protocol (NDP)

Interface type - Ethernet (802.3 and Ethernet), Wi-Fi, Loopback

Socket API- Two sets of socket APIs: Proprietary and BSP

Stack Compliance

Micrium uses Ixia’s IxANVL to confirm the compliance of the stack with the networking RFCs. IxANVL is popular among developers and manufacturers of networking equipment and internet devices for checking protocol compliance and interoperability.

RFCs supoprted by Micrium's TCP/IP stack
  • UDP (RFC #768)
  • TCP (RFC #793, #813, #879, #896, #2001, #2584, #2988)
  • TCP Congestion Control (RFC #5681)
  • TCP’s Retransmission Timer (RFC #6298)
  • Internet Protocol Specification (IPv4) (RFC #791, #950, #1071, #3927)
  • IP Datagram Reassembly Algorithms (RFC #815)
  • Ethernet Address Resolution Protocol (ARP) (RFC #826)
  • Internet Control Message Protocol Specification (ICMP) (RFC #792)
  • Host Extensions for IP Multicasting (RFC #1112)
  • Internet Group Management Protocol, Version 2 (IGMPv2) (RFC #2113)
  • IPv6 Specification (RFC #2460, #2464, #4291)
  • IPv6 Node Requirements (RFC #4294)
  • Internet Control Message Protocol Version 6 (ICMPv6) (RFC #4443)
  • Neighbor Discovery for IP version 6 (NDP) (RFC #4861)
  • Multicast Listener Discovery (MLD) for IPv6 (RFC #2710)
  • Basic Socket Interface Extensions for IPv6 (RFC #3493)
  • Default Address Selection for Internet Protocol version 6 (RFC #3484)
  • Ethernet (RFC #894, #1042)

TCP/IP Layers

Micrium's TCP/IP requires the presence of a kernel for task scheduling and mutual exclusion. To meet this requirement, Micrium provides source code to allow network applications to readily accommodate Micrium OS kernel.

Network Applications

Network Apps supoprted by Micrium's TCP/IP layers
DHCP Clinet

Dynamic Host Configuration Protocol – Client

  • Transmit and receive option is supported
  • IPv4 Only
DNS Client

Domain Name System – Client

  • Support IPv4 and IPv6
  • Auto select best address
  • Integrated cache
FTP Client

File Transfer Protocol – Client

  • Support authentication.
  • Transfer via buffers or files (file system required).
  • Support SSL (Secure Sockets Layer)
HTTP Client

Hypertext Transfer Protocol – Web Client

  • Full support for HTTP 1.1 (RFC 2616)
  • All HTTP methods suported (GET, POST, PUT, DELETE, HEAD, OPTIONS, and TRACE)
  • Support for WebSocket
  • Support for persistent connections
  • HTTP header field processing (HTTP cookies)
  • HTTP query string processing
  • Support multiple simultaneous connection with multiple HTTP Server
HTTP Server

Hypertext Transfer Protocol – Web Server

  • Supports multi connection - up to 255 client connections
  • Supports any file system, or can be used via a static file system, which is provided
  • Highly customizable via hook functions
  • Include add-on for advanced functionalities such as Authentication Module and REST Framework
MQTT Client

MQTT Messaging Protocol - Client

  • Supports multiple simultaneous connections with multiple MQTT brokers
  • Support for multiple message in the air simultaneously
  • Unlimited number of connections and messages
  • Support all Qualities of Service (QoS-0, QoS-1 & QoS-2)
SMTP Client

Simple Mail Transfer Protocol – Client

  • Support for SSL/TLS
  • Support Authentication
SNTP Client Simple Network Time Protocol – Client
Telnet Server

Telnet – Server 

  • Integrated with uCOS-Shell
  • Support authentication uCOS-Common
  • Support SSL (Secure Sockets Layer).
TFTP Client

Trivial File Transfer Protocol – Client

  • Transfer and reception via buffers or files (file system required).
TFTP Server

Trivial File Transfer Protocol – Server

  • Support any file system; a file system is required.
Contact Sales
Loading Results