FlexNet driver documentation
AXPDDRVR - AX.25 packet driver emulator

Description:

AX.25 packet driver Emulator.

This driver offers an AX.25 packet driver interface, which allows applications with their own AX.25 stack to exchange packets directly with PC/FlexNet. Applications that can take advantage of this driver include all derivatives of KA9Q-NET, such as JNOS, WNOS, GNOS, etc.

Command line parameters:

axpddrvr [-i[f]=<int>]

-h, -?	description of the parameters
-i	the interrupt number
-if	force the use of the specified interrupt number even if it is already in use WARNING: this is dangerous, it may crash your machine

Differences with ETHEREMU

Both PC/FlexNet modules offer a packet driver interface.

As opposed to ETHEREMU, AXPDDRVR is:

• a FlexNet L1 driver, thus it must be loaded before FLEX. ETHEREMU is a FlexNet application, which must be loaded after FLEX.
• an AX.25 packet driver. It works only with applications that include an AX.25 stack. It exchanges AX.25 packets directly. ETHEREMU however emulates an etherent packet driver and expects IP and ARP packets.

Application

AXPDDRVR manages multiple applications at the same time. All the packets however appear in the same FlexNet channel. It may be unloaded using FLEX /u. It may not be unloaded using the packet driver interface (eg. with TERMIN.COM). FLEX /u unloads it hardly, even if there are applications that access it. In this case a crash is likely. Be careful with DOS multitasking and shell escapes!

Example configuration

axpddrvr -i=0x65
loads the driver and instructs it to use interrupt 0x65.
attach packet 0x65 ax 5 256
instructs *NOS to install it as an interface with the name ax. The MTU shall be 256 and there shall be 5 buffers. The MTU is a TCP specific parameter which is documented in the *NOS documentation.
connect ax hb9jnx
connects the station HB9JNX via the interface.