User`s guide

54
K
A
DAK
KwikNet System Configuration
IPv4 Stack Parameters (continued)
IP Fragmentation
If you wish KwikNet to be able to split IP datagrams for transmission via a network
interface or path with a reduced IP data capacity, check this box. Otherwise, leave this
box unchecked.
Fragment with Zero Copies
If you are using custom device drivers which interface directly with the Turbo Treck
TCP/IP Stack and support its scattered send mechanism, then you can avoid an extra data
copy when an IP datagram has to be fragmented for transmission via your network
interfaces. To do so, check this box. Otherwise, leave this box unchecked.
If you are using any standard
KwikNet device driver or a device driver derived from the
KwikNet Ethernet or serial shell driver, leave this box unchecked.
IP Fragment Reassembly
If you wish KwikNet to be able to reassemble IP datagrams which arrive as multiple IP
datagram fragments, check this box and enter the maximum number of datagram
fragments which KwikNet must be able to queue for reassembly. Otherwise, leave this
box unchecked.
Path MTU Discovery
In order to determine if an IP datagram must be fragmented for transmission on a specific
network interface, KwikNet must determine the Maximum Transmission Unit (MTU)
(largest IP data payload) which the path to a particular destination permits. If you wish
KwikNet to use the Path MTU Discovery technique specified in RFC1191 to determine the
MTU to be used for communication with a particular destination, check this box.
Otherwise, leave this box unchecked to reduce the memory footprint.
IP Forwarding
If you want to support packet forwarding between IPv4 interfaces, check this box.
Otherwise, leave this box unchecked.
Note that packets will only be forwarded between IPv4 interfaces that are configured to
support forwarding.