>"
I understand that the ADDNODE command is used to add a new destination node or to modify and existing destination node in one's node table. However, I'm hoping someone could clarify the syntax as well as >the meaning of "destination" and "neighbor."
>
>ADDNODE [alias:]call port neighbor [via digi 1[,digi2]] quality [obscnt]"
?
?
from Kantronics manual:
?
NODE - The term node refers to a network node such as a G8BPQ, X1-J, or NET/ROM
node. Non-network nodes such as KA-Node, conference bridges, and digipeaters do
not apply to this concept of operation.
NEIGHBOR NODE - A neighbor node is a node that your node can connect to "direct",
without using an intermediate node. Note that digipeater operation is allowed (2 max.).
This means that a node can be "out of range", but can still be considered a neighbor
since the connect path does not use any other nodes. All known neighbor nodes are
displayed with the ROUTES command.
DISTANT NODE - A distant node is a node that is too far away from you to connect to
"direct", requiring the use of one or more network nodes to reach. Distant nodes will not
be displayed with the ROUTES command.
DESTINATION NODE - A destination node is a node that your node knows how to
connect to, either directly (i.e. neighbor node), or, in the case of a distant node, by using
one or more intermediate network nodes. All known destination nodes (neighbor nodes
and distant nodes) are displayed with the NODES command,
All neighbor nodes are destination nodes, but all destination nodes are not
necessarily neighbors. Destination nodes will automatically appear in the nodes table
by virtue of your node monitoring your neighbor node broadcasts. A neighbor node will
automatically be listed in your nodes table and routes table. Neighbor node broadcasts
also contain information about other nodes that you may or may not be able to hear
"direct". These distant nodes will also be listed in your nodes table if they pass the
criteria for being listed (MINQUAL), and if there is sufficient room for them to be listed
(NETDEST).?
?
?
?
"ADDNODE [alias:]call port neighbor [via digi1[,digi2]] quality [obscnt]
This command is used to add a new destination node or to modify an existing
destination node in your nodes table. If the optional obscnt (obsolescence count) is set
to 0, the node will be permanently listed in the nodes table. Such a route will not be
updated or dropped from the nodes table by the K-Net auto-routing logic. If the neighbor
node callsign entered is not in the neighbor routes table, it is added with the default
quality for the specified port. As long as MINQUAL is equal to or less than QUALITY,
destination nodes (neighbor nodes as well as distant nodes) will be added automatically
to your nodes table as neighbor node broadcasts are received.
?
EXAMPLE - Addnode KSLVN:WD0EMR-1 1 WK5M-1 200
?
K-Net responds: Node added with new route
?
This adds the KSLVN node with the netcall of WD0EMR-1 to the nodes table. KSLVN is
available on port 1 (1200 baud) of the KPC-3 using the WK5M-1 (netcall) node as your
neighbor. An initial quality of 200 has been assigned to the new node. Unless "locked
in" with the ADDROUTE command, this path quality will most likely change since it is
recalculated based on node broadcasts that are received. In this case, WK5M-1 was a
previously unknown neighbor and the new route was automatically added.
?
EXAMPLE - Addnode WLAW:W0XI-1 1 W0XI-1 200
?
K-Net responds: Node added with new route
This would add the WLAW node with the netcall of W0XI-1 to the nodes table. In this
case, W0XI-1 is also the neighbor and is available on port 1 with an initially assigned
quality of 200.
?
EXAMPLE - Addnode YORK:WA0CPS-1 1 WK5M-1 70
?
K-Net responds: Node added
Downloaded from www.Manualslib.com manuals search engine
117
?
This would add the YORK node with the netcall of WA0CPS-1 to the nodes table. Since
WK5M-1 is an existing route (neighbor) a new route is not added.
?
EXAMPLE - Addnode CRT:KG5DT-1 1 WK5M-1 700
?
K-Net responds: Node added
?
In this case, the optional obscnt (obsolescence count) has been specified as zero. This
special case is useful in the event that your node is not able to hear this neighbor's node
broadcasts (i.e. if a digipeater(s) or gateway is being used). Normally, if a node is not
heard from for a period of time, the obsolescence counter will eventually drop it out of
the nodes table. However, this node (CRT) will remain in the nodes table permanently,
unless removed by the sysop
