ATTACH LOGICAL INTERFACE COMMANDS

The second type of attach commands is for attaching servers rather than hardware ports. These commands have the same format as in the JNOS program. Throughout the rest of these sections, we will use the names port1, port2 and port3 to indicate the serial port and the two internal ports, respectively.

NETROM

The netrom interface is attached with the 'attach netrom' command. This command should not be needed in autoexec.nos as it is normally executed by default when the netrom server is started.

AXIP

To attach an AXIP tunnel, the format is

attach axip <name> <mtu> <ipaddress> <call>

If we have two systems capable of running axip,
'jnos1', call wg7j-1,  ip 44.26.0.162, and the other
'jnos2', call k7uyx-1, ip 44.26.0.98, then:

On one end of the tunnel, jnos1 has the following:

attach axip tunnel1 256 44.26.0.98 wg7j-10

On the other end of the tunnel, jnos2 has the line:

attach axip tunnel2 256 44.26.0.162 k7yux-10

A user connected to jnos1 will now see a new port called 'tunnel1' in the 'P' command. Users connected to jnos2 see a new port called 'tunnel2'. You can set descriptions with the 'ifconfig <iface> description' command.

If ax.25 station ka7ehk wants to connect cross band to jnos1 via jnos2, ka7ehk needs to know the callsign of the tunnel interface to use. Here, this call is k7uyx-10. Thus the following should be sent:

	connect wg7j-10 via k7uyx-10.

This is what goes around:

ka7ehk sends the connect attempt.

ka7ehk -> wg7j-10 v k7uyx-10

jnos2 receives this and decides the digi call is for the tunnel interface.

jnos2 swaps calls to keep track of the return path, and digis to port 'tunnel2'

ka7ehk -> wg7j-10 v k7uyx-1*

jnos1 receives this, and replies with the connect acknowledge (via tunnel1)

wg7j-10 -> ka7ehk v k7uyx-1

jnos2 receives this, examines call, swaps and digis to the 'real' radio port

wg7j-10 -> ka7ehk v k7uyx-10*

ka7ehk receives this, and the connection is established. All further data exchange will follow the same route !