Products
Treck Embedded IPv4
Treck IPv4 stack address IPv4 only needs for embedded systems that have no need to connect to an IPv6 network. Treck IPv4 has been the premium choice for embedded internet applications since 1997 and includes Ethernet support, Ping, RIP v2 Listener, IP, ICMP, ARP, UDP, TCP and a BSD 4.4 Sockets compatible interface.
Treck Embedded Mobile IP
Treck Mobile IP allows a mobile device to roam to different IP networks while still being identified by its original IP address. Designed to be used with Treck TCP/IP, it provides the same high quality and performance that embedded systems designers have come to expect from Treck.
Treck Embedded IGMP
IGMP (Internet Group Management Protocol) facilitates sending and receiving multicast messages. Unlike broadcast messages, multicast messages are sent to a group of machines that have joined the multicast group (even across routers). IGMP allows a device to join and leave various multicast groups that are managed by a router.
Treck Embedded Telnet Server
Treck Telnet simulates a dumb terminal connected to a host computer (or embedded device). This Telnet Server features seamless integration with the Treck TCP/IP stack, can be used with or without an RTOS, and can run as a single task while supporting multiple connections or in a "main line" loop.
Treck Embedded NAT
Treck's Network Address Translation allows an entire local network to share a single or several IP addresses. NAT alleviates the problems caused by a shortage of public IP addresses, and it is beneficial for devices that have a limited number of IP addresses due to cost restrictions.
Treck Universal Plug and Play
Treck Universal Plug and Play is a technology which enables you to implement network devices that can be controlled by Microsoft Windows clients. Examples of Universal Plug and Playenabled network devices include NAT firewalls, networked printers, A/V media servers and media renderers, networkenabled security cameras.
Treck SSL/TLS
SSL/TLS allows an SSL-enabled server to authenticate itself to an SSL-enabled client, and if necessary, allows the client to authenticate itself to the server. After the authentication and cryptology parameter negotiation, a secure channel is established so that the client and server can exchange information in a secure way.

