Online Amateur Radio Community Wiki

User Tools

Site Tools

Trace: • hlpgeneral • hlppztdos • hlpftp
packet:xrpi:manpages:hlpgeneral

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
packet:xrpi:manpages:hlpgeneral [2025/04/19 13:30] – created m0mzfpacket:xrpi:manpages:hlpgeneral [2025/04/19 18:01] (current) – removed m0mzf
Line 1: Line 1:
-=======General Help======= +
-=====AMSG.HLP===== +
-<code> +
-The AMSG command switches you into "APRS Messaging" mode, enabling you +
-to exchange messages and bulletins with APRS and UI-View users. +
-Syntax is "AM[sg] <port>", where <port> is the number of the radio +
-port on which traffic will be sent and received. e.g. "AM 13" will use +
-port 13. +
-</code> +
----- +
-=====ANSI.HLP===== +
-<code> +
-The ANSI command switches ANSI colour mode on/off, and reports the +
-current mode. It may be shortened to "AN". +
-    Syntax: AN[si] [on | off] +
-    Examples: ANSI          Reports current on / off state. +
-              ANSI ON       Turn colour on. +
-To use ANSI colour, you need an ANSI-capable terminal, such as +
-</code> +
----- +
-=====ARP.HLP===== +
-<code> +
-The ARP command displays the ARP (Address Resolution Protocol) table,  +
-</code> +
----- +
-=====BLOGCMDS.HLP===== +
-<code> +
-Blog commands are as follows (31 lines): +
-B[ye]       Returns you to the node (same as Q[uit]). +
-C[reate]    Begins the creation of a blog article (sysop-only). +
-D[elete]    Deletes an article or reply that you have entered. +
-H[elp]      Displays a help summary. +
-LIK[e] [n]  (shortcut "K") is used to "like" either the article you've +
-            just read, or article number "n". +
-L[ist]      Displays or re-displays the header information of up to 5 +
-            articles at a time. Headers are displayed in reverse +
-            chronological order, i.e. the most recent at the top. +
-N[ewer]     Displays up to 5 newer articles, i.e. forward in time. +
-O[lder]     Displays up to 5 older articles, i.e. back in time. +
-Q[uit]      Returns you to the node (same as B[ye]. +
-R[ead] n    Reads article number "n". +
-REP[ly] [n] (shortcut "Y") begins a reply to the article you've just +
-            read, or to article number "n". +
-V[iew]      View replies to an article. +
-</code> +
----- +
-=====BLOG.HLP===== +
-<code> +
-The BLOG command connects you to the sysop's blog, either at this +
-node, or at another XRouter. +
-    Syntax: BL[og] [nodecall | nodealias] +
-The blog is a text-only, packet radio version of a "web log". It is a +
-space for sysops to post "articles", which other people can "like" or +
-reply to. +
-Only SYSOPS can create original articles, but anyone may add comments +
-to an existing article. Comments are not restricted in size. +
-</code> +
----- +
-=====BYE.HLP===== +
-<code> +
-The "BYE" command, which can be abbreviated to "B" disconnects you  +
-from XRouter and terminates all dependent sessions. +
-This is useful when you do not have easy access to a TNC's "command  +
-mode", or when you have uplinked from another node with the "stay"  +
-</code> +
----- +
-=====CHAT.HLP===== +
-<code> +
-The CHAT command connects you to the chat server, either at this node, +
-or at another XRouter of your choice, allowing you to conduct +
-conferences with one or more other users.. +
-    Syntax: CH[at] [nodecall | nodealias] +
-There are 65536 separate channels (or "rooms") of which the first 256 +
-(*except room 101) are local to this system, and the remainder are +
-linked to other systems, allowing widely separated users to chat. +
-(*Room 101 links to RoundTable/BPQ chat, if sysop has configured it.) +
-The chat server may also be reached by connecting to its own callsign, +
-either directly or through the Netrom network, or by telnetting to +
-tcp port 3600 (if the sysop has enabled it). +
-</code> +
----- +
-=====CONNECT.HLP===== +
-<code> +
-The CONNECT command, which may be abbreviated to "C", instructs the  +
-node to make an outgoing (downlink) AX25 level 2 or 4 connection  +
-with another system. +
-If the target is a known node (i.e. one which is in the nodes table) a  +
-port number is not required, and will be ignored if supplied.  The  +
-node will attempt to make a level 4 connection with the target,  +
-using information from the routing tables.  However, a level 2  +
-connection with an immediately adjacent node may be forced, either by +
-using  the target's alias with an arbitrary SSID, specifying a port +
-number if required (e.g. C 4 MLVN-1), ot by prefixing the target's +
-nodecall with an exclamation mark (e.g. C 4 !G4FPV) +
-If the target is an XRouter, and it is in the nodes table, adding a +
-"service number" after the nodecall or alias, e.g. "C kidder 2", +
-connects you to that service, in this example the target's PMS. Type +
-"H SERVICES" for a list of XRouter's "standard services". +
-If the target is not a known node, XRouter will attempt to make a  +
-level 2 connection.  On multi-port systems, a port number must be  +
-specified. +
-The "V" (via) parameter allows up to 7 digipeaters to be specified,  +
-e.g.:  "C 3 G6YAK V G8NTU G8EPR" +
-The "S" (stay) parameter, e.g. "C <nodecall> S" causes the uplink  +
-session to stay connected when the downlink session to the target node  +
-</code> +
----- +
-=====CQ.HLP===== +
-<code> +
-The CQ command can only be used in LISTEN mode. It sends a CQ message +
-onto the frequency you are LISTENing on. Optional text and digipeater +
-path may be supplied. +
-    Syntax: CQ [v[ia] digi,digi...] [text] +
-The digipeater string, if included, must not include any spaces. +
-    Examples: CQ +
-              CQ Parks on the air +
-              CQ v g8pzt,m0wof Gloucester Docks +
-The message is sent only once, but you may repeat the command at +
-suitable intervals. +
-</code> +
----- +
-=====DATE.HLP===== +
-<code> +
-The DATE reports the system date at this node. +
-</code> +
----- +
-=====DX.HLP===== +
-<code> +
-The DX command displays a list of the most distant APRS stations heard +
-by XRouter, along with their positions, distances and headings. +
-    Syntax: DX [port] +
-If the optional port number is given, e.g. "DX 13", only the stations +
-received on that port will be shown. +
-Whether or not the DX list records digipeated stations depends on how +
-the sysop has configured it.  If included, digipeated stations are +
-clearly identifiable by an entry in the "Via" field, which is blank +
-for directly heard stations. +
-If the sysop hasn't bothered to define the router's position, no DX +
-</code> +
----- +
-=====ECHO.HLP===== +
-<code> +
-The ECHO command starts an echo session, in which anything you type +
-is echoed back to you.  This has little use, except for link testing. +
-An echo session can be terminated either by typing "/x" on a new line, +
-</code> +
----- +
-=====FINGER.HLP===== +
-<code> +
-The "FINGER" command display information about users of this and other  +
-systems. +
-    Syntax: FINGER <user | user@host | @host> +
-If the command is of the form "FINGER <user>", where <user> may be a  +
-callsign or other "handle" the router displays any information it has  +
-on that local user. +
-If the form "user@host" or "@host" is used, XRouter will attempt to  +
-resolve "host" into an IP address and establish a contact with  +
-the finger server on that host. +
-e.g. FINGER g8pzt          - Info on local user g8pzt +
-</code> +
----- +
-=====GPING.HLP===== +
-<code> +
-The GPING command sends a GCMP echo request to the specified target. +
-    Syntax: GP[ing] <addr> [len [sec]] +
-If the target understands the protocol it will return a reply, +
-allowing the number of hops and the round trip time to be estimated. +
-It is mainly of use as a network diagnostic. +
-Examples: GPING 131.91.2.1           Single ping of minimum size +
-          GPING 131.91.2.1 50        Single ping with 50 bytes data +
-          GPING 131.91.2.1 512 10    Ping 512 bytes every 10 secs +
-If no reply is received, either the target doesn't understand the +
-protocol, or hasn't been configured for GNET, or is currently +
-</code> +
----- +
-=====GTRACERT.HLP===== +
-<code> +
-The GTRACERT commmand traces the route to a Globalnet host. +
-    Syntax:  GT[racert] <addr> [maxhops [maxwait(ms)]] +
-    <addr> is the Globalnet address of the target host. +
-           (this is a dotted quad, but is NOT an IP address) +
-    [maxhops] is the maximum number of hops to trace (default 30). +
-    [maxwait] is the maximum time to wait for a reply from each +
-              router. The default is 4 seconds. +
-The only mandatory parameter is <addr>.  +
-Examples:   +
-    GT 87.127.21.3       - Trace 87.127.21.3 with default parameters. +
-    GT 44.141.91.2 10    - Trace 44.131.91.2 to a max of 10 hops. +
-</code> +
----- +
-=====HELP.HLP===== +
-<code> +
-The HELP command, which may be abbreviated to "H", displays help for  +
-commands and other topics. +
-    Syntax: HELP [cmd | topic] +
-If no arguments are given, a short text gives directions on how to  +
-access help. +
-If the argument is a topic or a command name, the help file for that  +
-command or topic is displayed.  The argument "*" will list all the  +
-help topics available. +
-Examples:  H *      - List available help topics. +
-</code> +
----- +
-[email protected]===== +
-<code> +
-The "@" command is used by remote sysops to request and answer  +
-the password challenge, in order to gain full sysop status. +
-If you enter "@" alone, the system replies with a matrix consisting of  +
-5 lines of 5 numbers.  +
-You must then choose ONE of the lines, and send the "@" command again, followed by the 5 characters from the password string which correspond to the 5 numbers on the chosen line.   +
-There must be a space after the "@" but no spaces between the +
-</code> +
----- +
-=====HOST.HLP===== +
-<code> +
-The HOST command displays information about a TCP/IP host, and is used +
-mainly for looking up a hostname from an IP address or vice versa. +
-   Syntax: HO[st] <hostname> | <ip_address> +
-   Examples: HO kidder.ampr.org +
-             HO 44.131.91.245 +
-The quality of the information returned depends on how the sysop has +
-configured the router and whether or not an external DNS can be +
-</code> +
----- +
-=====INFO.HLP===== +
-<code> +
-The INFO command, which may be abbreviated to "I", displays +
-information about the node and other topics chosen by the sysop. It +
-can also display information from other XRouter nodes. +
-    Syntax: I[NFO] [topic | nodecall | nodealias] +
-If you use "I" alone, some information about the node should be +
-displayed, if the sysop has set it up. +
-The command "I[nfo] PAGE" always provides a summary of the node info +
-If you send "I *", the available info topics are listed, and you can  +
-read one by sending "I" followed by a space, then the topic. +
-If the command's argument is the callsign or alias of another XRouter +
-that is in this node's table, a summary of information about that +
-node is displayed. +
-Examples: I FOURPAK   - Displays information about the FOURPAK group. +
-</code> +
----- +
-=====IP.HLP===== +
-<code> +
-The IP sub-commands are used to display and alter the contents of the  +
-table responsible for routing of IP datagrams. +
-The only one available to non-sysops is "IPR[outes]", which displays +
-the IP routing for amprnet data only. +
-"Len" is the number of bits (left to right) of the address which are +
-matched by the routing entry. +
-"Gateway" is where datagrams are sent, if not direct. "0.0.0.0" +
-denotes a direct route. +
-"Mode" has many variants, the most common is "d" (datagram). +
-A non-zero "Timer" denotes a temporary (learned) entry. +
-</code> +
----- +
-=====IPROUTE.HLP===== +
-<code> +
-The IPROUTE command, which may be abbreviated to IPR, displays the  +
-contents of the table responsible for routing of IP datagrams. +
-For each route it displays the IP address, the subnet mask, the  +
-gateway address, the port and the mode (Datagram, VC or Netrom). +
-"Len" is the number of bits (left to right) of the address which are +
-matched by the routing entry. +
-"Gateway" is where datagrams are sent, if not direct. "0.0.0.0" +
-denotes a direct route. +
-"Mode" has many variants, the most common is "d" (datagram). +
-</code> +
----- +
-=====J.HLP===== +
-<code> +
-The J (jlist) command lists the callsigns of the last 20 stations who +
-</code> +
----- +
-=====L4LINKS.HLP===== +
-<code> +
-The L4LINKS command shows information about the NetRom Layer 4 links +
-currently originating or termnating at this node. +
-    Syntax: L4[links] +
-The display is like this: +
-Local    Cct  Remote   @Host    Cct  S Txq Rxq  Rtt Tr T/o Con Cho Ack +
-G8PZT-9  0001 G8PZT-8  G8PZT-8  1253 2   0   0  288  0 120 121   0   0 +
-"Local" and "Remote" are the "user" callsigns. +
-"Host" is the other end's node callsign. +
-"Cct" is the circuit number. +
-"S" is the link state. +
-"Txq" is the number of frames queued for transmission. +
-"Rxq" is the number of frames queued in the receiver. +
-"Rtt" is the average Round Trip Time in milliseconds. +
-"Tr" is the number of retries. +
-"T/o" is the L4T1 interval in seconds. +
-"Con" is the remaining connection timer interval in seconds. +
-"Cho" is the remaining choke timer interval in seconds. +
-</code> +
----- +
-=====LANG.HLP===== +
-<code> +
-The LANG command shows the available languages, reports the +
-current language, and allows the language to be changed. +
-    Syntax: LA[ng] [en | fr | es | nl] +
-Only English (en), French (fr), Spanish (es) and Dutch (nl) are +
-</code> +
----- +
-=====LINKS.HLP===== +
-<code> +
-The LINKS command lists the AX25 layer 2 links originating or +
-terminating at this node. +
-It shows the callsigns being used at both ends of the link plus some +
-</code> +
----- +
-=====LISTEN.HLP===== +
-<code> +
-The LISTEN command, which can be abbreviated to "LIS", initiates +
-"listen mode" on a specified PORT. +
-In this mode you are able to "monitor" traffic on the chosen port, +
-and the node will accept incoming connections to your callsign. +
-    Syntax: LIS[ten] <portnum> [0] +
-Non-sysops may only listen on RADIO ports, and you can not listen on +
-the port which you are using to connect to the node. All the normal +
-node commands are available in this mode. +
-Traffic monitoring is enabled by default, but may be disabled by +
-supplying 0 (zero) as an optional additional argument.  +
-In listen mode, you may use the CQ command to advertise your presence. +
-Your SSID is inverted in the usual Net/Rom way, so if you are +
-connected to the node as G9XYZ, you will be listening and +
-broadcasting as G9XYZ-15. +
-To exit listen mode use "LISTEN 0" or "LISTEN OFF" +
-    See Also: CQ    - Call CQ whilst in listen mode. +
-</code> +
----- +
-=====MAN.HLP===== +
-<code> +
-The MAN command is used to access the online sysop's manual, which +
-is a collection of pages, each covering a different command or +
-topic. The MAN pages are designed for sysop use, and are not +
-available to non-sysops. +
-   Syntax: MAN [command | topic] +
-   Example: MAN ARP  -- Display manual page for ARP command. +
-Entering MAN alone displays a list of available pages. +
-To read a specific page enter MAN followed by the command or topic +
-for which you require help. +
-The manual is divided into several sections, usually indicated in +
-parentheses after the command name, e.g. ARP(1).  Section 1 is the  +
-</code> +
----- +
-=====MHEARD.HLP===== +
-<code> +
-If the facility is enabled on the specified port, the MHEARD command  +
-lists the most recently heard stations on that port, arranged in +
-descending time order. +
-    Syntax: M[heard] <portnum | ALL> +
-    Examples:  MH 4     - Lists stations recently heard on port 4 +
-               MH ALL   - Lists stations recently heard on any port +
-Each entry shows the date / time of last reception, and the total +
-number of frames heard from that station. +
-If the station was digipeated, the digipeater's callsign is shown +
-in the VIA column, and if the station's beacon included an APRS +
-position, that position is shown, alog with the distance and +
-direction from this node. +
-The characters in the TYPE field indicate whether or not the station +
-</code> +
----- +
-=====NFTP.HLP===== +
-<code> +
-The NFTP command is for sysops to exchange files between nodes, but +
-can also be used to exchange files between non-sysops and the node. +
-    Syntax: NF[tp] <nodecall> +
-In "non-sysop" mode <nodecall> MUST be the callsign or alias of the +
-node itself. +
-Upon successful connection, the user is granted access to a "public" +
-files area, which he can use to upload and download files using fairly +
-</code> +
----- +
-=====NODES.HLP===== +
-<code> +
-The NODES command, usually abbreviated to "N", displays the contents  +
-of the NetRom nodes table, showing which NetRom (but not KA) nodes are +
-known to the system. +
-Syntax: N[odes] [ <nodecall> |  * | > | < | + | A[dd] | B (y) +
-        | C (all) | D[rop] | F (rames) | H (ops) | HE[lp] | I (paddr) +
-        | N (etrom) | O (bsolete) | P (osition) | Q (ueue) | R (tt) +
-        | S (tats) | T (imes) | V (ia)]  +
-N by itself lists all the nodes except "hidden" nodes whose alias  +
-begins with the hash (#) character. "N *" includes the hidden ones. +
-If the argument is a known node call / alias e.g. "N MLVN" (wildcards +
-are accepted), the preferred route to the specified node, and up to +
-two alternative routes are displayed.  A chevron ">" in the left-most +
-column indicates the currently active route.  The first number shows +
-the overall path quality to the target node, the second is the  +
-"obsolescence count", and the third number is the port number. +
-</code> +
----- +
-=====NPING.HLP===== +
-<code> +
-The NPING command sends an echo request to the specified target via +
-the Netrom network. If the target understands the protocol it returns +
-a reply, allowing the number of hops and the round trip time to be +
-estimated. It is mainly of use as a network diagnostic. +
-   Syntax: NP[ing] <callsign | alias> [bytes [secs]]  +
-   Examples: NP GB7GC          Ping once with 0 byte payload. +
-             NP GLOS 100       Ping once with 100 byte payload. +
-             NP GLOS 50 30     Ping every 30 secs with 50 byte payload. +
-If no reply is received, either the target doesn't understand the +
-protocol, or is currently unreachable, or the ping was "lost" in +
-</code> +
----- +
-=====NRR.HLP===== +
-<code> +
-The NRR command sends a "record route" packet to the specified netrom +
-target system.  If the target understands the protocol it will return +
-a reply, allowing the path taken to be shown.  Each NRR-capable node +
-along the path inserts its own call into the packet. +
-   Syntax:    NRR <callsign | alias> +
-   Examples:  NRR GB7GC +
-              NRR FOD +
-If no reply is received, either the target doesn't understand the +
-protocol or the request or reply were lost in transit.  If the reply +
-contains only "?" in place of each callsign, it means there were no +
-NRR-capable nodes en-route to/from the target. +
-NRR is correctly handled by XR32, XRouter, (X)Net +
-NRR is not understood by: FPAC, TNOS, JNOS +
-</code> +
----- +
-=====NTRACERT.HLP===== +
-<code> +
-The NTRACERT (Netrom TraceRoute) commmand traces the route to a +
-NetRom node. +
-    Syntax: NT[racert] <node> [maxhops [maxwait(ms)]] +
-    <node>    is the callsign or alias of the target node. +
-    [maxhops] is the maximum number of hops to trace (default 30). +
-    [maxwait] is the maximum time to wait for a reply from each +
-              node. The default is 4 seconds. +
-The only mandatory parameter is <node>.  +
-Examples:   +
-        NT VA2OM       - Trace to VA2OM with default parameters. +
-        NT G7VJA-5 10  - Trace to G7VJA-5 to a max of 10 hops. +
-        NT XBAL 5 20   - Trace to XBAL, 5 hops, max 20secs. +
-At present, only XRouter nodes show in the trace. The operation can be +
-</code> +
----- +
-=====PING.HLP===== +
-<code> +
-The PING command sends ICMP echo request(s) to the specified IP  +
-address or hostname for the purposes of route testing. +
-    Syntax:  PING <hostname | ipaddr> [length [interval]] +
-An optional data portion of "length" bytes may be specified, and the  +
-echo request may optionally be repeated every "interval" seconds.  The  +
-process aborts if you send an empty line. +
-If there is a reply it will be displayed.  For repeating pings the  +
-system displays the number sent/rcvd, the average round trip time in  +
-milliseconds, and the success rate. +
-Examples:  PING 44.131.91.2           Single ping of minimum size +
-           PING 44.131.91.2 50        Single ping with 50 bytes data +
-           PING gb7pzt                Uses DNS to resolve host. +
-</code> +
----- +
-=====PMS.HLP===== +
-<code> +
-The PMS command connects the you either to this node's PMS (Personal +
-Message System), or to the PMS on another XRouter. +
-    Syntax: PM[s] [nodecall | nodealias] +
-The PMS is a no-frills mailbox similar to the one in a Tiny2 TNC, +
-allowing you to exchange messages and bulletins with other users, and +
-with the sysop. +
-If "PMS" is used on its own, you will be connected to the PMS at this +
-node. +
-If the argument is the nodecall or alias of another XRouter which is +
-in the nodes table (e.g. "PMS KIDDER"), you will be connected to the +
-PMS of that node instead. +
-Help for PMS commands is available by typing H at the PMS prompt. +
-</code> +
----- +
-=====PORTS.HLP===== +
-<code> +
-The PORTS command, normally abbreviated to "P", lists the available  +
-</code> +
----- +
-=====QUIT.HLP===== +
-<code> +
-The "QUIT" command, which can be abbreviated to "Q" disconnects you  +
-from the node and terminates all dependent sessions. +
-This is useful when you do not have easy access to a TNC's "command  +
-mode", or when you have uplinked from another node with the "stay"  +
-</code> +
----- +
-=====ROUTES.HLP===== +
-<code> +
-The ROUTES command, which may be abbreviated to "R", lists the  +
-immediately adjacent NetRom nodes, i.e. those who can be heard  +
-directly. +
-    Syntax: R[outes] [ A[dd] | D[rop]  | L[oad] |  R[etr] |  Q[ual] +
-                 | T [ime] | X[tra] ]  +
-            (Add, Drop and Load are sysop-only) +
-For each neighbour node the display shows the port number, the  +
-neighbour's callsign, the route quality, and the number of nodes  +
-accessible through that neighbour.  A chevron (>) in the left-most  +
-column indicates a route which is in use, and an exclamation mark (!)  +
-in the right-most column indicates that the data has been "locked in"  +
-by the sysop. +
-Additional information is displayed, depending on whch subcommand is +
-</code> +
----- +
-=====SEND.HLP===== +
-<code> +
-The SEND command sends an unproto (UI) packet on the specified port. +
-Up to 8 optional digis may be included. +
-   Syntax: SE[nd] <port> <call> [V digi,digi,..] <text> +
-   Examples: SEND 1 CQ V G8AKX,G8EPR Meet me on 144.800! +
-</code> +
----- +
-=====SERVICES.HLP===== +
-<code> +
-Modern XRouters support a list of "Standard Services", which can be +
-directly connected from another XRouter using "C <nodecall> <svcnum>". +
-These service numbers are the same on all nodes. Those marked with "*" +
-can easily be used by humans. The remainder may use machine-to-machine +
-protocols such as HTTP. +
-    Number  Service   Description +
-    ------------------------------------------------------------ +
-       0  * CMD       Normal connection to Node's command line +
-       1  * INFO      Standard Information server +
-       2  * PMS       Personal Message System +
-       3    BBS       (reserved for Bulletin Board System) +
-       4    DX        (reserved for DX cluster/dx-spot feed) +
-       5    TPP       (reserved for "Tampa Ping-Pong" chat) +
-       7  * ECHO      Echoes data back to sender +
-       8  * CHAT      XRChat server +
-       9  * DISCARD   Data sink +
-      10    RMS       (reserved for winlink RMS} +
-      11    BPQCHAT   (reserved for BPQ chat server) +
-      13  * DAYTIME   Local date/time (similar to RFC867) +
-      14  * APRS      APRS Server +
-      15    CUSTINF   (reserved for custom information file server) +
-      16  * WX        Local weather information +
-      17    TELEM     (reserved for Telemetry server) +
-      18    SMS       Short Message System server +
-      19  * CHARGEN   Generates a test pattern +
-      20    NDATA     (reserved for NFTP extension) +
-      21  * NFTP      Netrom File Transfer Protocol +
-      22    NSSH      (reserved for secure login - if legal?) +
-      23  * TELNET    Normal L4 login (same as 0) +
-      25    SMTP      Simple Mail Transfer Protocol server +
-      26  * MHEARD    MHEARD server (shows MH lists) +
-      27  * DXLIST    DX List server (shows DX lists) +
-      28  * WALL      Message wall / guestbook +
-      29  * BLOG      Sysop's Blog +
-      79  * FINGER    Finger server +
-      80    HTTP      NetromWeb (HTTP over Netrom) server +
-      87  * NTTY      Netrom TTY - Keyboard to keyboard chat +
-     110    POP3      POP3 server +
-</code> +
----- +
-=====STATS.HLP===== +
-<code> +
-The STATS command displays information about the performance of the  +
-router, such as the uptime, the no. of packets routed, error rates  +
-etc. +
-   Syntax: S[stats] [* | L1 | L2 | L3 | L4 | TCP | IP ] +
-   Examples: S       Display single page synopsis +
-             S *     Display all stats for all protocol layers +
-</code> +
----- +
-=====TELNET.HLP===== +
-<code> +
-The TELNET command allows users to "connect" to other TCP/IP systems,  +
-using a "shell" account, i.e. the user does not need to be running  +
-TCP/IP as XR32 handles the translation between TCP/IP and whatever +
-mode you are using. +
-    Syntax: TELNET <hostname | ipaddress> [port] +
-    <host> is the hostname or IP number of the target system. +
-The optional <port> parameter specifies the desired service on the  +
-target host.  If not supplied, the default is 23, i.e. the "Telnet" +
-port. Common port numbers are 21 (FTP), 23 (Telnet), 25 (SMTP), and +
-87 (TTYLINK). +
-Examples:  TELNET 44.131.90.6 21   Connect to FTP at 44.131.90.6 +
-           TELNET gb7lgs.ampr.org  Remote login to gb7lgs +
-</code> +
----- +
-=====TIME.HLP===== +
-<code> +
-The TIME command reports the local time at this (or another) node. +
-    Syntax: TI[me] [nodecall] +
-"TIME" by itself reports this system's local time. +
-"TIME nodecall" reports the local time and date at nodecall. At +
-</code> +
----- +
-=====TRACERT.HLP===== +
-<code> +
-The TRACERT commmand traces the route to a TCP/IP host. +
-    Syntax:  TR[acert] <host> [maxhops [maxwait(ms)]] +
-    <host>    is the hostname or IP address of the target host. +
-    [maxhops] is the maximum number of hops to trace (default 30). +
-    [maxwait] is the maximum time to wait for a reply from each +
-              router. The default is 4 seconds. +
-The only required parameter is <host>.  +
-Examples:   +
-        TR bbc.co.uk       - Trace bbc.co.uk with default parameters. +
-        TR 44.141.91.2 10  - Trace 44.131.91.2 to a max of 10 hops. +
-</code> +
----- +
-=====TTYLINK.HLP===== +
-<code> +
-The TTYLINK commmand allows you to chat directly to TCP/IP users. +
-    Syntax:  TT[YLINK] <hostname | ipaddress> [port] +
-This is similar to TELNET, except that the default port number is 87,  +
-which is reserved for keyboard to keyboard chat.  Other port numbers  +
-may be specified. +
-Examples:  TTY 44.131.91.4       - Chat to user of this IP address +
-</code> +
----- +
-=====USERS.HLP===== +
-<code> +
-The USERS command, usually abbreviated to "U", displays the circuits  +
-which originate or terminate at this node.  "Through" connections are  +
-not shown. +
-Established circuits are shown by <-->  and circuits being set up are  +
-shown thus:  <~~>. +
-UPLINK is a connection from a user (who may be located at another  +
-node) to this node, and DOWNLINK is a connection from this node to a  +
-user.  Uplink/downlink types may be L2 (ax25 level 2), L4 (ax25 level  +
-</code> +
----- +
-=====VERSION.HLP===== +
-<code> +
-The VERSION command, which may be abbreviated to "V", displays the  +
-</code> +
----- +
-=====WALLCMDS.HLP===== +
-<code> +
-Wall commands are as follows: +
-    [H]elp  [L]ist  [O]lder  [N]ewer  [W]rite  [D]elete  [Q]uit +
-H[elp]   Displays this message. +
-L[ist]   Displays or re-displays up to 10 messages at a time. Messages +
-         are displayed in reverse chronological order, i.e. the most +
-         recent at the top. +
-O[lder]  Displays up to 10 older messages, i.e. back in time. +
-N[ewer]  Displays up to 10 newer messages, i.e. forward in time. +
-W[rite]  Begins message entry. Messages can be up to 255 characters, +
-         and are posted upon receipt of a <CR> (carriage return). +
-D[elete] Deletes a message that you have just entered. +
-Q[uit]   Returns you to the node. +
-</code> +
----- +
-=====WALL.HLP===== +
-<code> +
-The WALL command connects you to the message "wall" either at this +
-node or at another XRouter of your choice. +
-    Syntax: W[all] [nodecall | nodealias] +
-The "wall" is a public message board / guestbook / notepad, where +
-anyone can write anything they like. Why not have a go? +
-Typing "WALL" by itself connects you to the local wall. Typing WALL +
-followed by the nodecall or alias of another XRouter that is in the +
-nodes table, For example "WALL KIDDER", connects you to the wall on +
-that node.  +
-</code> +
----- +
-=====WATCH.HLP===== +
-<code> +
-The WATCH command, which can be abbreviated to "WAT", allows you to +
-monitor packet traffic on one or more of the node's RF ports. +
-    Syntax: WAT[ch] port[+port..] | [OFF] +
-Non-sysops may only watch RADIO ports, and you can not watch the port +
-upon which you are connected to the node. Use "WATCH OFF" to +
-terminate traffic monitoring. +
-    Examples: WATCH 3 +
-              WAT 3+5 +
-              WATCH OFF +
-You may issue the command more than once, to watch additional ports. +
-All the normal node commands are available whilst in "watch" mode. If +
-the amount of monitored traffic exceeds the capacity of your uplink +
-with the node, some traffic may be discarded. +
-</code> +
----- +
-=====WX.HLP===== +
-<code> +
-The WX command is used to display a list of up to 5 local APRS weather +
-stations, and to display a weather summary from specified stations. +
-The information displayed includes: date and time of reading, distance +
-and direction of server, pressure, wind speed and direction, gust +
-speed, temperature, humidity, and rainfall. +
-    Syntax: WX [callsign] +
-If no argument is supplied, the callsigns of the available weather +
-stations (if any) are displayed. +
-If the argument is the callsign of one of the stations in the list, +
-the weather summary from that station will be displayed. +
-Examples: WX           - Display local APRS weather stations +
-</code> +
----- +
-=====YELL.HLP===== +
-<code> +
-The YELL commmand allows you to page the sysop for a chat. +
-    Syntax:  Y[ell] +
-The YELL command pages the sysop by sounding a distinctive bleep and +
-displaying a message.  If the sysop is available, she may then break +
-in on your session for a chat. +
-You should bear in mind that the sysop may be out of earshot or busy, +
-the sound may be disabled during unsociable hours, or the node may be +
-</code> +
-----+
packet/xrpi/manpages/hlpgeneral.1745069414.txt.gz · Last modified: 2025/04/19 13:30 by m0mzf