The Axports File

What does it do?

This file associates a callsign-SSID with the name of a port. This association must be unique, hence the use of the SSID. All port names must be unique and all the callsigns they 'point to' must be unique. At the beginning of each row, then, there must be a unique pair (the port name and the callsign-SSID) of data that does not occur in any other row! (No repeating groups... anywhere!)

This is among the first files read by the AX25 system. It links a callsign with a port. (These ports, through their callsigns, eventually become bound to configurable network devices, just like ppp0, or lo, and in fact become ax0, ax1, or ax2, etc., as they are called into service)

The file shown below is my actual axports file. Only the uncommented lines are actually read by the programs. You can see how I have tried many set ups and tested various ports. (Sometimes, a date and brief explanation can be a great help 6 months later...)

My Axports File 


# /etc/ax25/axports
# Mod: 07/27/97, 04-30-98
#
# port name....: Any meaningful combination of letters & numbers
# callsign.....: Your call sign (UPPER CASE) with an SSID, none defaults to -0
# speed........: What your TNC's serial line is set for, usually 9600
# paclen.......: One frame length
# window.......: Should be equal to, or less than, what's in your TNC
# description..: The frequency and/or a node name, or more info about the port 
#
# The format for this file is:
# ----------------------------------------------------------------------------
# port | callsign  | TNC   |         |         |
# name | w/ SSID   | speed |  paclen |  window |  description
# ----------------------------------------------------------------------------
#
# NOTE: there can be ONLY one occurrance of a port/callsign-ssid key!
#
# vhf   KA1FSB          9600    255     2       145.010 Mhz  "MBOS1-K1UGM" 1200 bps  KAM  LinuxNode
#
# vhf   KA1FSB-2        9600    255     2       145.010 Mhz  "MBOS1-K1UGM" 1200 bps  KAM   FSB-BBS
# 
#vhf    KA1FSB-8        1200    256     2       145.090 Mhz  "Wellesley, MA" 1200 bps  Radio AFSK Modem
#
bc0    KA1FSB-7        1200    256     2       145.090 Mhz  "Wellesley, MA" 1200 bps  Radio AFSK Modem
#
# aprs  KA1FSB-4        0       255     2       144.390 Mhz  APRS-Monitor  1200 bps  KAM node controller
#
# hftcp KA1FSB-1        9600    64      2       14.105 Mhz  Wellesley, MA    300 bps  KAM TCP/IP
# 
#
sm0    KA1FSB-8        1200    255     2       145.630 Mhz  "Wellesley, MA" 1200 bps soundmodem
#
#hf     KA1FSB          9600    64      1       14.105 Mhz  "NETWORK 105"    300 bps  KAM  PMS-BBS 
#
# hf1   KA1FSB-8        9600    255     2       14.105 Mhz   TCP/IP port   300 bps  KAM node controller
#
# vhf1  KA1FSB-9        9600    128     4       145.770 Mhz  Wellesley, MA
#
axip0   KA1FSB-10       38400   1024    2       Internal AXIP (Lan) Link: 44.56.26.10 <-> 44.56.26.11
#
#axip1  KA1FSB-11       38400   1024    2       Internal AXIP link
#
#jnos   KA1FSB-5        38400   1024    2       Internal Link
#

      Mail Document Request for:   axports
  A Few Caveats:

  • Be sure your local mailer is properly "hooked" into your browser.
  • Allow up to 24 hours for delivery, although 3-6 is typical...
  • Mailed copy, being the latest "on-line" version, may differ slightly from above.
  • Click on "Mail it to me" below to activate your mailer, then send from there.
  • Please don't change the subject field. (Additional text body comments OK.)
  • Sometimes server is down for extended periods of time... (1-10+ days)
  • (You obtain, modify and run all data/code at your own risk.)


Enough "excuses," just Mail it to me!

  What if ...

  • If your browser-linked mailer doesn't seem to respond, you may send a null-bodied email to ka1fsb@att.net with a subject of "Data Request - axports" not including the quotes... (Some browsers and their mail agents do not like excessive string data in the mailto format.)


(Courtesy KBNorton Computer Services)