The list of valid commands includes commands that may only be handled after a password verification has taken place. There are some commands which have additional capability after password verification has been provided. Below is a complete list of commands. The table includes whether the command requires password or not, and what command group it is in. I will create a web page for each command group and explain the commands in that group including syntax and expected response.
"User" Commands -- no password required
|
Full command name
|
Short description
|
? | Requests list of commands |
BYE | Disconnect from this node. |
CONNECT | Connect from this node to some other station or node |
INFO | Requests text INFO file from node |
L4T1 | Requests the ISO-Level-4 Timeout #1 value. This is an init value and is always the same. Set globally for all nodes. |
LINKS | Requests information about current ax.25 sessions |
LISTEN | Listen to specified port and print out traffic heard |
MHEARD | Monitor Heard -- Requests list of stations heard by the node on a particular port |
NODES | Requests a list of all nodes known by this node |
NRR | netrom route -- give with a destination node.
This is like traceroute unix command.
This sends a ping to a remote node and when it comes back, lists the path the ping took. |
PACLEN | Reads the packet length limit set in the node. I don't know why. Hint, it's 236 |
PASSWORD | Requests access to password protected commands. |
PORTS | Requests list of ports (radios) configured for the node |
ROUTES | Requests list of neighbor nodes for this node |
STATS | Requests file of statistics for this node. |
UNPROTO | Enters UNPROTO mode, where you can send UI messages.
The command format is UNPROTO Port CALL [Optional Digis].
When in Unproto Mode anything you type will be send as a UI frame to the port and destination you specified.
This could be used in conjunction with the LISTEN command to have an multiuser conversation.
Use Ctrl/Z to exit UNPROTO mode |
USERS | Requests list of stations connected into or through this node's command interpreter |
|
Note: All commands may be entered in lower case. They are not case sensitive.
|
| |
Consider this result: > 4 G0INA-3 120 48! |
> | This field can be blank or have a chevron. > means the link is in use. |
4 | port number, defines which radio the route is over. See PORTS command. |
G0INA–3 | Callsign and SSID of neighbor |
120 | Quality multipler, used to limit distribution of neighbor's node data |
48 | Number of nodes whose best route is over this neighbor |
! | Can be blank or exclamation. If blank, this neighbor was heard over the air and was not specified by the admin. If ! then this neighbor is locked in and will show on this list regardless of whether it is actually on the air. |
| |
Consider this result: > 4 G0INA-3 120 48! 19305 819 4% 0 0 21:40 0 |
> | This field can be blank or have a chevron. > means the link is in use. |
4 | port number, defines which radio the route is over. See PORTS command. |
G0INA–3 | Callsign and SSID of neighbor |
120 | Quality multipler, used to limit distribution of neighbor's node data |
48 | Number of nodes whose best route is over this neighbor |
! | Can be blank or exclamation. If blank, this neighbor was heard over the air and was not specified by the admin. If ! then this neighbor is locked in and will show on this list regardless of whether it is actually on the air. |
19305 | Info frames sent |
819 | Info frames retransmitted |
4% | Retry Rate - the ratio of the above 2, as a percentage(or * if both are zero) |
0 | Non-standard maxframe (from config file) |
0 | Non-standard frack ( ditto ) |
21:40 | Time the last NODES broadcast was heard from this node. |
0 | The last figure is only present if there is an active link. It is the number of frames queued to be sent. Up to and including version 4.05e, this only
counts frames queued above the link level - there may be up to another 8 queued at link level. With version 4.05f and above it includes all frames queued. |
Uptime (Days Hours Mins) | Shows how long ago the node started. In the above example it was 15 days ago |
Semaphore Get-Rel/Clashes | |
Buffers:Max/Cur/Min/Out/Wait | Count of buffers, used for packet frame handling.
Max is how many there is room for in system memory.
Cur is how any there are available when this STATS command was processed.
Min is how many there were when the node was most loaded.
Out is how many times a request for a buffer by the software was rejected because there were none available
Wait ?? Undefined in the documentation |
Known Nodes/Max Nodes | Known Nodes is how many nodes this node knows about right now.
Max Nodes is how many nodes the system was configured to have room for. |
L4 Connects Sent/Rxed | |
L4 Frames TX/RX/Resent/Reseq | The L4 frames resent count is the number retransmitted because an ACK wasnt received within the L4 timeout period. The Reseq count is the number of frames received out of sequence, but subsequently used because the missing frame(s) eventually arrived.
|
L3 Frames Relayed | |
|
Port 01 Port 02 Port 03 Port 32 | Column headers for each port. There is a set of level 2 counters for each port. Note that port 32 is automatically created to permit TARPN TX operation and refers to traffic through that interface. |
L2 Frames Digied | Frames using the legacy digipeater interface to relay through a port or across the node. Deprecated. |
L2 Frames Heard | |
L2 Frames Rxed | |
L2 Frames Sent | |
L2 Timeouts | |
REJ Frames Rxed | A large number in the 'REJ received' field may indicate that your Maxframe is too high. Similarly a large number in 'RX out of sequence' may indicate the the station talking to you has too large a maxframe. |
L2 Resequenced | |
Undrun/Poll T/o | Underuns indicate a similar problem in responding to TX interrupts, but only apply to HDLC cards. As you cant get a TX underrun on an async port, this field is also used to count timeouts on a polled KISS system. |
RX Overruns | RX Overruns indicate characters lost because the software didn't process the interrupts fast enough. If you are running KISS ports, and you get a lot (ie a significant percentage of L2 frames heard), try reducing the speed of the link from the PC to the TNC. If you are using an HDLC card (DRSI or PC120), particularly at high speed, then there isnt much you can do except buy a faster machine. (But I would like to hear from anyone having problems running at 9600 baud or above - I may be able to speed up the routines a bit). |
RX CRC Errors | . |
FRMRs Sent | . |
FRMRs Received | . |
Frames abandoned | Frames abandoned counts the number of frames discarded because they have been waiting to be sent (for DCD to clear) for more than 60 secs. If a lot occur, then either your squelch is a bit dodgy, or the channel is VERY busy. Only used for HDLC cards. |
Link Active % | Link Active shows two values for each port. The first is the % of time in the last minute that your station was transmitting, and the second the % the channel was active (sum of Transmitting and DCD active). Only maintained for HDLC ports. Note that of you are using SOFTDCD, then the indicated % active may be an overestimate. |
If you have more than 7 ports the display starts to look a bit untidy, so
there are now two options on the STATS command:
USERS command
The USERS command lists the stations currently using the node.
NOTTS:G8BPQ-3} G8BPQ Network System V3.21 (95)
Host6(NOTTS:G8BPQ-3)
Host3(NOTTS:G8BPQ-3) <--> Circuit(LRG7:G0GDR-1 G8BPQ-1)
Uplink(G9XXX) <~~> Downlink(G9YYY)
Host is an internal (Normally BBS Port)
Circuit is a link from/to another node.
Uplink is a connection from a normal Ax.25 station.
Downlink is a connection to a normal user.
The <--> indicates an active session. <~~> indicates a session being set up.
The number on the end of the header line is the number of free buffers.