 |
Basic Components
|
KADAK's KwikNet TCP/IP Stack
includes a fully compliant suite of protocols for Internet, intranet
and LAN use. The stack is organized as illustrated in the block diagram.
The KwikNet IPv4 Stack includes a fully compliant suite of network protocols.
Simple IP routing is supported and RIP is available if full routing
information is required.
The IP stack includes ARP for Ethernet
address resolution. Full ICMP as required to support TCP is included.
Other services include a BOOTP compatible DHCP client for initial IP address
assignment.
Concurrent network operations on multiple networks is standard assuring
proper multi-homed operation. Network interfaces can be predefined
or dynamically added at runtime.
The IPv4 stack is ready for use with a wide range of additional protocols
should you require the use of these optional KwikNet components.
Of course, all of these features are easily selectable using the
KwikNet Configuration Manager.
The KwikNet TCP Stack is ready for use with applications
requiring reliable, full duplex, streaming socket services for
connection oriented communication.
For applications which do not require the establishment of a reliable
connection, the KwikNet sockets interface can still be used for the
transmission and reception of UDP datagrams.
You have complete control over your sockets interface.
You can define the total number of sockets which your application can use,
restricting KwikNet's memory requirements to closely meet your needs.
You can also define the maximum number of backlogged connection requests
which a busy TCP server can tolerate, thereby further reducing memory waste
in embedded applications.
KwikNet includes network drivers for Ethernet and SLIP. An optional
PPP network driver is also available.
Multiple networks of each type can be supported concurrently by KwikNet.
The operation of these network drivers is determined by the settings
established on the "Ethernet" and
"PPP/SLIP" property pages presented by the
KwikNet Configuration Manager.
The KwikNet modem driver can be configured for use with any serial network,
be it SLIP or PPP. It provides dialing services using the Hayes AT
modem command set. The modem driver, if enabled, sits seamlessly between
the network driver and your serial device driver, using the I/O services
provided by the device driver.
If required, a login script can be followed for connection to
a remote host. Operation as a login server is also permitted.
In either case, the login script is provided by your application.
If your product is to use TCP/IP or just the IP protocol for communication,
it must have an IP address assigned to its network interface. However,
it is often desirable not to have a fixed IP address embedded in such
a product. KwikNet can be configured to provide services which permit your
application to act as a DHCP client to communicate with a DHCP server to
dynamically acquire an IP address. The DHCP client can also automatically
renew the lease for each negotiated IP address.
The KwikNet DHCP client for IPv4 also supports the older
Boot Protocol (BOOTP).
An optional KwikNet DHCP client for IPv4/v6 extends these DHCP services
for use with the KwikNet dual mode IPv4/v6 stack.
| 
