|
![]() |
FlexNet driver documentation
|
||||||||||||||||||||||
Description:AXIP driver. Warning: Configuring this driver is complicated. Knowledge on TCP/IP is required to use the driver. This driver encapsulates AX25 packets with an IP header and sends them via a packet driver on an ethernet network. The method used is described in RFC1226 and therefore compatible with the derivatives of KA9Q, such as WAMPES, WNOS and JNOS. The driver accesses an already resident ethernet packet driver. Command line parameters:ippd [-i=<int>] [-c=<chnum>] [-m=<myip>] [-p=<peerip>]
This driver supports multiple channels. There are however situations, where one nevertheless wants to load multiple IPPD: Configuring the channels (IPPDCFG)If IPPDCFG is called without parameters, it displays a list of all IPPD drivers found and of all channels. IPPDCFG with parameters sets a channel. All the parameters of the driver may be used (without -i and -m), and the following parameters are new:
LimitationsThis driver was developed to connect PC/FlexNet with a KA9Q derivative over a LOCAL net. This leaded to simplifications. ARPThe ARP implementation is minimal. At driver startup, the ethernet address of the gateway is queried. If no answer is received during about 10 seconds, the driver issues a warning and tries to get the ethernet address about once every minute. ARP packets sent to the broadcast address are monitored and evaluated. The driver responds to ARP queries during the driver run. IPIP is also simplified. IP fragmentation is not supported, since this would complicate the driver very much (it would need timers and reassembly buffers). So all networks between the two stations must have a minimal MTU of about 300 bytes! So the driver is not suited to build wormhole links to australia. Only IP version 4 is understood (the currently usual version). The protocol number used is 93 (consistent with RFC1226). The TTL is fixed 64. IP options are not sent. For security reasons only packets where both IP addresses match the expected ones are accepted. It is thus not possible to realise broadcast nets as with IPXPD. ICMPOnly ICMP Echo Request messages will be decoded and answered with an ICMP Echo Reply message. Other ICMP messages will neither be generated nor received. |