unzip linuxnet.zipTo start linuxnet from the command line enter:
./linuxnetNow You should see the following:
********** HighSpeedTNC3 *********
* (X)NET Router Firmware
*
* DAMA/TURBOXHOST Version 1.32 *
* (C) '93 - '01 by Jimy, DL1GJI *
* 300 channel 0 KByte
RAM *
**********************************
Congratulation: (X)NET runs on Your Linux platform. To connect the Node press the <ESC> Key and enter:
c nocallYou will get a "* Connected to" message and a prompt. Now enter:
=> sysOK, now You are Sysop. You can now set the terminal call and the node call with:
=> my tcall dl1xyz
=> my call db0xyz
attach sdev0 kiss 0 1 19200 /dev/ttyS0This command attaches a KISS driver on the (X)NET device sdev0 on (X)NET port 0 using the Linux device /dev/ttyS0 (COM1) and 19200 baud tty speed.
detach <device>In the above example You would enter
detach sdev0the driver will be stopped and sdev0 can be attached again. For more details on attaching various hardware see the chapter "Attach Examples".
Devices | Class | Driver |
AX0 to AXF | Kernel AX25 devices | AX25 |
IP0 to IPF | AXIP, AXUDP devices | AXIP, AXUDP |
NULL | pseudo device for tests | ECHO |
SDEV0 to SDEVF | Serial devices (tty) | KISS, RMNC, SLIP, SMACK, SRPM, TRKISS,
TRSMACK |
VANESSA | Vanessa Cards | AX25 |
With the attach command the devices are assigned to drivers, (X)NET ports and Linux devices. The SDEV[0-f] devices are intended to be attached to ttys (e.g. /dev/ttyS0). The AX[0-f] devices can be assigned to network devices (e.g. bcsh0).
attach sdev0 kiss 0 1 19200 /dev/ttyS0If Your TNC has SMACK checksum KISS You should use the SMACK driver:
attach sdev0 smack 0 1 19200 /dev/ttyS0
attach sdev0 smack 0 2 115200 /dev/ttyS0Now ports 0 and 1 have been simultaneously attached.
attach sdev0 srpm 0 4 115200 /dev/ttyS0Now ports 0 to 3 have been simultaneously attached. The Serial Ring Protocol finds out how many ports are available and detects also the AX.25 baud rates automatically. On the TNC3 You have to run TRKISS.APL. On TNC2 You should use trkiss.bin EPROMs for this configuration.
attach ip0 axip 4 1 215.32.10.3Now all packets sent on port 4 are encapsulated in AXIP and transmitted to 215.32.10.3. All AXIP frames coming from 215.32.10.3 are now heard on port 4. For security reasons AXIP packets from other IPs are discarded.
attach ip0 axudp 4 1 215.32.10.3Now the frames are encapsulated in User Datagram Protocol (UDP) instead of AXIP. The destination and the local UDP port number are both 93.
att ip1 axudp 3 1 l94 d6093 192.168.44.1The "l94" sets the local UDP port number to 94. "d6093" sets the destination port number to 6093.
attach ip0 axip 3 1 cp 192.168.44.4
attach ip1 axip 4 1 cp 192.168.44.5
attach ip2 axip 5 1 cp 192.168.44.6
All three ports have to be attached separately. The Option "c" is used to suppress AXIP CRC calculation and checking (this is not necessary on a local ethernet). The Option "p" allows MAC parameters to be set via AXIP (TxDelay, Persistence and so on).
# Install Network Interface bcsh0 for a BayCom Modem on COM1
shell setserial /dev/ttyS0 uart none
shell modprobe baycom_ser_hdx mode="ser12*"
shell ifconfig bcsh0 hw ax25 dummy up
# Attach BayCom Modem to (X)NET
attach ax0 ax25 0 1 bcsh0