User`s guide

KwikNet Overview
K
A
DAK
5
The Treck TCP/IP User Manual
The Treck TCP/IP User Manual provides extensive documentation of the Turbo Treck
TCP/IP Stack and the many optional protocol components which it supports. Much of
the documentation is tutorial in nature and for this reason deserves careful reading.
Chapter 1 provides an excellent introduction to network protocols, what they are and
how they are used. Chapter 2 introduces the sockets interface commonly used for
programming using the UDP and TCP protocols.
Chapters 3 and 4 of the Treck TCP/IP User Manual are devoted to the porting and
configuration process. With KwikNet, the porting has been done and the components
which you wish to use are ready for use. All of the application interfaces required by the
Turbo Treck TCP/IP Stack are provided by KwikNet. The choices of components and
features to be used in your application are easily made using the KwikNet Configuration
Builder with its built-in help service to guide you to the proper selection.
If you do plan to use KwikNet with your own RTOS or single threaded system on a
particular target processor with your own software development tools, the KwikNet
Porting Kit makes it easy. You can simply adapt the sample KwikNet RT/OS interface for
your use. And chances are that KwikNet already includes board support and compiler
support for your target and tools. In any case, you do not need to know how KwikNet and
the Treck TCP/IP Stack actually operate in order to adapt KwikNet for your use.
Chapter 5 presents the Programmer's Reference, the application programming interface
(API) provided by the Turbo Treck TCP/IP Stack. Note that the standard BSD sockets
API described in this chapter is accessed from KwikNet as described in Chapter 5 of the
KwikNet User's Guide. Treck offers a number of sockets extensions and callback services
which are only accessible via the Treck sockets API. Treck also provides an extensive
API for access to features managed by the Address Resolution Protocol (ARP).
A significant portion of Chapter 5 is devoted to Treck initialization, timer management,
device driver services and Ethernet, SLIP and PPP network management services.
KwikNet's network management and device driver interfaces utilize these functions on
your behalf. Hence, all but the very few services of this type listed in Chapter 4.5 of the
KwikNet User's Guide can be safely ignored by your application.
Treck provides a comprehensive set of replacement functions for the standard C runtime
library, some of which are documented in Chapter 5. However, these functions are not
used by KwikNet. The standard C runtime library is used by KwikNet to avoid duplication
of code in the memory footprint.
Chapter 6 describes a number of services offered by the Turbo Treck TCP/IP Stack,
many of which are provided by optional components. KwikNet includes support for
PING, file services and network statistics dumps as standard features. PING services are
accessed using the Treck API. The optional
KwikNet DNS Client, if enabled, is
automatically initialized and configured when KwikNet starts. DNS services are then
available via the Treck API.
The
KwikNet Universal File System (UFS) Interface gives Turbo Treck access to all of the
file systems supported by the UFS. You can therefore safely ignore the Treck file system
API specification in Chapter 6.