| Parameter 1 Max destination node list size; (default=100,
minimum=1, maximum=400)
|
| Defines the maximum number destination nodes allowed in the node's
routing table. Each destination consumes 32 bytes of RAM. The
system node operator (SNO) can use this parameter to limit the amount of
RAM that is allocated to the routing table, thus ensuring that sufficient
space remains for other node buffers. Normally there are 720 free buffers
in the X-1J4 node at startup.
|
|
| Parameter 2 Worst quality for auto-update; ( default=60,
minimum=0, maximum=255)
|
| Defines the poorest route quality that can be added to the node's
automatic routing table. The system node operator (SNO) can use this
parameter to limit the automatic routing update function to accept
only higher-quality routes. In addition, the automatic update
function can be disabled altogether by setting this parameter to zero.
|
|
|
Parameter 3 Channel 0 (Radio Port) quality; (default=60,
minimum=0, maximum=255)
|
|
Defines the quality of the radio channel connected to the node's
HDLC port. The system node operator (SNO) should set this parameter to
an appropriate quality value in accordance with the speed, reliability,
and congestion anticipated on the channel. The default value
of 192 is appropriate for a 1200-baud user-accessible frequency.
|
|
|
Parameter 4 Channel 1 (RS232 Port) quality; ( default=255,
minimum=0, maximum=255)
|
|
Defines the quality of the TNC-to-TNC interconnect channel connected
to the node's RS232 port. The system node operator (SNO) should set this
parameter to an appropriate quality value in accordance with the speed,
reliability, and congestion anticipated on the channel. The default value
of 255 is appropriate for a 9600-baud two-modem interconnect cabled gateway.
|
|
|
Parameter 5 Obsolescence count initializer; ( default=9,
minimum=0, maximum=255)
|
|
Defines the initial value given to the obsolescence counter of a
route that has been recently added or updated by the node's automatic
routing table. The obsolescence count of a route is also reinitialized
to this value whenever the route is successfully used or when the period
set to the noted value shown in the STATS table of the X-1J4 node. The
obsolescence count of a route is decremented once each auto-update broadcast
interval (see parameter 7). Periodic decrementing of route obsolescence
counts can be disabled altogether by setting this parameter to zero (0).
|
|
|
Parameter 6 Obsolescence count minimum to be broadcast
( default=5, minimum=1, maximum=255)
|
|
|
In the X-1J4 node, this parameter defines the minimum obsolescence count
threshhold below which a route will not be included in the node's automatic
routing broadcasts. The purpose of this threshhold is to prevent the node from
broadcasting out dated routing information to other nodes. Under normal circumstances
this parameter should be assigned a value no greater than the value of parameter 5.
If parameter 5 is greater, the X-1J4 node's broadcasts will NOT include destination
nodes other than itself.
|
|
|
Parameter 7 Auto-update broadcast interval (seconds) ( default=1800,
minimum=0, maximum=65535)
|
|
|
Defines the number of seconds between automatic routing broadcasts issued by the node.
The default value of 3600 specifies an hourly broadcast. X-1J4 node broadcasts can
be disabled altogether by setting this parameter to zero (0).
|
|
|
Parameter 8 Network TIME TO LIVE initializer
( default=16, minimum=0, maximum=255)
|
|
|
Defines the initial value of the time-to-live; field in the Network
Header of all network-layer frames originated by this node. The time-to-live field
is decremented by each intermediate node that relays the frame. If the time-to-live
value ever reaches zero, the frame is discarded. This protects the network against
frames living forever as the result of a routing loop.
|
|
|
Parameter 9 Transport timeout (seconds) ( default=180,
minimum=5, maximum=600)
|
|
|
Defines the number of seconds between transport-layer retries.
|
|
|
Parameter 10 Transport maximum tries ( default=3, minimum=2,
maximum=127)
|
|
|
Defines the maximum number of transport-layer tries attempted before a circuit failure is
reported.
|
|
|
Parameter 11 Transport acknowledge delay (seconds) ( default=2,
minimum=1, maximum=60)
|
|
Defines the number of seconds' delay used by the transport layer from the time it receives
an information message until it sends an information-acknowledge message. The purpose of
this delay is to give the acknowledgement an opportunity to be added to another outgoing
information frame or packet.
|
|
|
Parameter 12 Transport busy delay (seconds) ( default=60,
minimum=1, maximum=1000)
|
|
|
Defines the maximum number of seconds that the transport layer will remain choked; as the result of an incoming message
that has the choke flag bit set. The purpose of this timeout is to prevent an
infinite hangup in the event that the unchoke message is lost.
|
|
|
Parameter 13 Transport requested window size (frames)
( default=4, minimum=1, maximum=127)
|
|
Defines the maximum number of incoming, out-of-sequence, information messages that the
transport layer will buffer while waiting for the next expected information message to arrive. Also defines
the maximum number of outgoing information messages that the transport layer will send
without receiving acknowledgement.
|
|
|
Parameter 14 Congestion control threshhold (frames) ( default=4,
minimum=1, maximum=127)
|
|
Defines the maximum allowable backlog of messages that the transport layer will buffer
before it sends a choke message. Also defines the maximum allowable backlog of frames
that the link layer will buffer before it sends an receive-not-ready (RNR) control
frame.
|
|
|
Parameter 15 No-activity timeout (seconds) (default=900,
minimum=0, maximum=65535)
|
|
Defines the maximum number of seconds that a transport-layer circuit or a link-layer
connection can remain idle (i.e., no information transfer in either direction) before
it is automatically disconnected.
|
|
|
Parameter 16 P-persistence (p=/256) ( default=64,
minimum=0, maximum=255)
|
|
Together with slot time (parameter #17), defines the exponential delay algorithm
used by the node when keying up its transmitter. When the node has something to
transmit and the channel is clear, the node generates a random integer in the
range 0 - 255. If the random number is less than or equal to the P-persistence
parameter, the node keys up its transmitter immediately. Otherwise, the
node delays for one slot time, generates a new random number, and repeats the procedure.
|
|
|
Parameter 17 Slot time (10ms increments) ( default=10,
minimum=0, maximum=127)
|
|
Together with P-persistence (parameter #16), defines the exponential delay algorithm
used by the node when keying up its transmitter. The default value of 10 corresponds
to a slot time of 100 milliseconds. NOTE to the wise... and maybe the "unwise,"
setting this parameter to 0 (zero) may make the node respond fast! Maybe too fast.
|
|
|
Parameter 18 Link T1 timeout frack; (seconds)
( default=5, minimum=1, maximum=15)
|
|
Defines the number of seconds between link-layer retries. When digipeating is used,
this value is multiplied by 2 x D+1, where D is the number of digipeaters.
|
|
|
Parameter 19 Link transmit window size maxframe;
( default=3, minimum=1, maximum=7)
|
|
Defines the maximum number of outgoing information frames that the link layer will send
without receiving acknowledgement.
|
|
|
Parameter 20 Link maximum tries ( default=10, minimum=0,
maximum=127)
|
|
Defines the maximum number of tries that the link layer will attempt before reporting a
link failure. If this parameter is set to zero (0), the link layer will retry forever
(we recommend that this parameter is NEVER set to zero (0) ).
|
|
|
Parameter 21 Link T2 timeout (10ms increments) (default=200,
minimum=0, maximum=65535)
|
|
Defines the delay (measured in 10-millisecond increments) used by the link layer from the
time it receives an information frame until it sends an acknowledgement (RR, RNR, or REJ)
control frame. The purpose of this delay is to give the acknowledgement an opportunity
to be attached to another outgoing information frame.
|
|
|
Parameter 22 Link T3 timeout (10ms increments) (default=0,
minimum=0, maximum=65535)
|
|
Defines the maximum no-activity period (measured in 10-millisecond increments) permitted
by the link layer before it issues a poll to make sure the link is still intact. This
timeout is also used to break link-layer choke deadlocks. NOTE: This parameter is
the same as CHECK, and can be defaulted to 0 as a means of reducing node QRM.
|
|
|
Parameter 23 AX.25 digipeating (1=enabled, 0=disabled)
(default=0, minimum=0, maximum=1)
|
|
Defines whether or not the node will perform AX.25 digipeating. The default value of 1
causes digipeating to be enabled.
|
|
|
Parameter 24 Validate callsigns (1=enabled, 0=disabled)
(default=1, minimum=0, maximum=1)
|
|
Defines whether or not the node will perform validation checks on amateur callsigns.
The default value of 1 causes callsign validation to be enabled.
|
|
NOTE; If callsign validation is turned OFF (0), users will experience long
delays if they request connects to inactive nodes before getting back a FAILURE WITH,
response.
|
|
|
Parameter 25 Station ID beacons (2=on, 1=conditional,
0=off) (default=2, minimum=0, maximum=2)
|
|
Defines whether or not the node will broadcast station-identification beacons.
The default value of 2 causes station identification to be broadcast every 10 minutes.
The value of 1 causes station identification to be broadcast only if the node has
transmitted since the last beacon. A zero (0) will disable station identification.
|
|
NOTE; Many sysops set this parameter to 0 as a means to reduce unnecessary node
QRM on the channel. The X-1J4 node ID's itself each time it sends a packet, so no legal
requirement to have ID's turned on.
|
|
|
Parameter 26 CQ Broadcasts (1=0n, 0=off) (default=1,
minimum=0, maximum=1)
|
|
Defines whether or not the node will broadcast AX.25 UI-frames in response to the CQ command.
Even if such broadcasts are disabled by setting this parameter to zero, the other features of
the CQ command continue to operate normally. The default value of 1 enables CQ broadcasts.
NOTE; When a station connected to an X-1J4 node through several distant nodes issues
a UI QRA command, the distant node will poll stations that have the QRA feature
for an ID. After about 40 seconds, the station that sent the polling (UI QRA) can issue the
Mheard command and receive a list of the station that identified in the area of the distant
X-1J4 node that was polled.
|
|
|
WebMaster, Buck Rogers K4ABT "
