6
K
DAK
KwikNet Overview
KwikNet
provides access to all of the network statistics maintained by the Turbo Treck
TCP/IP Stack and it optional components. You can therefore safely ignore the Treck
network statistics logging API presented in Chapter 6.
The KwikNet TFTP and Telnet clients and servers are not derived from the equivalent
Treck components. Hence the description of the Treck TFTP and Telnet options in
Chapter 6 can be safely ignored.
The KwikNet SMTP client and server are not derived from the equivalent Treck
components. Hence the Treck SMTP Client manual can be safely ignored.
Chapter 7 describes a number of protocols which the Turbo Treck TCP/IP Stack
supports, many of which are provided by optional components. KwikNet includes dialer
services as a standard feature. KwikNet also includes support for DHCP and BOOTP for
systems that only incorporate IPv4. For such systems, DHCP and BOOTP services are
automatically employed for networks configured to require their use. An optional
KwikNet component is available to provide DHCP support for systems that use both Ipv4
and IPv6.
KwikNet includes modem support for serial networks. For modems requiring dialing
services, the KwikNet modem driver provides dialer scripting services which are
compatible with the Treck dialer API. You can therefore safely ignore the Treck dialer
API presented in Chapter 7.
KwikNet supports Auto IP, IGMP, NAT and PPP, all of which are optional components.
Auto IP negotiation is automatically employed for Ethernet networks configured to use
the feature. IGMP and NAT, if enabled, are automatically initialized and configured
when KwikNet starts. IGMP and NAT services are then available via the Treck API.
KwikNet has complete support for PPP networks. The use of PPP is greatly simplified by
the KwikNet Configuration Builder which lets you predefine a PPP network and specify all
of the PPP options which must be negotiated when the network is opened. By so doing,
you can safely ignore most of the Treck PPP services presented in Chapter 7.
Appendices A and B in the Treck TCP/IP User Manual can be safely ignored. In
particular, ignore the section of Appendix B which describes a method of using
KADAK's AMX 86 RTOS with the Turbo Treck TCP/IP Stack without
KwikNet.
Appendix C provides useful hints for debugging.
The Treck TCP/IP User Manual describes how to port the
Turbo Treck TCP/IP Stack for use with any RTOS and how
to configure it for your own use. The Treck stack is ready
for use with KwikNet. The Treck port has been done.
Furthermore, the KwikNet Configuration Builder can be
used to configure KwikNet for your system without having
to edit the Treck TRSYSTEM.H header file.
Comments to this Manuals