DXSpider Documentation Wiki - User contributions [en-gb]

Useful Daily Commands For Sysops

2025-11-20T09:29:39Z

G0TRT: added update_sysop.pl for changing the cluster callsign

There are many commands! Some are more useful than others, some are used more frequently that others, some are used at the command prompt, some are used in the console. Here are some of those useful commands that sysops might use on most days, and some of those search strings that help you pluck information from the data files or live streams.

===Linux prompt===

* ./watchdbg 'PC92\^VE7CCD-1' - looking for troubling data out of this node. Note: the ^ needs to be escaped with \
* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.
* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.
* ./grepdbg 'progress' "(CMD: \'dx )" - see all the spots originating from your node (the space after the dx is very important). grepdbg can also be used instead of watchdbg, or vice versa. For more information on watchdbg and grepdbg see the "[[DXSpider_Tracing_Debug_Entries|Tracing Debug Entries]]" page.
* sudo service dxspider restart
* update_sysop.pl - if a cluster callsign needs to change then edit the variables such as sysop callsign within DXVars.pm then run /spider/perl/update_sysop.pl
===Console commands===

* sh/external_ip - just checking to see if your ip address changed since your last visit.
* sh/ver - did your node update last night? This will show you what version of dxspider you're running.
* sh/node - are all of your node links up?
* sh/user - all the users.
* directory - any new mail on your node?
* links - just who is connected, and what about them?
* set/register G0AYD - G0AYD sent you a message that he wants to be able to use your node for sending spots.
* stat/user <callsign> - everything you want to know about <callsign>
* sh/hf - a table of spot quantities, per day, per band, for the last month.
* set/var @main::localhost_names ('127.0.0.1', '::1', '192.168.1.127','192.168.1.154','192.168.1.110') - sets all of the IP addresses in your LAN
* sh/var @main::localhost_names - all of your IP addresses.
* mnodes - orderly listing of connected nodes (not included in DXSpider unless Kin's script is installed).
* musers - about all those connected users (not included in DXSpider unless Kin's script is installed).
* who - a list of the connected nodes and users, with some useful info about them.
* rcmd g6nhu-2 sh/ver - did G6NHU update his node?
* sh/debug - did I leave debug running? Is that why my disk is full!

Template:Main Page pdf

2025-04-24T20:51:43Z

G0TRT: /* Sysops */

<div style="background:#f9f9f9;padding:0px;border:1px solid #aaaaaa;margin-bottom:15px">
<div style="font-size:125%;color:#336699;padding:0.4em;background-color:#eeeeee;border-bottom:1px solid #aaaaaa;vertical-align:top">

*'''Manuals'''

</div>
<div style="background-color:#fff;padding:0.4em 0.4em 0.4em 0.4em;font-size:95%">
==General==
* [https://wiki.dxcluster.org/wiki/Authors_and_Contributors Authors and Contributors]
* [https://wiki.dxcluster.org/wiki/DXSpider_FAQ FAQ]
==Users==
* [https://wiki.dxcluster.org/wiki/DXSpider_User_Manual User Manual]
* [https://wiki.dxcluster.org/wiki/DXSpider_Filtering_Manual Filtering Manual]
* [https://wiki.dxcluster.org/wiki/DXSpider_User_Command_Reference User Command Reference]
==Sysops==
* [https://wiki.dxcluster.org/wiki/DXSpider_Installation_Manual_(New) Installation Manual (New)]
* [https://wiki.dxcluster.org/wiki/DXSpider_Configuration_Manual Configuration Manual (New)]
* [https://wiki.dxcluster.org/wiki/Node_configuration_for_user_access Node Configuration for User Access (New)]
* [https://wiki.dxcluster.org/wiki/DXSpider_Installation_Manual Installation Manual (Legacy)]
* [https://wiki.dxcluster.org/wiki/DXSpider_Administration_Manual Administration Manual (Legacy)]
* [https://wiki.dxcluster.org/wiki/DXSpider_Sysop_Command_Reference Sysop Command Reference]
* [https://wiki.dxcluster.org/wiki/DXSpider_Variables_Reference Variables Reference]
* [https://wiki.dxcluster.org/wiki/DXSpider_Debug_Commands_and_Levels Debug Commands and Levels]
* [https://wiki.dxcluster.org/wiki/DXSpider_Tracing_Debug_Entries Tracing Debug Entries]
* [https://wiki.dxcluster.org/wiki/Analysing_the_RBN Analysing the RBN]
* [https://wiki.dxcluster.org/wiki/DXSpider_PC_Packet_Cluster_Protocol The PC Packet Cluster protocol]
* [https://wiki.dxcluster.org/wiki/Backup DX Spider Backup]
* [https://wiki.dxcluster.org/wiki/DXSpider_Kin's_Helper_Script_Info Kin's Helper Script Info]
* [https://wiki.dxcluster.org/wiki/Useful_Daily_Commands_For_Sysops Useful Daily Commands For Sysops]
* [https://wiki.dxcluster.org/wiki/UPDATE.mojo Update from v1.55 to v1.57 Mojo]
* [https://wiki.dxcluster.org/wiki/Restoring_the_user_DB_(Mojo_branch) Backup/Restore/Transfer the User Database]

The [http://www.dxcluster.org/download/ latest release] of the DXSpider program can be downloaded from http://www.dxcluster.org

</div>
</div>

Backup

2025-04-24T20:48:56Z

G0TRT: Created page with "As DX Spider runs on Linux it is very simple to keep a constant back up of DX spider either onboard, off-board, or even somewhere remote. To install a backup of your node your new system will need to install dxspider and its dependencies, and then copy your existing ~/spider/* and sub-directories over the top of your new installation. This should bring your whole configuration, connections, scripts, crontab etc. The [https://www.geeksforgeeks.org/rsync-command-in-linux..."

As DX Spider runs on Linux it is very simple to keep a constant back up of DX spider either onboard, off-board, or even somewhere remote.

To install a backup of your node your new system will need to install dxspider and its dependencies, and then copy your existing ~/spider/* and sub-directories over the top of your new installation. This should bring your whole configuration, connections, scripts, crontab etc.

The [https://www.geeksforgeeks.org/rsync-command-in-linux-with-examples/ rsync] package will be used to copy ~/spider/* to your backup location.

rsync -ar /home/sysop/ /home/sysop/usb1/

Running this command once will copy all files in /home/sysop/ into the location /home/sysop/usb1/ In this case usb1 is a usb thumb drive that's plugged into the computer running DX Spider

In order to have the rsync command run frequently, to capture changes, it's added to the computer's crontab as explained at the [https://linuxhandbook.com/crontab/ Linux Handbook]

Using this method, even after reboot, rsync will run as often as crontab makes it, and when there is a system failure, or you want to add a test node to your setup, use the contest of your thumb drive to quickly copy across your original configuration

DXSpider Sysop Command Reference

2025-04-18T10:04:07Z

G0TRT: /* show/contest */

==ACCEPT==
* '''accept''' set a filter to accept something
* Create a filter to accept something. There are 2 types of filter, accept and reject. See ''Help Filtering'' for more info.

===accept/announce <call> [input] [0-9] <pattern>===
* '''accept/announce''' <call> [input] [0-9] <pattern> - Announce filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
accept/ann by G,M,2
accept/ann input node_default by G,M,2
accept/ann user_default by G,M,2

===accept/announce [0-9] <pattern>===
*accept/announce [0-9] <pattern> - Set an 'accept' filter line for announce
Create an 'accept this announce' line for a filter. An accept filter line means that if the announce matches this filter it is passed onto the user. See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
info <string> - eg: iota or qsl
by <prefixes> - eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> - eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,NH
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states>
channel <prefixes> wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX
some examples:
acc/ann dest 6MUK
acc/ann 2 by_zone 14,15,16
(this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
or
acc/ann by G,M,2
for american states
acc/ann by_state va,nh,ri,nh
You can use the tag 'all' to accept everything eg:
acc/ann all
but this probably for advanced users...

===accept/route <call> [0-9] <pattern>===
*accept/route <call> [0-9] <pattern> - Set an 'accept' filter line for routing
Create an 'accept this routing PC Protocol' line for a filter. An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter it is passed thru that interface. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:
call <prefixes>
the callsign of the thingy
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,NH
origin <prefixes>
really the interface it came in on
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,NH
some examples:
acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
you can now use 'by' as a synonym for 'call' so:
by = call by_dxcc = call_dxcc
you can use the tag 'all' to accept everything eg:
acc/route all

===accept/spots <call> [input] [0-9] <pattern>===
*accept/spots <call> [input] [0-9] <pattern> - Spot filter sysop version
This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:
accept/spot db0sue-7 1 by_zone 14,15,16
accept/spot node_default all
set/hops node_default 10
accept/spot user_default by G,M,2

===accept/spots [0-9] <pattern>===
*accept/spots [0-9] <pattern> - Set an 'accept' filter line for spots
Create an 'accept this spot' line for a filter. An accept filter line means that if the spot matches this filter it ispassed onto the user. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on <range> same as 'freq'
call <prefixes> eg: G,PA,HB9
info <string> eg: iota or qsl
by <prefixes>
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states> eg: VA,NH,RI,ME
origin <prefixes>
channel <prefixes>
'call' means the callsign that has spotted 'by' whoever. For frequencies, you can use any of the band names defined in SHOW/BANDS and you can use a sub-band name like: cw, rtty, data, ssb -thus: hf/ssb. You can also just have a simple range like: 0/30000 -this is more efficient than saying simply: freq HF (but don't get too hung up about that)some examples:
acc/spot 1 on hf/cw
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
You can use the tag 'all' to accept everything, eg:
acc/spot 3 all
for US states
acc/spots by_state VA,NH,RI,MA,ME
but this probably for advanced users...

===accept/wcy <call> [input] [0-9] <pattern>===
*accept/wcy <call> [input] [0-9] <pattern> - WCY filter sysop version
This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:
accept/wcy node_default all set/hops node_default 10

===accept/wcy [0-9] <pattern>===
*accept/wcy [0-9] <pattern> - set an 'accept' WCY filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them).This command is really provided for future use. See HELP FILTER for information.

===accept/wwv <call> [input] [0-9] <pattern>===
*accept/wwv <call> [input] [0-9] <pattern> - WWV filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
accept/wwv db0sue-7 1 by_zone 4
accept/wwv node_default all set/hops node_default 10
accept/wwv user_default by W,K

===accept/wwv [0-9] <pattern>===
*accept/wwv [0-9] <pattern> - set an 'accept' WWV filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
for example:
accept/wwv by_zone 4
is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). See HELP FILTER for information.

==ANNOUNCE==
===announce <text>===
*announce <text> - Send an announcement to LOCAL users only
<text> is the text of the announcement you wish to broadcast

===announce full <text>===
*announce full <text> - Send an announcement cluster wide
This will send your announcement cluster wide

===announce sysop <text>===
*announce sysop <text> - Send an announcement to Sysops only

==APROPOS==
===apropos <string>===
*apropos <string> - Search help database for <string>
Search the help database for <string> (it isn't case sensitive), and print the names of all the commands that may be relevant.

==BLANK==
===blank [<string>] [<nn>]===
*blank [<string>] [<nn>] - Print nn (default 1) blank lines (or strings)
In its basic form this command prints one or more blank lines. However if you pass it a string it will replicate the string for the width of the screen (default 80) and then print that one or more times, so:
blank 2
prints two blank lines
blank -
prints a row of - characters once.
blank abc
prints 'abcabcabcabcabcabc....'This is really only of any use in a script file and you can print a maximum of 9 lines.

==BYE==
===bye===
*bye - Exit from the cluster
This will disconnect you from the cluster

==CATCHUP==
===catchup <node call> all|[<msgno> ...]===
*catchup <node call> all|[<msgno> ...] - Mark a message as sent

==CHAT==
===chat <group> <text>===
*chat <group> <text> - Chat or Conference to a group
It is now possible to JOIN a group and have network wide conferencing to that group. DXSpider does not (and probably will not) implement the AK1A conference mode as this seems very limiting, is hardly used and doesn't seem to work too well anyway. This system uses the existing ANN system and is compatible with both other DXSpider nodes and AK1A clusters (they use ANN/<group>). You can be a member of as many "groups" as you want. To join a group type:
JOIN FOC (where FOC is the group name)
To leave a group type:
LEAVE FOC
You can see which groups you are in by typing:
STAT/USER
and you can see whether your mate is in the group, if he connects to the same node as you, by typing:
STAT/USER g1tlh
To send a message to a group type:
CHAT FOC hello everyone
or
CH #9000 hello I am back
See also JOIN, LEAVE, SHOW/CHAT

==CLEAR==
===clear/announce <callsign> [input] [0-9|all]===
*clear/announce <callsign> [input] [0-9|all] - Clear a announce filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/announce [1|all]===
*clear/announce [1|all] - Clear a announce filter line
This command allows you to clear (remove) a line in a announce filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

===clear/route <callsign> [input] [0-9|all]===
*clear/route <callsign> [input] [0-9|all] - Clear a route filter line
A sysop can clear an input or normal output filter for a user or then ode_default or user_default.

===clear/route [1|all]===
*clear/route [1|all] - Clear a route filter line
This command allows you to clear (remove) a line in a route filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

===clear/spots <callsign> [input] [0-9|all]===
*clear/spots <callsign> [input] [0-9|all] - Clear a spot filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/spots [0-9|all]===
*clear/spots [0-9|all] - Clear a spot filter line
This command allows you to clear (remove) a line in a spot filter or to remove the whole filter. If you have a filter:
acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
and you say:
clear/spot 1
you will be left with:
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
If you do:
clear/spot all
the filter will be completely removed.

===clear/wcy <callsign> [input] [0-9|all]===
*clear/wcy <callsign> [input] [0-9|all] - Clear a WCY filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/wcy [1|all]===
*clear/wcy [1|all] - Clear a WCY filter line
This command allows you to clear (remove) a line in a WCY filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

===clear/wwv <callsign> [input] [0-9|all]===
*clear/wwv <callsign> [input] [0-9|all] - Clear a WWV filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/wwv [1|all]===
clear/wwv [1|all] - Clear a WWV filter line
This command allows you to clear (remove) a line in a WWV filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

==CONNECT==
===connect <callsign>===
*connect <callsign> - Start a connection to another DX Cluster
Start a connection process that will culminate in a new connection to the DX cluster <callsign>. This process creates a new 'client' process which will use the script in /spider/connect/<callsign> to effect the 'chat' exchange necessary to traverse the network(s) to logon to the cluster <callsign>.

==DBAVAIL==
===dbavail===
*dbavail - Show a list of all the Databases in the system
Title says it all really, this command lists all the databases defined in the system. It is also aliased to SHOW/COMMAND.

==DBCREATE==
===dbcreate <name>===
*dbcreate <name> - Create a database entry

===dbcreate <name> chain <name> [<name>..]===
*dbcreate <name> chain <name> [<name>..] - Create a chained database entry

===dbcreate <name> cmd <dxspider command>===
*dbcreate <name> cmd <dxspider command> - make a local command available as a DB
DBCREATE allows you to define a database in the system. It doesn't actually create anything, just defines it. The databases that are created are simple DB_File hash databases, they are therefore already 'indexed'. You can define a local database with the first form of the command eg:
DBCREATE oblast
You can also chain databases with the addition of the 'chain' keyword. This will search each database one after the other. A typical example is:
DBCREATE sdx_qsl chain sql_ad
No checking is done to see if the any of the chained databases exist, in fact it is usually better to do the above statement first then do each of the chained databases. Databases can exist offsite. To define a database that lives on another node do:
DBCREATE buckmaster remote gb7dxc
Remote databases cannot be chained; however, the last database in a a chain can be a remote database eg:
DBCREATE qsl chain gb7dxc
To see what databases have been defined do:
DBAVAIL (or it will have been aliased to SHOW/COMMAND)
It would be normal for you to add an entry into your local Aliases file to allow people to use the 'SHOW/<dbname>' style syntax. So you would need to add a line like:
's' => [ .. .. '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', .. .. ],
to allow
SH/BUCK g1tlh
to work as they may be used to.You can also make local commands available as 'pseudo' databases. Youcan therefore make spider special commands available as a database. Iimagine that this will be primarily useful for remote access from legacy nodes. For example:-
DBCREATE dxqsl cmd show/dxqsl
You also use one of these databases in a chain. This may be useful locally. See DBIMPORT for the importing of existing AK1A format data to databases. See DBSHOW for generic database enquiry

===dbcreate <name> remote <node>===
*dbcreate <name> remote <node> - Create a remote database entry

==DBIMPORT==
===dbimport <dbname> <filename>===
*dbimport <dbname> <filename> - Import AK1A data into a database
If you want to import or update data in bulk to a database you can use this command. It will either create or update entries into an existing database. For example:
DBIMPORT oblast /tmp/OBLAST.FUL
will import the standard OBLAST database that comes with AK1A into the oblast database held locally.

==DBREMOVE==
===dbremove <dbname>===
*dbremove <dbname> - Delete a database
DBREMOVE will completely remove a database entry and also delete any datafile that is associated with it. There is no warning, no comeback, no safety net. For example:
DBREMOVE oblast
will remove the oblast database from the system and it will also remove the associated data file. I repeat: There is no warning, no comeback, no safety net. You have been warned.

==DBSHOW==
===dbshow <dbname> <key>===
*dbshow <dbname> <key> - Display an entry, if it exists, in a database
This is the generic user interface to the database to the database system. It is expected that the sysop will add an entry to the local Aliases file so that users can use the more familiar AK1A style of enquiry such as:
SH/BUCK G1TLH
but if he hasn't and the database really does exist (use DBAVAIL or SHOW/COMMAND to find out) you can do the same thing with:
DBSHOW buck G1TLH

==DEBUG==
===debug===
*debug - Set the cluster program into debug mode
Executing this command will only have an effect if you are running the cluster in debug mode i.e.
perl -d cluster.pl
It will interrupt the cluster just after the debug command has finished.

The full debug command set is on the [[DXSpider Debug Commands and Levels|debug commands and levels]] page

==DELETE==
===delete/usdb <callsign> ...===
*delete/usdb <callsign> ... - Delete this user from the US State Database
This command will completely remove a one or more callsigns from the US States database. There is NO SECOND CHANCE. It goes without saying that you should use this command CAREFULLY! Note that these callsigns may be re-instated by any weekly updates from the FCC.

===delete/user <callsign> ...===
*delete/user <callsign> ... - Delete this user from the User Database
This command will completely remove a one or more users from the database. There is NO SECOND CHANCE. It goes without saying that you should use this command CAREFULLY!

==DEMONSTRATE==
===demonstrate <call> <command>===
*demonstrate <call> <command> - Demonstrate a command to another user
This command is provided so that sysops can demonstrate commands to other users. It runs a command as though that user had typed it in and then sends the output to that user, together with the command that caused it.
DEMO g7brn sh/dx iota oc209
DEMO g1tlh set/here
Note that this command is similar to SPOOF and will have the same side effects. Commands are run at the privilege of the user which is being demonstrated to.

==DIRECTORY==
===directory===
*directory - List messages

===directory <from>-<to>===
*directory <from>-<to> - List messages <from> message <to> message
List the messages in the messages directory. If there is a 'p' one space after the message number then it is a personal message. If there is a '-' between the message number and the 'p' then this indicates that the message has been read. You can use shell escape characters such as '*' and '?' in the <call>fields. You can combine some of the various directory commands together eg:
DIR TO G1TLH 5
or
DIR SUBJECT IOTA 200-250
You can abbreviate all the commands to one letter and use ak1a syntax:
DIR/T G1* 10
DIR/S QSL 10-100 5

===directory <nn>===
*directory <nn> - List last <nn> messages

===directory all===
*directory all - List all messages

===directory from <call>===
*directory from <call> - List all messages from <call>

===directory new===
*directory new - List all new messages

===directory own===
*directory own - List your own messages

===directory subject <string>===
*directory subject <string> - List all messages with <string> in subject

===directory to <call>===
*directory to <call> - List all messages to <call>

===directory- ===
directory-
Sysops can see all users' messages.

==DISCONNECT==
===disconnect <call> [<call> ...]===
*disconnect <call> [<call> ...] - Disconnect a user or cluster
Disconnect any <call> connected locally

==DX==
===dx [by <call>] <freq> <call> <remarks>===
dx [by <call>] <freq> <call> <remarks> - Send a DX spot
This is how you send a DX Spot to other users. You can, in fact, now enter the <freq> and the <call> either way round.
DX FR0G 144.600
DX 144.600 FR0G
DX 144600 FR0G
will all give the same result. You can add some remarks to the end of the command and they will be added to the spot.
DX FR0G 144600 this is a test
You can credit someone else by saying:
DX by G1TLH FR0G 144.600 he isn't on the cluster
The <freq> is compared against the available bands set up in the cluster. See SHOW/BANDS for more information.

==ECHO==
===echo <line>===
echo <line> - Echo the line to the output
This command is useful in scripts and so forth for printing the line that you give to the command to the output. You can use this in user_default scripts and the SAVE command for titling and so forth. The script will interpret certain standard "escape" sequences as follows:
\t - becomes a TAB character (0x09 in ascii)
\a - becomes a BEEP character (0x07 in ascii)
\n - prints a new line
So the following example:
echo GB7DJK is a dxcluster
produces:
GB7DJK is a dxcluster
on the output. You don't need a \n on the end of the line you want to send.

==EXPORT==
===export <msgno> <filename>===
*export <msgno> <filename> - Export a message to a file
Export a message to a file. This command can only be executed on a local console with a fully privileged user. The file produced will be in a form ready to be imported back into the cluster by placing it in the import directory (/spider/msg/import).This command cannot overwrite an existing file. This is to provide some measure of security. Any files written will owned by the same user as the main cluster, otherwise you can put the new files anywhere the cluster can access. For example:
EXPORT 2345 /tmp/a

===export_users [<filename>]===
*export_users [<filename>] - Export the users database to ascii
Export the users database to a file in ascii format. If no file name is given then it will export the file to /spider/data/user_asc. If the file already exists it will be renamed to <filename>.o. In fact up to 5 generations of the file can be kept each one with an extra 'o' on the suffix. BE WARNED: this will write to any file you have write access to. No check is made on the filename (if any) that you specify.

==FILTERING==
===filtering...===
*filtering... - Filtering things in DXSpider
There are a number of things you can filter in the DXSpider system. They all use the same general mechanism. In general terms you can create a 'reject' or an 'accept' filter which can have up to 10 lines in it. You do this using, for example:
accept/spots .....
reject/spots .....
where ..... are the specific commands for that type of filter. There are filters for spots, wwv, announce, wcy and (for sysops) connects. See each different accept or reject command reference for more details. There is also a command to clear out one or more lines in a filter and one to show you what you have set. They are:
clear/spots 1
clear/spots all
and
show/filter
There is clear/xxxx command for each type of filter. For now we are going to use spots for the examples, but you can apply the principles to all types of filter. There are two main types of filter 'accept' or 'reject'; which you use depends entirely on how you look at the world and what is least writing to achieve what you want. Each filter has 10 lines (of any length) which are tried in order. If a line matches then the action you have specified is taken (ie reject means ignore it and accept means gimme it). The important thing to remember is that if you specify a 'reject' filter (all the lines in it say 'reject/spots' (for instance)) then if a spot comes in that doesn't match any of the lines then you will get it BUT if you specify an 'accept' filter then any spots that don't match are dumped. For example if I have a one line accept filter:
accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
then automatically you will ONLY get VHF spots from or to CQ zones 1415 and 16. If you set a reject filter like:
reject/spots on hf/cw
Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA and will work it even on CW then you could say:
reject/spots on hf/cw and not info iota
But in that case you might only be interested in iota and say:
accept/spots not on hf/cw or info iota
which is exactly the same. You should choose one or the other until you are comfortable with the way it works. Yes, you can mix them (actually you can have an accept AND a reject on the same line) but don't try this at home until you can analyze the results that you get without ringing up the sysop for help. Another useful addition now is filtering by US state
accept/spots by_state VA,NH,RI,ME
You can arrange your filter lines into logical units, either for your own understanding or simply convenience. I have one set frequently:
reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
What this does is to ignore all HF CW spots (being a class B I can't read any CW and couldn't possibly be interested in HF :-) and also rejects any spots on VHF which don't either originate or spot someone in Europe. This is an example where you would use the line number (1 and 2 in this case), if you leave the digit out, the system assumes '1'. Digits'0'-'9' are available. You can leave the word 'and' out if you want, it is implied. You can use any number of brackets to make the 'expression' as you want it. There are things called precedence rules working here which mean that you will NEED brackets in a situation like line 2 because, without it, will assume:
(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
annoying, but that is the way it is. If you use OR - use brackets. Whilst we are here CASE is not important. 'And BY_Zone' is just 'and by_zone'. If you want to alter your filter you can just redefine one or more lines of it or clear out one line. For example:
reject/spots 1 on hf/ssb
or
clear/spots 1
To remove the filter in its entirty:
clear/spots all
There are similar CLEAR commands for the other filters:
clear/announce
clear/wcy
clear/wwv
ADVANCED USERS: Once you are happy with the results you get, you may like to experiment. my example that filters hf/cw spots and accepts vhf/uhf spots from EU can be written with a mixed filter, eg:
rej/spot on hf/cw acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
each filter slot actually has a 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE the accept slot. It was mentioned earlier that after a reject test that doesn't match, the default for following tests is 'accept', the reverse is true for 'accept'. In the example what happens is that the reject is executed first, any non hf/cw spot is passed to the accept line, which lets thru everything else on HF. The next filter line lets through just VHF/UHF spots from EU.

==FORWARD==
===forward/latlong <node_call>===
*forward/latlong <node_call> - Send latitude and longitude information to another cluster
This command sends all the latitude and longitude information that your cluster is holding against callsigns. One advantage of receiving this information is that more locator information is held by you. This means that more locators are given on the DX line assuming you have SET/DXGRID enabled. This could be a LOT of information though, so it is not recommended on slow links.

===forward/opernam <call>===
*forward/opernam <call> - Send out information on this <call> to all clusters
This command sends out any information held in the user file which can be broadcast in PC41 protocol packets. This information is Name, QTH, Locationand Homenode. PC41s are only sent for the information that is available.

==FTx==
===enable/autoftx===
*enable/autoftx - Enable detected automatically generated FTx spots to be output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

===enable/ftx===
*enable/ftx - Enable FTx spots to be output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

===disable/autoftx===
*disable/autoftx - Disable detected automatically generated FTx spots from being output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

===disable/ftx===
*disable/ftx - Disable FTx spots from being output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

==HELP==
===help===
help - The HELP Command
HELP is available for a number of commands. The syntax is:
HELP <cmd>
Where <cmd> is the name of the command you want help on. All commands can be abbreviated, so SHOW/DX can be abbreviated to SH/DX, ANNOUNCE can be shortened to AN and so on. Look at the APROPOS <string> command which will search the help database for the <string> you specify and give you a list of likely commands to look at with HELP.

==INIT==
===init <node>===
*init <node> - Re-initialize a link to an AK1A compatible node
This command attempts to re-initialize a link to a (usually) AK1A node that has got confused, usually by a protocol loop of some kind. It may work - but you usually will be better off simply disconnecting it (or better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your node>). Best of luck - you will need it.

==JOIN==
===join <group>===
*join <group> - Join a chat or conference group
JOIN allows you to join a network wide conference group. To join a group (called FOC in this case) type:
JOIN FOC
See also CHAT, LEAVE, SHOW/CHAT

==KILL==
===kill===
*kill
As a sysop you can kill any message on the system.

===kill <from msgno>-<to msgno>===
*kill <from msgno>-<to msgno> - Delete a range of messages

===kill <from>-<to>===
*kill <from>-<to> - Remove a range of messages from the system

===kill <msgno> [<msgno..]===
*kill <msgno> [<msgno..] - Delete a message from the local system

===kill <msgno> [<msgno> ...]===
*kill <msgno> [<msgno> ...] - Remove or erase a message from the system
You can get rid of any message to or originating from your callsign using this command. You can remove more than one message at a time.

===kill expunge <msgno> [<msgno..]===
*kill expunge <msgno> [<msgno..] - Expunge a message
Deleting a message using the normal KILL commands only marks that message for deletion. The actual deletion only happens later (usually two days later). The KILL EXPUNGE command causes the message to be truly deleted more or less immediately. It otherwise is used in the same way as the KILL command.

===kill from <call>===
*kill from <call> - Remove all messages from a callsign

===kill full <msgno> [<msgno..]===
*kill full <msgno> [<msgno..] - Delete a message from the whole cluster
Delete a message from the local system. You will only be able to delete messages that you have originated or been sent (unless you are the sysop).
KILL 1234-1255
Will delete all the messages that you own between msgnos 1234 and 1255.
KILL from g1tlh
will delete all the messages from g1tlh (if you are g1tlh). Similarly:
KILL to g1tlh
will delete all messages to g1tlh.
KILL FULL 1234
will delete a message (usually a 'bulletin') from the whole cluster system. This uses the subject field, so any messages that have exactly thesame subject will be deleted. Beware!

===kill full <msgno> [<msgno]===
*kill full <msgno> [<msgno] - Remove a message from the entire cluster
Remove this message from the entire cluster system as well as your node.

===kill to <call>===
*kill to <call> - Remove all messages to a callsign

===kill from <regex>===
*kill from <regex> - Delete messages FROM a callsign or pattern

===kill to <regex>===
*kill to <regex> - Delete messages TO a callsign or pattern

==LEAVE==
===leave <group>===
*leave <group> - Leave a chat or conference group
LEAVE allows you to leave a network wide conference group. To leave agroup (called FOC in this case) type:
LEAVE FOC
See also CHAT, JOIN, SHOW/CHAT

==LINKS==
===links===
*links - Show which nodes is physically connected
This is a quick listing that shows which links are connected and some information about them. See WHO for a list of all connections.

==LOAD==
===load/aliases===
*load/aliases - Reload the command alias table
Reload the /spider/cmd/Aliases file after you have edited it. You will need to do this if you change this file whilst the cluster is running in order for the changes to take effect.

===load/badmsg===
*load/badmsg - Reload the bad msg table
Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst the cluster is running. This table contains a number of perl regular expressions which are searched for in the fields targeted of each message. If any of them match then that message is immediately deleted on receipt.

===load/badwords===
*load/badwords - Reload the bad words table
Reload the /spider/data/badwords file if you have changed it manually whilst the cluster is running. This file contains a list of words which, if found on certain text portions of PC protocol, will cause those protocol frames to be rejected. It will all put out a message if any of these words are used on the announce, dx and talk commands. The words can be one or more on a line, lines starting with '#' are ignored.

===load/bands===
*load/bands - Reload the band limits table
Reload the /spider/data/bands.pl file if you have changed it manually whilst the cluster is running.

===load/cmd_cache===
*load/cmd_cache - Reload the automatic command cache
Normally, if you change a command file in the cmd or local_cmd tree it will automatically be picked up by the cluster program. Sometimes it can get confused if you are doing a lot of moving commands about or delete a command in the local_cmd tree and want to use the normal one again. Execute this command to reset everything back to the state it was just after a cluster restart.

===load/forward===
*load/forward - Reload the msg forwarding routing table
Reload the /spider/msg/forward.pl file if you have changed it manually whilst the cluster is running.

===load/keps===
*load/keps - Load new keps data

===load/keps [nn]===
*load/keps [nn] - Load new keps data from message
If there is no message number then reload the current Keps data from the Keps.pm data file. You create this file by running
/spider/perl/convkeps.pl <filename>
on a file containing NASA 2 line keps as a message issued by AMSAT. If there is a message number, then it will take the message, run convkeps.pl on it and then load the data, all in one step. These messages are sent to ALL by GB7DJK (and others) from time to time.

===load/messages===
*load/messages - Reload the system messages file
If you change the /spider/perl/Messages file (usually whilst fiddling/writing new commands) you can have them take effect during a cluster session by executing this command. You need to do this if get something like :
unknown message 'xxxx' in lang 'en'

===load/prefixes===
*load/prefixes - Reload the prefix table
Reload the /spider/data/prefix_data.pl file if you have changed it manually whilst the cluster is running.

==MERGE==
===merge <node> [<no spots>/<no wwv>]===
*merge <node> [<no spots>/<no wwv>] - Ask for the latest spots and WWV
MERGE allows you to bring your spot and wwv database up to date. By default it will request the last 10 spots and 5 WWVs from the node you select. The node must be connected locally. You can request any number of spots or wwv and although they will be appended to your databases they will not duplicate any that have recently been added (the last 2 days for spots and last month for WWV data).

==MSG==
===msg <cmd> <msgno> [data ... ]===
*msg <cmd> <msgno> [data ... ] - Alter various message parameters
Alter message parameters like To, From, Subject, whether private or bulletin or return receipt (RR) is required or whether to keep this message from timing out.
MSG TO <msgno> <call> - change TO callsign to <call>
MSG FRom <msgno> <call> - change FROM callsign to <call>
MSG PRrivate <msgno> - set private flag
MSG NOPRrivate <msgno> - unset private flag
MSG RR <msgno> - set RR flag
MSG NORR <msgno> - unset RR flag
MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
MSG NOKEep <msgno> - unset the keep flag
MSG SUbject <msgno> <new> - change the subject to <new>
MSG WAittime <msgno> - remove any waitting time for this message
MSG NOREad <msgno> - mark message as unread
MSG REad <msgno> - mark message as read
MSG QUeue - queue any outstanding bulletins
MSG QUeue 1 - queue any outstanding private messages
You can look at the status of a message by using:
STAT/MSG <msgno>
This will display more information on the message than DIR does.

==PC==
===pc <call> <text>===
*pc <call> <text> - Send arbitrary text to a connected callsign
Send some arbitrary text to a locally connected callsign. No processing is done on the text. This command allows you to send PC Protocol to unstick things if problems arise (messages get stuck etc). eg:
pc gb7djk PC33^GB7TLH^GB7DJK^400^
or
pc G1TLH Try doing that properly!!!
Send any text you like to the callsign requested. This is used mainly to send PC protocol to connected nodes either for testing or to unstick things. You can also use in the same way as a talk command to a connected user but without any processing, added of "from <blah> to <blah" or whatever.

==PING==
===ping <node call>===
*ping <node call> - Check the link quality between nodes
This command allows you to send a frame to another cluster node on the network and get a return frame. The time it takes to do this is a good indication of the quality of the link. The actual time it takes is output to the console in seconds. Any visible cluster node can be PINGed.

==RCMD==
===rcmd <node call> <cmd>===
*rcmd <node call> <cmd> - Send a command to another DX Cluster
This command allows you to send nearly any command to another DX Cluster node that is connected to the system. Whether you get any output is dependent on a) whether the other system knows that the node callsign of this cluster is in fact a node b) whether the other system is allowing RCMDs from this node and c) whether you have permission to send this command at all.

==READ==
===read===
*read - Read the next unread personal message addressed to you

===read <msgno>===
*read <msgno> - Read the specified message
You can read any messages that are sent as 'non-personal' and also any message either sent by or sent to your callsign.

===read-===
*read-
As a sysop you may read any message on the system

==REJECT==
===reject===
*reject - Set a filter to reject something
Create a filter to reject something. There are 2 types of filter, accept and reject. See HELP FILTERING for more info.

===reject/announce <call> [input] [0-9] <pattern>===
*reject/announce <call> [input] [0-9] <pattern> - Announce filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/ann by G,M,2
reject/ann input node_default by G,M,2
reject/ann user_default by G,M,2

===reject/announce [0-9] <pattern>===
*reject/announce [0-9] <pattern> - Set a 'reject' filter line for announce
Create an 'reject this announce' line for a filter. A reject filter line means that if the announce matches this filter it is passed onto the user. See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
info <string> eg: iota or qsl
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states> eg: VA,NH,RI,ME
channel <prefixes>
wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX
some examples:
rej/ann by_zone 14,15,16 and not by G,M,2
You can use the tag 'all' to reject everything eg:
rej/ann all
but this probably for advanced users...

===reject/route <call> [0-9] <pattern>===
*reject/route <call> [0-9] <pattern> - Set an 'reject' filter line for routing
Create an 'reject this routing PC Protocol' line for a filter. An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter it is NOT passed thru that interface. See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
call <prefixes> the callsign of the thingy
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,ME
origin <prefixes>
really the interface it came in on
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,ME
some examples:
rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
You can use the tag 'all' to reject everything eg:
rej/route all (equiv to [very] restricted mode)
as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.

===reject/spots <call> [input] [0-9] <pattern>===
*reject/spots <call> [input] [0-9] <pattern> - Spot filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/spot db0sue-7 1 by_zone 14,15,16
reject/spot node_default all set/hops node_default 10
reject/spot user_default by G,M,2

===reject/spots [0-9] <pattern>===
*reject/spots [0-9] <pattern> - Set a 'reject' filter line for spots
Create a 'reject this spot' line for a filter. A reject filter line means that if the spot matches this filter it is dumped (not passed on). See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on <range> same as 'freq'
call <prefixes> eg: G,PA,HB9i
nfo <string> eg: iota or qsl
by <prefixes>
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states> eg: VA,NH,RI,ME
origin <prefixes>
channel <prefixes>
'call' means the callsign that has spotted 'by' whoever. For frequencies, you can use any of the band names defined in SHOW/BANDS and you can use a sub-band name like: cw, rtty, data, ssb -thus: hf/ssb. You can also just have a simple range like: 0/30000 -this is more efficient than saying simply: on HF (but don't get too hung up about that)some examples:
rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
You can use the tag 'all' to reject everything eg:
rej/spot 3 all
but this probably for advanced users...

===reject/wcy <call> [input] [0-9] <pattern>===
*reject/wcy <call> [input] [0-9] <pattern> - WCY filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/wcy gb7djk all

===reject/wcy [0-9] <pattern>===
reject/wcy [0-9] <pattern> - set a 'reject' WCY filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them). This command is really provided for future use. See HELP FILTER for information.

===reject/wwv <call> [input] [0-9] <pattern>===
*reject/wwv <call> [input] [0-9] <pattern> - WWV filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/wwv db0sue-7 1 by_zone 4
reject/wwv node_default all
reject/wwv user_default by W

===reject/wwv [0-9] <pattern>===
*reject/wwv [0-9] <pattern> - set a 'reject' WWV filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
for example
reject/wwv by_zone 14,15,16
is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). See HELP FILTER for information.

==REPLY==
===reply===
*reply - Reply (privately) to the last message that you have read

===reply <msgno>===
*reply <msgno> - Reply (privately) to the specified message

===reply b <msgno>===
*reply b <msgno> - Reply as a Bulletin to the specified message

===reply noprivate <msgno>===
*reply noprivate <msgno> - Reply as a Bulletin to the specified message

===reply rr <msgno>===
*reply rr <msgno> - Reply to the specified message with read receipt
You can reply to a message and the subject will automatically have "Re:" inserted in front of it, if it isn't already present. You can also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B that you can use with the SEND command (see SEND for further details)

==SAVE==
===save [-d -t -a] <filename> "<cmd>" [...]===
*save [-d -t -a] <filename> "<cmd>" [...] Save command output to a file
This sysop only command allows you to save the output of one or more commands to a file. For example:
save /spider/packclus/dxstats show/dxstat
will save the output of the normal command "show/dxstat" to the file "dxstats" in the files area. You can have some extra flags to the save which will either date stamp or time stamp or both the filename so:
save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
save -t /tmp/a <cmd> creates /tmp/a_2301Z
save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
The -a flag means append to the file instead of overwriting it. You can have more than one command on the line, to do this you MUST enclose each command in double quotes (") eg:
save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
or
save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
You can only write into places that the cluster has permission for (which is that of the "sysop" user [which had BETTER NOT BE "root"]), you will need to create any directories you want to put stuff in beforehand as well. It is likely that you will want to run these commands in a crontab type situation. You would do that something like:
0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
Note that you still enclose each command with (") characters but you must enclose the entire save command in (') characters. Now in fact, this can be varied if you know what you are doing. See the admin manual for more details.

==SEND==
===send <call> [<call> ...]===
*send <call> [<call> ...] - Send a message to one or more callsigns

===send copy <msgno> <call>===
send copy <msgno> <call> - Send a copy of a message to someone

===send noprivate <call>===
*send noprivate <call> - Send a message to all stations
All the SEND commands will create a message which will be sent either to an individual callsign or to one of the 'bulletin' addresses. SEND <call> on its own acts as though you had typed SEND PRIVATE, that is it will mark the message as personal and send it to the cluster node that that callsign is connected to. If the <call> you have specified is in fact a known bulletin category on your node (eg: ALL) then the message should automatically become a bulletin. You can have more than one callsign in all of the SEND commands. You can have multiple qualifiers so that you can have for example:
SEND RR COPY 123 PRIVATE G1TLH G0RDI
which should send a copy of message 123 to G1TLH and G0RDI and you will receive a read receipt when they have read the message. SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak). SP is an alias for SEND PRIVATE. The system will ask you for a subject. Conventionally this should be no longer than 29 characters for compatibility. Most modern cluster software should accept more. You will now be prompted to start entering your text. You finish the message by entering '/EX' on a new line. For instance:
... bye then Jim 73 Dirk /ex
If you have started a message and you don't want to keep it then you can abandon the message with '/ABORT' on a new line, like:
line 1 line 2 oh I just can't be bothered with this /abort
If you abort the message it will NOT be sent. When you are entering the text of your message, most normal output (such as DX announcements and so on are suppressed and stored for latter display(up to 20 such lines are stored, as new ones come along, so the oldest lines are dropped). Also, you can enter normal commands commands (and get the output immediately) whilst in the middle of a message. You do this by typing the command preceded by a '/' character on a new line, so:
/dx g1tlh 144010 strong signal
Will issue a dx announcement to the rest of the cluster. Also, you can add the output of a command to your message by preceding the command with '//', thus :
//sh/vhftable
This will show YOU the output from SH/VHFTABLE and also store it in the message. You can carry on with the message until you are ready to send it.

===send private <call>===
*send private <call> - Send a personal message

===send rr <call>===
*send rr <call> - Send a message and ask for a read receipt

==SET==
===set/address <your address>===
*set/address <your address> - Record your postal address

===set/announce===
*set/announce - Allow announce messages to come out on your terminal

===set/anntalk===
*set/anntalk - Allow talk like announce messages on your terminal

===set/arcluster <call> [<call>..]===
*set/arcluster <call> [<call>..] - Make the callsign an AR-Cluster node

===set/baddx <call>..===
*set/baddx <call>.. - Stop callsigns in a dx spot being propagated

===set/badnode <call>..===
*set/badnode <call>.. - Stop spots from this node being propagated

===set/badspotter <call>..===
*set/badspotter <call>.. - Stop spots from this callsign being propagated

===set/badword <word>..===
*set/badword <word>.. - Stop things with this word being propagated

===set/bbs <call> [<call>..]===
*set/bbs <call> [<call>..] - Make the callsign a BBS

===set/beep===
*set/beep - Add a beep to DX and other messages on your terminal

===set/clx <call> [<call>..]===
*set/clx <call> [<call>..] - Make the callsign an CLX node

===set/debug <name>===
*set/debug <name> - Add a debug level to the debug set

===set/dx===
*set/dx - Allow DX messages to come out on your terminal

===set/dxcq===
*set/dxcq - Show CQ Zones on the end of DX announcements

===set/dxgrid===
*set/dxgrid - Allow QRA Grid Squares on the end of DX announcements

===set/dxitu===
*set/dxitu - Show ITU Zones on the end of DX announcements

===set/dxnet <call> [<call>..]===
*set/dxnet <call> [<call>..] - Make the callsign an DXNet node

===set/echo===
*set/echo - Make the cluster echo your input

===set/email <email> ...===
*set/email <email> ... - Set email address(es) and forward your personals

===set/external_ip <external_ip>===
*set/external_ip - Set the external IPv4 address for the node and the local terminal masquerade automatically with best effort.

===set/here===
*set/here - Tell the system you are present at your terminal

===set/homenode <node>===
*set/homenode <node> - Set your normal cluster callsign
Tell the cluster system where you normally connect to. Any Messages sent to you will normally find their way there should you not be connected.eg:
SET/HOMENODE gb7djk

===set/hops <call> ann|spots|route|wwv|wcy <n>===
*set/hops <call> ann|spots|route|wwv|wcy <n> - Set hop count

===set/isolate===
*set/isolate - Isolate a node from the rest of the network
Connect a node to your system in such a way that you are a full protocol member of its network and can see all spots on it, but nothing either leaks out from it nor goes back into from the rest of the nodes connected to you. You can potentially connect several nodes in this way.

===set/language <lang>===
*set/language <lang> - Set the language you want to use
You can select the language that you want the cluster to use. Currently the languages available are en (English), de (German), es (Spanish),Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).

===set/location <lat & long>===
*set/location <lat & long> - Set your latitude and longitude

===set/lockout <call>===
*set/lockout <call> - Stop a callsign connecting to the cluster

===set/logininfo===
*set/logininfo - Inform when a station logs in/out locally

===set/name <your name>===
*set/name <your name> - Set your name
Tell the system what your name is eg:
SET/NAME Dirk

===set/node <call> [<call>..]===
*set/node <call> [<call>..] - Make the callsign an AK1A cluster
Tell the system that the call(s) are to be treated as AK1A cluster and fed PC Protocol rather normal user commands.

===set/obscount <count> <call>===
*set/obscount <count> <call> - Set the 'pump-up' obscelence PING counter
From 1.35 onwards neighboring nodes are pinged at regular intervals (see SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up' counter which is decremented on every outgoing ping and then reset to the 'obscount' value on every incoming ping. The default value of this parameter is 2. What this means is that a neighbouring node will be pinged twice at (default) 300 second intervals and if no reply has been heard just before what would be the third attempt, that node is disconnected. If a ping is heard then the obscount is reset to the full value. Using default values, if a node has not responded to a ping within 15 minutes, it is disconnected. You can set this parameter between 1 and 9. It is STRONGLY recommended that you don't change the default.

===set/page <lines per page>===
*set/page <lines per page> - Set the lines per page
Tell the system how many lines you wish on a page when the number of line of output from a command is more than this. The default is 20. Setting it explicitly to 0 will disable paging.
SET/PAGE 30 SET/PAGE 0
The setting is stored in your user profile.

===set/password===
*set/password - Set your own password
This command only works for a 'telnet' user (currently). It will only work if you have a password already set. This initial password can only be set by the sysop. When you execute this command it will ask you for your old password, then ask you to type in your new password twice (to make sure you get it right). You may or may not see the data echoed on the screen as you type, depending on the type of telnet client you have.

===set/password <callsign> <string>===
*set/password <callsign> <string> - Set a users password
The password for a user can only be set by a full sysop. The string can contain any characters. The way this field is used depends on context. If it is being used in the SYSOP command context then you are offered 5 random numbers and you have to supply the corresponding letters. This is now mainly for ax25 connections. If it is being used on incoming telnet connections then, if a password is set or the:
set/var $main::passwdreq = 1
command is executed in the startup script, then a password prompt is given after the normal 'login:' prompt.

===set/pinginterval <time> <nodecall>===
*set/pinginterval <time> <nodecall> - Set ping time to neighbouring nodes
As from release 1.35 all neighbouring nodes are pinged at regular intervals in order to determine the rolling quality of the link and, in future, to affect routing decisions. The default interval is 300 secs or 5 minutes. You can use this command to set a different interval. Please don't. But if you do the value you enter is treated as minutes up 30 and seconds for numbers greater than that. This is used also to help determine when a link is down at the far end(as certain cluster software doesn't always notice), see SET/OBSCOUNT for more information. If you must change it (and it may be useful for internet connected nodes on dynamic IP addresses that go away after a set time of usage) the time can be specified as:
5 which if less than 30 is converted to minutes otherwise is taken as the no of seconds between pings.
120s 120 seconds
5m 5 minutes
1h 1 hour
Please be aware that this causes traffic to occur on the link, setting this value too low may annoy your neighbours beyond the point of endurance! You can switch this off by setting it to 0.

===set/privilege <n> <call> [<call..]===
*set/privilege <n> <call> [<call..] - Set privilege level on a call
Set the privilege level on a callsign. The privilege levels that pertain to commands are as default:
0 - normal user
1 - allow remote nodes normal user RCMDs
5 - various privileged commands (including shutdown, but not disconnect), the normal level for another node.
8 - more privileged commands (including disconnect)
9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS LEVEL.
If you are a sysop and you come in as a normal user on a remote connection your privilege will automatically be set to 0.

===set/prompt <string>===
*set/prompt <string> - Set your prompt to <string>

===set/qra <locator>===
*set/qra <locator> - Set your QRA Grid locator
Tell the system what your QRA (or Maidenhead) locator is. If you have not done a SET/LOCATION then your latitude and longitude will be set roughly correctly (assuming your locator is correct ;-). For example:
SET/QRA JO02LQ

===set/qth <your qth>===
*set/qth <your qth> - Set your QTH
Tell the system where you are. For example:
SET/QTH East Dereham, Norfolk

===set/register <call> ...===
set/register <call> ... - Mark a user as registered

===set/seeme===
*set/seeme - see spots or your call
This command will enable the output of all RBN spots, of your call, to be seen regardless of processing.
Ex:
DX de W1NT-#: 7002.5 WI3W CW 22dB **SEEME** FN20 0204Z
DX de NU4F-#: 7002.5 WI3W CW 10dB **SEEME** FN20 0204Z
DX de WS3W-#: 7002.5 WI3W CW 12dB **SEEME** FN20 0204Z
DX de VE3EID-#: 7002.5 WI3W CW 26dB **SEEME** FN20 0204Z
DX de WC8GOP-#: 7002.6 WI3W CW 9dB **SEEME** FN20 0205Z
DX de KD7EFG-#: 7002.5 WI3W CW 17dB **SEEME** FN20 0205Z

===set/spider <call> [<call>..]===
*set/spider <call> [<call>..] - Make the callsign an DXSpider node
Tell the system that the call(s) are to be treated as DXSpider node and fed new style DX Protocol rather normal user commands.

===set/startup===
*set/startup - Create your own startup script
Create a startup script of DXSpider commands which will be executed every time that you login into this node. You can only input the whole script afresh, it is not possible to 'edit' it. Inputting a new script is just like typing in a message using SEND. To finish inputting type: /EX on a newline, to abandon the script type: /ABORT. You may find the (curiously named) command BLANK useful to break up the output. If you simply want a blank line, it is easier to input one or more spaces and press the <return> key. See UNSET/STARTUP to remove a script.

===set/startup <call>===
*set/startup <call> - Create a user startup script

===set/sys_location <lat & long>===
*set/sys_location <lat & long> - Set your cluster latitude and longitude
In order to get accurate headings and such like you must tell the system what your latitude and longitude is. If you have not yet done a SET/QRA then this command will set your QRA locator for you. For example:
SET/LOCATION 52 22 N 0 57 E

===set/sys_qra <locator>===
*set/sys_qra <locator> - Set your cluster QRA Grid locator

===set/talk===
*set/talk - Allow TALK messages to come out on your terminal

===set/usdb <call> <state> <city>===
*set/usdb <call> <state> <city> - add/update a US DB callsign
This command allows you to add or alter a callsign in the US state database. Use with extreme caution. Anything you do here will be overwritten by any weekly updates that affect this callsign
set/usdb g1tlh nh downtown rindge
see also DELETE/USDB

===set/usstate===
*set/usstate - Allow US State info on the end of DX announcements

===set/wcy===
*set/wcy - Allow WCY messages to come out on your terminal

===set/wwv===
*set/wwv - Allow WWV messages to come out on your terminal

===set/wx===
*set/wx - Allow WX messages to come out on your terminal

==SHOW==
===show/baddx===
*show/baddx - Show all the bad dx calls in the system
Display all the bad dx callsigns in the system, see SET/BADDX for more information.

===show/badnode===
*show/badnode - Show all the bad nodes in the system
Display all the bad node callsigns in the system, see SET/BADNODE for more information.

===show/badspotter===
*show/badspotter - Show all the bad spotters in the system
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER for more information.

===show/badword===
*show/badword - Show all the bad words in the system
Display all the bad words in the system, see SET/BADWORD for more information.

===show/chat [<group>] [<lines>]===
*show/chat [<group>] [<lines>] - Show any chat or conferencing
This command allows you to see any chat or conferencing that has occurred whilst you were away. SHOW/CHAT on its own will show data for all groups. If you use a group name then it will show only chat for that group.

===show/configuration [<node>]===
*show/configuration [<node>] - Show all the nodes and users visible
This command allows you to see all the users that can be seen and the nodes to which they are connected. This command is normally abbreviated to: sh/c. Normally, the list returned will be just for the nodes from your country (because the list otherwise will be very long).
SH/C ALL
will produce a complete list of all nodes. BE WARNED: the list that is returned can be VERY long. It is possible to supply a node or part of a prefix and you will get a list of the users for that node or list of nodes starting with that prefix.
SH/C GB7DJK
SH/C SK

===show/connect===
*show/connect - Show all the active connections
This command shows information on all the active connections known to the node. This command gives slightly more information than WHO.

===show/contest===
*show/contest - Show all the contests for 8 days
Show all known contests which are maintained at 'WA7BNM Contest Calendar: 8-Day Calendar': http://www.contestcalendar.com/weeklycont.php

The following need to be set for this to work:
* $Internet::allow = 1
* $Internet::contest_host = "contest.dxtron.com"

===show/date [<prefix>|<callsign>]===
*show/date [<prefix>|<callsign>] - Show the local time
This is very nearly the same as SHOW/TIME, the only difference the format of the date string if no arguments are given. If no prefixes or callsigns are given then this command returns the local time and UTC as the computer has it right now. If you give some prefixes then it will show UTC and UTC + the local offset (not including DST) at the prefixes or callsigns that you specify.

===show/db0sdx <callsign>===
*show/db0sdx <callsign> - Show QSL information from DB0SDX database
This command queries the DB0SDX QSL server on the internet and returns any information available for that callsign. This service is provided for users of this software by http://www.qslinfo.de. See also SHOW/QRZ, SHOW/WM7D.

===show/debug===
*show/debug - Show what levels of debug information you are logging

===show/dup_ann===
*show/dup_ann - Show duplicate announcement records

===show/dup_spots===
*show/dup_spots - Show duplicate spot records

===show/dx===
*show/dx - Interrogate the spot database
If you just type SHOW/DX you will get the last so many spots (sysop configurable, but usually 10). In addition you can add any number of these commands in very nearly any order to the basic SHOW/DX command, they are:
on <band> - eg 160m 20m 2m 23cm 6mm
on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
on <from>/<to> - eg 1000/4000 14000-30000 (in Khz) <from>-<to>
<number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
<prefix> - for a spotted callsign beginning with <prefix>
*<suffix> - for a spotted callsign ending in <suffix>
*<string>* - for a spotted callsign containing <string>
day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
info <text> - any spots containing <text> in the info or remarks
by <call> - any spots spotted by <call> (spotter <call> is the same).
qsl - this automatically looks for any qsl info on the call held in the spot database.
iota [<iota>] - If the iota island number is missing it will look for the string iota and anything which looks like an iota island number. If you specify then it will look for that island.
qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2 You can also use this with the 'by' keyword so eg by W dxcc
real or rt - Format the output the same as for real time spots. The formats are deliberately different (so you can tell one sort from the other). This is useful for some logging programs that can't cope with normal sh/dx output. An alias of SHOW/FDX is available.
filter - Filter the spots, before output, with the user's spot filter. An alias of SHOW/MYDX is available.
zone <zones> - look for spots in the cq zone (or zones) specified. zones are numbers separated by commas.
by_zone <zones> - look for spots spotted by people in the cq zone specified.
itu <itus> - look for spots in the itu zone (or zones) specified itu zones are numbers separated by commas.
by_itu <itus> - look for spots spotted by people in the itu zone specified.
state <list> - look for spots in the US state (or states) specified The list is two letter state codes separated by commas.
by_state <list> - look for spots spotted by people in the US state specified.
e.g.
SH/DX 9m0
SH/DX on 20m info iota
SH/DX 9a on vhf day 30
SH/DX rf1p qsl
SH/DX iota
SH/DX iota eu-064
SH/DX qra jn86
SH/DX dxcc oq2
SH/DX dxcc oq2 by w dxcc
SH/DX zone 4,5,6
SH/DX by_zone 4,5,6
SH/DX state in,oh
SH/DX by_state in,oh

===show/dxcc <prefix>===
*show/dxcc <prefix> - Interrogate the spot database by country
This command takes the <prefix> (which can be a full or partial callsign if desired), looks up which internal country number it is and then displays all the spots as per SH/DX for that country. This is now an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this command. e.g.
SH/DXCC G SH/DXCC W on 20m iota
This can be done with the SHOW/DX command like this:
SH/DX dxcc g
SH/DX dxcc w on 20m iota
This is an alias for: SH/DX dxcc

===show/dxqsl <callsign>===
*show/dxqsl <callsign> - Show any QSL info gathered from spots
The node collects information from the comment fields in spots (things like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database. This command allows you to interrogate that database and if the callsign is found will display the manager(s) that people have spotted. This information is NOT reliable, but it is normally reasonably accurate if it is spotted enough times. For example:
sh/dxqsl 4k9w
You can check the raw input spots yourself with:
sh/dx 4k9w qsl
This gives you more background information.

===show/dxstats [days] [date]===
*show/dxstats [days] [date] - Show the DX Statistics
Show the total DX spots for the last <days> no of days (default is 31), starting from a <date> (default: today).

===show/external_ip===
*show/external_ip - Show the external IP set/detected for the node and local terminal masquerade

===show/fdx===
*show/fdx - Show the DX data in realtime format.
Normally SHOW/DX outputs spot data in a different format to the realtime data. This is a deliberate policy (so you can tell the difference between the two). Some logging programs cannot handle this so SHOW/FDX outputs historical data in real time format. This is an alias for: SHOW/DX real

===show/files [<file area> [<string>]]===
*show/files [<file area> [<string>]] - List the contents of a file area
SHOW/FILES on its own will show you a list of the various file areas available on the system. To see the contents of a particular file area type:
SH/FILES <file area>
where <file area> is the name of the file area you want to see the contents of. You can also use shell globbing characters like '*' and '?' in a string to see a selection of files in a file area eg:
SH/FILES bulletins arld*
See also TYPE - to see the contents of a file.

===show/filter===
*show/filter - Show the contents of all the filters you have set
Show the contents of all the filters that are set. This command displays all the filters set - for all the various categories.

===show/hfstats [days] [date]===
*show/hfstats [days] [date] - Show the HF DX Statistics
Show the HF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a <date> (default: today).

===show/hftable [days] [date] [prefix ...]===
*show/hftable [days] [date] [prefix ...] - Show the HF DX Spotter Table
Show the HF DX Spotter table for the list of prefixes for the last <days> no of days (default is 31), starting from a <date> (default: today). If there are no prefixes then it will show the table for your country. Remember that some countries have more than one "DXCC country" in them (eg G :-), to show them (assuming you are not in G already which is specially treated in the code) you must list all the relevant prefixes
sh/hftable g gm gd gi gj gw gu
Note that the prefixes are converted into country codes so you don't have to list all possible prefixes for each country. If you want more or less days than the default simply include the number you require:
sh/hftable 20 pa
If you want to start at a different day, simply add the date in some recognizable form:
sh/hftable 2 25nov02
sh/hftable 2 25-nov-02
sh/hftable 2 021125
sh/hftable 2 25/11/02
This will show the stats for your DXCC for that CQWW contest weekend. You can specify either prefixes or full callsigns (so you can see how you did against all your mates). You can also say 'all' which will then print the worldwide statistics.
sh/hftable all

===show/hops <call> [ann|spots|route|wcy|wwv]===
*show/hops <call> [ann|spots|route|wcy|wwv] - Show the hop counts for a node
This command shows the hop counts set up for a node. You can specify which category you want to see. If you leave the category out then all the categories will be listed.

===show/isolate===
*show/isolate - Show list of ISOLATED nodes

===show/lockout <prefix>|all===
*show/lockout <prefix>|all - Show the list of locked out or excluded callsigns

===show/log [<callsign>]===
*show/log [<callsign>] - Show excerpts from the system log
This command outputs a short section of the system log. On its own it will output a general logfile. With the optional callsign it will show output from the log associated with that callsign.

===show/moon [ndays] [<prefix>|<callsign>]===
*show/moon [ndays] [<prefix>|<callsign>] - Show Moon rise and set times
Show the Moon rise and set times for a (list of) prefixes or callsigns, together with the azimuth and elevation of the sun currently at those locations. If you don't specify any prefixes or callsigns, it will show the times for your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), together with the current azimuth and elevation. In addition, it will show the illuminated fraction of the moons disk. If all else fails it will show the Moonrise and set times for the node that you are connected to. For example:
SH/MOON SH/MOON G1TLH W5UN
You can also use this command to see into the past or the future, so if you want to see yesterday's times then do:
SH/MOON -1
or in three days time:
SH/MOON +3 W9
Up to 366 days can be checked both in the past and in the future. Please note that the rise and set times are given as the UTC times of rise and set on the requested UTC day.

===show/muf <prefix> [<hours>][long]===
*show/muf <prefix> [<hours>][long] - Show the likely propagation to a prefix
This command allow you to estimate the likelihood of you contacting a station with the prefix you have specified. The output assumes a modest power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD). The result predicts the most likely operating frequencies and signal levels for high frequency (shortwave) radio propagation paths on specified days of the year and hours of the day. It is most useful for paths between 250 km and 6000 km, but can be used with reduced accuracy for paths shorter or longer than this. The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and used to predict the MUF given the predicted flux, day of the year, hour of the day and geographic coordinates of the transmitter and receiver. This routine is reasonably accurate for the purposes here, with a claimed RMS error of 3.8 MHz, but much smaller and less complex than the programs used by major shortwave broadcasting organizations, such as the Voice of America. The command will display some header information detailing its assumptions, together with the locations, latitude and longitudes and bearings. It will then show UTC (UT), local time at the other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path(Zen) and the likely signal strengths. Then for each frequency for which the system thinks there is a likelihood of a circuit it prints a value. The value is currently a likely S meter reading based on the conventional 6dB / S point scale. If the value has a '+' appended it means that it is 1/2 an S point stronger. If the value is proceeded by an 'm' it means that there is likely to be much fading and by an 's' that the signal is likely to be noisy. By default SHOW/MUF will show the next two hours worth of data. You can specify anything up to 24 hours worth of data by appending the no of hours required after the prefix. For example:
SH/MUF W
produces:
RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms Location Lat / Long Azim East Dereham, Norfolk 52 41 N 0 57 E 47 United-States-W 43 0 N 87 54 W 299 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0 18 23 11.5 -35 mS0+ mS2 S3 19 0 11.2 -41 mS0+ mS2 S3
indicating that you will have weak, fading circuits on top band and 80m but usable signals on 40m (about S3). inputting:
SH/MUF W 24
will get you the above display, but with the next 24 hours worth of propagation data.
SH/MUF W L 24
SH/MUF W 24 Long
Gives you an estimate of the long path propagation characteristics. It should be noted that the figures will probably not be very useful, nor terrible accurate, but it is included for completeness.

===show/mydx===
*show/mydx - Show the DX data filtered with your spot filter.
SHOW/DX potentially shows all the spots available in the system. Using SHOW/MYDX will, instead, filter the available spots using any spot filter that you have set, first. This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow you to customize the spots that you receive. So if you have said: ACC/SPOT on hf Doing a SHOW/MYDX will now only, ever, show HF spots. All the other options on SH/DX can still be used.

===show/newconfiguration [<node>]===
*show/newconfiguration [<node>] - Show all the nodes and users visible
This command allows you to see all the users that can be seen and the nodes to which they are connected. This command produces essentially the same information as SHOW/CONFIGURATION except that it shows all the duplication of any routes that might be present. It also uses a different format which may not take up quite as much space if you don't have any loops. BE WARNED: the list that is returned can be VERY long!

===show/newconfiguration/node===
*show/newconfiguration/node - Show all the nodes connected locally
Show all the nodes connected to this node in the new format.

===show/node [<callsign> ...]===
*show/node [<callsign> ...] - Show the type and version number of nodes
Show the type and version (if connected) of the nodes specified on the command line. If no callsigns are specified then a sorted list of all the non-user callsigns known to the system will be displayed.

===show/prefix <callsign>===
*show/prefix <callsign> - Interrogate the prefix database
This command takes the <callsign> (which can be a full or partial callsign or a prefix), looks up which internal country number it is and then displays all the relevant prefixes for that country together with the internal country no, the CQ and ITU regions. See also SHOW/DXCC.

===show/program===
*show/program - Show the locations of all the included program modules
Show the name and location where every program module was load from. This is useful for checking where you think you have loaded a .pm file from.

===show/qra <lat> <long>===
*show/qra <lat> <long> - Convert lat/long to a QRA Grid locator
This is a multipurpose command that allows you either to calculate the distance and bearing between two locators or (if only one locator is given on the command line) the distance and bearing from your station to the locator. For example:
SH/QRA IO92Q
SH/QRA JN06 IN73
The first example will show the distance and bearing to the locator from yourself, the second example will calculate the distance and bearing from the first locator to the second. You can use 4 or 6 character locators. It is also possible to convert a latitude and longitude to a locator by using this command with a latitude and longitude as an argument, for example:
SH/QRA 52 41 N 0 58 E

===show/qra <locator> [<locator>]===
*show/qra <locator> [<locator>] - Show distance between QRA Grid locators

===show/qrz <callsign>===
*show/qrz <callsign> - Show any callbook details on a callsign
This command queries the QRZ callbook server on the internet and returns any information available for that callsign. This service is provided for users of this software by http://www.qrz.com See also SHOW/WM7D for an alternative.

===show/registered [<prefix>]===
*show/registered [<prefix>] - Show the registered users

===show/route <callsign> ...===
*show/route <callsign> ... - Show the route to the callsign
This command allows you to see to which node the callsigns specified are connected. It is a sort of inverse sh/config.
sh/route n2tly

===show/satellite <name> [<hours> <interval>]===
*show/satellite <name> [<hours> <interval>] - Show tracking data
Show the tracking data from your location to the satellite of your choice from now on for the next few hours. If you use this command without a satellite name it will display a list of all the satellites known currently to the system. If you give a name then you can obtain tracking data of all the passes that start and finish 5 degrees below the horizon. As default it will give information for the next three hours for every five minute period. You can alter the number of hours and the step size, within certain limits. Each pass in a period is separated with a row of '-----' characters. So for example:
SH/SAT AO-10
SH/SAT FENGYUN1 12 2

===show/startup===
*show/startup - View your own startup script
View the contents of a startup script created with SET/STARTUP.

===show/startup <call>===
*show/startup <call> - View a user startup script

===show/station all [<regex>]===
*show/station all [<regex>] - Show list of users in the system

===show/station [<callsign> ..]===
*show/station [<callsign> ..] - Show information about a callsign
Show the information known about a callsign and whether (and where) that callsign is connected to the cluster.
SH/ST G1TLH
If no callsign is given then show the information for yourself.

===show/sun [ndays] [<prefix>|<callsign>]===
*show/sun [ndays] [<prefix>|<callsign>] - Show sun rise and set times
Show the sun rise and set times for a (list of) prefixes or callsigns, together with the azimuth and elevation of the sun currently at those locations. If you don't specify any prefixes or callsigns, it will show the times for your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), together with the current azimuth and elevation. If all else fails it will show the sunrise and set times for the node that you are connected to. For example:
SH/SUN
SH/SUN G1TLH K9CW ZS
You can also use this command to see into the past or the future, so if you want to see yesterday's times then do:
SH/SUN -1
or in three days time:
SH/SUN +3 W9
Up to 366 days can be checked both in the past and in the future. Please note that the rise and set times are given as the UTC times of rise and set on the requested UTC day.

===show/time [<prefix>|<callsign>]===
*show/time [<prefix>|<callsign>] - Show the local time
If no prefixes or callsigns are given then this command returns the local time and UTC as the computer has it right now. If you give some prefixes then it will show UTC and UTC + the local offset (not including DST) at the prefixes or callsigns that you specify.

===show/usdb [call ..]===
*show/usdb [call ..] - Show information held on the FCC Call database
Show the City and State of a Callsign held on the FCC database if his is being run on this system, eg:
sh/usdb k1xx

===show/vhfstats [days] [date]===
*show/vhfstats [days] [date] - Show the VHF DX Statistics
Show the VHF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a date (default: today).

===show/vhftable [days] [date] [prefix ...]===
*show/vhftable [days] [date] [prefix ...] - Show the VHF DX Spotter Table
Show the VHF DX Spotter table for the list of prefixes for the last <days> no of days (default is 31), starting from a date (default: today). If there are no prefixes then it will show the table for your country. Remember that some countries have more than one "DXCC country" in them (eg G :-), to show them (assuming you are not in G already which is specially treated in the code) you must list all the relevant prefixes:
sh/vhftable g gm gd gi gj gw gu
Note that the prefixes are converted into country codes so you don't have to list all possible prefixes for each country. If you want more or less days than the default simply include the number you require:
sh/vhftable 20 pa
If you want to start at a different day, simply add the date in some recognizable form:
sh/vhftable 2 25nov02
sh/vhftable 2 25-nov-02
sh/vhftable 2 021125
sh/vhftable 2 25/11/02
This will show the stats for your DXCC for that CQWW contest weekend. You can specify either prefixes or full callsigns (so you can see how you did against all your mates). You can also say 'all' which will then print the worldwide statistics.
sh/vhftable all

===show/wcy===
*show/wcy - Show last 10 WCY broadcasts

===show/wcy <n>===
show/wcy <n> - Show last <n> WCY broadcasts
Display the most recent WCY information that has been received by the system.

===show/wm7d <callsign>===
*show/wm7d <callsign> - Show callbook details on a US callsigns
This command queries the WM7D callbook server on the internet and returns any information available for that US callsign. This service is provided for users of this software by http://www.wm7d.net. See also SHOW/QRZ.

===show/wwv===
*show/wwv - Show last 10 WWV broadcasts

===show/wwv <n>===
*show/wwv <n> - Show last <n> WWV broadcasts
Display the most recent WWV information that has been received by the system.

==SHUTDOWN==
===shutdown===
shutdown - Shutdown the cluster
Shutdown the cluster and disconnect all the users

==SPOOF==
===spoof <call> <command>===
*spoof <call> <command> - Do a command as though you are another user
This command is provided so that sysops can set a user's parameters without me having to write a special 'sysop' version for every user command. It allows you to pretend that you are doing the command as the user you specify.eg:
SPOOF G1TLH set/name Dirk
SPOOF G1TLH set/qra JO02LQ

==STAT==
===stat/channel [<callsign>]===
*stat/channel [<callsign>] - Show the status of a channel on the cluster
Show the internal status of the channel object either for the channel that you are on or else for the callsign that you asked for. Only the fields that are defined (in perl term) will be displayed.

===stat/db <dbname>===
*stat/db <dbname> - Show the status of a database
Show the internal status of a database descriptor. Depending on your privilege level you will see more or less information. This command is unlikely to be of much use to anyone other than a sysop.

===stat/msg===
*stat/msg - Show the status of the message system

===stat/msg <msgno>===
*stat/msg <msgno> - Show the status of a message
This command shows the internal status of a message and includes information such as to whom it has been forwarded, its size, origin etc etc. If no message number is given then the status of the message system is displayed.

===stat/route_node <callsign>===
*stat/route_node <callsign> - Show the data in a Route::Node object

===stat/route_node all===
*stat/route_node all - Show list of all Route::Node objects

===stat/route_user <callsign>===
*stat/route_user <callsign> - Show the data in a Route::User object

===stat/route_user all===
*stat/route_user all - Show list of all Route::User objects

===stat/user [<callsign>]===
*stat/user [<callsign>] - Show the full status of a user
Shows the full contents of a user record including all the secret flags and stuff. Only the fields that are defined (in perl term) will be displayed.

==SYSOP==
===sysop===
sysop - Regain your privileges if you login remotely
The system automatically reduces your privilege level to that of anormal user if you login in remotely. This command allows you to regain your normal privilege level. It uses the normal system: five numbers are returned that are indexes into the character array that is your assigned password (see SET/PASSWORD). The indexes start from zero. You are expected to return a string which contains the characters required in the correct order. You may intersperse those characters with others to obscure your reply for any watchers. For example (and these values are for explanation :-):
password = 012345678901234567890123456789 > sysop 22 10 15 17 3
you type:
aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
They will all match. If there is no password you will still be offered numbers but nothing will happen when you input a string. Any match is case sensitive.

==TALK==
===talk <call> > <node> [<text>]===
*talk <call> > <node> [<text>] - Send a text message to another station via a node
Send a short message to any other station that is visible on the cluster system. You can send it to anyone you can see with a SHOW/CONFIGURATION command, they don't have to be connected locally. The second form of TALK is used when other cluster nodes are connected with restricted information. This usually means that they don't send the user information usually associated with logging on and off the cluster. If you know that G3JNB is likely to be present on GB7TLH, but you can only see GB7TLH in the SH/C list but with no users, then you would use the second form of the talk message. If you want to have a ragchew with someone you can leave the text message out and the system will go into 'Talk' mode. What this means is that a short message is sent to the recipient telling them that you are in a 'Talking' frame of mind and then you just type - everything you send will go to the station that you asked for. All the usual announcements, spots and so on will still come out on your terminal. If you want to do something (such as send a spot) you precede the normal command with a '/' character, eg:
/DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
To leave talk mode type:
/EX
If you are in 'Talk' mode, there is an extension to the '/' command which allows you to send the output to all the people you are talking to. You do with the '//' command. For example:
//sh/hftable
will send the hftable as you have it to all the people you are currently talking to.

===talk <call> [<text>]===
*talk <call> [<text>] - Send a text message to another station

==TYPE==
===type <filearea>/<name>===
*type <filearea>/<name> - Look at the contents of a file in one of the file areas
Type out the contents of a file in a file area. So, for example, in file area 'bulletins' you want to look at file 'arld051' you would enter:
TYPE bulletins/arld051
See also SHOW/FILES to see what file areas are available and a list of content.

==UNCATCHUP==
===uncatchup <node call> all|[msgno> ...]===
*uncatchup <node call> all|[msgno> ...] - Unmark a message as sent
When you send messages the fact that you have forwarded it to another node is remembered so that it isn't sent again. When you have a new partner node and you add their callsign to your /spider/msg/forward.pl file, all outstanding non-private messages will be forwarded to them. This may well be ALL the non-private messages. You can prevent this by using these commands:
catchup GB7DJK all
catchup GB7DJK 300 301 302 303 500-510
and to undo what you have just done:
uncatchup GB7DJK all
uncatchup GB7DJK 300 301 302 303 500-510
which will arrange for them to be forward candidates again. Order is not important.

==UNSET==
===unset/announce===
unset/announce - Stop announce messages coming out on your terminal

===unset/anntalk===
*unset/anntalk - Stop talk like announce messages on your terminal
The announce system on legacy cluster nodes is used as a talk substitute because the network is so poorly connected. If you:
unset/anntalk
you will suppress several of these announces, you may miss the odd useful one as well, but you would probably miss them anyway in the welter of useless ones.
set/anntalk
allows you to see them again. This is the default.

===unset/baddx <call>..===
*unset/baddx <call>.. - Propagate a dx spot with this callsign again
Setting a word as 'baddx' will prevent spots with that word in the 'spotted' field (as in: DX 14001.1 FR0G) of a DX spot from going any further. They will not be displayed and they will not be sent onto other nodes. The word must be written in full, no wild cards are allowed eg:
set/baddx FORSALE VIDEO FR0G
To allow a word again, use the following command ...
unset/baddx VIDEO

===unset/badnode <call>..===
*unset/badnode <call>.. - Allow spots from this node again
Setting a callsign as a 'badnode' will prevent spots from that node going any further. They will not be displayed and they will not be sent onto other nodes. The call must be a full eg:
set/badnode K1TTT
will stop anything from K1TTT. If you want SSIDs as well then you must enter them specifically.
unset/badnode K1TTT
will allow spots from him again. Use with extreme care. This command may well be superseded by FILTERing.

===unset/badspotter <call>..===
*unset/badspotter <call>.. - Allow spots from this callsign again
Setting a callsign as a 'badspotter' will prevent spots from this callsign going any further. They will not be displayed and they will not be sent onto other nodes. The call must be written in full, no wild cards are allowed eg:
set/badspotter VE2STN
will stop anything from VE2STN. This command will automatically stop spots from this user, regardless of whether or which SSID he uses. DO NOT USE SSIDs in the callsign, just use the callsign as above or below.
unset/badspotter VE2STN
will allow spots from him again. Use with extreme care. This command may well be superseded by FILTERing.

===unset/badword <word>..===
*unset/badword <word>.. - Propagate things with this word again
Setting a word as a 'badword' will prevent things like spots, announces or talks with this word in the the text part from going any further. They will not be displayed and they will not be sent onto other nodes. The word must be written in full, no wild cards are allowed eg:
set/badword annihilate annihilated annihilation
will stop anything with these words in the text.
unset/badword annihilated
will allow text with this word again.

===unset/beep===
*unset/beep - Stop beeps for DX and other messages on your terminal

===unset/debug <name>===
*unset/debug <name> - Remove a debug level from the debug set
You can choose to log several different levels. The levels are
chan state msg cron connect
You can show what levels you are logging with SHOW/DEBUG

===unset/dx===
*unset/dx - Stop DX messages coming out on your terminal

===unset/dxcq===
*unset/dxcq - Stop CQ Zones on the end of DX announcements
Display both the Spotter's and the Spotted's CQ Zone on the end of a DX announcement (there is just enough room). Some user programs cannot cope with this. The Spotter's CQ is on the RHS of the time, the Spotted's CQ is on the LHS. Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE. Do a STAT/USER to see which flags you have set if you are confused.

===unset/dxgrid===
*unset/dxgrid - Stop QRA Grid Squares on the end of DX announcements
A standard feature which is enabled in version 1.43 and above is that if the spotter's grid square is known it is output on the end of a DX announcement (there is just enough room). Some user programs cannot cope with this. You can use this command to reset (or set)this feature. Conflicts with: SET/DXCQ, SET/DXITU. Do a STAT/USER to see which flags you have set if you are confused.

===unset/dxitu===
*unset/dxitu - Stop ITU Zones on the end of DX announcements
Display both the Spotter's and the Spotted's ITU Zone on the end of a DX announcement (there is just enough room). Some user programs cannot cope with this. The Spotter's ITU is on the RHS of the time, the Spotted's ITU is on the LHS. Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE. Do a STAT/USER to see which flags you have set if you are confused.

===unset/echo===
*unset/echo - Stop the cluster echoing your input
If you are connected via a telnet session, different implementations of telnet handle echo differently depending on whether you are connected via port 23 or some other port. You can use this command to change the setting appropriately. The setting is stored in your user profile. YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.

===unset/email===
*unset/email - Stop personal msgs being forwarded by email
If any personal messages come in for your callsign then you can use these commands to control whether they are forwarded onto your email address. To enable the forwarding do something like:
SET/EMAIL mike.tubby@somewhere.com
You can have more than one email address (each one separated by a space). Emails are forwarded to all the email addresses you specify. You can disable forwarding by:
UNSET/EMAIL

===unset/here===
*unset/here - Tell the system you are absent from your terminal

===unset/hops <call> ann|spots|route|wwv|wcy===
*unset/hops <call> ann|spots|route|wwv|wcy - Unset hop count
Set the hop count for a particular type of broadcast for a node. This command allows you to set up special hop counts for a node for currently: announce, spots, wwv and wcy broadcasts.eg:
set/hops gb7djk ann 10
set/hops gb7mbc spots 20
Set SHOW/HOPS for information on what is already set. This commandcreates a filter and works in conjunction with the filter system. You can unset the hops with command UNSET/HOPS. For example:
unset/hops gb7djk ann
unset/hops gb7mbc spots

===unset/isolate===
*unset/isolate - Stop Isolation of a node from the rest of the network
Remove isolation from a node - SET/ISOLATE

===unset/lockout <call>===
*unset/lockout <call> - Allow a callsign to connect to the cluster

===unset/logininfo===
*unset/logininfo - No longer inform when a station logs in/out locally

===unset/password <call> ...===
*unset/password <call> ... - Delete (remove) a user's password
This command allows the sysop to completely delete and remove a password for a user.

===unset/privilege===
*unset/privilege - Remove any privilege for this session
You can use this command to 'protect' this session from unauthorized use. If you want to get your normal privilege back you will need to either logout and login again (if you are on a console) or use the SYSOP command.

===unset/prompt===
*unset/prompt - Set your prompt back to default
This command will set your user prompt to the string that you say. The point of this command to enable a user to interface to programs that are looking for a specific prompt (or else you just want a different prompt).
SET/PROMPT clx >
There are some substitutions that can be added to the prompt:
%C - callsign [which will have ( and ) around it if not here]
%D - date
%T - time
%M - cluster 'mycall'
The standard prompt is defined as:
SET/PROMPT %C de %M %D %T dxspider >
UNSET/PROMPT will undo the SET/PROMPT command and set your prompt back to normal.

===unset/register <call> ...===
*unset/register <call> ... - Mark a user as not registered
Registration is a concept that you can switch on by executing the
set/var $main::regreq = 1
command (usually in your startup file). If a user is NOT registered then, firstly, instead of the normal motd file (/spider/data/motd) being sent to the user at startup, the user is sent the motd_nor file instead. Secondly, the non-registered user only has READ-ONLY access to the node. The non-registered user cannot use DX, ANN etc. The only exception to this is that a non-registered user can TALK or SEND messages to the sysop.

===unset/startup===
*unset/startup - Remove your own startup script
You can remove your startup script with UNSET/STARTUP.

===unset/startup <call>===
*unset/startup <call> - Remove a user startup script

===unset/talk===
*unset/talk - Stop TALK messages coming out on your terminal

===unset/usstate===
*unset/usstate - Stop US State info on the end of DX announcements
If the spotter's or spotted's US State is known it is output on the end of a DX announcement (there is just enough room). A spotter's state will appear on the RHS of the time (like SET/DXGRID) and the spotted's state will appear on the LHS of thetime field. Any information found will override any locator information from SET/DXGRID. Some user programs cannot cope with this. You can use this command to reset (or set) this feature. Conflicts with: SET/DXCQ, SET/DXITU. Do a STAT/USER to see which flags you have set if you are confused.

===unset/wcy===
*unset/wcy - Stop WCY messages coming out on your terminal

===unset/wwv===
*unset/wwv - Stop WWV messages coming out on your terminal

===unset/wx===
*unset/wx - Stop WX messages coming out on your terminal

==WHO==
===who===
*who - Show who is physically connected
This is a quick listing that shows which callsigns are connected and what sort of connection they have.

==WX==
===wx <text>===
*wx <text> - Send a weather message to local users

===wx full <text>===
*wx full <text> - Send a weather message to all cluster users

===wx sysop <text>===
*wx sysop <text> - Send a weather message to other clusters only
Weather messages can sometimes be useful if you are experiencing an extreme that may indicate enhanced conditions.

Analysing the RBN

2025-04-16T20:47:20Z

G0TRT: /* Decoding the data */

==Background==

The Reverse Beacon Network (RBN) is a network of receivers, listening, decoding and providing information on received amateur radio signals.

===Watching RBN spots===

In order to watch data from the RBN, assuming that a connect is already made, ensure that debug is set to progress from the console:

set/deb progress

At the command prompt use the following to watch RBN spots flow:

./watchdbg 'progress' 'RBN: SPOT'

or the following to search for a specific aspect such as the callsign G3MD

./grepdbg 'progress' 'RBN: SPOT' 'G3MD'

===Example data===

15:59:41 (progress) RBN: SPOT key: 'G3MD|101220' = G3MD on 10121.9 by SQ5J @ 1559Z Q:9* route: SK0MMR dwell: 7s QRGScore: 17 Deviants: 1/9 (SQ5J:+0.1)
15:59:41 (progress) RBN: SPOT key: 'VE1VDM/B|281741' = VE1VDM/B on 28174.1 by NU4F @ 1555Z Q:2+ route: SK0MMR dwell: 3m 54s QRGScore: 10 Deviants: 0/2
15:59:41 (progress) RBN: SPOT key: 'VP2VI|248950' = VP2VI on 24895 by NN3RP @ 1559Z Q:9*+ route: SK0MMR dwell: 10s QRGScore: 5 Deviants: 1/5 (W3OA:+0.1)
15:59:42 (progress) RBN: SPOT key: 'DL4HG|70291' = DL4HG on 7029.1 by HB9BXE @ 1559Z Q:9* route: SK0MMR dwell: 9s QRGScore: 39 Deviants: 1/9 (DL0PF:+0.1)
15:59:45 (progress) RBN: SPOT key: 'AO100IAR|140850' = AO100IAR on 14085 by VE3EID @ 1556Z Q:2 route: SK0MMR dwell: 3m 5s QRGScore: 9 Deviants: 0/2

===Decoding the data===

This information is in the RBN.mojo file.

* Q is quality, and is the number of skimmers that have received the signal Q:8 would mean that the signal has been heard by 8 receivers. If they did not agree on a frequency this is indicated by a '*'. The frequency shown is the majority decision. If this station has been active for for a while and they are still calling CQ after some time (configurable, but nominally 60 minutes), then a '+' character will be added. If Q:1 is seen on a CW spot, then only one skimmer has seen that spot and the callsign *could* be wrong, But if Q is Q:2 and above, then the callsign is much more likely to be correct.
* Dwell - needs describing
* QRGScore - needs describing
* Deviants - needs describing

Analysing the RBN

2025-04-16T20:46:31Z

G0TRT: /* Decoding the data */

==Background==

The Reverse Beacon Network (RBN) is a network of receivers, listening, decoding and providing information on received amateur radio signals.

===Watching RBN spots===

In order to watch data from the RBN, assuming that a connect is already made, ensure that debug is set to progress from the console:

set/deb progress

At the command prompt use the following to watch RBN spots flow:

./watchdbg 'progress' 'RBN: SPOT'

or the following to search for a specific aspect such as the callsign G3MD

./grepdbg 'progress' 'RBN: SPOT' 'G3MD'

===Example data===

15:59:41 (progress) RBN: SPOT key: 'G3MD|101220' = G3MD on 10121.9 by SQ5J @ 1559Z Q:9* route: SK0MMR dwell: 7s QRGScore: 17 Deviants: 1/9 (SQ5J:+0.1)
15:59:41 (progress) RBN: SPOT key: 'VE1VDM/B|281741' = VE1VDM/B on 28174.1 by NU4F @ 1555Z Q:2+ route: SK0MMR dwell: 3m 54s QRGScore: 10 Deviants: 0/2
15:59:41 (progress) RBN: SPOT key: 'VP2VI|248950' = VP2VI on 24895 by NN3RP @ 1559Z Q:9*+ route: SK0MMR dwell: 10s QRGScore: 5 Deviants: 1/5 (W3OA:+0.1)
15:59:42 (progress) RBN: SPOT key: 'DL4HG|70291' = DL4HG on 7029.1 by HB9BXE @ 1559Z Q:9* route: SK0MMR dwell: 9s QRGScore: 39 Deviants: 1/9 (DL0PF:+0.1)
15:59:45 (progress) RBN: SPOT key: 'AO100IAR|140850' = AO100IAR on 14085 by VE3EID @ 1556Z Q:2 route: SK0MMR dwell: 3m 5s QRGScore: 9 Deviants: 0/2

===Decoding the data===

* Q is quality, and is the number of skimmers that have received the signal Q:8 would mean that the signal has been heard by 8 receivers. If they did not agree on a frequency this is indicated by a '*'. The frequency shown is the majority decision. If this station has been active for for a while and they are still calling CQ after some time (configurable, but nominally 60 minutes), then a '+' character will be added. If Q:1 is seen on a CW spot, then only one skimmer has seen that spot and the callsign *could* be wrong, But if Q is Q:2 and above, then the callsign is much more likely to be correct.
* Dwell - needs describing
* QRGScore - needs describing
* Deviants - needs describing

Template:Main Page pdf

2025-04-16T16:47:04Z

G0TRT: Added a link to Analysing the RBN

<div style="background:#f9f9f9;padding:0px;border:1px solid #aaaaaa;margin-bottom:15px">
<div style="font-size:125%;color:#336699;padding:0.4em;background-color:#eeeeee;border-bottom:1px solid #aaaaaa;vertical-align:top">

*'''Manuals'''

</div>
<div style="background-color:#fff;padding:0.4em 0.4em 0.4em 0.4em;font-size:95%">
==General==
* [https://wiki.dxcluster.org/wiki/Authors_and_Contributors Authors and Contributors]
* [https://wiki.dxcluster.org/wiki/DXSpider_FAQ FAQ]
==Users==
* [https://wiki.dxcluster.org/wiki/DXSpider_User_Manual User Manual]
* [https://wiki.dxcluster.org/wiki/DXSpider_Filtering_Manual Filtering Manual]
* [https://wiki.dxcluster.org/wiki/DXSpider_User_Command_Reference User Command Reference]
==Sysops==
* [https://wiki.dxcluster.org/wiki/DXSpider_Installation_Manual_(New) Installation Manual (New)]
* [https://wiki.dxcluster.org/wiki/DXSpider_Configuration_Manual Configuration Manual (New)]
* [https://wiki.dxcluster.org/wiki/Node_configuration_for_user_access Node Configuration for User Access (New)]
* [https://wiki.dxcluster.org/wiki/DXSpider_Installation_Manual Installation Manual (Legacy)]
* [https://wiki.dxcluster.org/wiki/DXSpider_Administration_Manual Administration Manual (Legacy)]
* [https://wiki.dxcluster.org/wiki/DXSpider_Sysop_Command_Reference Sysop Command Reference]
* [https://wiki.dxcluster.org/wiki/DXSpider_Variables_Reference Variables Reference]
* [https://wiki.dxcluster.org/wiki/DXSpider_Debug_Commands_and_Levels Debug Commands and Levels]
* [https://wiki.dxcluster.org/wiki/DXSpider_Tracing_Debug_Entries Tracing Debug Entries]
* [https://wiki.dxcluster.org/wiki/Analysing_the_RBN Analysing the RBN]
* [https://wiki.dxcluster.org/wiki/DXSpider_PC_Packet_Cluster_Protocol The PC Packet Cluster protocol]
* [https://wiki.dxcluster.org/wiki/DXSpider_Kin's_Helper_Script_Info Kin's Helper Script Info]
* [https://wiki.dxcluster.org/wiki/Useful_Daily_Commands_For_Sysops Useful Daily Commands For Sysops]
* [https://wiki.dxcluster.org/wiki/UPDATE.mojo Update from v1.55 to v1.57 Mojo]
* [https://wiki.dxcluster.org/wiki/Restoring_the_user_DB_(Mojo_branch) Backup/Restore/Transfer the User Database]

The [http://www.dxcluster.org/download/ latest release] of the DXSpider program can be downloaded from http://www.dxcluster.org

</div>
</div>

Analysing the RBN

2025-04-16T16:44:30Z

G0TRT: Page needs completing

==Background==

The Reverse Beacon Network (RBN) is a network of receivers, listening, decoding and providing information on received amateur radio signals.

===Watching RBN spots===

In order to watch data from the RBN, assuming that a connect is already made, ensure that debug is set to progress from the console:

set/deb progress

At the command prompt use the following to watch RBN spots flow:

./watchdbg 'progress' 'RBN: SPOT'

or the following to search for a specific aspect such as the callsign G3MD

./grepdbg 'progress' 'RBN: SPOT' 'G3MD'

===Example data===

15:59:41 (progress) RBN: SPOT key: 'G3MD|101220' = G3MD on 10121.9 by SQ5J @ 1559Z Q:9* route: SK0MMR dwell: 7s QRGScore: 17 Deviants: 1/9 (SQ5J:+0.1)
15:59:41 (progress) RBN: SPOT key: 'VE1VDM/B|281741' = VE1VDM/B on 28174.1 by NU4F @ 1555Z Q:2+ route: SK0MMR dwell: 3m 54s QRGScore: 10 Deviants: 0/2
15:59:41 (progress) RBN: SPOT key: 'VP2VI|248950' = VP2VI on 24895 by NN3RP @ 1559Z Q:9*+ route: SK0MMR dwell: 10s QRGScore: 5 Deviants: 1/5 (W3OA:+0.1)
15:59:42 (progress) RBN: SPOT key: 'DL4HG|70291' = DL4HG on 7029.1 by HB9BXE @ 1559Z Q:9* route: SK0MMR dwell: 9s QRGScore: 39 Deviants: 1/9 (DL0PF:+0.1)
15:59:45 (progress) RBN: SPOT key: 'AO100IAR|140850' = AO100IAR on 14085 by VE3EID @ 1556Z Q:2 route: SK0MMR dwell: 3m 5s QRGScore: 9 Deviants: 0/2

===Decoding the data===

* Q is quality is the number of skimmers that have received the signal Q:3 would mean that the signal has been heard by 3 receivers.
* QRGScore
* Deviants

Analysing the RBN

2025-04-16T16:29:42Z

G0TRT: Added example data

Analysing the RBN

2025-04-16T16:28:35Z

G0TRT: Starting the page

Administration

2025-04-15T15:48:38Z

G0TRT: /* How can I get Spider to restart automatically if it crashes? */ linked to the auto-start page

==Administration==

===How can I get Spider to restart automatically if it crashes?===

This really depends on the flavour of Linux and the system it uses. They're being captured on the [[Auto-start]] page.

===How can I monitor traffic to and from a node or user?===

There are 2 ways to achieve this. You can use the tail command like this ..

tail -f /spider/data/debug/167.dat |grep G0VGS

or in later versions of Spider, there is a command called watchdbg in which case you simply type ..

watchdbg G0VGS

===I see spots coming in my debug log, but none go out to the users===

Please check the time on your PC.

All spots are checked that they are no more than 15 minutes in the future and 60 minutes in the past. If your clock on your client prompt (or console.pl display) is not set to the correct time in GMT (UTC) and is more than one hour out (say on your local (summer) time) then the test will fail and no spots will come out. Neither will they be stored.

If you are connected to the internet, most linux distributions have an implementation of ntpd. The Microsoft Windows 2003, XP, 2000 and NT machine clock can also be set to be synchronized to an NTP source. This can be done in the standard time configuration screen. There is also the simple nettime program for Windows 95/98/ME.

===My neighbouring node cannot use the RCMD command to me, he just keeps getting the "tut tut" message===

Assuming that the permissions are set correctly (perm level 5 required), it could be that the home_node is set incorrectly. You can reset the home_node using the spoof command like this ..

spoof gb7adx set/home gb7adx

Assuming that the node_call you are changing is gb7adx.

===I do not seem to be sending any bulletin mail to my link partners, what is wrong?===

There is a file in /spider/msg called forward.pl.issue. Rename this to forward.pl and edit it to meet your requirements. You will need to issue the command load/forward or restart Spider for the changes to take effect.

===How can I automatically limit the amount of debug logfiles that are stored?===

Use the tmpwatch command. Create a file in /etc/cron.daily/ containing the line ...

/usr/sbin/tmpwatch -f 240 /spider/data/debug

Remember to make it executable! This will limit your debug data down to the last 10 days.

However, modern versions of DXSpider will do this for you, so this is now probably unnecessary.

===I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?===

Almost certainly this is a change in the db format of perl. Follow these few steps to correct the problem.

*stop the cluster (disable any autostart in inittab)

*cd /spider/data

*issue the command: perl user_asc

*restart the cluster

That should solve the problem.

===Since I last updated I seem to be getting duplicate spots appearing===

What has probably happened is that the dupefile has got corrupted in some way. Simply delete the /spider/data/dupefile and restart the cluster. It may take a little time to become fully functional but should solve your problem.

===I have deleted a message but it is still there, why?===

This is now the way messages are handled for deletion in Spider. If you look closely you will see a 'D' following the message number. This message is marked for deletion and will be deleted in 2 days if nothing further is done. Optionally you can use the command delete/expunge to delete it immediately.

===I have updated from CVS and I get all sorts of errors when I restart===

Whenever you update from CVS, a log is displayed. Next to each file that is downloaded there is a letter, e.g.:

? fred.pl
? jim
..
.
..
cvs server: Updating perl
P cluster.pl
C Messages
M Internet.pm
U DXProt.pm
..
.
..

For normal CVS use you should only ever see the letters 'P', 'U' or '?'. The letter 'P' means that the file has changed in CVS and is more recent than the one that is currently on your system. You will also see the letter '?', which means that there is a file that you (or the system) has created that CVS doesn't know about and isn't under its control. These are all normal and good.

Sometimes you will see the letter 'U' next to a file. This means that it is a new file that you don't currently have. This is also OK.

However, if you see the letter 'C' or 'M', that means that CVS thinks that the file has changed locally. For the letter 'C', it has changed sufficiently near to one or more modifications which CVS wants to download to your system. For the 'M', CVS thinks that it is OK to make the change (you may also see some messages about "merging revision 1.xx with 1.yy"). Neither of these things are good. Files that are under the control of CVS must not be changed by sysops. It is the files that have the 'C' next to them that will show the errors that you are complaining about and they will be things like:-

Syntax error near '<<<<' at line 23
Syntax error near '===' at line 40
Syntax error near '>>>' at line 51

You will not necessarily see all of the errors shown but you will get one or more sets of some of them. The cure is simple:

*identify the file that is causing the problem.

*remove the file.

*run the cvs update again.

You will see that file come back (with a letter 'U' next to it). That will be the correct file as CVS thinks it should be. If you still have a problem, then get onto the dxspider-support mailing list.

If all else fails (or you have several conflicts) you can safely remove the entire /spider/perl and /spider/cmd directories and then run the cvs update. They will all be recreated in their pristine condition.

===I have done a CVS update, restarted and it says that "fileX" is missing===

The correct way to run cvs is:-

cd /spider
cvs -z3 update -d

The '-d' is crucial. It makes sure that any new directories, that may contain new code, are created and that new code downloaded. I have absolutely no idea why this is not the default, seeing as CVS (in other circumstances) happily recurses its merry way down a directory tree, but there you are.

WinCVS and other graphical CVS frontends have a checkbox for the update screen called something like "create sub-directories" (it may be hidden in some sub-screen - go look for it if it isn't obvious). Make sure that this box is checked. If you can make this the default setting in the program's setup screen then please do that. It will save you a lot of pulled hair.

===How do enable Internet connectivity for the cluster scripts?===

If you're getting this error: "Sorry, Internet access is not enabled" whilst using some of the show functions then you need to enable connectivity by copying Internet.pm from /spider/perl/ to /spider/local/ where you can edit it. If you are using complex passwords it is worth encapsulating them so that DXSpider interprets them correctly eg

'eCgm&S@u54d4Twr\8/Cezae' rather than eCgm&S@u54d4Twr\8/Cezae

Auto-start

2025-04-15T15:12:39Z

G0TRT: Created page with "It is useful to have the DX Cluster auto-start when the computer starts. The method used is entirely dependent on the flavour of Linux being used. ====Ubuntu - systemd==== Copy the dxspider.service file into the Linux file system. # cp /spider/dxspider.service /etc/systemd/system/ Start the service # systemctl start dxspider.service On some systems it may also need enabling # systemctl enable dxspider.service Become the sysop user # su - sysop Verify the clu..."

It is useful to have the DX Cluster auto-start when the computer starts. The method used is entirely dependent on the flavour of Linux being used.

====Ubuntu - systemd====

Copy the dxspider.service file into the Linux file system.

# cp /spider/dxspider.service /etc/systemd/system/
Start the service
# systemctl start dxspider.service
On some systems it may also need enabling
# systemctl enable dxspider.service

Become the sysop user
# su - sysop

Verify the cluster is running by opening the admin console
$ dx

Ubuntu 24.04

2025-04-15T15:00:20Z

G0TRT: /* Installation */

=== Installing dxspider 'mojo' branch on Ubuntu 24.04 ===
This should cover most Debian based distros, but we do not have confirmation yet. If you have trouble, please, reach out to the DXSpider Support List or the Discord server listed at the bottom right of the main page.

==== Prerequisites ====

A stock install of Ubuntu server edition, install the '''standard version, NOT the light version'''. The default settings are fine and no extra packages are required at install time.

Note: If you choose to try this on a cloud hosting service (i.e. AWS, DigitalOcean) be aware you will need to verify the default Canonical repositories are in use.
sudo add-apt-repository universe
sudo add-apt-repository multiverse
sudo apt update
As part of the standard install you will be asked to create a user account on the system, choose strong passwords.

This is the account that you will use to manage the Ubuntu server and will have sudo privileges. Dxspider does not require sudo access and you will create a separate 'sysop' account for dxspider to use as part of the installation.

Enable ssh as you will require this for administration.

In these notes command executed as root are prefixed with #

Commands executed as the user ‘sysop’ are prefixed with $

At various points during the installation text files will need to be edited at the command line, 'nano' and 'vim' are both choices built into the stock Ubuntu server install. If you do not already have a familiarity with vim, nano is probably the choice you want.

Download the latest Ubuntu server install image from here [https://releases.ubuntu.com Ubuntu]

==== Installation ====

Login as the user you created at install time and become root.

$ sudo su -

Create the sysop user & group , this is the user that the dxcluster will run as.

# adduser sysop

Add your normal login user to the sysop group, this allows the normal login user to interact with the cluster via the ‘dx’ command etc.
*Note however the sysop user must be used for administration involving file system access such as the creation of new connection scripts, git updates etc.

# usermod -a -G sysop <login_user>

Install packages that will be required for dxspider, we are going to go directly to mojo branch. All the packages required are in the apt packaging system so we shall install from there.

# apt install procps git build-essential libtimedate-perl libnet-telnet-perl libdigest-sha-perl libdata-structure-util-perl libmojo-ioloop-readwriteprocess-perl libjson-perl gcc libmath-round-perl libnet-cidr-lite-perl libcurses-perl libdbi-perl cpanminus

You will also need to ensure that you have the Perl library for the database you intend using, e.g. for SQLite:
apt install libdbd-sqlite3-perl

or for MySQL / MariaDB:
apt install libdbd-mysql-perl

We will make some links now, whilst we are still root.

# ln -s /home/sysop/spider /spider
# ln -s /spider/perl/console.pl /usr/local/bin/dx
# ln -s /spider/perl/*dbg /usr/local/bin

Now would also be a very good time to consider one’s firewall requirements, for example:

# ufw allow 7300/tcp
# ufw allow ssh
# ufw enable

We have done everything we need to do for now as the root user, for the rest of the install we will be the user “sysop”

change to the sysop user
# su - sysop

We want to install dxspider, Mojo branch.

$ git clone -b mojo git://scm.dxcluster.org/scm/spider

Change into the newly created spider directory.

$ cd spider

Make our local directories.

$ mkdir local_cmd
$ mkdir local_data
$ mkdir local

Configure DXvars, this is where the parameters for the cluster are defined.

$ cp perl/DXVars.pm.issue local/DXVars.pm

Edit local/DXVars.pm to define the various parameters that are appropriate for your cluster.

$ cp perl/Listeners.pm local/

Edit local/Listeners.pm and follow instructions, generally if you do have a static ipv6 address it’s worth configuring for dual stack these days, however before you will see ipv6 users you will also need to ensure that you have the appropriate AAAA DNS record in place for the v6 address of your dxcluster.

Create a connect script to connect to your peer node(s).

$ cd /spider/connect/
$ cp gb7tlh <peer-node>

Edit this file with your chosen editor so that the telnet address and port are correct for your peer node(s) and set your own node callsign.

We need to build from source the client program

$ cd /spider/src
$ make

You should see this complete with no errors and how have an executable file called client.

Change to the base spider directory
$ cd /spider

Now we need to set up the sysop user for dxpsider, this is based on the configuration in /spider/local/DXVars.pm and you will need to rerun this command if you change details pertaining to the sysop.
$ perl/create_sysop.pl

Run the cluster

$ perl/cluster.pl

Assuming there are no errors, it will start up.

Now it’s time to connect to the node and check that it’s working ok.
Open a second ssh session to your server and become sysop.

$ sudo su - sysop

Issue the ‘dx’ command to access the dxcluster administration console.
$ dx

We need to tell the node the callsign (including any SSID) of it’s peer node(s), this has to be done both ends so you will need to have agreement in place with other node(s) you wish to peer with.

set/spider <peer-node>

Now it’s time to connect and see if things are working.

connect <peer-node>

If all is good you should see spots start arriving.
At this point you may wish to confirm remote telnet access is working also.

Time to tidy up the installation and set up dxspider to start as a service, exit the console
by issuing the ‘bye’ command.
bye

Firstly, as the user sysop we will set up the dxpsider crontab file. This controls things that dxpsider should do on a regular schedule, like check that it is connected to upstream nodes, update databases etc.

$ cd /spider/local_cmd/
now use an editor to create a file called crontab.
$ vim crontab

With the contents below (replacing <peer-node> with the call of the upstream peer node).
This will set up a simple schedule that will check very minute to see if the node is connected to it’s peer, if not connection will be attempted.

# Dxspider crontab file
# m h dm m dw
* * * * * start_connect('<peer-node>') unless connected('<peer-node>')
#

Further help on crontab scheduling can be found here [https://crontab.guru/]

Now we will install the systemd service file for the dxpsider service and enable it.

We must become root, however since the sysop user does not have sudo privileges, we will first have to drop back to our login user.

sysop@ei7mre-2:~$ exit
bminish@ei7mre-2:~$ sudo su -
[sudo] password for bminish:
root@ei7mre-2:~#

====Setting the cluster to auto-start====

Now we will copy the service file to /etc/systemd/system/

# cp /spider/dxspider.service /etc/systemd/system/
And start the service
# systemctl start dxspider.service
On some systems it may also need enabling
# systemctl enable dxspider.service

Become the sysop user
# su - sysop

Verify the cluster is running by opening the admin console
$ dx

Administration

2025-04-11T11:30:33Z

G0TRT: /* How do enable Internet connectivity for the cluster scripts? */

==Administration==

===How can I get Spider to restart automatically if it crashes?===

Put this line into /etc/inittab ..

DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop > /dev/tty7

Run telinit q as root. Spider will restart so be aware. However, any time you reboot, cluster.pl will start in tty7 and if it crashes, it should restart ok.

===How can I monitor traffic to and from a node or user?===

There are 2 ways to achieve this. You can use the tail command like this ..

tail -f /spider/data/debug/167.dat |grep G0VGS

or in later versions of Spider, there is a command called watchdbg in which case you simply type ..

watchdbg G0VGS

===I see spots coming in my debug log, but none go out to the users===

Please check the time on your PC.

All spots are checked that they are no more than 15 minutes in the future and 60 minutes in the past. If your clock on your client prompt (or console.pl display) is not set to the correct time in GMT (UTC) and is more than one hour out (say on your local (summer) time) then the test will fail and no spots will come out. Neither will they be stored.

If you are connected to the internet, most linux distributions have an implementation of ntpd. The Microsoft Windows 2003, XP, 2000 and NT machine clock can also be set to be synchronized to an NTP source. This can be done in the standard time configuration screen. There is also the simple nettime program for Windows 95/98/ME.

===My neighbouring node cannot use the RCMD command to me, he just keeps getting the "tut tut" message===

Assuming that the permissions are set correctly (perm level 5 required), it could be that the home_node is set incorrectly. You can reset the home_node using the spoof command like this ..

spoof gb7adx set/home gb7adx

Assuming that the node_call you are changing is gb7adx.

===I do not seem to be sending any bulletin mail to my link partners, what is wrong?===

There is a file in /spider/msg called forward.pl.issue. Rename this to forward.pl and edit it to meet your requirements. You will need to issue the command load/forward or restart Spider for the changes to take effect.

===How can I automatically limit the amount of debug logfiles that are stored?===

Use the tmpwatch command. Create a file in /etc/cron.daily/ containing the line ...

/usr/sbin/tmpwatch -f 240 /spider/data/debug

Remember to make it executable! This will limit your debug data down to the last 10 days.

However, modern versions of DXSpider will do this for you, so this is now probably unnecessary.

===I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?===

Almost certainly this is a change in the db format of perl. Follow these few steps to correct the problem.

*stop the cluster (disable any autostart in inittab)

*cd /spider/data

*issue the command: perl user_asc

*restart the cluster

That should solve the problem.

===Since I last updated I seem to be getting duplicate spots appearing===

What has probably happened is that the dupefile has got corrupted in some way. Simply delete the /spider/data/dupefile and restart the cluster. It may take a little time to become fully functional but should solve your problem.

===I have deleted a message but it is still there, why?===

This is now the way messages are handled for deletion in Spider. If you look closely you will see a 'D' following the message number. This message is marked for deletion and will be deleted in 2 days if nothing further is done. Optionally you can use the command delete/expunge to delete it immediately.

===I have updated from CVS and I get all sorts of errors when I restart===

Whenever you update from CVS, a log is displayed. Next to each file that is downloaded there is a letter, e.g.:

? fred.pl
? jim
..
.
..
cvs server: Updating perl
P cluster.pl
C Messages
M Internet.pm
U DXProt.pm
..
.
..

For normal CVS use you should only ever see the letters 'P', 'U' or '?'. The letter 'P' means that the file has changed in CVS and is more recent than the one that is currently on your system. You will also see the letter '?', which means that there is a file that you (or the system) has created that CVS doesn't know about and isn't under its control. These are all normal and good.

Sometimes you will see the letter 'U' next to a file. This means that it is a new file that you don't currently have. This is also OK.

However, if you see the letter 'C' or 'M', that means that CVS thinks that the file has changed locally. For the letter 'C', it has changed sufficiently near to one or more modifications which CVS wants to download to your system. For the 'M', CVS thinks that it is OK to make the change (you may also see some messages about "merging revision 1.xx with 1.yy"). Neither of these things are good. Files that are under the control of CVS must not be changed by sysops. It is the files that have the 'C' next to them that will show the errors that you are complaining about and they will be things like:-

Syntax error near '<<<<' at line 23
Syntax error near '===' at line 40
Syntax error near '>>>' at line 51

You will not necessarily see all of the errors shown but you will get one or more sets of some of them. The cure is simple:

*identify the file that is causing the problem.

*remove the file.

*run the cvs update again.

You will see that file come back (with a letter 'U' next to it). That will be the correct file as CVS thinks it should be. If you still have a problem, then get onto the dxspider-support mailing list.

If all else fails (or you have several conflicts) you can safely remove the entire /spider/perl and /spider/cmd directories and then run the cvs update. They will all be recreated in their pristine condition.

===I have done a CVS update, restarted and it says that "fileX" is missing===

The correct way to run cvs is:-

cd /spider
cvs -z3 update -d

The '-d' is crucial. It makes sure that any new directories, that may contain new code, are created and that new code downloaded. I have absolutely no idea why this is not the default, seeing as CVS (in other circumstances) happily recurses its merry way down a directory tree, but there you are.

WinCVS and other graphical CVS frontends have a checkbox for the update screen called something like "create sub-directories" (it may be hidden in some sub-screen - go look for it if it isn't obvious). Make sure that this box is checked. If you can make this the default setting in the program's setup screen then please do that. It will save you a lot of pulled hair.

===How do enable Internet connectivity for the cluster scripts?===

If you're getting this error: "Sorry, Internet access is not enabled" whilst using some of the show functions then you need to enable connectivity by copying Internet.pm from /spider/perl/ to /spider/local/ where you can edit it. If you are using complex passwords it is worth encapsulating them so that DXSpider interprets them correctly eg

'eCgm&S@u54d4Twr\8/Cezae' rather than eCgm&S@u54d4Twr\8/Cezae

Administration

2025-04-11T11:30:13Z

G0TRT: /* How do enable Internet connectivity for the cluster scripts? */

Information, files and useful programs

2025-04-11T11:23:59Z

G0TRT: /* The QRZ callbook */

==Information, files and useful programs==

===MOTD===

One of the more important things a cluster sysop needs to do is to get information to his users. The simplest way to do this is to have a banner that is sent to the user on login. This is know as a "message of the day" or "motd". To set this up, simply create a file in /spider/data called motd and edit it to say whatever you want. It is purely a text file and will be sent automatically to anyone logging in to the cluster.

===MOTD_NOR===

This message of the day file lives in the same directory as the standard motd file but is only sent to non-registered users. Once registered they will receive the same message as any other user.

===Downtime message===

If for any reason the cluster is down, maybe for upgrade or maintenance but the machine is still running, a message can be sent to the user advising them of the fact. This message lives in the /spider/data directory and is called "offline". Simply create the file and edit it to say whatever you wish. This file will be sent to a user attempting to log into the cluster when DXSpider is not actually running.

===Other text messages===

You can set other text messages to be read by the user if they input the file name. This could be for news items or maybe information for new users. To set this up, make a directory under /spider called packclus. Under this directory you can create files called news or newuser for example. In fact you can create files with any names you like. These can be listed by the user with the command ....

show/files

They can be read by the user by typing the command ....

type news

If the file they want to read is called news. You could also set an alias for this in the Alias file to allow them just to type news.

You can also store other information in this directory, either directly or nested under directories. One use for this would be to store DX bulletins such as the OPDX bulletins. These can be listed and read by the user. To keep things tidy, make a directory under /spider/packclus called bulletin. Now copy any OPDX or similar bulletins into it. These can be listed by the user in the same way as above using the �[4mshow/files�[24m command with an extension for the bulletin directory you have just created, like this ....

show/files bulletin

An example would look like this ....

sh/files
bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z

You can see that in the files area (basically the packclus directory) there is a file called news and a directory called bulletin. You can also see that dates they were created. In the case of the file news, you can also see the time it was last modified, a good clue as to whether the file has been updated since you last read it. To read the file called news you would simply issue the command ....

type news

To look what is in the bulletin directory you issue the command ....

show/files bulletin
opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
Press Enter to continue, A to abort (16 lines) >

You can now read any file in this directory using the type command, like this ....

type bulletin/opdx391
Ohio/Penn DX Bulletin No. 391
The Ohio/Penn Dx PacketCluster
DX Bulletin No. 391
BID: $OPDX.391
January 11, 1999
Editor Tedd Mirgliotta, KB8NW
Provided by BARF-80 BBS Cleveland, Ohio
Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
& The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
Press Enter to continue, A to abort (508 lines) >

The page length will of course depend on what you have it set to!

===The Aliases file===

You will find a file in /spider/cmd/ called Aliases. This is the file that controls what a user gets when issuing a command. It is also possible to create your own aliases for databases and files you create locally.

You should not alter the original file in /spider/cmd/ but create a new file with the same name in /spider/local_cmd. This means that any new Aliases files that is downloaded will not overwrite your self created Aliases and also that you do not override any new Aliases with your copy in /spider/local_cmd/. You must remember that any files you store in /spider/local/ or /spider/local_cmd override the originals if the same lines are used in both files.

The best way of dealing with all this then is to only put your own locally created Aliases in the copy in /spider/local_cmd. The example below is currently in use at GB7MBC.

#
# Local Aliases File
#
package CmdAlias;

%alias = (
'n' => [
'^news$', 'type news', 'type',
],
's' => [
'^sh\w*/buck$', 'show/qrz', 'show',
'^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
'^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
'^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
'^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
],
)

Each alphabetical section should be preceded by the initial letter and the section should be wrapped in square brackets as you can see. The syntax is straightforward. The first section on each line is the new command that will be allowed once the alias is included. The second section is the command it is replacing and the last section is the actual command that is being used.

The eagle-eyed amongst you will have noticed that in the first section, the new alias command has a '^' at the start and a '$' at the end. Basically these force a perfect match on the alias. The '^' says match the beginning exactly and the with similar commands.

I have 3 different types of alias in this file. At the top is an alias for 'news'. This is a file I have created in the /spider/packclus/ directory where I can inform users of new developments or points of interest. In it's initial form a user would have to use the command type news. The alias allows them to simply type news to get the info. Second is an alias for the show/qrz command so that those users used to the original show/buck command in AK1A will not get an error, and the rest of the lines are for locally created databases so that a user can type show/hftest instead of having to use the command dbshow hftest which is not as intuitive.

This file is just an example and you should edit it to your own requirements. Once created, simply issue the command load/alias at the cluster prompt as the sysop user and the aliases should be available.

===Console.pl===

In later versions of Spider a simple console program is provided for the sysop. This has a type ahead buffer with line editing facilities and colour for spots, announces etc. To use this program, simply use console.pl instead of client.

To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the file with your favourite editor.

===Updating kepler data===

Spider has a powerful and flexible show/satellite command. In order for this to be accurate, the kepler data has to be updated regularly. In general, this data is available as an email or via cluster mail. Updating it is simple. First you need to export the mail message as a file. You do this with the export command from the cluster prompt as the sysop. For example ...

export 5467 /spider/perl/keps.in

would export message number 5467 as a file called keps.in in the /spider/perl directory.

Now login to a VT as sysop and cd /spider/perl. There is a command in the perl directory called �[4mconvkeps.pl�[24m. All we need to do now is convert the file like so ...

./convkeps.pl keps.in

Now go back to the cluster and issue the command ...

load/keps

That is it! the kepler data has been updated.

===The QRZ callbook===

The command sh/qrz will only work if you have a paid subscription to the XML logbook service. First you need to get a user ID and password from qrz.com. Simply go to the site and create one. Second you need to upgrade your account by paying for the XML logbook subscription. If you haven't previously, you need to copy the file /spider/perl/Internet.pm to /spider/local and alter it to match your user ID and password. You also at this point need to set $allow=1 to complete the setup. It's worth noting that using ‘::’ rather than ‘0.0.0.0’ allows IPV6 as well as IPV4.

===Connecting logging programs===

There appear to be very few logging programs out there that support telnet especially the popular ones like LogEQF, Turbolog etc. This can make it difficult to connect to your own cluster! The way to do it is to make the logging program think it has a TNC attached to a com port on the logging PC and 'push' a linux login out to it. This is achieved very simply by the use of agetty.

All that is required is to add a line in /etc/inittab to have the client ready for a connection on the com port of your choice. Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1 for com2 etc.

c4:2345:respawn:/sbin/agetty -L 9600 ttyS1

Add this after the standard runlevel lines in /etc/inittab. The above line works on ttyS1 (com2). Now as root, issue the command telinit q and it should be ready for connection. All that is required is a 3 wire serial lead (tx, rx and signal ground). Tell you logging program to use 8n1 at 9600 baud and you should see a Linux login prompt. Login as normal and then telnet from there to the cluster.

Administration

2025-04-11T11:11:29Z

G0TRT: Added Intenet connectivity

Node configuration for user access

2025-04-11T09:50:53Z

G0TRT:

===User Registration===
----
There are two types of user in a DXSpider node, a registered user and an unregistered user.
By default, all users belong to the unregistered category.

===Node in UNREGISTERED Mode===
----
This is the default way of working, but not necessarily the best.

The global variable that sets the node type is '''$main::reqreg'''
and its default value is '''0'''.
<pre>
set/var $main::reqreg = 0
</pre>

In this mode the sysop doesn't have to register users, but if they are registered, then it will simply be a database entry.
Both types of user will have the same capabilities to send and receive SPOTS, ANN, etc

===Node in REGISTRATION Mode===
----
To activate registration, the global variable '''$main::reqreg''' must be set to '''1'''.
The way to change it is

<pre>
set/var $main::reqreg = 1
</pre>

When this mode is activated, only users that the sysop has registered will be able to send and receive SPOTS, ANN, etc. Unregistered users will only be able to receive information.

The way to register/unregister a user is as follows:
<pre>
set/register <call>
unset/register <call>
</pre>

You can check which users we have registered using

<pre>
sh/register <call>
</pre>

A specific login banner for registered users can be shown. The file containing it is the following

<pre>
/spider/_local_data/motd
</pre>

When an unregistered user starts the login process, they can be sent a different file that can be configured to say that they are not registered and how to register should they wish to do so. This file is ...

<pre>
/spider/local_data/motd_nor
</pre>

===Password Usage===
----
By default, a user does not get prompted for a password at login. For additional security, a user can request a password be set for them. They simply need to request a password that they provide to the sysop.

It should be noted that this only works on the node they regularly use. Their password is not propagated across the network for security reasons.

For a user to be assigned a password, the sysop needs to use the command ...

<pre>
set/password <call> <string>
</pre>

and the user can change his password with the command

<pre>
set/password
Enter old password:
Enter new password:
Re-enter new password:
Password changed
</pre>

===Node in NO PASSWORD Mode===
----
The global variable '''$main::passwdreq''' is set to '''0''' by default. This does not mean that they cannot have a password set, only that users are not forced to have a password.

To see the value of the variable use ...

<pre>
sh/var $main::passwdreq
</pre>

===Node in PASSWORD Mode===
----
If we set the '''$main::passwdreq''' variable to '''1''', we will force any user logging in to the node to use a password as well as their callsign, otherwise they will not be able to access the node.

The node will not establish the session if there is no positive authentication.

To set this mode of operation:

<pre>
set/var $main::passwdreq = 1
</pre>

===How To protect your cluster node (Recommended configuration)===

----
One way to control the correct use of our node, is to use the combination of registration and password as follows.

We enable the registration for all the users

<pre>
set/var $main::reqreg = 1
</pre>

The beauty of this is that people who try to login with callsigns like ID1OT or even using random callsigns cannot post spots or announcements from the node.

Unless the cluster node is a small club node or similar, it is probably a good idea not to force people to have a password. It may put some people off and it will be a LOT of work for the sysop. Most users will be protected by registration

<pre>
set/var $main::passwdreq = 0
</pre>

Of course, a user may wish to have a password set to increase their security on the node, meaning that unless someone also knows the password, their call cannot be used by someone else unless they know the password.

<pre>
set/register <call>
set/password <call> <string>
</pre>

It is <b>strongly</b> suggested that sysops enable registration to try and combat the increasing misuse on the cluster network

===Make Changes Permanent===
----
Although sysops can enable or disable these variables at any time from the console, this will only be enabled until the node is restarted. if we want to keep them during the startup of the node, we must edit the file ...

<pre>
/spider/scripts/startup
</pre>

and include the following lines
<pre>
set/var $main::reqreg = 1
set/var $main::passwdreq = 0
</pre>

The changes to this file will not take effect until there is a reboot, so we can activate it manually the first time from the console by typing
<pre>
set/var $main::reqreg = 1
set/var $main::passwdreq = 0
</pre>

Node configuration for user access

2025-04-11T09:50:33Z

G0TRT: Removed bolding from headings

===User Registration===
----
There are two types of user in a DXSpider node, a registered user and an unregistered user.
By default, all users belong to the unregistered category.

===Node in UNREGISTERED Mode===
----
This is the default way of working, but not necessarily the best.

The global variable that sets the node type is '''$main::reqreg'''
and its default value is '''0'''.
<pre>
set/var $main::reqreg = 0
</pre>

In this mode the sysop doesn't have to register users, but if they are registered, then it will simply be a database entry.
Both types of user will have the same capabilities to send and receive SPOTS, ANN, etc

===Node in REGISTRATION Mode===
----
To activate registration, the global variable '''$main::reqreg''' must be set to '''1'''.
The way to change it is

<pre>
set/var $main::reqreg = 1
</pre>

When this mode is activated, only users that the sysop has registered will be able to send and receive SPOTS, ANN, etc. Unregistered users will only be able to receive information.

The way to register/unregister a user is as follows:
<pre>
set/register <call>
unset/register <call>
</pre>

You can check which users we have registered using

<pre>
sh/register <call>
</pre>

A specific login banner for registered users can be shown. The file containing it is the following

<pre>
/spider/_local_data/motd
</pre>

When an unregistered user starts the login process, they can be sent a different file that can be configured to say that they are not registered and how to register should they wish to do so. This file is ...

<pre>
/spider/local_data/motd_nor
</pre>

===Password Usage===
----
By default, a user does not get prompted for a password at login. For additional security, a user can request a password be set for them. They simply need to request a password that they provide to the sysop.

It should be noted that this only works on the node they regularly use. Their password is not propagated across the network for security reasons.

For a user to be assigned a password, the sysop needs to use the command ...

<pre>
set/password <call> <string>
</pre>

and the user can change his password with the command

<pre>
set/password
Enter old password:
Enter new password:
Re-enter new password:
Password changed
</pre>

===Node in NO PASSWORD Mode===
----
The global variable '''$main::passwdreq''' is set to '''0''' by default. This does not mean that they cannot have a password set, only that users are not forced to have a password.

To see the value of the variable use ...

<pre>
sh/var $main::passwdreq
</pre>

===Node in PASSWORD Mode===
----
If we set the '''$main::passwdreq''' variable to '''1''', we will force any user logging in to the node to use a password as well as their callsign, otherwise they will not be able to access the node.

The node will not establish the session if there is no positive authentication.

To set this mode of operation:

<pre>
set/var $main::passwdreq = 1
</pre>

==='''How To protect your cluster node (Recommended configuration)'''===

----
One way to control the correct use of our node, is to use the combination of registration and password as follows.

We enable the registration for all the users

<pre>
set/var $main::reqreg = 1
</pre>

The beauty of this is that people who try to login with callsigns like ID1OT or even using random callsigns cannot post spots or announcements from the node.

Unless the cluster node is a small club node or similar, it is probably a good idea not to force people to have a password. It may put some people off and it will be a LOT of work for the sysop. Most users will be protected by registration

<pre>
set/var $main::passwdreq = 0
</pre>

Of course, a user may wish to have a password set to increase their security on the node, meaning that unless someone also knows the password, their call cannot be used by someone else unless they know the password.

<pre>
set/register <call>
set/password <call> <string>
</pre>

It is <b>strongly</b> suggested that sysops enable registration to try and combat the increasing misuse on the cluster network

===Make Changes Permanent===
----
Although sysops can enable or disable these variables at any time from the console, this will only be enabled until the node is restarted. if we want to keep them during the startup of the node, we must edit the file ...

<pre>
/spider/scripts/startup
</pre>

and include the following lines
<pre>
set/var $main::reqreg = 1
set/var $main::passwdreq = 0
</pre>

The changes to this file will not take effect until there is a reboot, so we can activate it manually the first time from the console by typing
<pre>
set/var $main::reqreg = 1
set/var $main::passwdreq = 0
</pre>

DXSpider Configuration Manual

2025-04-11T08:53:34Z

G0TRT: Added a link to Setting up scripts - startup, and default_user

===Configuration Guides===
* [https://wiki.dxcluster.org/wiki/Configure_Node_with_more_than_one_local_IP_(Mojo_branch) Configure Node with more than one Local IP (Mojo branch)]
* [https://wiki.dxcluster.org/wiki/Configure_node_with_Dynamic_IP_(Mojo_branch) Configure Node with Dynamic IP (Mojo branch)]
* [https://wiki.dxcluster.org/wiki/Create_a_secure_connection_between_nodes Create a Secure Connection Between Nodes]
* [https://wiki.dxcluster.org/wiki/How_to_connect_DXSpider_to_RBN How to Connect DXSpider to RBN]
* [https://wiki.dxcluster.org/wiki/Scripts Setting up scripts - startup, and default_user]

Scripts

2025-04-11T08:49:50Z

G0TRT: /* user_default */

==Scripts==

The directory /spider/scripts is a place for scripts to be placed. The main script in this directory is called startup that can be used to make changes to the cluster from the default settings on startup. This script is executed immediately after all initialisation of the node is done but before any connections are possible. The other two files are startup.issue, which is a minimal file to use to build a startup and user_default.issue

===startup===

#
#
# lines starting with a # are ignored
#
# set maximum no of spots allowed to 100
set/var $Spot::maxspots = 100
#
# reject node adverts
rej/ann node_default input info telnet,cluster,7000,7300,7373,8000,8888,9000,17300
#
# reject D0 and D1 prefixes which aren't on the ITU list
rej/spot node_default input 2 call d0,d1
rej/spot node_default input 3 by d0,d1
#
# set outbound spider connections with nodes you've paired with
set/spider g1abc-2
set/spider gb7abc-1
#
# make instant connections to nodes
connect g1abc-2
connect gb7abc-1
#
# make people register before they can send spots
# 1 is on, 0 is off
set/var $main::reqreg = 1
#
# make people use a password to login
# 1 is on, 0 is off
set/var $main::passwdreq = 0
#
# set the node's external dynamic IP
set/external_ip
#
# set the node and logging pc IPv4s
# gather ip address from your network and add them at the end using ,'192.168.1.144' for example
set/var @main::localhost_names ('127.0.0.1', '::1', '192.168.1.123','192.168.1.134')
#
#EOF

===user_default===

The user_default.issue file, when copied to user_default or a callsign, is used to deliver initial information to a user. The file below will show the relevant information at login:

#
# standard user default script
#
blank +
sh/dx 5
blank -
sh/u
blank -
sh/wwv 1
blank -
sh/wcy 1
blank +
#
#EOF

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1814.0 DL3RBF/P 11-Apr-2025 0839Z SOTA activation DM/RP-001 <ON6ZQ>
7190.0 EA2CCG/P 11-Apr-2025 0839Z POTA ES-0261 ES-0921 <EA7KOY>
14042.0 F5NLX/P 11-Apr-2025 0839Z FFF 1027 POTA FR-3758 WCA F-07<F5MGS>
18104.0 RC0AT 11-Apr-2025 0839Z www.TNXQSO.com <R1NA>
7048.2 VA3JPX 11-Apr-2025 0838Z <KA2G>
-------------------------------------------------------------------------------
Callsigns connected to G0TRT-9
G1ABC G0TRT G3XVL WI3W G0FOZ
-------------------------------------------------------------------------------
Date Hour SFI A K Forecast Logger
11-Apr-2025 06 153 17 3 No Storms -> No Storms <W0MU>
-------------------------------------------------------------------------------
Date Hour SFI A K Exp.K R SA GMF Aurora Logger
11-Apr-2025 08 153 22 3 3 112 eru act no <DK0WCY>
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Nodes: 6/380 Users [Loc/Clr]: 5/4725 Max: 4/4725 - Uptime: 9h 59m 25s

Scripts

2025-04-11T08:49:24Z

G0TRT: /* user_default */

Scripts

2025-04-11T08:49:05Z

G0TRT: /* startup */

Scripts

2025-04-11T08:48:20Z

G0TRT:

DXSpider Configuration Manual

2025-04-11T07:46:36Z

G0TRT: Undo revision 391 by G0TRT (talk)

DXSpider Configuration Manual

2025-04-11T07:44:35Z

G0TRT: Added a link to a new Startup script example page

DXSpider Kin's Helper Script Info

2025-04-10T09:17:52Z

G0TRT: Added a link to the GitHub repo

The following are resources to help with Kin EA3CV's scripts on[https://github.com/EA3CV/dxspider%20info GitHub].

* [https://wiki.dxcluster.org/wiki/Setting_up_the_EA3CV_contributions_repository Setting up the EA3CV contributions repository]
* [https://wiki.dxcluster.org/wiki/Updating_Public_IP_and/or_Local_IPs_(set/update_ip) Updating Public IP and/or/Local IPs]
* [https://wiki.dxcluster.org/wiki/List_of_nodes_for_mobile_use List of nodes for mobile use (mnodes)]
* [https://wiki.dxcluster.org/wiki/List_of_users_for_mobile_use List of users for mobile use (musers)]
* [https://wiki.dxcluster.org/wiki/Node_configuration_for_user_access Node configuration for user access]
* [https://wiki.dxcluster.org/wiki/Configure_node_with_Dynamic_IP_(Mojo_branch) Configure node with Dynamic IP]
* [https://wiki.dxcluster.org/wiki/Configure_Node_with_more_than_one_local_IP_(Mojo_branch) Configure Node with more than one local IP]
* [https://wiki.dxcluster.org/wiki/Create_a_secure_connection_between_nodes Create a secure connection between nodes]
* [https://wiki.dxcluster.org/wiki/DXSpider_MOJO_Version_Update_Script DXSpider MOJO Version Update Script]
* [https://wiki.dxcluster.org/wiki/Sending_messages_to_the_sysop_via_Telegram Sending messages to the sysop via Telegram ]
* [https://wiki.dxcluster.org/wiki/Node_Backup_and_Update_with_check_build Node Backup and Update with check_build ]

Useful Daily Commands For Sysops

2025-04-09T20:55:27Z

G0TRT: Added set/var @main::localhost_names

There are many commands! Some are more useful than others, some are used more frequently that others, some are used at the command prompt, some are used in the console. Here are some of those useful commands that sysops might use on most days, and some of those search strings that help you pluck information from the data files or live streams.

===Linux prompt===

* ./watchdbg 'PC92\^VE7CCD-1' - looking for troubling data out of this node. Note: the ^ needs to be escaped with \
* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.
* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.
* sudo service dxspider restart
grepdbg can also be used instead of watchdbg. For more information on watchdbg and grepdbg see the "[[DXSpider_Tracing_Debug_Entries|Tracing Debug Entries]]" page.

===Console commands===

* sh/external_ip - just checking to see if your ip address changed since your last visit.
* sh/ver - did your node update last night? This will show you what version of dxspider you're running.
* sh/node - are all of your node links up?
* sh/user - all the users.
* directory - any new mail on your node?
* links - just who is connected, and what about them?
* set/register G0AYD - G0AYD sent you a message that he wants to be able to use your node for sending spots.
* stat/user <callsign> - everything you want to know about <callsign>
* sh/hf - a table of spot quantities, per day, per band, for the last month.
* set/var @main::localhost_names ('127.0.0.1', '::1', '192.168.1.127','192.168.1.154','192.168.1.110') - sets all of the IP addresses in your LAN
* sh/var @main::localhost_names - all of your IP addresses.
* mnodes - orderly listing of connected nodes (not included in DXSpider unless Kin's script is installed).
* musers - about all those connected users (not included in DXSpider unless Kin's script is installed).
* who - a list of the connected nodes and users, with some useful info about them.
* rcmd g6nhu-2 sh/ver - did G6NHU update his node?
* sh/debug - did I leave debug running? Is that why my disk is full!

Useful Daily Commands For Sysops

2025-04-08T05:26:17Z

G0TRT: Link updated

There are many commands! Some are more useful than others, some are used more frequently that others, some are used at the command prompt, some are used in the console. Here are some of those useful commands that sysops might use on most days, and some of those search strings that help you pluck information from the data files or live streams.

===Linux prompt===

* ./watchdbg 'PC92\^VE7CCD-1' - looking for troubling data out of this node. Note: the ^ needs to be escaped with \
* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.
* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.
* sudo service dxspider restart
grepdbg can also be used instead of watchdbg. For more information on watchdbg and grepdbg see the "[[DXSpider_Tracing_Debug_Entries|Tracing Debug Entries]]" page.

===Console commands===

* sh/external_ip - just checking to see if your ip address changed since your last visit.
* sh/ver - did your node update last night? This will show you what version of dxspider you're running.
* sh/node - are all of your node links up?
* sh/user - all the users.
* directory - any new mail on your node?
* links - just who is connected, and what about them?
* set/register G0AYD - G0AYD sent you a message that he wants to be able to use your node for sending spots.
* stat/user <callsign> - everything you want to know about <callsign>
* sh/hf - a table of spot quantities, per day, per band, for the last month.
* sh/var @main::localhost_names - all of your IP addresses.
* mnodes - orderly listing of connected nodes (not included in DXSpider unless Kin's script is installed).
* musers - about all those connected users (not included in DXSpider unless Kin's script is installed).
* who - a list of the connected nodes and users, with some useful info about them.
* rcmd g6nhu-2 sh/ver - did G6NHU update his node?
* sh/debug - did I leave debug running? Is that why my disk is full!

Useful Daily Commands For Sysops

2025-04-07T21:41:11Z

G0TRT:

Useful Daily Commands For Sysops

2025-04-07T21:35:00Z

G0TRT: Initial set

Template:Main Page pdf

2025-04-07T21:07:17Z

G0TRT: Added Useful Daily Commands For Sysops

<div style="background:#f9f9f9;padding:0px;border:1px solid #aaaaaa;margin-bottom:15px">
<div style="font-size:125%;color:#336699;padding:0.4em;background-color:#eeeeee;border-bottom:1px solid #aaaaaa;vertical-align:top">

*'''Manuals'''

</div>
<div style="background-color:#fff;padding:0.4em 0.4em 0.4em 0.4em;font-size:95%">
==General==
* [https://wiki.dxcluster.org/wiki/Authors_and_Contributors Authors and Contributors]
* [https://wiki.dxcluster.org/wiki/DXSpider_FAQ FAQ]
==Users==
* [https://wiki.dxcluster.org/wiki/DXSpider_User_Manual User Manual]
* [https://wiki.dxcluster.org/wiki/DXSpider_Filtering_Manual Filtering Manual]
* [https://wiki.dxcluster.org/wiki/DXSpider_User_Command_Reference User Command Reference]
==Sysops==
* [https://wiki.dxcluster.org/wiki/DXSpider_Installation_Manual_(New) Installation Manual (New)]
* [https://wiki.dxcluster.org/wiki/DXSpider_Configuration_Manual Configuration Manual (New)]
* [https://wiki.dxcluster.org/wiki/Node_configuration_for_user_access Node Configuration for User Access (New)]
* [https://wiki.dxcluster.org/wiki/DXSpider_Installation_Manual Installation Manual (Legacy)]
* [https://wiki.dxcluster.org/wiki/DXSpider_Administration_Manual Administration Manual (Legacy)]
* [https://wiki.dxcluster.org/wiki/DXSpider_Sysop_Command_Reference Sysop Command Reference]
* [https://wiki.dxcluster.org/wiki/DXSpider_Variables_Reference Variables Reference]
* [https://wiki.dxcluster.org/wiki/DXSpider_Debug_Commands_and_Levels Debug Commands and Levels]
* [https://wiki.dxcluster.org/wiki/DXSpider_Tracing_Debug_Entries Tracing Debug Entries]
* [https://wiki.dxcluster.org/wiki/DXSpider_PC_Packet_Cluster_Protocol The PC Packet Cluster protocol]
* [https://wiki.dxcluster.org/wiki/DXSpider_Kin's_Helper_Script_Info Kin's Helper Script Info]
* [https://wiki.dxcluster.org/wiki/Useful_Daily_Commands_For_Sysops Useful Daily Commands For Sysops]

The [http://www.dxcluster.org/download/ latest release] of the DXSpider program can be downloaded from http://www.dxcluster.org

</div>
</div>

Web based statistics

2025-04-05T17:50:18Z

G0TRT: Complete scrub based on Mike G3YPP's notes

==Web based statistics==

===Generic installation===

The Multi Router Traffic Grapher ([https://oss.oetiker.ch/mrtg/ MRTG]) uses network traffic to provide a graphical representation of cluster traffic. An example can be seen with the [https://dxc.mx0nca.uk/mrtg/stats.html node statistics for MX0NCA]

Setting up a web environment such as Apache2 is outside the scope of this page, and whilst MRTG can be downloaded from its [https://oss.oetiker.ch/mrtg/download.en.html website], it can generally be installed as a Linux package. Under Debian the package is called mrtg, installing it this way will ensure that all dependencies are installed. Using the root account at the Linux prompt:

sudo apt-get update
sudo apt-get -y install mrtg

As sysop, copy the image files from MRTG (in /usr/share/mrtg) to your ../spider/html/mrtg. MRTG can make many graphs, and it's possible to select which you don't and don't want, but initially it's worth getting them all. At the console run the command:

mrtg all

Then at the Linux command prompt, as sysop, in ../spider/html/mrtg run the command below putting your node callsign in place of <node-name>

indexmaker --output stats.html --columns=1 --title "Node statistics for <node-name>" ../../mrtg/mrtg.cfg

Your web server needs to know where the files are to publish, using the link below is one approach. As the sysop, in /home/sysop/ run the following command

sudo ln -s /spider/html/mrtg /var/www/<domain name>/public_html

Your browser should now see the graphs at http(s)://<domain-name>/mrtg/stats.html

To get refreshed graphs every 5 minutes, add the following line into your dxspider crontab:-

# Update stats for mrtg on website
00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')

This will update the site every 5 minutes.

DXSpider Tracing Debug Entries

2025-04-05T08:41:14Z

G0TRT:

==General Information==

DXspider has the ability to log information at various levels, and those levels are set using the [[DXSpider Sysop Command Reference#DEBUG|debug]] tool in conjunction with the [https://wiki.dxcluster.org/wiki/DXSpider_Debug_Commands_and_Levels| debug levels]. Whilst this information is capture in data files in ../spider/local_data/debug/ it can also be seen in realtime from the command line prompt. Once the debug level is set the watchdbg tool can be used from ../spider/perl/ to watch the cluster's full data stream. This can be a very busy stream but it can be filtered for easier scrutiny.

===Filtering traces===

To trace incoming messages the I is used, and for outbound the D is used:

'<- I' or ' I '

'<- D' or ' D '

====Trace examples====

To watch all outbound spots from this node.
./watchdbg ' D ' 'PC[16]1'
or just
./watchdbg '\-> D'

====Saving to a file====

The debug files will save these traces, and those files can then be searched. But it is possible to save the traces to a specific file by using pipe | to push them to a file.
./watchdbg ' D ' 'PC[16]1' | grep <thing to search for> | trace.txt

DXSpider Tracing Debug Entries

2025-04-05T08:35:44Z

G0TRT: /* Filtering traces */

==General Information==

DXspider has the ability to log information at various levels, and those levels are set using the [[DXSpider Sysop Command Reference#DEBUG|debug]] tool in conjunction with the [https://wiki.dxcluster.org/wiki/DXSpider_Debug_Commands_and_Levels| debug levels]. Whilst this information is capture in data files in ../spider/local_data/debug/ it can also be seen in realtime from the command line prompt. Once the debug level is set the watchdbg tool can be used from ../spider/perl/ to watch the cluster's full data stream. This can be a very busy stream but it can be filtered for easier scrutiny.

===Filtering traces===

To trace incoming messages the I is used, and for outbound the D is used:

'<- I' or ' I '

'<- D' or ' D '

====Examples====

To watch all outbound spots from this node.
./watchdbg ' D ' 'PC[16]1'
or just
./watchdbg '\-> D'

DXSpider Tracing Debug Entries

2025-04-05T08:24:41Z

G0TRT: /* General Information */

DXSpider Tracing Debug Entries

2025-04-05T08:21:33Z

G0TRT:

DXSpider Tracing Debug Entries

2025-04-05T08:17:33Z

G0TRT: General Information start point

==General Information==

DXspider has the ability to log information at various levels, and those levels are set using the [[https://wiki.dxcluster.org/wiki/DXSpider_Sysop_Command_Reference#DEBUG|debug]] tool in conjunction with the [[https://wiki.dxcluster.org/wiki/DXSpider_Debug_Commands_and_Levels|debug levels]]. Whilst this information is capture in data files in ../spider/local_data/debug/ it can also be seen in realtime from the command line prompt.

DXSpider Sysop Command Reference

2025-04-05T08:12:23Z

G0TRT: /* debug */

==ACCEPT==
* '''accept''' set a filter to accept something
* Create a filter to accept something. There are 2 types of filter, accept and reject. See ''Help Filtering'' for more info.

===accept/announce <call> [input] [0-9] <pattern>===
* '''accept/announce''' <call> [input] [0-9] <pattern> - Announce filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
accept/ann by G,M,2
accept/ann input node_default by G,M,2
accept/ann user_default by G,M,2

===accept/announce [0-9] <pattern>===
*accept/announce [0-9] <pattern> - Set an 'accept' filter line for announce
Create an 'accept this announce' line for a filter. An accept filter line means that if the announce matches this filter it is passed onto the user. See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
info <string> - eg: iota or qsl
by <prefixes> - eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> - eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,NH
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states>
channel <prefixes> wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX
some examples:
acc/ann dest 6MUK
acc/ann 2 by_zone 14,15,16
(this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
or
acc/ann by G,M,2
for american states
acc/ann by_state va,nh,ri,nh
You can use the tag 'all' to accept everything eg:
acc/ann all
but this probably for advanced users...

===accept/route <call> [0-9] <pattern>===
*accept/route <call> [0-9] <pattern> - Set an 'accept' filter line for routing
Create an 'accept this routing PC Protocol' line for a filter. An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter it is passed thru that interface. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:
call <prefixes>
the callsign of the thingy
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,NH
origin <prefixes>
really the interface it came in on
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,NH
some examples:
acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
you can now use 'by' as a synonym for 'call' so:
by = call by_dxcc = call_dxcc
you can use the tag 'all' to accept everything eg:
acc/route all

===accept/spots <call> [input] [0-9] <pattern>===
*accept/spots <call> [input] [0-9] <pattern> - Spot filter sysop version
This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:
accept/spot db0sue-7 1 by_zone 14,15,16
accept/spot node_default all
set/hops node_default 10
accept/spot user_default by G,M,2

===accept/spots [0-9] <pattern>===
*accept/spots [0-9] <pattern> - Set an 'accept' filter line for spots
Create an 'accept this spot' line for a filter. An accept filter line means that if the spot matches this filter it ispassed onto the user. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on <range> same as 'freq'
call <prefixes> eg: G,PA,HB9
info <string> eg: iota or qsl
by <prefixes>
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states> eg: VA,NH,RI,ME
origin <prefixes>
channel <prefixes>
'call' means the callsign that has spotted 'by' whoever. For frequencies, you can use any of the band names defined in SHOW/BANDS and you can use a sub-band name like: cw, rtty, data, ssb -thus: hf/ssb. You can also just have a simple range like: 0/30000 -this is more efficient than saying simply: freq HF (but don't get too hung up about that)some examples:
acc/spot 1 on hf/cw
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
You can use the tag 'all' to accept everything, eg:
acc/spot 3 all
for US states
acc/spots by_state VA,NH,RI,MA,ME
but this probably for advanced users...

===accept/wcy <call> [input] [0-9] <pattern>===
*accept/wcy <call> [input] [0-9] <pattern> - WCY filter sysop version
This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:
accept/wcy node_default all set/hops node_default 10

===accept/wcy [0-9] <pattern>===
*accept/wcy [0-9] <pattern> - set an 'accept' WCY filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them).This command is really provided for future use. See HELP FILTER for information.

===accept/wwv <call> [input] [0-9] <pattern>===
*accept/wwv <call> [input] [0-9] <pattern> - WWV filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
accept/wwv db0sue-7 1 by_zone 4
accept/wwv node_default all set/hops node_default 10
accept/wwv user_default by W,K

===accept/wwv [0-9] <pattern>===
*accept/wwv [0-9] <pattern> - set an 'accept' WWV filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
for example:
accept/wwv by_zone 4
is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). See HELP FILTER for information.

==ANNOUNCE==
===announce <text>===
*announce <text> - Send an announcement to LOCAL users only
<text> is the text of the announcement you wish to broadcast

===announce full <text>===
*announce full <text> - Send an announcement cluster wide
This will send your announcement cluster wide

===announce sysop <text>===
*announce sysop <text> - Send an announcement to Sysops only

==APROPOS==
===apropos <string>===
*apropos <string> - Search help database for <string>
Search the help database for <string> (it isn't case sensitive), and print the names of all the commands that may be relevant.

==BLANK==
===blank [<string>] [<nn>]===
*blank [<string>] [<nn>] - Print nn (default 1) blank lines (or strings)
In its basic form this command prints one or more blank lines. However if you pass it a string it will replicate the string for the width of the screen (default 80) and then print that one or more times, so:
blank 2
prints two blank lines
blank -
prints a row of - characters once.
blank abc
prints 'abcabcabcabcabcabc....'This is really only of any use in a script file and you can print a maximum of 9 lines.

==BYE==
===bye===
*bye - Exit from the cluster
This will disconnect you from the cluster

==CATCHUP==
===catchup <node call> all|[<msgno> ...]===
*catchup <node call> all|[<msgno> ...] - Mark a message as sent

==CHAT==
===chat <group> <text>===
*chat <group> <text> - Chat or Conference to a group
It is now possible to JOIN a group and have network wide conferencing to that group. DXSpider does not (and probably will not) implement the AK1A conference mode as this seems very limiting, is hardly used and doesn't seem to work too well anyway. This system uses the existing ANN system and is compatible with both other DXSpider nodes and AK1A clusters (they use ANN/<group>). You can be a member of as many "groups" as you want. To join a group type:
JOIN FOC (where FOC is the group name)
To leave a group type:
LEAVE FOC
You can see which groups you are in by typing:
STAT/USER
and you can see whether your mate is in the group, if he connects to the same node as you, by typing:
STAT/USER g1tlh
To send a message to a group type:
CHAT FOC hello everyone
or
CH #9000 hello I am back
See also JOIN, LEAVE, SHOW/CHAT

==CLEAR==
===clear/announce <callsign> [input] [0-9|all]===
*clear/announce <callsign> [input] [0-9|all] - Clear a announce filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/announce [1|all]===
*clear/announce [1|all] - Clear a announce filter line
This command allows you to clear (remove) a line in a announce filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

===clear/route <callsign> [input] [0-9|all]===
*clear/route <callsign> [input] [0-9|all] - Clear a route filter line
A sysop can clear an input or normal output filter for a user or then ode_default or user_default.

===clear/route [1|all]===
*clear/route [1|all] - Clear a route filter line
This command allows you to clear (remove) a line in a route filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

===clear/spots <callsign> [input] [0-9|all]===
*clear/spots <callsign> [input] [0-9|all] - Clear a spot filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/spots [0-9|all]===
*clear/spots [0-9|all] - Clear a spot filter line
This command allows you to clear (remove) a line in a spot filter or to remove the whole filter. If you have a filter:
acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
and you say:
clear/spot 1
you will be left with:
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
If you do:
clear/spot all
the filter will be completely removed.

===clear/wcy <callsign> [input] [0-9|all]===
*clear/wcy <callsign> [input] [0-9|all] - Clear a WCY filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/wcy [1|all]===
*clear/wcy [1|all] - Clear a WCY filter line
This command allows you to clear (remove) a line in a WCY filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

===clear/wwv <callsign> [input] [0-9|all]===
*clear/wwv <callsign> [input] [0-9|all] - Clear a WWV filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/wwv [1|all]===
clear/wwv [1|all] - Clear a WWV filter line
This command allows you to clear (remove) a line in a WWV filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

==CONNECT==
===connect <callsign>===
*connect <callsign> - Start a connection to another DX Cluster
Start a connection process that will culminate in a new connection to the DX cluster <callsign>. This process creates a new 'client' process which will use the script in /spider/connect/<callsign> to effect the 'chat' exchange necessary to traverse the network(s) to logon to the cluster <callsign>.

==DBAVAIL==
===dbavail===
*dbavail - Show a list of all the Databases in the system
Title says it all really, this command lists all the databases defined in the system. It is also aliased to SHOW/COMMAND.

==DBCREATE==
===dbcreate <name>===
*dbcreate <name> - Create a database entry

===dbcreate <name> chain <name> [<name>..]===
*dbcreate <name> chain <name> [<name>..] - Create a chained database entry

===dbcreate <name> cmd <dxspider command>===
*dbcreate <name> cmd <dxspider command> - make a local command available as a DB
DBCREATE allows you to define a database in the system. It doesn't actually create anything, just defines it. The databases that are created are simple DB_File hash databases, they are therefore already 'indexed'. You can define a local database with the first form of the command eg:
DBCREATE oblast
You can also chain databases with the addition of the 'chain' keyword. This will search each database one after the other. A typical example is:
DBCREATE sdx_qsl chain sql_ad
No checking is done to see if the any of the chained databases exist, in fact it is usually better to do the above statement first then do each of the chained databases. Databases can exist offsite. To define a database that lives on another node do:
DBCREATE buckmaster remote gb7dxc
Remote databases cannot be chained; however, the last database in a a chain can be a remote database eg:
DBCREATE qsl chain gb7dxc
To see what databases have been defined do:
DBAVAIL (or it will have been aliased to SHOW/COMMAND)
It would be normal for you to add an entry into your local Aliases file to allow people to use the 'SHOW/<dbname>' style syntax. So you would need to add a line like:
's' => [ .. .. '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', .. .. ],
to allow
SH/BUCK g1tlh
to work as they may be used to.You can also make local commands available as 'pseudo' databases. Youcan therefore make spider special commands available as a database. Iimagine that this will be primarily useful for remote access from legacy nodes. For example:-
DBCREATE dxqsl cmd show/dxqsl
You also use one of these databases in a chain. This may be useful locally. See DBIMPORT for the importing of existing AK1A format data to databases. See DBSHOW for generic database enquiry

===dbcreate <name> remote <node>===
*dbcreate <name> remote <node> - Create a remote database entry

==DBIMPORT==
===dbimport <dbname> <filename>===
*dbimport <dbname> <filename> - Import AK1A data into a database
If you want to import or update data in bulk to a database you can use this command. It will either create or update entries into an existing database. For example:
DBIMPORT oblast /tmp/OBLAST.FUL
will import the standard OBLAST database that comes with AK1A into the oblast database held locally.

==DBREMOVE==
===dbremove <dbname>===
*dbremove <dbname> - Delete a database
DBREMOVE will completely remove a database entry and also delete any datafile that is associated with it. There is no warning, no comeback, no safety net. For example:
DBREMOVE oblast
will remove the oblast database from the system and it will also remove the associated data file. I repeat: There is no warning, no comeback, no safety net. You have been warned.

==DBSHOW==
===dbshow <dbname> <key>===
*dbshow <dbname> <key> - Display an entry, if it exists, in a database
This is the generic user interface to the database to the database system. It is expected that the sysop will add an entry to the local Aliases file so that users can use the more familiar AK1A style of enquiry such as:
SH/BUCK G1TLH
but if he hasn't and the database really does exist (use DBAVAIL or SHOW/COMMAND to find out) you can do the same thing with:
DBSHOW buck G1TLH

==DEBUG==
===debug===
*debug - Set the cluster program into debug mode
Executing this command will only have an effect if you are running the cluster in debug mode i.e.
perl -d cluster.pl
It will interrupt the cluster just after the debug command has finished.

The full debug command set is on the [[DXSpider Debug Commands and Levels|debug commands and levels]] page

==DELETE==
===delete/usdb <callsign> ...===
*delete/usdb <callsign> ... - Delete this user from the US State Database
This command will completely remove a one or more callsigns from the US States database. There is NO SECOND CHANCE. It goes without saying that you should use this command CAREFULLY! Note that these callsigns may be re-instated by any weekly updates from the FCC.

===delete/user <callsign> ...===
*delete/user <callsign> ... - Delete this user from the User Database
This command will completely remove a one or more users from the database. There is NO SECOND CHANCE. It goes without saying that you should use this command CAREFULLY!

==DEMONSTRATE==
===demonstrate <call> <command>===
*demonstrate <call> <command> - Demonstrate a command to another user
This command is provided so that sysops can demonstrate commands to other users. It runs a command as though that user had typed it in and then sends the output to that user, together with the command that caused it.
DEMO g7brn sh/dx iota oc209
DEMO g1tlh set/here
Note that this command is similar to SPOOF and will have the same side effects. Commands are run at the privilege of the user which is being demonstrated to.

==DIRECTORY==
===directory===
*directory - List messages

===directory <from>-<to>===
*directory <from>-<to> - List messages <from> message <to> message
List the messages in the messages directory. If there is a 'p' one space after the message number then it is a personal message. If there is a '-' between the message number and the 'p' then this indicates that the message has been read. You can use shell escape characters such as '*' and '?' in the <call>fields. You can combine some of the various directory commands together eg:
DIR TO G1TLH 5
or
DIR SUBJECT IOTA 200-250
You can abbreviate all the commands to one letter and use ak1a syntax:
DIR/T G1* 10
DIR/S QSL 10-100 5

===directory <nn>===
*directory <nn> - List last <nn> messages

===directory all===
*directory all - List all messages

===directory from <call>===
*directory from <call> - List all messages from <call>

===directory new===
*directory new - List all new messages

===directory own===
*directory own - List your own messages

===directory subject <string>===
*directory subject <string> - List all messages with <string> in subject

===directory to <call>===
*directory to <call> - List all messages to <call>

===directory- ===
directory-
Sysops can see all users' messages.

==DISCONNECT==
===disconnect <call> [<call> ...]===
*disconnect <call> [<call> ...] - Disconnect a user or cluster
Disconnect any <call> connected locally

==DX==
===dx [by <call>] <freq> <call> <remarks>===
dx [by <call>] <freq> <call> <remarks> - Send a DX spot
This is how you send a DX Spot to other users. You can, in fact, now enter the <freq> and the <call> either way round.
DX FR0G 144.600
DX 144.600 FR0G
DX 144600 FR0G
will all give the same result. You can add some remarks to the end of the command and they will be added to the spot.
DX FR0G 144600 this is a test
You can credit someone else by saying:
DX by G1TLH FR0G 144.600 he isn't on the cluster
The <freq> is compared against the available bands set up in the cluster. See SHOW/BANDS for more information.

==ECHO==
===echo <line>===
echo <line> - Echo the line to the output
This command is useful in scripts and so forth for printing the line that you give to the command to the output. You can use this in user_default scripts and the SAVE command for titling and so forth. The script will interpret certain standard "escape" sequences as follows:
\t - becomes a TAB character (0x09 in ascii)
\a - becomes a BEEP character (0x07 in ascii)
\n - prints a new line
So the following example:
echo GB7DJK is a dxcluster
produces:
GB7DJK is a dxcluster
on the output. You don't need a \n on the end of the line you want to send.

==EXPORT==
===export <msgno> <filename>===
*export <msgno> <filename> - Export a message to a file
Export a message to a file. This command can only be executed on a local console with a fully privileged user. The file produced will be in a form ready to be imported back into the cluster by placing it in the import directory (/spider/msg/import).This command cannot overwrite an existing file. This is to provide some measure of security. Any files written will owned by the same user as the main cluster, otherwise you can put the new files anywhere the cluster can access. For example:
EXPORT 2345 /tmp/a

===export_users [<filename>]===
*export_users [<filename>] - Export the users database to ascii
Export the users database to a file in ascii format. If no file name is given then it will export the file to /spider/data/user_asc. If the file already exists it will be renamed to <filename>.o. In fact up to 5 generations of the file can be kept each one with an extra 'o' on the suffix. BE WARNED: this will write to any file you have write access to. No check is made on the filename (if any) that you specify.

==FILTERING==
===filtering...===
*filtering... - Filtering things in DXSpider
There are a number of things you can filter in the DXSpider system. They all use the same general mechanism. In general terms you can create a 'reject' or an 'accept' filter which can have up to 10 lines in it. You do this using, for example:
accept/spots .....
reject/spots .....
where ..... are the specific commands for that type of filter. There are filters for spots, wwv, announce, wcy and (for sysops) connects. See each different accept or reject command reference for more details. There is also a command to clear out one or more lines in a filter and one to show you what you have set. They are:
clear/spots 1
clear/spots all
and
show/filter
There is clear/xxxx command for each type of filter. For now we are going to use spots for the examples, but you can apply the principles to all types of filter. There are two main types of filter 'accept' or 'reject'; which you use depends entirely on how you look at the world and what is least writing to achieve what you want. Each filter has 10 lines (of any length) which are tried in order. If a line matches then the action you have specified is taken (ie reject means ignore it and accept means gimme it). The important thing to remember is that if you specify a 'reject' filter (all the lines in it say 'reject/spots' (for instance)) then if a spot comes in that doesn't match any of the lines then you will get it BUT if you specify an 'accept' filter then any spots that don't match are dumped. For example if I have a one line accept filter:
accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
then automatically you will ONLY get VHF spots from or to CQ zones 1415 and 16. If you set a reject filter like:
reject/spots on hf/cw
Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA and will work it even on CW then you could say:
reject/spots on hf/cw and not info iota
But in that case you might only be interested in iota and say:
accept/spots not on hf/cw or info iota
which is exactly the same. You should choose one or the other until you are comfortable with the way it works. Yes, you can mix them (actually you can have an accept AND a reject on the same line) but don't try this at home until you can analyze the results that you get without ringing up the sysop for help. Another useful addition now is filtering by US state
accept/spots by_state VA,NH,RI,ME
You can arrange your filter lines into logical units, either for your own understanding or simply convenience. I have one set frequently:
reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
What this does is to ignore all HF CW spots (being a class B I can't read any CW and couldn't possibly be interested in HF :-) and also rejects any spots on VHF which don't either originate or spot someone in Europe. This is an example where you would use the line number (1 and 2 in this case), if you leave the digit out, the system assumes '1'. Digits'0'-'9' are available. You can leave the word 'and' out if you want, it is implied. You can use any number of brackets to make the 'expression' as you want it. There are things called precedence rules working here which mean that you will NEED brackets in a situation like line 2 because, without it, will assume:
(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
annoying, but that is the way it is. If you use OR - use brackets. Whilst we are here CASE is not important. 'And BY_Zone' is just 'and by_zone'. If you want to alter your filter you can just redefine one or more lines of it or clear out one line. For example:
reject/spots 1 on hf/ssb
or
clear/spots 1
To remove the filter in its entirty:
clear/spots all
There are similar CLEAR commands for the other filters:
clear/announce
clear/wcy
clear/wwv
ADVANCED USERS: Once you are happy with the results you get, you may like to experiment. my example that filters hf/cw spots and accepts vhf/uhf spots from EU can be written with a mixed filter, eg:
rej/spot on hf/cw acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
each filter slot actually has a 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE the accept slot. It was mentioned earlier that after a reject test that doesn't match, the default for following tests is 'accept', the reverse is true for 'accept'. In the example what happens is that the reject is executed first, any non hf/cw spot is passed to the accept line, which lets thru everything else on HF. The next filter line lets through just VHF/UHF spots from EU.

==FORWARD==
===forward/latlong <node_call>===
*forward/latlong <node_call> - Send latitude and longitude information to another cluster
This command sends all the latitude and longitude information that your cluster is holding against callsigns. One advantage of receiving this information is that more locator information is held by you. This means that more locators are given on the DX line assuming you have SET/DXGRID enabled. This could be a LOT of information though, so it is not recommended on slow links.

===forward/opernam <call>===
*forward/opernam <call> - Send out information on this <call> to all clusters
This command sends out any information held in the user file which can be broadcast in PC41 protocol packets. This information is Name, QTH, Locationand Homenode. PC41s are only sent for the information that is available.

==FTx==
===enable/autoftx===
*enable/autoftx - Enable detected automatically generated FTx spots to be output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

===enable/ftx===
*enable/ftx - Enable FTx spots to be output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

===disable/autoftx===
*disable/autoftx - Disable detected automatically generated FTx spots from being output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

===disable/ftx===
*disable/ftx - Disable FTx spots from being output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

==HELP==
===help===
help - The HELP Command
HELP is available for a number of commands. The syntax is:
HELP <cmd>
Where <cmd> is the name of the command you want help on. All commands can be abbreviated, so SHOW/DX can be abbreviated to SH/DX, ANNOUNCE can be shortened to AN and so on. Look at the APROPOS <string> command which will search the help database for the <string> you specify and give you a list of likely commands to look at with HELP.

==INIT==
===init <node>===
*init <node> - Re-initialize a link to an AK1A compatible node
This command attempts to re-initialize a link to a (usually) AK1A node that has got confused, usually by a protocol loop of some kind. It may work - but you usually will be better off simply disconnecting it (or better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your node>). Best of luck - you will need it.

==JOIN==
===join <group>===
*join <group> - Join a chat or conference group
JOIN allows you to join a network wide conference group. To join a group (called FOC in this case) type:
JOIN FOC
See also CHAT, LEAVE, SHOW/CHAT

==KILL==
===kill===
*kill
As a sysop you can kill any message on the system.

===kill <from msgno>-<to msgno>===
*kill <from msgno>-<to msgno> - Delete a range of messages

===kill <from>-<to>===
*kill <from>-<to> - Remove a range of messages from the system

===kill <msgno> [<msgno..]===
*kill <msgno> [<msgno..] - Delete a message from the local system

===kill <msgno> [<msgno> ...]===
*kill <msgno> [<msgno> ...] - Remove or erase a message from the system
You can get rid of any message to or originating from your callsign using this command. You can remove more than one message at a time.

===kill expunge <msgno> [<msgno..]===
*kill expunge <msgno> [<msgno..] - Expunge a message
Deleting a message using the normal KILL commands only marks that message for deletion. The actual deletion only happens later (usually two days later). The KILL EXPUNGE command causes the message to be truly deleted more or less immediately. It otherwise is used in the same way as the KILL command.

===kill from <call>===
*kill from <call> - Remove all messages from a callsign

===kill full <msgno> [<msgno..]===
*kill full <msgno> [<msgno..] - Delete a message from the whole cluster
Delete a message from the local system. You will only be able to delete messages that you have originated or been sent (unless you are the sysop).
KILL 1234-1255
Will delete all the messages that you own between msgnos 1234 and 1255.
KILL from g1tlh
will delete all the messages from g1tlh (if you are g1tlh). Similarly:
KILL to g1tlh
will delete all messages to g1tlh.
KILL FULL 1234
will delete a message (usually a 'bulletin') from the whole cluster system. This uses the subject field, so any messages that have exactly thesame subject will be deleted. Beware!

===kill full <msgno> [<msgno]===
*kill full <msgno> [<msgno] - Remove a message from the entire cluster
Remove this message from the entire cluster system as well as your node.

===kill to <call>===
*kill to <call> - Remove all messages to a callsign

===kill from <regex>===
*kill from <regex> - Delete messages FROM a callsign or pattern

===kill to <regex>===
*kill to <regex> - Delete messages TO a callsign or pattern

==LEAVE==
===leave <group>===
*leave <group> - Leave a chat or conference group
LEAVE allows you to leave a network wide conference group. To leave agroup (called FOC in this case) type:
LEAVE FOC
See also CHAT, JOIN, SHOW/CHAT

==LINKS==
===links===
*links - Show which nodes is physically connected
This is a quick listing that shows which links are connected and some information about them. See WHO for a list of all connections.

==LOAD==
===load/aliases===
*load/aliases - Reload the command alias table
Reload the /spider/cmd/Aliases file after you have edited it. You will need to do this if you change this file whilst the cluster is running in order for the changes to take effect.

===load/badmsg===
*load/badmsg - Reload the bad msg table
Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst the cluster is running. This table contains a number of perl regular expressions which are searched for in the fields targeted of each message. If any of them match then that message is immediately deleted on receipt.

===load/badwords===
*load/badwords - Reload the bad words table
Reload the /spider/data/badwords file if you have changed it manually whilst the cluster is running. This file contains a list of words which, if found on certain text portions of PC protocol, will cause those protocol frames to be rejected. It will all put out a message if any of these words are used on the announce, dx and talk commands. The words can be one or more on a line, lines starting with '#' are ignored.

===load/bands===
*load/bands - Reload the band limits table
Reload the /spider/data/bands.pl file if you have changed it manually whilst the cluster is running.

===load/cmd_cache===
*load/cmd_cache - Reload the automatic command cache
Normally, if you change a command file in the cmd or local_cmd tree it will automatically be picked up by the cluster program. Sometimes it can get confused if you are doing a lot of moving commands about or delete a command in the local_cmd tree and want to use the normal one again. Execute this command to reset everything back to the state it was just after a cluster restart.

===load/forward===
*load/forward - Reload the msg forwarding routing table
Reload the /spider/msg/forward.pl file if you have changed it manually whilst the cluster is running.

===load/keps===
*load/keps - Load new keps data

===load/keps [nn]===
*load/keps [nn] - Load new keps data from message
If there is no message number then reload the current Keps data from the Keps.pm data file. You create this file by running
/spider/perl/convkeps.pl <filename>
on a file containing NASA 2 line keps as a message issued by AMSAT. If there is a message number, then it will take the message, run convkeps.pl on it and then load the data, all in one step. These messages are sent to ALL by GB7DJK (and others) from time to time.

===load/messages===
*load/messages - Reload the system messages file
If you change the /spider/perl/Messages file (usually whilst fiddling/writing new commands) you can have them take effect during a cluster session by executing this command. You need to do this if get something like :
unknown message 'xxxx' in lang 'en'

===load/prefixes===
*load/prefixes - Reload the prefix table
Reload the /spider/data/prefix_data.pl file if you have changed it manually whilst the cluster is running.

==MERGE==
===merge <node> [<no spots>/<no wwv>]===
*merge <node> [<no spots>/<no wwv>] - Ask for the latest spots and WWV
MERGE allows you to bring your spot and wwv database up to date. By default it will request the last 10 spots and 5 WWVs from the node you select. The node must be connected locally. You can request any number of spots or wwv and although they will be appended to your databases they will not duplicate any that have recently been added (the last 2 days for spots and last month for WWV data).

==MSG==
===msg <cmd> <msgno> [data ... ]===
*msg <cmd> <msgno> [data ... ] - Alter various message parameters
Alter message parameters like To, From, Subject, whether private or bulletin or return receipt (RR) is required or whether to keep this message from timing out.
MSG TO <msgno> <call> - change TO callsign to <call>
MSG FRom <msgno> <call> - change FROM callsign to <call>
MSG PRrivate <msgno> - set private flag
MSG NOPRrivate <msgno> - unset private flag
MSG RR <msgno> - set RR flag
MSG NORR <msgno> - unset RR flag
MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
MSG NOKEep <msgno> - unset the keep flag
MSG SUbject <msgno> <new> - change the subject to <new>
MSG WAittime <msgno> - remove any waitting time for this message
MSG NOREad <msgno> - mark message as unread
MSG REad <msgno> - mark message as read
MSG QUeue - queue any outstanding bulletins
MSG QUeue 1 - queue any outstanding private messages
You can look at the status of a message by using:
STAT/MSG <msgno>
This will display more information on the message than DIR does.

==PC==
===pc <call> <text>===
*pc <call> <text> - Send arbitrary text to a connected callsign
Send some arbitrary text to a locally connected callsign. No processing is done on the text. This command allows you to send PC Protocol to unstick things if problems arise (messages get stuck etc). eg:
pc gb7djk PC33^GB7TLH^GB7DJK^400^
or
pc G1TLH Try doing that properly!!!
Send any text you like to the callsign requested. This is used mainly to send PC protocol to connected nodes either for testing or to unstick things. You can also use in the same way as a talk command to a connected user but without any processing, added of "from <blah> to <blah" or whatever.

==PING==
===ping <node call>===
*ping <node call> - Check the link quality between nodes
This command allows you to send a frame to another cluster node on the network and get a return frame. The time it takes to do this is a good indication of the quality of the link. The actual time it takes is output to the console in seconds. Any visible cluster node can be PINGed.

==RCMD==
===rcmd <node call> <cmd>===
*rcmd <node call> <cmd> - Send a command to another DX Cluster
This command allows you to send nearly any command to another DX Cluster node that is connected to the system. Whether you get any output is dependent on a) whether the other system knows that the node callsign of this cluster is in fact a node b) whether the other system is allowing RCMDs from this node and c) whether you have permission to send this command at all.

==READ==
===read===
*read - Read the next unread personal message addressed to you

===read <msgno>===
*read <msgno> - Read the specified message
You can read any messages that are sent as 'non-personal' and also any message either sent by or sent to your callsign.

===read-===
*read-
As a sysop you may read any message on the system

==REJECT==
===reject===
*reject - Set a filter to reject something
Create a filter to reject something. There are 2 types of filter, accept and reject. See HELP FILTERING for more info.

===reject/announce <call> [input] [0-9] <pattern>===
*reject/announce <call> [input] [0-9] <pattern> - Announce filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/ann by G,M,2
reject/ann input node_default by G,M,2
reject/ann user_default by G,M,2

===reject/announce [0-9] <pattern>===
*reject/announce [0-9] <pattern> - Set a 'reject' filter line for announce
Create an 'reject this announce' line for a filter. A reject filter line means that if the announce matches this filter it is passed onto the user. See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
info <string> eg: iota or qsl
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states> eg: VA,NH,RI,ME
channel <prefixes>
wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX
some examples:
rej/ann by_zone 14,15,16 and not by G,M,2
You can use the tag 'all' to reject everything eg:
rej/ann all
but this probably for advanced users...

===reject/route <call> [0-9] <pattern>===
*reject/route <call> [0-9] <pattern> - Set an 'reject' filter line for routing
Create an 'reject this routing PC Protocol' line for a filter. An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter it is NOT passed thru that interface. See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
call <prefixes> the callsign of the thingy
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,ME
origin <prefixes>
really the interface it came in on
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,ME
some examples:
rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
You can use the tag 'all' to reject everything eg:
rej/route all (equiv to [very] restricted mode)
as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.

===reject/spots <call> [input] [0-9] <pattern>===
*reject/spots <call> [input] [0-9] <pattern> - Spot filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/spot db0sue-7 1 by_zone 14,15,16
reject/spot node_default all set/hops node_default 10
reject/spot user_default by G,M,2

===reject/spots [0-9] <pattern>===
*reject/spots [0-9] <pattern> - Set a 'reject' filter line for spots
Create a 'reject this spot' line for a filter. A reject filter line means that if the spot matches this filter it is dumped (not passed on). See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on <range> same as 'freq'
call <prefixes> eg: G,PA,HB9i
nfo <string> eg: iota or qsl
by <prefixes>
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states> eg: VA,NH,RI,ME
origin <prefixes>
channel <prefixes>
'call' means the callsign that has spotted 'by' whoever. For frequencies, you can use any of the band names defined in SHOW/BANDS and you can use a sub-band name like: cw, rtty, data, ssb -thus: hf/ssb. You can also just have a simple range like: 0/30000 -this is more efficient than saying simply: on HF (but don't get too hung up about that)some examples:
rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
You can use the tag 'all' to reject everything eg:
rej/spot 3 all
but this probably for advanced users...

===reject/wcy <call> [input] [0-9] <pattern>===
*reject/wcy <call> [input] [0-9] <pattern> - WCY filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/wcy gb7djk all

===reject/wcy [0-9] <pattern>===
reject/wcy [0-9] <pattern> - set a 'reject' WCY filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them). This command is really provided for future use. See HELP FILTER for information.

===reject/wwv <call> [input] [0-9] <pattern>===
*reject/wwv <call> [input] [0-9] <pattern> - WWV filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/wwv db0sue-7 1 by_zone 4
reject/wwv node_default all
reject/wwv user_default by W

===reject/wwv [0-9] <pattern>===
*reject/wwv [0-9] <pattern> - set a 'reject' WWV filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
for example
reject/wwv by_zone 14,15,16
is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). See HELP FILTER for information.

==REPLY==
===reply===
*reply - Reply (privately) to the last message that you have read

===reply <msgno>===
*reply <msgno> - Reply (privately) to the specified message

===reply b <msgno>===
*reply b <msgno> - Reply as a Bulletin to the specified message

===reply noprivate <msgno>===
*reply noprivate <msgno> - Reply as a Bulletin to the specified message

===reply rr <msgno>===
*reply rr <msgno> - Reply to the specified message with read receipt
You can reply to a message and the subject will automatically have "Re:" inserted in front of it, if it isn't already present. You can also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B that you can use with the SEND command (see SEND for further details)

==SAVE==
===save [-d -t -a] <filename> "<cmd>" [...]===
*save [-d -t -a] <filename> "<cmd>" [...] Save command output to a file
This sysop only command allows you to save the output of one or more commands to a file. For example:
save /spider/packclus/dxstats show/dxstat
will save the output of the normal command "show/dxstat" to the file "dxstats" in the files area. You can have some extra flags to the save which will either date stamp or time stamp or both the filename so:
save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
save -t /tmp/a <cmd> creates /tmp/a_2301Z
save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
The -a flag means append to the file instead of overwriting it. You can have more than one command on the line, to do this you MUST enclose each command in double quotes (") eg:
save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
or
save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
You can only write into places that the cluster has permission for (which is that of the "sysop" user [which had BETTER NOT BE "root"]), you will need to create any directories you want to put stuff in beforehand as well. It is likely that you will want to run these commands in a crontab type situation. You would do that something like:
0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
Note that you still enclose each command with (") characters but you must enclose the entire save command in (') characters. Now in fact, this can be varied if you know what you are doing. See the admin manual for more details.

==SEND==
===send <call> [<call> ...]===
*send <call> [<call> ...] - Send a message to one or more callsigns

===send copy <msgno> <call>===
send copy <msgno> <call> - Send a copy of a message to someone

===send noprivate <call>===
*send noprivate <call> - Send a message to all stations
All the SEND commands will create a message which will be sent either to an individual callsign or to one of the 'bulletin' addresses. SEND <call> on its own acts as though you had typed SEND PRIVATE, that is it will mark the message as personal and send it to the cluster node that that callsign is connected to. If the <call> you have specified is in fact a known bulletin category on your node (eg: ALL) then the message should automatically become a bulletin. You can have more than one callsign in all of the SEND commands. You can have multiple qualifiers so that you can have for example:
SEND RR COPY 123 PRIVATE G1TLH G0RDI
which should send a copy of message 123 to G1TLH and G0RDI and you will receive a read receipt when they have read the message. SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak). SP is an alias for SEND PRIVATE. The system will ask you for a subject. Conventionally this should be no longer than 29 characters for compatibility. Most modern cluster software should accept more. You will now be prompted to start entering your text. You finish the message by entering '/EX' on a new line. For instance:
... bye then Jim 73 Dirk /ex
If you have started a message and you don't want to keep it then you can abandon the message with '/ABORT' on a new line, like:
line 1 line 2 oh I just can't be bothered with this /abort
If you abort the message it will NOT be sent. When you are entering the text of your message, most normal output (such as DX announcements and so on are suppressed and stored for latter display(up to 20 such lines are stored, as new ones come along, so the oldest lines are dropped). Also, you can enter normal commands commands (and get the output immediately) whilst in the middle of a message. You do this by typing the command preceded by a '/' character on a new line, so:
/dx g1tlh 144010 strong signal
Will issue a dx announcement to the rest of the cluster. Also, you can add the output of a command to your message by preceding the command with '//', thus :
//sh/vhftable
This will show YOU the output from SH/VHFTABLE and also store it in the message. You can carry on with the message until you are ready to send it.

===send private <call>===
*send private <call> - Send a personal message

===send rr <call>===
*send rr <call> - Send a message and ask for a read receipt

==SET==
===set/address <your address>===
*set/address <your address> - Record your postal address

===set/announce===
*set/announce - Allow announce messages to come out on your terminal

===set/anntalk===
*set/anntalk - Allow talk like announce messages on your terminal

===set/arcluster <call> [<call>..]===
*set/arcluster <call> [<call>..] - Make the callsign an AR-Cluster node

===set/baddx <call>..===
*set/baddx <call>.. - Stop callsigns in a dx spot being propagated

===set/badnode <call>..===
*set/badnode <call>.. - Stop spots from this node being propagated

===set/badspotter <call>..===
*set/badspotter <call>.. - Stop spots from this callsign being propagated

===set/badword <word>..===
*set/badword <word>.. - Stop things with this word being propagated

===set/bbs <call> [<call>..]===
*set/bbs <call> [<call>..] - Make the callsign a BBS

===set/beep===
*set/beep - Add a beep to DX and other messages on your terminal

===set/clx <call> [<call>..]===
*set/clx <call> [<call>..] - Make the callsign an CLX node

===set/debug <name>===
*set/debug <name> - Add a debug level to the debug set

===set/dx===
*set/dx - Allow DX messages to come out on your terminal

===set/dxcq===
*set/dxcq - Show CQ Zones on the end of DX announcements

===set/dxgrid===
*set/dxgrid - Allow QRA Grid Squares on the end of DX announcements

===set/dxitu===
*set/dxitu - Show ITU Zones on the end of DX announcements

===set/dxnet <call> [<call>..]===
*set/dxnet <call> [<call>..] - Make the callsign an DXNet node

===set/echo===
*set/echo - Make the cluster echo your input

===set/email <email> ...===
*set/email <email> ... - Set email address(es) and forward your personals

===set/external_ip <external_ip>===
*set/external_ip - Set the external IPv4 address for the node and the local terminal masquerade automatically with best effort.

===set/here===
*set/here - Tell the system you are present at your terminal

===set/homenode <node>===
*set/homenode <node> - Set your normal cluster callsign
Tell the cluster system where you normally connect to. Any Messages sent to you will normally find their way there should you not be connected.eg:
SET/HOMENODE gb7djk

===set/hops <call> ann|spots|route|wwv|wcy <n>===
*set/hops <call> ann|spots|route|wwv|wcy <n> - Set hop count

===set/isolate===
*set/isolate - Isolate a node from the rest of the network
Connect a node to your system in such a way that you are a full protocol member of its network and can see all spots on it, but nothing either leaks out from it nor goes back into from the rest of the nodes connected to you. You can potentially connect several nodes in this way.

===set/language <lang>===
*set/language <lang> - Set the language you want to use
You can select the language that you want the cluster to use. Currently the languages available are en (English), de (German), es (Spanish),Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).

===set/location <lat & long>===
*set/location <lat & long> - Set your latitude and longitude

===set/lockout <call>===
*set/lockout <call> - Stop a callsign connecting to the cluster

===set/logininfo===
*set/logininfo - Inform when a station logs in/out locally

===set/name <your name>===
*set/name <your name> - Set your name
Tell the system what your name is eg:
SET/NAME Dirk

===set/node <call> [<call>..]===
*set/node <call> [<call>..] - Make the callsign an AK1A cluster
Tell the system that the call(s) are to be treated as AK1A cluster and fed PC Protocol rather normal user commands.

===set/obscount <count> <call>===
*set/obscount <count> <call> - Set the 'pump-up' obscelence PING counter
From 1.35 onwards neighboring nodes are pinged at regular intervals (see SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up' counter which is decremented on every outgoing ping and then reset to the 'obscount' value on every incoming ping. The default value of this parameter is 2. What this means is that a neighbouring node will be pinged twice at (default) 300 second intervals and if no reply has been heard just before what would be the third attempt, that node is disconnected. If a ping is heard then the obscount is reset to the full value. Using default values, if a node has not responded to a ping within 15 minutes, it is disconnected. You can set this parameter between 1 and 9. It is STRONGLY recommended that you don't change the default.

===set/page <lines per page>===
*set/page <lines per page> - Set the lines per page
Tell the system how many lines you wish on a page when the number of line of output from a command is more than this. The default is 20. Setting it explicitly to 0 will disable paging.
SET/PAGE 30 SET/PAGE 0
The setting is stored in your user profile.

===set/password===
*set/password - Set your own password
This command only works for a 'telnet' user (currently). It will only work if you have a password already set. This initial password can only be set by the sysop. When you execute this command it will ask you for your old password, then ask you to type in your new password twice (to make sure you get it right). You may or may not see the data echoed on the screen as you type, depending on the type of telnet client you have.

===set/password <callsign> <string>===
*set/password <callsign> <string> - Set a users password
The password for a user can only be set by a full sysop. The string can contain any characters. The way this field is used depends on context. If it is being used in the SYSOP command context then you are offered 5 random numbers and you have to supply the corresponding letters. This is now mainly for ax25 connections. If it is being used on incoming telnet connections then, if a password is set or the:
set/var $main::passwdreq = 1
command is executed in the startup script, then a password prompt is given after the normal 'login:' prompt.

===set/pinginterval <time> <nodecall>===
*set/pinginterval <time> <nodecall> - Set ping time to neighbouring nodes
As from release 1.35 all neighbouring nodes are pinged at regular intervals in order to determine the rolling quality of the link and, in future, to affect routing decisions. The default interval is 300 secs or 5 minutes. You can use this command to set a different interval. Please don't. But if you do the value you enter is treated as minutes up 30 and seconds for numbers greater than that. This is used also to help determine when a link is down at the far end(as certain cluster software doesn't always notice), see SET/OBSCOUNT for more information. If you must change it (and it may be useful for internet connected nodes on dynamic IP addresses that go away after a set time of usage) the time can be specified as:
5 which if less than 30 is converted to minutes otherwise is taken as the no of seconds between pings.
120s 120 seconds
5m 5 minutes
1h 1 hour
Please be aware that this causes traffic to occur on the link, setting this value too low may annoy your neighbours beyond the point of endurance! You can switch this off by setting it to 0.

===set/privilege <n> <call> [<call..]===
*set/privilege <n> <call> [<call..] - Set privilege level on a call
Set the privilege level on a callsign. The privilege levels that pertain to commands are as default:
0 - normal user
1 - allow remote nodes normal user RCMDs
5 - various privileged commands (including shutdown, but not disconnect), the normal level for another node.
8 - more privileged commands (including disconnect)
9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS LEVEL.
If you are a sysop and you come in as a normal user on a remote connection your privilege will automatically be set to 0.

===set/prompt <string>===
*set/prompt <string> - Set your prompt to <string>

===set/qra <locator>===
*set/qra <locator> - Set your QRA Grid locator
Tell the system what your QRA (or Maidenhead) locator is. If you have not done a SET/LOCATION then your latitude and longitude will be set roughly correctly (assuming your locator is correct ;-). For example:
SET/QRA JO02LQ

===set/qth <your qth>===
*set/qth <your qth> - Set your QTH
Tell the system where you are. For example:
SET/QTH East Dereham, Norfolk

===set/register <call> ...===
set/register <call> ... - Mark a user as registered

===set/spider <call> [<call>..]===
*set/spider <call> [<call>..] - Make the callsign an DXSpider node
Tell the system that the call(s) are to be treated as DXSpider node and fed new style DX Protocol rather normal user commands.

===set/startup===
*set/startup - Create your own startup script
Create a startup script of DXSpider commands which will be executed every time that you login into this node. You can only input the whole script afresh, it is not possible to 'edit' it. Inputting a new script is just like typing in a message using SEND. To finish inputting type: /EX on a newline, to abandon the script type: /ABORT. You may find the (curiously named) command BLANK useful to break up the output. If you simply want a blank line, it is easier to input one or more spaces and press the <return> key. See UNSET/STARTUP to remove a script.

===set/startup <call>===
*set/startup <call> - Create a user startup script

===set/sys_location <lat & long>===
*set/sys_location <lat & long> - Set your cluster latitude and longitude
In order to get accurate headings and such like you must tell the system what your latitude and longitude is. If you have not yet done a SET/QRA then this command will set your QRA locator for you. For example:
SET/LOCATION 52 22 N 0 57 E

===set/sys_qra <locator>===
*set/sys_qra <locator> - Set your cluster QRA Grid locator

===set/talk===
*set/talk - Allow TALK messages to come out on your terminal

===set/usdb <call> <state> <city>===
*set/usdb <call> <state> <city> - add/update a US DB callsign
This command allows you to add or alter a callsign in the US state database. Use with extreme caution. Anything you do here will be overwritten by any weekly updates that affect this callsign
set/usdb g1tlh nh downtown rindge
see also DELETE/USDB

===set/usstate===
*set/usstate - Allow US State info on the end of DX announcements

===set/wcy===
*set/wcy - Allow WCY messages to come out on your terminal

===set/wwv===
*set/wwv - Allow WWV messages to come out on your terminal

===set/wx===
*set/wx - Allow WX messages to come out on your terminal

==SHOW==
===show/baddx===
*show/baddx - Show all the bad dx calls in the system
Display all the bad dx callsigns in the system, see SET/BADDX for more information.

===show/badnode===
*show/badnode - Show all the bad nodes in the system
Display all the bad node callsigns in the system, see SET/BADNODE for more information.

===show/badspotter===
*show/badspotter - Show all the bad spotters in the system
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER for more information.

===show/badword===
*show/badword - Show all the bad words in the system
Display all the bad words in the system, see SET/BADWORD for more information.

===show/chat [<group>] [<lines>]===
*show/chat [<group>] [<lines>] - Show any chat or conferencing
This command allows you to see any chat or conferencing that has occurred whilst you were away. SHOW/CHAT on its own will show data for all groups. If you use a group name then it will show only chat for that group.

===show/configuration [<node>]===
*show/configuration [<node>] - Show all the nodes and users visible
This command allows you to see all the users that can be seen and the nodes to which they are connected. This command is normally abbreviated to: sh/c. Normally, the list returned will be just for the nodes from your country (because the list otherwise will be very long).
SH/C ALL
will produce a complete list of all nodes. BE WARNED: the list that is returned can be VERY long. It is possible to supply a node or part of a prefix and you will get a list of the users for that node or list of nodes starting with that prefix.
SH/C GB7DJK
SH/C SK

===show/configuration/node===
*show/configuration/node - Show all the nodes connected locally
Show all the nodes connected to this node.

===show/connect===
*show/connect - Show all the active connections
This command shows information on all the active connections known to the node. This command gives slightly more information than WHO.

===show/contest <year and month>===
*show/contest <year and month> - Show all the contests for a month
Show all known contests which are maintained at http://www.sk3bg.se/contest/ for a particular month or year. The format is reasonably flexible. For example:
SH/CONTEST sep2003
SH/CONTEST 03 march

===show/date [<prefix>|<callsign>]===
*show/date [<prefix>|<callsign>] - Show the local time
This is very nearly the same as SHOW/TIME, the only difference the format of the date string if no arguments are given. If no prefixes or callsigns are given then this command returns the local time and UTC as the computer has it right now. If you give some prefixes then it will show UTC and UTC + the local offset (not including DST) at the prefixes or callsigns that you specify.

===show/db0sdx <callsign>===
*show/db0sdx <callsign> - Show QSL information from DB0SDX database
This command queries the DB0SDX QSL server on the internet and returns any information available for that callsign. This service is provided for users of this software by http://www.qslinfo.de. See also SHOW/QRZ, SHOW/WM7D.

===show/debug===
*show/debug - Show what levels of debug information you are logging

===show/dup_ann===
*show/dup_ann - Show duplicate announcement records

===show/dup_spots===
*show/dup_spots - Show duplicate spot records

===show/dx===
*show/dx - Interrogate the spot database
If you just type SHOW/DX you will get the last so many spots (sysop configurable, but usually 10). In addition you can add any number of these commands in very nearly any order to the basic SHOW/DX command, they are:
on <band> - eg 160m 20m 2m 23cm 6mm
on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
on <from>/<to> - eg 1000/4000 14000-30000 (in Khz) <from>-<to>
<number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
<prefix> - for a spotted callsign beginning with <prefix>
*<suffix> - for a spotted callsign ending in <suffix>
*<string>* - for a spotted callsign containing <string>
day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
info <text> - any spots containing <text> in the info or remarks
by <call> - any spots spotted by <call> (spotter <call> is the same).
qsl - this automatically looks for any qsl info on the call held in the spot database.
iota [<iota>] - If the iota island number is missing it will look for the string iota and anything which looks like an iota island number. If you specify then it will look for that island.
qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2 You can also use this with the 'by' keyword so eg by W dxcc
real or rt - Format the output the same as for real time spots. The formats are deliberately different (so you can tell one sort from the other). This is useful for some logging programs that can't cope with normal sh/dx output. An alias of SHOW/FDX is available.
filter - Filter the spots, before output, with the user's spot filter. An alias of SHOW/MYDX is available.
zone <zones> - look for spots in the cq zone (or zones) specified. zones are numbers separated by commas.
by_zone <zones> - look for spots spotted by people in the cq zone specified.
itu <itus> - look for spots in the itu zone (or zones) specified itu zones are numbers separated by commas.
by_itu <itus> - look for spots spotted by people in the itu zone specified.
state <list> - look for spots in the US state (or states) specified The list is two letter state codes separated by commas.
by_state <list> - look for spots spotted by people in the US state specified.
e.g.
SH/DX 9m0
SH/DX on 20m info iota
SH/DX 9a on vhf day 30
SH/DX rf1p qsl
SH/DX iota
SH/DX iota eu-064
SH/DX qra jn86
SH/DX dxcc oq2
SH/DX dxcc oq2 by w dxcc
SH/DX zone 4,5,6
SH/DX by_zone 4,5,6
SH/DX state in,oh
SH/DX by_state in,oh

===show/dxcc <prefix>===
*show/dxcc <prefix> - Interrogate the spot database by country
This command takes the <prefix> (which can be a full or partial callsign if desired), looks up which internal country number it is and then displays all the spots as per SH/DX for that country. This is now an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this command. e.g.
SH/DXCC G SH/DXCC W on 20m iota
This can be done with the SHOW/DX command like this:
SH/DX dxcc g
SH/DX dxcc w on 20m iota
This is an alias for: SH/DX dxcc

===show/dxqsl <callsign>===
*show/dxqsl <callsign> - Show any QSL info gathered from spots
The node collects information from the comment fields in spots (things like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database. This command allows you to interrogate that database and if the callsign is found will display the manager(s) that people have spotted. This information is NOT reliable, but it is normally reasonably accurate if it is spotted enough times. For example:
sh/dxqsl 4k9w
You can check the raw input spots yourself with:
sh/dx 4k9w qsl
This gives you more background information.

===show/dxstats [days] [date]===
*show/dxstats [days] [date] - Show the DX Statistics
Show the total DX spots for the last <days> no of days (default is 31), starting from a <date> (default: today).

===show/external_ip===
*show/external_ip - Show the external IP set/detected for the node and local terminal masquerade

===show/fdx===
*show/fdx - Show the DX data in realtime format.
Normally SHOW/DX outputs spot data in a different format to the realtime data. This is a deliberate policy (so you can tell the difference between the two). Some logging programs cannot handle this so SHOW/FDX outputs historical data in real time format. This is an alias for: SHOW/DX real

===show/files [<file area> [<string>]]===
*show/files [<file area> [<string>]] - List the contents of a file area
SHOW/FILES on its own will show you a list of the various file areas available on the system. To see the contents of a particular file area type:
SH/FILES <file area>
where <file area> is the name of the file area you want to see the contents of. You can also use shell globbing characters like '*' and '?' in a string to see a selection of files in a file area eg:
SH/FILES bulletins arld*
See also TYPE - to see the contents of a file.

===show/filter===
*show/filter - Show the contents of all the filters you have set
Show the contents of all the filters that are set. This command displays all the filters set - for all the various categories.

===show/hfstats [days] [date]===
*show/hfstats [days] [date] - Show the HF DX Statistics
Show the HF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a <date> (default: today).

===show/hftable [days] [date] [prefix ...]===
*show/hftable [days] [date] [prefix ...] - Show the HF DX Spotter Table
Show the HF DX Spotter table for the list of prefixes for the last <days> no of days (default is 31), starting from a <date> (default: today). If there are no prefixes then it will show the table for your country. Remember that some countries have more than one "DXCC country" in them (eg G :-), to show them (assuming you are not in G already which is specially treated in the code) you must list all the relevant prefixes
sh/hftable g gm gd gi gj gw gu
Note that the prefixes are converted into country codes so you don't have to list all possible prefixes for each country. If you want more or less days than the default simply include the number you require:
sh/hftable 20 pa
If you want to start at a different day, simply add the date in some recognizable form:
sh/hftable 2 25nov02
sh/hftable 2 25-nov-02
sh/hftable 2 021125
sh/hftable 2 25/11/02
This will show the stats for your DXCC for that CQWW contest weekend. You can specify either prefixes or full callsigns (so you can see how you did against all your mates). You can also say 'all' which will then print the worldwide statistics.
sh/hftable all

===show/hops <call> [ann|spots|route|wcy|wwv]===
*show/hops <call> [ann|spots|route|wcy|wwv] - Show the hop counts for a node
This command shows the hop counts set up for a node. You can specify which category you want to see. If you leave the category out then all the categories will be listed.

===show/isolate===
*show/isolate - Show list of ISOLATED nodes

===show/lockout <prefix>|all===
*show/lockout <prefix>|all - Show the list of locked out or excluded callsigns

===show/log [<callsign>]===
*show/log [<callsign>] - Show excerpts from the system log
This command outputs a short section of the system log. On its own it will output a general logfile. With the optional callsign it will show output from the log associated with that callsign.

===show/moon [ndays] [<prefix>|<callsign>]===
*show/moon [ndays] [<prefix>|<callsign>] - Show Moon rise and set times
Show the Moon rise and set times for a (list of) prefixes or callsigns, together with the azimuth and elevation of the sun currently at those locations. If you don't specify any prefixes or callsigns, it will show the times for your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), together with the current azimuth and elevation. In addition, it will show the illuminated fraction of the moons disk. If all else fails it will show the Moonrise and set times for the node that you are connected to. For example:
SH/MOON SH/MOON G1TLH W5UN
You can also use this command to see into the past or the future, so if you want to see yesterday's times then do:
SH/MOON -1
or in three days time:
SH/MOON +3 W9
Up to 366 days can be checked both in the past and in the future. Please note that the rise and set times are given as the UTC times of rise and set on the requested UTC day.

===show/muf <prefix> [<hours>][long]===
*show/muf <prefix> [<hours>][long] - Show the likely propagation to a prefix
This command allow you to estimate the likelihood of you contacting a station with the prefix you have specified. The output assumes a modest power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD). The result predicts the most likely operating frequencies and signal levels for high frequency (shortwave) radio propagation paths on specified days of the year and hours of the day. It is most useful for paths between 250 km and 6000 km, but can be used with reduced accuracy for paths shorter or longer than this. The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and used to predict the MUF given the predicted flux, day of the year, hour of the day and geographic coordinates of the transmitter and receiver. This routine is reasonably accurate for the purposes here, with a claimed RMS error of 3.8 MHz, but much smaller and less complex than the programs used by major shortwave broadcasting organizations, such as the Voice of America. The command will display some header information detailing its assumptions, together with the locations, latitude and longitudes and bearings. It will then show UTC (UT), local time at the other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path(Zen) and the likely signal strengths. Then for each frequency for which the system thinks there is a likelihood of a circuit it prints a value. The value is currently a likely S meter reading based on the conventional 6dB / S point scale. If the value has a '+' appended it means that it is 1/2 an S point stronger. If the value is proceeded by an 'm' it means that there is likely to be much fading and by an 's' that the signal is likely to be noisy. By default SHOW/MUF will show the next two hours worth of data. You can specify anything up to 24 hours worth of data by appending the no of hours required after the prefix. For example:
SH/MUF W
produces:
RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms Location Lat / Long Azim East Dereham, Norfolk 52 41 N 0 57 E 47 United-States-W 43 0 N 87 54 W 299 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0 18 23 11.5 -35 mS0+ mS2 S3 19 0 11.2 -41 mS0+ mS2 S3
indicating that you will have weak, fading circuits on top band and 80m but usable signals on 40m (about S3). inputting:
SH/MUF W 24
will get you the above display, but with the next 24 hours worth of propagation data.
SH/MUF W L 24
SH/MUF W 24 Long
Gives you an estimate of the long path propagation characteristics. It should be noted that the figures will probably not be very useful, nor terrible accurate, but it is included for completeness.

===show/mydx===
*show/mydx - Show the DX data filtered with your spot filter.
SHOW/DX potentially shows all the spots available in the system. Using SHOW/MYDX will, instead, filter the available spots using any spot filter that you have set, first. This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow you to customize the spots that you receive. So if you have said: ACC/SPOT on hf Doing a SHOW/MYDX will now only, ever, show HF spots. All the other options on SH/DX can still be used.

===show/newconfiguration [<node>]===
*show/newconfiguration [<node>] - Show all the nodes and users visible
This command allows you to see all the users that can be seen and the nodes to which they are connected. This command produces essentially the same information as SHOW/CONFIGURATION except that it shows all the duplication of any routes that might be present. It also uses a different format which may not take up quite as much space if you don't have any loops. BE WARNED: the list that is returned can be VERY long!

===show/newconfiguration/node===
*show/newconfiguration/node - Show all the nodes connected locally
Show all the nodes connected to this node in the new format.

===show/node [<callsign> ...]===
*show/node [<callsign> ...] - Show the type and version number of nodes
Show the type and version (if connected) of the nodes specified on the command line. If no callsigns are specified then a sorted list of all the non-user callsigns known to the system will be displayed.

===show/prefix <callsign>===
*show/prefix <callsign> - Interrogate the prefix database
This command takes the <callsign> (which can be a full or partial callsign or a prefix), looks up which internal country number it is and then displays all the relevant prefixes for that country together with the internal country no, the CQ and ITU regions. See also SHOW/DXCC.

===show/program===
*show/program - Show the locations of all the included program modules
Show the name and location where every program module was load from. This is useful for checking where you think you have loaded a .pm file from.

===show/qra <lat> <long>===
*show/qra <lat> <long> - Convert lat/long to a QRA Grid locator
This is a multipurpose command that allows you either to calculate the distance and bearing between two locators or (if only one locator is given on the command line) the distance and bearing from your station to the locator. For example:
SH/QRA IO92Q
SH/QRA JN06 IN73
The first example will show the distance and bearing to the locator from yourself, the second example will calculate the distance and bearing from the first locator to the second. You can use 4 or 6 character locators. It is also possible to convert a latitude and longitude to a locator by using this command with a latitude and longitude as an argument, for example:
SH/QRA 52 41 N 0 58 E

===show/qra <locator> [<locator>]===
*show/qra <locator> [<locator>] - Show distance between QRA Grid locators

===show/qrz <callsign>===
*show/qrz <callsign> - Show any callbook details on a callsign
This command queries the QRZ callbook server on the internet and returns any information available for that callsign. This service is provided for users of this software by http://www.qrz.com See also SHOW/WM7D for an alternative.

===show/registered [<prefix>]===
*show/registered [<prefix>] - Show the registered users

===show/route <callsign> ...===
*show/route <callsign> ... - Show the route to the callsign
This command allows you to see to which node the callsigns specified are connected. It is a sort of inverse sh/config.
sh/route n2tly

===show/satellite <name> [<hours> <interval>]===
*show/satellite <name> [<hours> <interval>] - Show tracking data
Show the tracking data from your location to the satellite of your choice from now on for the next few hours. If you use this command without a satellite name it will display a list of all the satellites known currently to the system. If you give a name then you can obtain tracking data of all the passes that start and finish 5 degrees below the horizon. As default it will give information for the next three hours for every five minute period. You can alter the number of hours and the step size, within certain limits. Each pass in a period is separated with a row of '-----' characters. So for example:
SH/SAT AO-10
SH/SAT FENGYUN1 12 2

===show/startup===
*show/startup - View your own startup script
View the contents of a startup script created with SET/STARTUP.

===show/startup <call>===
*show/startup <call> - View a user startup script

===show/station all [<regex>]===
*show/station all [<regex>] - Show list of users in the system

===show/station [<callsign> ..]===
*show/station [<callsign> ..] - Show information about a callsign
Show the information known about a callsign and whether (and where) that callsign is connected to the cluster.
SH/ST G1TLH
If no callsign is given then show the information for yourself.

===show/sun [ndays] [<prefix>|<callsign>]===
*show/sun [ndays] [<prefix>|<callsign>] - Show sun rise and set times
Show the sun rise and set times for a (list of) prefixes or callsigns, together with the azimuth and elevation of the sun currently at those locations. If you don't specify any prefixes or callsigns, it will show the times for your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), together with the current azimuth and elevation. If all else fails it will show the sunrise and set times for the node that you are connected to. For example:
SH/SUN
SH/SUN G1TLH K9CW ZS
You can also use this command to see into the past or the future, so if you want to see yesterday's times then do:
SH/SUN -1
or in three days time:
SH/SUN +3 W9
Up to 366 days can be checked both in the past and in the future. Please note that the rise and set times are given as the UTC times of rise and set on the requested UTC day.

===show/time [<prefix>|<callsign>]===
*show/time [<prefix>|<callsign>] - Show the local time
If no prefixes or callsigns are given then this command returns the local time and UTC as the computer has it right now. If you give some prefixes then it will show UTC and UTC + the local offset (not including DST) at the prefixes or callsigns that you specify.

===show/usdb [call ..]===
*show/usdb [call ..] - Show information held on the FCC Call database
Show the City and State of a Callsign held on the FCC database if his is being run on this system, eg:
sh/usdb k1xx

===show/vhfstats [days] [date]===
*show/vhfstats [days] [date] - Show the VHF DX Statistics
Show the VHF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a date (default: today).

===show/vhftable [days] [date] [prefix ...]===
*show/vhftable [days] [date] [prefix ...] - Show the VHF DX Spotter Table
Show the VHF DX Spotter table for the list of prefixes for the last <days> no of days (default is 31), starting from a date (default: today). If there are no prefixes then it will show the table for your country. Remember that some countries have more than one "DXCC country" in them (eg G :-), to show them (assuming you are not in G already which is specially treated in the code) you must list all the relevant prefixes:
sh/vhftable g gm gd gi gj gw gu
Note that the prefixes are converted into country codes so you don't have to list all possible prefixes for each country. If you want more or less days than the default simply include the number you require:
sh/vhftable 20 pa
If you want to start at a different day, simply add the date in some recognizable form:
sh/vhftable 2 25nov02
sh/vhftable 2 25-nov-02
sh/vhftable 2 021125
sh/vhftable 2 25/11/02
This will show the stats for your DXCC for that CQWW contest weekend. You can specify either prefixes or full callsigns (so you can see how you did against all your mates). You can also say 'all' which will then print the worldwide statistics.
sh/vhftable all

===show/wcy===
*show/wcy - Show last 10 WCY broadcasts

===show/wcy <n>===
show/wcy <n> - Show last <n> WCY broadcasts
Display the most recent WCY information that has been received by the system.

===show/wm7d <callsign>===
*show/wm7d <callsign> - Show callbook details on a US callsigns
This command queries the WM7D callbook server on the internet and returns any information available for that US callsign. This service is provided for users of this software by http://www.wm7d.net. See also SHOW/QRZ.

===show/wwv===
*show/wwv - Show last 10 WWV broadcasts

===show/wwv <n>===
*show/wwv <n> - Show last <n> WWV broadcasts
Display the most recent WWV information that has been received by the system.

==SHUTDOWN==
===shutdown===
shutdown - Shutdown the cluster
Shutdown the cluster and disconnect all the users

==SPOOF==
===spoof <call> <command>===
*spoof <call> <command> - Do a command as though you are another user
This command is provided so that sysops can set a user's parameters without me having to write a special 'sysop' version for every user command. It allows you to pretend that you are doing the command as the user you specify.eg:
SPOOF G1TLH set/name Dirk
SPOOF G1TLH set/qra JO02LQ

==STAT==
===stat/channel [<callsign>]===
*stat/channel [<callsign>] - Show the status of a channel on the cluster
Show the internal status of the channel object either for the channel that you are on or else for the callsign that you asked for. Only the fields that are defined (in perl term) will be displayed.

===stat/db <dbname>===
*stat/db <dbname> - Show the status of a database
Show the internal status of a database descriptor. Depending on your privilege level you will see more or less information. This command is unlikely to be of much use to anyone other than a sysop.

===stat/msg===
*stat/msg - Show the status of the message system

===stat/msg <msgno>===
*stat/msg <msgno> - Show the status of a message
This command shows the internal status of a message and includes information such as to whom it has been forwarded, its size, origin etc etc. If no message number is given then the status of the message system is displayed.

===stat/route_node <callsign>===
*stat/route_node <callsign> - Show the data in a Route::Node object

===stat/route_node all===
*stat/route_node all - Show list of all Route::Node objects

===stat/route_user <callsign>===
*stat/route_user <callsign> - Show the data in a Route::User object

===stat/route_user all===
*stat/route_user all - Show list of all Route::User objects

===stat/user [<callsign>]===
*stat/user [<callsign>] - Show the full status of a user
Shows the full contents of a user record including all the secret flags and stuff. Only the fields that are defined (in perl term) will be displayed.

==SYSOP==
===sysop===
sysop - Regain your privileges if you login remotely
The system automatically reduces your privilege level to that of anormal user if you login in remotely. This command allows you to regain your normal privilege level. It uses the normal system: five numbers are returned that are indexes into the character array that is your assigned password (see SET/PASSWORD). The indexes start from zero. You are expected to return a string which contains the characters required in the correct order. You may intersperse those characters with others to obscure your reply for any watchers. For example (and these values are for explanation :-):
password = 012345678901234567890123456789 > sysop 22 10 15 17 3
you type:
aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
They will all match. If there is no password you will still be offered numbers but nothing will happen when you input a string. Any match is case sensitive.

==TALK==
===talk <call> > <node> [<text>]===
*talk <call> > <node> [<text>] - Send a text message to another station via a node
Send a short message to any other station that is visible on the cluster system. You can send it to anyone you can see with a SHOW/CONFIGURATION command, they don't have to be connected locally. The second form of TALK is used when other cluster nodes are connected with restricted information. This usually means that they don't send the user information usually associated with logging on and off the cluster. If you know that G3JNB is likely to be present on GB7TLH, but you can only see GB7TLH in the SH/C list but with no users, then you would use the second form of the talk message. If you want to have a ragchew with someone you can leave the text message out and the system will go into 'Talk' mode. What this means is that a short message is sent to the recipient telling them that you are in a 'Talking' frame of mind and then you just type - everything you send will go to the station that you asked for. All the usual announcements, spots and so on will still come out on your terminal. If you want to do something (such as send a spot) you precede the normal command with a '/' character, eg:
/DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
To leave talk mode type:
/EX
If you are in 'Talk' mode, there is an extension to the '/' command which allows you to send the output to all the people you are talking to. You do with the '//' command. For example:
//sh/hftable
will send the hftable as you have it to all the people you are currently talking to.

===talk <call> [<text>]===
*talk <call> [<text>] - Send a text message to another station

==TYPE==
===type <filearea>/<name>===
*type <filearea>/<name> - Look at the contents of a file in one of the file areas
Type out the contents of a file in a file area. So, for example, in file area 'bulletins' you want to look at file 'arld051' you would enter:
TYPE bulletins/arld051
See also SHOW/FILES to see what file areas are available and a list of content.

==UNCATCHUP==
===uncatchup <node call> all|[msgno> ...]===
*uncatchup <node call> all|[msgno> ...] - Unmark a message as sent
When you send messages the fact that you have forwarded it to another node is remembered so that it isn't sent again. When you have a new partner node and you add their callsign to your /spider/msg/forward.pl file, all outstanding non-private messages will be forwarded to them. This may well be ALL the non-private messages. You can prevent this by using these commands:
catchup GB7DJK all
catchup GB7DJK 300 301 302 303 500-510
and to undo what you have just done:
uncatchup GB7DJK all
uncatchup GB7DJK 300 301 302 303 500-510
which will arrange for them to be forward candidates again. Order is not important.

==UNSET==
===unset/announce===
unset/announce - Stop announce messages coming out on your terminal

===unset/anntalk===
*unset/anntalk - Stop talk like announce messages on your terminal
The announce system on legacy cluster nodes is used as a talk substitute because the network is so poorly connected. If you:
unset/anntalk
you will suppress several of these announces, you may miss the odd useful one as well, but you would probably miss them anyway in the welter of useless ones.
set/anntalk
allows you to see them again. This is the default.

===unset/baddx <call>..===
*unset/baddx <call>.. - Propagate a dx spot with this callsign again
Setting a word as 'baddx' will prevent spots with that word in the 'spotted' field (as in: DX 14001.1 FR0G) of a DX spot from going any further. They will not be displayed and they will not be sent onto other nodes. The word must be written in full, no wild cards are allowed eg:
set/baddx FORSALE VIDEO FR0G
To allow a word again, use the following command ...
unset/baddx VIDEO

===unset/badnode <call>..===
*unset/badnode <call>.. - Allow spots from this node again
Setting a callsign as a 'badnode' will prevent spots from that node going any further. They will not be displayed and they will not be sent onto other nodes. The call must be a full eg:
set/badnode K1TTT
will stop anything from K1TTT. If you want SSIDs as well then you must enter them specifically.
unset/badnode K1TTT
will allow spots from him again. Use with extreme care. This command may well be superseded by FILTERing.

===unset/badspotter <call>..===
*unset/badspotter <call>.. - Allow spots from this callsign again
Setting a callsign as a 'badspotter' will prevent spots from this callsign going any further. They will not be displayed and they will not be sent onto other nodes. The call must be written in full, no wild cards are allowed eg:
set/badspotter VE2STN
will stop anything from VE2STN. This command will automatically stop spots from this user, regardless of whether or which SSID he uses. DO NOT USE SSIDs in the callsign, just use the callsign as above or below.
unset/badspotter VE2STN
will allow spots from him again. Use with extreme care. This command may well be superseded by FILTERing.

===unset/badword <word>..===
*unset/badword <word>.. - Propagate things with this word again
Setting a word as a 'badword' will prevent things like spots, announces or talks with this word in the the text part from going any further. They will not be displayed and they will not be sent onto other nodes. The word must be written in full, no wild cards are allowed eg:
set/badword annihilate annihilated annihilation
will stop anything with these words in the text.
unset/badword annihilated
will allow text with this word again.

===unset/beep===
*unset/beep - Stop beeps for DX and other messages on your terminal

===unset/debug <name>===
*unset/debug <name> - Remove a debug level from the debug set
You can choose to log several different levels. The levels are
chan state msg cron connect
You can show what levels you are logging with SHOW/DEBUG

===unset/dx===
*unset/dx - Stop DX messages coming out on your terminal

===unset/dxcq===
*unset/dxcq - Stop CQ Zones on the end of DX announcements
Display both the Spotter's and the Spotted's CQ Zone on the end of a DX announcement (there is just enough room). Some user programs cannot cope with this. The Spotter's CQ is on the RHS of the time, the Spotted's CQ is on the LHS. Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE. Do a STAT/USER to see which flags you have set if you are confused.

===unset/dxgrid===
*unset/dxgrid - Stop QRA Grid Squares on the end of DX announcements
A standard feature which is enabled in version 1.43 and above is that if the spotter's grid square is known it is output on the end of a DX announcement (there is just enough room). Some user programs cannot cope with this. You can use this command to reset (or set)this feature. Conflicts with: SET/DXCQ, SET/DXITU. Do a STAT/USER to see which flags you have set if you are confused.

===unset/dxitu===
*unset/dxitu - Stop ITU Zones on the end of DX announcements
Display both the Spotter's and the Spotted's ITU Zone on the end of a DX announcement (there is just enough room). Some user programs cannot cope with this. The Spotter's ITU is on the RHS of the time, the Spotted's ITU is on the LHS. Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE. Do a STAT/USER to see which flags you have set if you are confused.

===unset/echo===
*unset/echo - Stop the cluster echoing your input
If you are connected via a telnet session, different implementations of telnet handle echo differently depending on whether you are connected via port 23 or some other port. You can use this command to change the setting appropriately. The setting is stored in your user profile. YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.

===unset/email===
*unset/email - Stop personal msgs being forwarded by email
If any personal messages come in for your callsign then you can use these commands to control whether they are forwarded onto your email address. To enable the forwarding do something like:
SET/EMAIL mike.tubby@somewhere.com
You can have more than one email address (each one separated by a space). Emails are forwarded to all the email addresses you specify. You can disable forwarding by:
UNSET/EMAIL

===unset/here===
*unset/here - Tell the system you are absent from your terminal

===unset/hops <call> ann|spots|route|wwv|wcy===
*unset/hops <call> ann|spots|route|wwv|wcy - Unset hop count
Set the hop count for a particular type of broadcast for a node. This command allows you to set up special hop counts for a node for currently: announce, spots, wwv and wcy broadcasts.eg:
set/hops gb7djk ann 10
set/hops gb7mbc spots 20
Set SHOW/HOPS for information on what is already set. This commandcreates a filter and works in conjunction with the filter system. You can unset the hops with command UNSET/HOPS. For example:
unset/hops gb7djk ann
unset/hops gb7mbc spots

===unset/isolate===
*unset/isolate - Stop Isolation of a node from the rest of the network
Remove isolation from a node - SET/ISOLATE

===unset/lockout <call>===
*unset/lockout <call> - Allow a callsign to connect to the cluster

===unset/logininfo===
*unset/logininfo - No longer inform when a station logs in/out locally

===unset/password <call> ...===
*unset/password <call> ... - Delete (remove) a user's password
This command allows the sysop to completely delete and remove a password for a user.

===unset/privilege===
*unset/privilege - Remove any privilege for this session
You can use this command to 'protect' this session from unauthorized use. If you want to get your normal privilege back you will need to either logout and login again (if you are on a console) or use the SYSOP command.

===unset/prompt===
*unset/prompt - Set your prompt back to default
This command will set your user prompt to the string that you say. The point of this command to enable a user to interface to programs that are looking for a specific prompt (or else you just want a different prompt).
SET/PROMPT clx >
There are some substitutions that can be added to the prompt:
%C - callsign [which will have ( and ) around it if not here]
%D - date
%T - time
%M - cluster 'mycall'
The standard prompt is defined as:
SET/PROMPT %C de %M %D %T dxspider >
UNSET/PROMPT will undo the SET/PROMPT command and set your prompt back to normal.

===unset/register <call> ...===
*unset/register <call> ... - Mark a user as not registered
Registration is a concept that you can switch on by executing the
set/var $main::regreq = 1
command (usually in your startup file). If a user is NOT registered then, firstly, instead of the normal motd file (/spider/data/motd) being sent to the user at startup, the user is sent the motd_nor file instead. Secondly, the non-registered user only has READ-ONLY access to the node. The non-registered user cannot use DX, ANN etc. The only exception to this is that a non-registered user can TALK or SEND messages to the sysop.

===unset/startup===
*unset/startup - Remove your own startup script
You can remove your startup script with UNSET/STARTUP.

===unset/startup <call>===
*unset/startup <call> - Remove a user startup script

===unset/talk===
*unset/talk - Stop TALK messages coming out on your terminal

===unset/usstate===
*unset/usstate - Stop US State info on the end of DX announcements
If the spotter's or spotted's US State is known it is output on the end of a DX announcement (there is just enough room). A spotter's state will appear on the RHS of the time (like SET/DXGRID) and the spotted's state will appear on the LHS of thetime field. Any information found will override any locator information from SET/DXGRID. Some user programs cannot cope with this. You can use this command to reset (or set) this feature. Conflicts with: SET/DXCQ, SET/DXITU. Do a STAT/USER to see which flags you have set if you are confused.

===unset/wcy===
*unset/wcy - Stop WCY messages coming out on your terminal

===unset/wwv===
*unset/wwv - Stop WWV messages coming out on your terminal

===unset/wx===
*unset/wx - Stop WX messages coming out on your terminal

==WHO==
===who===
*who - Show who is physically connected
This is a quick listing that shows which callsigns are connected and what sort of connection they have.

==WX==
===wx <text>===
*wx <text> - Send a weather message to local users

===wx full <text>===
*wx full <text> - Send a weather message to all cluster users

===wx sysop <text>===
*wx sysop <text> - Send a weather message to other clusters only
Weather messages can sometimes be useful if you are experiencing an extreme that may indicate enhanced conditions.

Configure Node with more than one local IP (Mojo branch)

2025-04-05T07:28:03Z

G0TRT: Added sh/var @main::localhost_names

NOTE: You do <b>NOT</b> need to fiddle with this unless you specifically have more than just the normal definitions of localhost. So for 'normal' nodes with one external interface, <b>YOU DO NOT NEED TO DO ANY OF THIS</b>.

If you need to configure a node with more than one local IP address, you can do this in the Mojo branch. This allows other IP addresses to be treated in the same way as localhost.

These can be set in the '''/spider/scripts/startup''' file.

The variable '''@main::localhost_names''' is used to achieve this.

You must include ALL the normal localhost names + any other interface names that you might want to include:

set/var @main::localhost_names ('127.0.0.1', '::1', '192.168.1.30', '172.16.0.20')

You can simplify this by using the qw() option, like this ...

set/var @main::localhost_names qw(127.0.0.1 ::1 192.168.1.30 172.16.0.20)

but either will work. You can define as many IP addresses as you like and they can be IPV4 or 6.

To find the Local IPs you can use the following command at the command line:

hostname -I

You can also update the cluster immediately by adding the following line in the console:

set/var @main::localhost_names qw(127.0.0.1 ::1 192.168.1.30 172.16.0.20)

To see what values the cluster has use the following in the console:

sh/var @main::localhost_names

Again, remember You do <b>NOT</b> need to fiddle with this unless you specifically have more than just the normal definitions of localhost. So for 'normal' nodes with one external interface, <b>YOU DO NOT NEED TO DO ANY OF THIS</b>.

There is a script called update_ip.pl (in contributions) that automatically updates this variable.

It can be downloaded at [https://raw.githubusercontent.com/EA3CV/dxspider_info/main/update_ip.pl]

DXSpider Sysop Command Reference

2025-04-05T05:25:57Z

G0TRT: /* debug */ changed the link to commands and levels

==ACCEPT==
* '''accept''' set a filter to accept something
* Create a filter to accept something. There are 2 types of filter, accept and reject. See ''Help Filtering'' for more info.

===accept/announce <call> [input] [0-9] <pattern>===
* '''accept/announce''' <call> [input] [0-9] <pattern> - Announce filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
accept/ann by G,M,2
accept/ann input node_default by G,M,2
accept/ann user_default by G,M,2

===accept/announce [0-9] <pattern>===
*accept/announce [0-9] <pattern> - Set an 'accept' filter line for announce
Create an 'accept this announce' line for a filter. An accept filter line means that if the announce matches this filter it is passed onto the user. See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
info <string> - eg: iota or qsl
by <prefixes> - eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> - eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,NH
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states>
channel <prefixes> wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX
some examples:
acc/ann dest 6MUK
acc/ann 2 by_zone 14,15,16
(this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
or
acc/ann by G,M,2
for american states
acc/ann by_state va,nh,ri,nh
You can use the tag 'all' to accept everything eg:
acc/ann all
but this probably for advanced users...

===accept/route <call> [0-9] <pattern>===
*accept/route <call> [0-9] <pattern> - Set an 'accept' filter line for routing
Create an 'accept this routing PC Protocol' line for a filter. An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter it is passed thru that interface. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:
call <prefixes>
the callsign of the thingy
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,NH
origin <prefixes>
really the interface it came in on
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,NH
some examples:
acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
you can now use 'by' as a synonym for 'call' so:
by = call by_dxcc = call_dxcc
you can use the tag 'all' to accept everything eg:
acc/route all

===accept/spots <call> [input] [0-9] <pattern>===
*accept/spots <call> [input] [0-9] <pattern> - Spot filter sysop version
This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:
accept/spot db0sue-7 1 by_zone 14,15,16
accept/spot node_default all
set/hops node_default 10
accept/spot user_default by G,M,2

===accept/spots [0-9] <pattern>===
*accept/spots [0-9] <pattern> - Set an 'accept' filter line for spots
Create an 'accept this spot' line for a filter. An accept filter line means that if the spot matches this filter it ispassed onto the user. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on <range> same as 'freq'
call <prefixes> eg: G,PA,HB9
info <string> eg: iota or qsl
by <prefixes>
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states> eg: VA,NH,RI,ME
origin <prefixes>
channel <prefixes>
'call' means the callsign that has spotted 'by' whoever. For frequencies, you can use any of the band names defined in SHOW/BANDS and you can use a sub-band name like: cw, rtty, data, ssb -thus: hf/ssb. You can also just have a simple range like: 0/30000 -this is more efficient than saying simply: freq HF (but don't get too hung up about that)some examples:
acc/spot 1 on hf/cw
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
You can use the tag 'all' to accept everything, eg:
acc/spot 3 all
for US states
acc/spots by_state VA,NH,RI,MA,ME
but this probably for advanced users...

===accept/wcy <call> [input] [0-9] <pattern>===
*accept/wcy <call> [input] [0-9] <pattern> - WCY filter sysop version
This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:
accept/wcy node_default all set/hops node_default 10

===accept/wcy [0-9] <pattern>===
*accept/wcy [0-9] <pattern> - set an 'accept' WCY filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them).This command is really provided for future use. See HELP FILTER for information.

===accept/wwv <call> [input] [0-9] <pattern>===
*accept/wwv <call> [input] [0-9] <pattern> - WWV filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
accept/wwv db0sue-7 1 by_zone 4
accept/wwv node_default all set/hops node_default 10
accept/wwv user_default by W,K

===accept/wwv [0-9] <pattern>===
*accept/wwv [0-9] <pattern> - set an 'accept' WWV filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
for example:
accept/wwv by_zone 4
is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). See HELP FILTER for information.

==ANNOUNCE==
===announce <text>===
*announce <text> - Send an announcement to LOCAL users only
<text> is the text of the announcement you wish to broadcast

===announce full <text>===
*announce full <text> - Send an announcement cluster wide
This will send your announcement cluster wide

===announce sysop <text>===
*announce sysop <text> - Send an announcement to Sysops only

==APROPOS==
===apropos <string>===
*apropos <string> - Search help database for <string>
Search the help database for <string> (it isn't case sensitive), and print the names of all the commands that may be relevant.

==BLANK==
===blank [<string>] [<nn>]===
*blank [<string>] [<nn>] - Print nn (default 1) blank lines (or strings)
In its basic form this command prints one or more blank lines. However if you pass it a string it will replicate the string for the width of the screen (default 80) and then print that one or more times, so:
blank 2
prints two blank lines
blank -
prints a row of - characters once.
blank abc
prints 'abcabcabcabcabcabc....'This is really only of any use in a script file and you can print a maximum of 9 lines.

==BYE==
===bye===
*bye - Exit from the cluster
This will disconnect you from the cluster

==CATCHUP==
===catchup <node call> all|[<msgno> ...]===
*catchup <node call> all|[<msgno> ...] - Mark a message as sent

==CHAT==
===chat <group> <text>===
*chat <group> <text> - Chat or Conference to a group
It is now possible to JOIN a group and have network wide conferencing to that group. DXSpider does not (and probably will not) implement the AK1A conference mode as this seems very limiting, is hardly used and doesn't seem to work too well anyway. This system uses the existing ANN system and is compatible with both other DXSpider nodes and AK1A clusters (they use ANN/<group>). You can be a member of as many "groups" as you want. To join a group type:
JOIN FOC (where FOC is the group name)
To leave a group type:
LEAVE FOC
You can see which groups you are in by typing:
STAT/USER
and you can see whether your mate is in the group, if he connects to the same node as you, by typing:
STAT/USER g1tlh
To send a message to a group type:
CHAT FOC hello everyone
or
CH #9000 hello I am back
See also JOIN, LEAVE, SHOW/CHAT

==CLEAR==
===clear/announce <callsign> [input] [0-9|all]===
*clear/announce <callsign> [input] [0-9|all] - Clear a announce filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/announce [1|all]===
*clear/announce [1|all] - Clear a announce filter line
This command allows you to clear (remove) a line in a announce filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

===clear/route <callsign> [input] [0-9|all]===
*clear/route <callsign> [input] [0-9|all] - Clear a route filter line
A sysop can clear an input or normal output filter for a user or then ode_default or user_default.

===clear/route [1|all]===
*clear/route [1|all] - Clear a route filter line
This command allows you to clear (remove) a line in a route filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

===clear/spots <callsign> [input] [0-9|all]===
*clear/spots <callsign> [input] [0-9|all] - Clear a spot filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/spots [0-9|all]===
*clear/spots [0-9|all] - Clear a spot filter line
This command allows you to clear (remove) a line in a spot filter or to remove the whole filter. If you have a filter:
acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
and you say:
clear/spot 1
you will be left with:
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
If you do:
clear/spot all
the filter will be completely removed.

===clear/wcy <callsign> [input] [0-9|all]===
*clear/wcy <callsign> [input] [0-9|all] - Clear a WCY filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/wcy [1|all]===
*clear/wcy [1|all] - Clear a WCY filter line
This command allows you to clear (remove) a line in a WCY filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

===clear/wwv <callsign> [input] [0-9|all]===
*clear/wwv <callsign> [input] [0-9|all] - Clear a WWV filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/wwv [1|all]===
clear/wwv [1|all] - Clear a WWV filter line
This command allows you to clear (remove) a line in a WWV filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

==CONNECT==
===connect <callsign>===
*connect <callsign> - Start a connection to another DX Cluster
Start a connection process that will culminate in a new connection to the DX cluster <callsign>. This process creates a new 'client' process which will use the script in /spider/connect/<callsign> to effect the 'chat' exchange necessary to traverse the network(s) to logon to the cluster <callsign>.

==DBAVAIL==
===dbavail===
*dbavail - Show a list of all the Databases in the system
Title says it all really, this command lists all the databases defined in the system. It is also aliased to SHOW/COMMAND.

==DBCREATE==
===dbcreate <name>===
*dbcreate <name> - Create a database entry

===dbcreate <name> chain <name> [<name>..]===
*dbcreate <name> chain <name> [<name>..] - Create a chained database entry

===dbcreate <name> cmd <dxspider command>===
*dbcreate <name> cmd <dxspider command> - make a local command available as a DB
DBCREATE allows you to define a database in the system. It doesn't actually create anything, just defines it. The databases that are created are simple DB_File hash databases, they are therefore already 'indexed'. You can define a local database with the first form of the command eg:
DBCREATE oblast
You can also chain databases with the addition of the 'chain' keyword. This will search each database one after the other. A typical example is:
DBCREATE sdx_qsl chain sql_ad
No checking is done to see if the any of the chained databases exist, in fact it is usually better to do the above statement first then do each of the chained databases. Databases can exist offsite. To define a database that lives on another node do:
DBCREATE buckmaster remote gb7dxc
Remote databases cannot be chained; however, the last database in a a chain can be a remote database eg:
DBCREATE qsl chain gb7dxc
To see what databases have been defined do:
DBAVAIL (or it will have been aliased to SHOW/COMMAND)
It would be normal for you to add an entry into your local Aliases file to allow people to use the 'SHOW/<dbname>' style syntax. So you would need to add a line like:
's' => [ .. .. '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', .. .. ],
to allow
SH/BUCK g1tlh
to work as they may be used to.You can also make local commands available as 'pseudo' databases. Youcan therefore make spider special commands available as a database. Iimagine that this will be primarily useful for remote access from legacy nodes. For example:-
DBCREATE dxqsl cmd show/dxqsl
You also use one of these databases in a chain. This may be useful locally. See DBIMPORT for the importing of existing AK1A format data to databases. See DBSHOW for generic database enquiry

===dbcreate <name> remote <node>===
*dbcreate <name> remote <node> - Create a remote database entry

==DBIMPORT==
===dbimport <dbname> <filename>===
*dbimport <dbname> <filename> - Import AK1A data into a database
If you want to import or update data in bulk to a database you can use this command. It will either create or update entries into an existing database. For example:
DBIMPORT oblast /tmp/OBLAST.FUL
will import the standard OBLAST database that comes with AK1A into the oblast database held locally.

==DBREMOVE==
===dbremove <dbname>===
*dbremove <dbname> - Delete a database
DBREMOVE will completely remove a database entry and also delete any datafile that is associated with it. There is no warning, no comeback, no safety net. For example:
DBREMOVE oblast
will remove the oblast database from the system and it will also remove the associated data file. I repeat: There is no warning, no comeback, no safety net. You have been warned.

==DBSHOW==
===dbshow <dbname> <key>===
*dbshow <dbname> <key> - Display an entry, if it exists, in a database
This is the generic user interface to the database to the database system. It is expected that the sysop will add an entry to the local Aliases file so that users can use the more familiar AK1A style of enquiry such as:
SH/BUCK G1TLH
but if he hasn't and the database really does exist (use DBAVAIL or SHOW/COMMAND to find out) you can do the same thing with:
DBSHOW buck G1TLH

==DEBUG==
===debug===
*debug - Set the cluster program into debug mode
Executing this command will only have an effect if you are running the cluster in debug mode i.e.
perl -d cluster.pl
It will interrupt the cluster just after the debug command has finished.

The full debug command set is on the [[DXSpider Debug Commands and Levels|debug commands]] page

==DELETE==
===delete/usdb <callsign> ...===
*delete/usdb <callsign> ... - Delete this user from the US State Database
This command will completely remove a one or more callsigns from the US States database. There is NO SECOND CHANCE. It goes without saying that you should use this command CAREFULLY! Note that these callsigns may be re-instated by any weekly updates from the FCC.

===delete/user <callsign> ...===
*delete/user <callsign> ... - Delete this user from the User Database
This command will completely remove a one or more users from the database. There is NO SECOND CHANCE. It goes without saying that you should use this command CAREFULLY!

==DEMONSTRATE==
===demonstrate <call> <command>===
*demonstrate <call> <command> - Demonstrate a command to another user
This command is provided so that sysops can demonstrate commands to other users. It runs a command as though that user had typed it in and then sends the output to that user, together with the command that caused it.
DEMO g7brn sh/dx iota oc209
DEMO g1tlh set/here
Note that this command is similar to SPOOF and will have the same side effects. Commands are run at the privilege of the user which is being demonstrated to.

==DIRECTORY==
===directory===
*directory - List messages

===directory <from>-<to>===
*directory <from>-<to> - List messages <from> message <to> message
List the messages in the messages directory. If there is a 'p' one space after the message number then it is a personal message. If there is a '-' between the message number and the 'p' then this indicates that the message has been read. You can use shell escape characters such as '*' and '?' in the <call>fields. You can combine some of the various directory commands together eg:
DIR TO G1TLH 5
or
DIR SUBJECT IOTA 200-250
You can abbreviate all the commands to one letter and use ak1a syntax:
DIR/T G1* 10
DIR/S QSL 10-100 5

===directory <nn>===
*directory <nn> - List last <nn> messages

===directory all===
*directory all - List all messages

===directory from <call>===
*directory from <call> - List all messages from <call>

===directory new===
*directory new - List all new messages

===directory own===
*directory own - List your own messages

===directory subject <string>===
*directory subject <string> - List all messages with <string> in subject

===directory to <call>===
*directory to <call> - List all messages to <call>

===directory- ===
directory-
Sysops can see all users' messages.

==DISCONNECT==
===disconnect <call> [<call> ...]===
*disconnect <call> [<call> ...] - Disconnect a user or cluster
Disconnect any <call> connected locally

==DX==
===dx [by <call>] <freq> <call> <remarks>===
dx [by <call>] <freq> <call> <remarks> - Send a DX spot
This is how you send a DX Spot to other users. You can, in fact, now enter the <freq> and the <call> either way round.
DX FR0G 144.600
DX 144.600 FR0G
DX 144600 FR0G
will all give the same result. You can add some remarks to the end of the command and they will be added to the spot.
DX FR0G 144600 this is a test
You can credit someone else by saying:
DX by G1TLH FR0G 144.600 he isn't on the cluster
The <freq> is compared against the available bands set up in the cluster. See SHOW/BANDS for more information.

==ECHO==
===echo <line>===
echo <line> - Echo the line to the output
This command is useful in scripts and so forth for printing the line that you give to the command to the output. You can use this in user_default scripts and the SAVE command for titling and so forth. The script will interpret certain standard "escape" sequences as follows:
\t - becomes a TAB character (0x09 in ascii)
\a - becomes a BEEP character (0x07 in ascii)
\n - prints a new line
So the following example:
echo GB7DJK is a dxcluster
produces:
GB7DJK is a dxcluster
on the output. You don't need a \n on the end of the line you want to send.

==EXPORT==
===export <msgno> <filename>===
*export <msgno> <filename> - Export a message to a file
Export a message to a file. This command can only be executed on a local console with a fully privileged user. The file produced will be in a form ready to be imported back into the cluster by placing it in the import directory (/spider/msg/import).This command cannot overwrite an existing file. This is to provide some measure of security. Any files written will owned by the same user as the main cluster, otherwise you can put the new files anywhere the cluster can access. For example:
EXPORT 2345 /tmp/a

===export_users [<filename>]===
*export_users [<filename>] - Export the users database to ascii
Export the users database to a file in ascii format. If no file name is given then it will export the file to /spider/data/user_asc. If the file already exists it will be renamed to <filename>.o. In fact up to 5 generations of the file can be kept each one with an extra 'o' on the suffix. BE WARNED: this will write to any file you have write access to. No check is made on the filename (if any) that you specify.

==FILTERING==
===filtering...===
*filtering... - Filtering things in DXSpider
There are a number of things you can filter in the DXSpider system. They all use the same general mechanism. In general terms you can create a 'reject' or an 'accept' filter which can have up to 10 lines in it. You do this using, for example:
accept/spots .....
reject/spots .....
where ..... are the specific commands for that type of filter. There are filters for spots, wwv, announce, wcy and (for sysops) connects. See each different accept or reject command reference for more details. There is also a command to clear out one or more lines in a filter and one to show you what you have set. They are:
clear/spots 1
clear/spots all
and
show/filter
There is clear/xxxx command for each type of filter. For now we are going to use spots for the examples, but you can apply the principles to all types of filter. There are two main types of filter 'accept' or 'reject'; which you use depends entirely on how you look at the world and what is least writing to achieve what you want. Each filter has 10 lines (of any length) which are tried in order. If a line matches then the action you have specified is taken (ie reject means ignore it and accept means gimme it). The important thing to remember is that if you specify a 'reject' filter (all the lines in it say 'reject/spots' (for instance)) then if a spot comes in that doesn't match any of the lines then you will get it BUT if you specify an 'accept' filter then any spots that don't match are dumped. For example if I have a one line accept filter:
accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
then automatically you will ONLY get VHF spots from or to CQ zones 1415 and 16. If you set a reject filter like:
reject/spots on hf/cw
Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA and will work it even on CW then you could say:
reject/spots on hf/cw and not info iota
But in that case you might only be interested in iota and say:
accept/spots not on hf/cw or info iota
which is exactly the same. You should choose one or the other until you are comfortable with the way it works. Yes, you can mix them (actually you can have an accept AND a reject on the same line) but don't try this at home until you can analyze the results that you get without ringing up the sysop for help. Another useful addition now is filtering by US state
accept/spots by_state VA,NH,RI,ME
You can arrange your filter lines into logical units, either for your own understanding or simply convenience. I have one set frequently:
reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
What this does is to ignore all HF CW spots (being a class B I can't read any CW and couldn't possibly be interested in HF :-) and also rejects any spots on VHF which don't either originate or spot someone in Europe. This is an example where you would use the line number (1 and 2 in this case), if you leave the digit out, the system assumes '1'. Digits'0'-'9' are available. You can leave the word 'and' out if you want, it is implied. You can use any number of brackets to make the 'expression' as you want it. There are things called precedence rules working here which mean that you will NEED brackets in a situation like line 2 because, without it, will assume:
(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
annoying, but that is the way it is. If you use OR - use brackets. Whilst we are here CASE is not important. 'And BY_Zone' is just 'and by_zone'. If you want to alter your filter you can just redefine one or more lines of it or clear out one line. For example:
reject/spots 1 on hf/ssb
or
clear/spots 1
To remove the filter in its entirty:
clear/spots all
There are similar CLEAR commands for the other filters:
clear/announce
clear/wcy
clear/wwv
ADVANCED USERS: Once you are happy with the results you get, you may like to experiment. my example that filters hf/cw spots and accepts vhf/uhf spots from EU can be written with a mixed filter, eg:
rej/spot on hf/cw acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
each filter slot actually has a 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE the accept slot. It was mentioned earlier that after a reject test that doesn't match, the default for following tests is 'accept', the reverse is true for 'accept'. In the example what happens is that the reject is executed first, any non hf/cw spot is passed to the accept line, which lets thru everything else on HF. The next filter line lets through just VHF/UHF spots from EU.

==FORWARD==
===forward/latlong <node_call>===
*forward/latlong <node_call> - Send latitude and longitude information to another cluster
This command sends all the latitude and longitude information that your cluster is holding against callsigns. One advantage of receiving this information is that more locator information is held by you. This means that more locators are given on the DX line assuming you have SET/DXGRID enabled. This could be a LOT of information though, so it is not recommended on slow links.

===forward/opernam <call>===
*forward/opernam <call> - Send out information on this <call> to all clusters
This command sends out any information held in the user file which can be broadcast in PC41 protocol packets. This information is Name, QTH, Locationand Homenode. PC41s are only sent for the information that is available.

==FTx==
===enable/autoftx===
*enable/autoftx - Enable detected automatically generated FTx spots to be output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

===enable/ftx===
*enable/ftx - Enable FTx spots to be output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

===disable/autoftx===
*disable/autoftx - Disable detected automatically generated FTx spots from being output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

===disable/ftx===
*disable/ftx - Disable FTx spots from being output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

==HELP==
===help===
help - The HELP Command
HELP is available for a number of commands. The syntax is:
HELP <cmd>
Where <cmd> is the name of the command you want help on. All commands can be abbreviated, so SHOW/DX can be abbreviated to SH/DX, ANNOUNCE can be shortened to AN and so on. Look at the APROPOS <string> command which will search the help database for the <string> you specify and give you a list of likely commands to look at with HELP.

==INIT==
===init <node>===
*init <node> - Re-initialize a link to an AK1A compatible node
This command attempts to re-initialize a link to a (usually) AK1A node that has got confused, usually by a protocol loop of some kind. It may work - but you usually will be better off simply disconnecting it (or better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your node>). Best of luck - you will need it.

==JOIN==
===join <group>===
*join <group> - Join a chat or conference group
JOIN allows you to join a network wide conference group. To join a group (called FOC in this case) type:
JOIN FOC
See also CHAT, LEAVE, SHOW/CHAT

==KILL==
===kill===
*kill
As a sysop you can kill any message on the system.

===kill <from msgno>-<to msgno>===
*kill <from msgno>-<to msgno> - Delete a range of messages

===kill <from>-<to>===
*kill <from>-<to> - Remove a range of messages from the system

===kill <msgno> [<msgno..]===
*kill <msgno> [<msgno..] - Delete a message from the local system

===kill <msgno> [<msgno> ...]===
*kill <msgno> [<msgno> ...] - Remove or erase a message from the system
You can get rid of any message to or originating from your callsign using this command. You can remove more than one message at a time.

===kill expunge <msgno> [<msgno..]===
*kill expunge <msgno> [<msgno..] - Expunge a message
Deleting a message using the normal KILL commands only marks that message for deletion. The actual deletion only happens later (usually two days later). The KILL EXPUNGE command causes the message to be truly deleted more or less immediately. It otherwise is used in the same way as the KILL command.

===kill from <call>===
*kill from <call> - Remove all messages from a callsign

===kill full <msgno> [<msgno..]===
*kill full <msgno> [<msgno..] - Delete a message from the whole cluster
Delete a message from the local system. You will only be able to delete messages that you have originated or been sent (unless you are the sysop).
KILL 1234-1255
Will delete all the messages that you own between msgnos 1234 and 1255.
KILL from g1tlh
will delete all the messages from g1tlh (if you are g1tlh). Similarly:
KILL to g1tlh
will delete all messages to g1tlh.
KILL FULL 1234
will delete a message (usually a 'bulletin') from the whole cluster system. This uses the subject field, so any messages that have exactly thesame subject will be deleted. Beware!

===kill full <msgno> [<msgno]===
*kill full <msgno> [<msgno] - Remove a message from the entire cluster
Remove this message from the entire cluster system as well as your node.

===kill to <call>===
*kill to <call> - Remove all messages to a callsign

===kill from <regex>===
*kill from <regex> - Delete messages FROM a callsign or pattern

===kill to <regex>===
*kill to <regex> - Delete messages TO a callsign or pattern

==LEAVE==
===leave <group>===
*leave <group> - Leave a chat or conference group
LEAVE allows you to leave a network wide conference group. To leave agroup (called FOC in this case) type:
LEAVE FOC
See also CHAT, JOIN, SHOW/CHAT

==LINKS==
===links===
*links - Show which nodes is physically connected
This is a quick listing that shows which links are connected and some information about them. See WHO for a list of all connections.

==LOAD==
===load/aliases===
*load/aliases - Reload the command alias table
Reload the /spider/cmd/Aliases file after you have edited it. You will need to do this if you change this file whilst the cluster is running in order for the changes to take effect.

===load/badmsg===
*load/badmsg - Reload the bad msg table
Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst the cluster is running. This table contains a number of perl regular expressions which are searched for in the fields targeted of each message. If any of them match then that message is immediately deleted on receipt.

===load/badwords===
*load/badwords - Reload the bad words table
Reload the /spider/data/badwords file if you have changed it manually whilst the cluster is running. This file contains a list of words which, if found on certain text portions of PC protocol, will cause those protocol frames to be rejected. It will all put out a message if any of these words are used on the announce, dx and talk commands. The words can be one or more on a line, lines starting with '#' are ignored.

===load/bands===
*load/bands - Reload the band limits table
Reload the /spider/data/bands.pl file if you have changed it manually whilst the cluster is running.

===load/cmd_cache===
*load/cmd_cache - Reload the automatic command cache
Normally, if you change a command file in the cmd or local_cmd tree it will automatically be picked up by the cluster program. Sometimes it can get confused if you are doing a lot of moving commands about or delete a command in the local_cmd tree and want to use the normal one again. Execute this command to reset everything back to the state it was just after a cluster restart.

===load/forward===
*load/forward - Reload the msg forwarding routing table
Reload the /spider/msg/forward.pl file if you have changed it manually whilst the cluster is running.

===load/keps===
*load/keps - Load new keps data

===load/keps [nn]===
*load/keps [nn] - Load new keps data from message
If there is no message number then reload the current Keps data from the Keps.pm data file. You create this file by running
/spider/perl/convkeps.pl <filename>
on a file containing NASA 2 line keps as a message issued by AMSAT. If there is a message number, then it will take the message, run convkeps.pl on it and then load the data, all in one step. These messages are sent to ALL by GB7DJK (and others) from time to time.

===load/messages===
*load/messages - Reload the system messages file
If you change the /spider/perl/Messages file (usually whilst fiddling/writing new commands) you can have them take effect during a cluster session by executing this command. You need to do this if get something like :
unknown message 'xxxx' in lang 'en'

===load/prefixes===
*load/prefixes - Reload the prefix table
Reload the /spider/data/prefix_data.pl file if you have changed it manually whilst the cluster is running.

==MERGE==
===merge <node> [<no spots>/<no wwv>]===
*merge <node> [<no spots>/<no wwv>] - Ask for the latest spots and WWV
MERGE allows you to bring your spot and wwv database up to date. By default it will request the last 10 spots and 5 WWVs from the node you select. The node must be connected locally. You can request any number of spots or wwv and although they will be appended to your databases they will not duplicate any that have recently been added (the last 2 days for spots and last month for WWV data).

==MSG==
===msg <cmd> <msgno> [data ... ]===
*msg <cmd> <msgno> [data ... ] - Alter various message parameters
Alter message parameters like To, From, Subject, whether private or bulletin or return receipt (RR) is required or whether to keep this message from timing out.
MSG TO <msgno> <call> - change TO callsign to <call>
MSG FRom <msgno> <call> - change FROM callsign to <call>
MSG PRrivate <msgno> - set private flag
MSG NOPRrivate <msgno> - unset private flag
MSG RR <msgno> - set RR flag
MSG NORR <msgno> - unset RR flag
MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
MSG NOKEep <msgno> - unset the keep flag
MSG SUbject <msgno> <new> - change the subject to <new>
MSG WAittime <msgno> - remove any waitting time for this message
MSG NOREad <msgno> - mark message as unread
MSG REad <msgno> - mark message as read
MSG QUeue - queue any outstanding bulletins
MSG QUeue 1 - queue any outstanding private messages
You can look at the status of a message by using:
STAT/MSG <msgno>
This will display more information on the message than DIR does.

==PC==
===pc <call> <text>===
*pc <call> <text> - Send arbitrary text to a connected callsign
Send some arbitrary text to a locally connected callsign. No processing is done on the text. This command allows you to send PC Protocol to unstick things if problems arise (messages get stuck etc). eg:
pc gb7djk PC33^GB7TLH^GB7DJK^400^
or
pc G1TLH Try doing that properly!!!
Send any text you like to the callsign requested. This is used mainly to send PC protocol to connected nodes either for testing or to unstick things. You can also use in the same way as a talk command to a connected user but without any processing, added of "from <blah> to <blah" or whatever.

==PING==
===ping <node call>===
*ping <node call> - Check the link quality between nodes
This command allows you to send a frame to another cluster node on the network and get a return frame. The time it takes to do this is a good indication of the quality of the link. The actual time it takes is output to the console in seconds. Any visible cluster node can be PINGed.

==RCMD==
===rcmd <node call> <cmd>===
*rcmd <node call> <cmd> - Send a command to another DX Cluster
This command allows you to send nearly any command to another DX Cluster node that is connected to the system. Whether you get any output is dependent on a) whether the other system knows that the node callsign of this cluster is in fact a node b) whether the other system is allowing RCMDs from this node and c) whether you have permission to send this command at all.

==READ==
===read===
*read - Read the next unread personal message addressed to you

===read <msgno>===
*read <msgno> - Read the specified message
You can read any messages that are sent as 'non-personal' and also any message either sent by or sent to your callsign.

===read-===
*read-
As a sysop you may read any message on the system

==REJECT==
===reject===
*reject - Set a filter to reject something
Create a filter to reject something. There are 2 types of filter, accept and reject. See HELP FILTERING for more info.

===reject/announce <call> [input] [0-9] <pattern>===
*reject/announce <call> [input] [0-9] <pattern> - Announce filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/ann by G,M,2
reject/ann input node_default by G,M,2
reject/ann user_default by G,M,2

===reject/announce [0-9] <pattern>===
*reject/announce [0-9] <pattern> - Set a 'reject' filter line for announce
Create an 'reject this announce' line for a filter. A reject filter line means that if the announce matches this filter it is passed onto the user. See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
info <string> eg: iota or qsl
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states> eg: VA,NH,RI,ME
channel <prefixes>
wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX
some examples:
rej/ann by_zone 14,15,16 and not by G,M,2
You can use the tag 'all' to reject everything eg:
rej/ann all
but this probably for advanced users...

===reject/route <call> [0-9] <pattern>===
*reject/route <call> [0-9] <pattern> - Set an 'reject' filter line for routing
Create an 'reject this routing PC Protocol' line for a filter. An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter it is NOT passed thru that interface. See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
call <prefixes> the callsign of the thingy
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,ME
origin <prefixes>
really the interface it came in on
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,ME
some examples:
rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
You can use the tag 'all' to reject everything eg:
rej/route all (equiv to [very] restricted mode)
as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.

===reject/spots <call> [input] [0-9] <pattern>===
*reject/spots <call> [input] [0-9] <pattern> - Spot filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/spot db0sue-7 1 by_zone 14,15,16
reject/spot node_default all set/hops node_default 10
reject/spot user_default by G,M,2

===reject/spots [0-9] <pattern>===
*reject/spots [0-9] <pattern> - Set a 'reject' filter line for spots
Create a 'reject this spot' line for a filter. A reject filter line means that if the spot matches this filter it is dumped (not passed on). See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on <range> same as 'freq'
call <prefixes> eg: G,PA,HB9i
nfo <string> eg: iota or qsl
by <prefixes>
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states> eg: VA,NH,RI,ME
origin <prefixes>
channel <prefixes>
'call' means the callsign that has spotted 'by' whoever. For frequencies, you can use any of the band names defined in SHOW/BANDS and you can use a sub-band name like: cw, rtty, data, ssb -thus: hf/ssb. You can also just have a simple range like: 0/30000 -this is more efficient than saying simply: on HF (but don't get too hung up about that)some examples:
rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
You can use the tag 'all' to reject everything eg:
rej/spot 3 all
but this probably for advanced users...

===reject/wcy <call> [input] [0-9] <pattern>===
*reject/wcy <call> [input] [0-9] <pattern> - WCY filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/wcy gb7djk all

===reject/wcy [0-9] <pattern>===
reject/wcy [0-9] <pattern> - set a 'reject' WCY filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them). This command is really provided for future use. See HELP FILTER for information.

===reject/wwv <call> [input] [0-9] <pattern>===
*reject/wwv <call> [input] [0-9] <pattern> - WWV filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/wwv db0sue-7 1 by_zone 4
reject/wwv node_default all
reject/wwv user_default by W

===reject/wwv [0-9] <pattern>===
*reject/wwv [0-9] <pattern> - set a 'reject' WWV filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
for example
reject/wwv by_zone 14,15,16
is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). See HELP FILTER for information.

==REPLY==
===reply===
*reply - Reply (privately) to the last message that you have read

===reply <msgno>===
*reply <msgno> - Reply (privately) to the specified message

===reply b <msgno>===
*reply b <msgno> - Reply as a Bulletin to the specified message

===reply noprivate <msgno>===
*reply noprivate <msgno> - Reply as a Bulletin to the specified message

===reply rr <msgno>===
*reply rr <msgno> - Reply to the specified message with read receipt
You can reply to a message and the subject will automatically have "Re:" inserted in front of it, if it isn't already present. You can also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B that you can use with the SEND command (see SEND for further details)

==SAVE==
===save [-d -t -a] <filename> "<cmd>" [...]===
*save [-d -t -a] <filename> "<cmd>" [...] Save command output to a file
This sysop only command allows you to save the output of one or more commands to a file. For example:
save /spider/packclus/dxstats show/dxstat
will save the output of the normal command "show/dxstat" to the file "dxstats" in the files area. You can have some extra flags to the save which will either date stamp or time stamp or both the filename so:
save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
save -t /tmp/a <cmd> creates /tmp/a_2301Z
save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
The -a flag means append to the file instead of overwriting it. You can have more than one command on the line, to do this you MUST enclose each command in double quotes (") eg:
save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
or
save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
You can only write into places that the cluster has permission for (which is that of the "sysop" user [which had BETTER NOT BE "root"]), you will need to create any directories you want to put stuff in beforehand as well. It is likely that you will want to run these commands in a crontab type situation. You would do that something like:
0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
Note that you still enclose each command with (") characters but you must enclose the entire save command in (') characters. Now in fact, this can be varied if you know what you are doing. See the admin manual for more details.

==SEND==
===send <call> [<call> ...]===
*send <call> [<call> ...] - Send a message to one or more callsigns

===send copy <msgno> <call>===
send copy <msgno> <call> - Send a copy of a message to someone

===send noprivate <call>===
*send noprivate <call> - Send a message to all stations
All the SEND commands will create a message which will be sent either to an individual callsign or to one of the 'bulletin' addresses. SEND <call> on its own acts as though you had typed SEND PRIVATE, that is it will mark the message as personal and send it to the cluster node that that callsign is connected to. If the <call> you have specified is in fact a known bulletin category on your node (eg: ALL) then the message should automatically become a bulletin. You can have more than one callsign in all of the SEND commands. You can have multiple qualifiers so that you can have for example:
SEND RR COPY 123 PRIVATE G1TLH G0RDI
which should send a copy of message 123 to G1TLH and G0RDI and you will receive a read receipt when they have read the message. SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak). SP is an alias for SEND PRIVATE. The system will ask you for a subject. Conventionally this should be no longer than 29 characters for compatibility. Most modern cluster software should accept more. You will now be prompted to start entering your text. You finish the message by entering '/EX' on a new line. For instance:
... bye then Jim 73 Dirk /ex
If you have started a message and you don't want to keep it then you can abandon the message with '/ABORT' on a new line, like:
line 1 line 2 oh I just can't be bothered with this /abort
If you abort the message it will NOT be sent. When you are entering the text of your message, most normal output (such as DX announcements and so on are suppressed and stored for latter display(up to 20 such lines are stored, as new ones come along, so the oldest lines are dropped). Also, you can enter normal commands commands (and get the output immediately) whilst in the middle of a message. You do this by typing the command preceded by a '/' character on a new line, so:
/dx g1tlh 144010 strong signal
Will issue a dx announcement to the rest of the cluster. Also, you can add the output of a command to your message by preceding the command with '//', thus :
//sh/vhftable
This will show YOU the output from SH/VHFTABLE and also store it in the message. You can carry on with the message until you are ready to send it.

===send private <call>===
*send private <call> - Send a personal message

===send rr <call>===
*send rr <call> - Send a message and ask for a read receipt

==SET==
===set/address <your address>===
*set/address <your address> - Record your postal address

===set/announce===
*set/announce - Allow announce messages to come out on your terminal

===set/anntalk===
*set/anntalk - Allow talk like announce messages on your terminal

===set/arcluster <call> [<call>..]===
*set/arcluster <call> [<call>..] - Make the callsign an AR-Cluster node

===set/baddx <call>..===
*set/baddx <call>.. - Stop callsigns in a dx spot being propagated

===set/badnode <call>..===
*set/badnode <call>.. - Stop spots from this node being propagated

===set/badspotter <call>..===
*set/badspotter <call>.. - Stop spots from this callsign being propagated

===set/badword <word>..===
*set/badword <word>.. - Stop things with this word being propagated

===set/bbs <call> [<call>..]===
*set/bbs <call> [<call>..] - Make the callsign a BBS

===set/beep===
*set/beep - Add a beep to DX and other messages on your terminal

===set/clx <call> [<call>..]===
*set/clx <call> [<call>..] - Make the callsign an CLX node

===set/debug <name>===
*set/debug <name> - Add a debug level to the debug set

===set/dx===
*set/dx - Allow DX messages to come out on your terminal

===set/dxcq===
*set/dxcq - Show CQ Zones on the end of DX announcements

===set/dxgrid===
*set/dxgrid - Allow QRA Grid Squares on the end of DX announcements

===set/dxitu===
*set/dxitu - Show ITU Zones on the end of DX announcements

===set/dxnet <call> [<call>..]===
*set/dxnet <call> [<call>..] - Make the callsign an DXNet node

===set/echo===
*set/echo - Make the cluster echo your input

===set/email <email> ...===
*set/email <email> ... - Set email address(es) and forward your personals

===set/external_ip <external_ip>===
*set/external_ip - Set the external IPv4 address for the node and the local terminal masquerade automatically with best effort.

===set/here===
*set/here - Tell the system you are present at your terminal

===set/homenode <node>===
*set/homenode <node> - Set your normal cluster callsign
Tell the cluster system where you normally connect to. Any Messages sent to you will normally find their way there should you not be connected.eg:
SET/HOMENODE gb7djk

===set/hops <call> ann|spots|route|wwv|wcy <n>===
*set/hops <call> ann|spots|route|wwv|wcy <n> - Set hop count

===set/isolate===
*set/isolate - Isolate a node from the rest of the network
Connect a node to your system in such a way that you are a full protocol member of its network and can see all spots on it, but nothing either leaks out from it nor goes back into from the rest of the nodes connected to you. You can potentially connect several nodes in this way.

===set/language <lang>===
*set/language <lang> - Set the language you want to use
You can select the language that you want the cluster to use. Currently the languages available are en (English), de (German), es (Spanish),Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).

===set/location <lat & long>===
*set/location <lat & long> - Set your latitude and longitude

===set/lockout <call>===
*set/lockout <call> - Stop a callsign connecting to the cluster

===set/logininfo===
*set/logininfo - Inform when a station logs in/out locally

===set/name <your name>===
*set/name <your name> - Set your name
Tell the system what your name is eg:
SET/NAME Dirk

===set/node <call> [<call>..]===
*set/node <call> [<call>..] - Make the callsign an AK1A cluster
Tell the system that the call(s) are to be treated as AK1A cluster and fed PC Protocol rather normal user commands.

===set/obscount <count> <call>===
*set/obscount <count> <call> - Set the 'pump-up' obscelence PING counter
From 1.35 onwards neighboring nodes are pinged at regular intervals (see SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up' counter which is decremented on every outgoing ping and then reset to the 'obscount' value on every incoming ping. The default value of this parameter is 2. What this means is that a neighbouring node will be pinged twice at (default) 300 second intervals and if no reply has been heard just before what would be the third attempt, that node is disconnected. If a ping is heard then the obscount is reset to the full value. Using default values, if a node has not responded to a ping within 15 minutes, it is disconnected. You can set this parameter between 1 and 9. It is STRONGLY recommended that you don't change the default.

===set/page <lines per page>===
*set/page <lines per page> - Set the lines per page
Tell the system how many lines you wish on a page when the number of line of output from a command is more than this. The default is 20. Setting it explicitly to 0 will disable paging.
SET/PAGE 30 SET/PAGE 0
The setting is stored in your user profile.

===set/password===
*set/password - Set your own password
This command only works for a 'telnet' user (currently). It will only work if you have a password already set. This initial password can only be set by the sysop. When you execute this command it will ask you for your old password, then ask you to type in your new password twice (to make sure you get it right). You may or may not see the data echoed on the screen as you type, depending on the type of telnet client you have.

===set/password <callsign> <string>===
*set/password <callsign> <string> - Set a users password
The password for a user can only be set by a full sysop. The string can contain any characters. The way this field is used depends on context. If it is being used in the SYSOP command context then you are offered 5 random numbers and you have to supply the corresponding letters. This is now mainly for ax25 connections. If it is being used on incoming telnet connections then, if a password is set or the:
set/var $main::passwdreq = 1
command is executed in the startup script, then a password prompt is given after the normal 'login:' prompt.

===set/pinginterval <time> <nodecall>===
*set/pinginterval <time> <nodecall> - Set ping time to neighbouring nodes
As from release 1.35 all neighbouring nodes are pinged at regular intervals in order to determine the rolling quality of the link and, in future, to affect routing decisions. The default interval is 300 secs or 5 minutes. You can use this command to set a different interval. Please don't. But if you do the value you enter is treated as minutes up 30 and seconds for numbers greater than that. This is used also to help determine when a link is down at the far end(as certain cluster software doesn't always notice), see SET/OBSCOUNT for more information. If you must change it (and it may be useful for internet connected nodes on dynamic IP addresses that go away after a set time of usage) the time can be specified as:
5 which if less than 30 is converted to minutes otherwise is taken as the no of seconds between pings.
120s 120 seconds
5m 5 minutes
1h 1 hour
Please be aware that this causes traffic to occur on the link, setting this value too low may annoy your neighbours beyond the point of endurance! You can switch this off by setting it to 0.

===set/privilege <n> <call> [<call..]===
*set/privilege <n> <call> [<call..] - Set privilege level on a call
Set the privilege level on a callsign. The privilege levels that pertain to commands are as default:
0 - normal user
1 - allow remote nodes normal user RCMDs
5 - various privileged commands (including shutdown, but not disconnect), the normal level for another node.
8 - more privileged commands (including disconnect)
9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS LEVEL.
If you are a sysop and you come in as a normal user on a remote connection your privilege will automatically be set to 0.

===set/prompt <string>===
*set/prompt <string> - Set your prompt to <string>

===set/qra <locator>===
*set/qra <locator> - Set your QRA Grid locator
Tell the system what your QRA (or Maidenhead) locator is. If you have not done a SET/LOCATION then your latitude and longitude will be set roughly correctly (assuming your locator is correct ;-). For example:
SET/QRA JO02LQ

===set/qth <your qth>===
*set/qth <your qth> - Set your QTH
Tell the system where you are. For example:
SET/QTH East Dereham, Norfolk

===set/register <call> ...===
set/register <call> ... - Mark a user as registered

===set/spider <call> [<call>..]===
*set/spider <call> [<call>..] - Make the callsign an DXSpider node
Tell the system that the call(s) are to be treated as DXSpider node and fed new style DX Protocol rather normal user commands.

===set/startup===
*set/startup - Create your own startup script
Create a startup script of DXSpider commands which will be executed every time that you login into this node. You can only input the whole script afresh, it is not possible to 'edit' it. Inputting a new script is just like typing in a message using SEND. To finish inputting type: /EX on a newline, to abandon the script type: /ABORT. You may find the (curiously named) command BLANK useful to break up the output. If you simply want a blank line, it is easier to input one or more spaces and press the <return> key. See UNSET/STARTUP to remove a script.

===set/startup <call>===
*set/startup <call> - Create a user startup script

===set/sys_location <lat & long>===
*set/sys_location <lat & long> - Set your cluster latitude and longitude
In order to get accurate headings and such like you must tell the system what your latitude and longitude is. If you have not yet done a SET/QRA then this command will set your QRA locator for you. For example:
SET/LOCATION 52 22 N 0 57 E

===set/sys_qra <locator>===
*set/sys_qra <locator> - Set your cluster QRA Grid locator

===set/talk===
*set/talk - Allow TALK messages to come out on your terminal

===set/usdb <call> <state> <city>===
*set/usdb <call> <state> <city> - add/update a US DB callsign
This command allows you to add or alter a callsign in the US state database. Use with extreme caution. Anything you do here will be overwritten by any weekly updates that affect this callsign
set/usdb g1tlh nh downtown rindge
see also DELETE/USDB

===set/usstate===
*set/usstate - Allow US State info on the end of DX announcements

===set/wcy===
*set/wcy - Allow WCY messages to come out on your terminal

===set/wwv===
*set/wwv - Allow WWV messages to come out on your terminal

===set/wx===
*set/wx - Allow WX messages to come out on your terminal

==SHOW==
===show/baddx===
*show/baddx - Show all the bad dx calls in the system
Display all the bad dx callsigns in the system, see SET/BADDX for more information.

===show/badnode===
*show/badnode - Show all the bad nodes in the system
Display all the bad node callsigns in the system, see SET/BADNODE for more information.

===show/badspotter===
*show/badspotter - Show all the bad spotters in the system
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER for more information.

===show/badword===
*show/badword - Show all the bad words in the system
Display all the bad words in the system, see SET/BADWORD for more information.

===show/chat [<group>] [<lines>]===
*show/chat [<group>] [<lines>] - Show any chat or conferencing
This command allows you to see any chat or conferencing that has occurred whilst you were away. SHOW/CHAT on its own will show data for all groups. If you use a group name then it will show only chat for that group.

===show/configuration [<node>]===
*show/configuration [<node>] - Show all the nodes and users visible
This command allows you to see all the users that can be seen and the nodes to which they are connected. This command is normally abbreviated to: sh/c. Normally, the list returned will be just for the nodes from your country (because the list otherwise will be very long).
SH/C ALL
will produce a complete list of all nodes. BE WARNED: the list that is returned can be VERY long. It is possible to supply a node or part of a prefix and you will get a list of the users for that node or list of nodes starting with that prefix.
SH/C GB7DJK
SH/C SK

===show/configuration/node===
*show/configuration/node - Show all the nodes connected locally
Show all the nodes connected to this node.

===show/connect===
*show/connect - Show all the active connections
This command shows information on all the active connections known to the node. This command gives slightly more information than WHO.

===show/contest <year and month>===
*show/contest <year and month> - Show all the contests for a month
Show all known contests which are maintained at http://www.sk3bg.se/contest/ for a particular month or year. The format is reasonably flexible. For example:
SH/CONTEST sep2003
SH/CONTEST 03 march

===show/date [<prefix>|<callsign>]===
*show/date [<prefix>|<callsign>] - Show the local time
This is very nearly the same as SHOW/TIME, the only difference the format of the date string if no arguments are given. If no prefixes or callsigns are given then this command returns the local time and UTC as the computer has it right now. If you give some prefixes then it will show UTC and UTC + the local offset (not including DST) at the prefixes or callsigns that you specify.

===show/db0sdx <callsign>===
*show/db0sdx <callsign> - Show QSL information from DB0SDX database
This command queries the DB0SDX QSL server on the internet and returns any information available for that callsign. This service is provided for users of this software by http://www.qslinfo.de. See also SHOW/QRZ, SHOW/WM7D.

===show/debug===
*show/debug - Show what levels of debug information you are logging

===show/dup_ann===
*show/dup_ann - Show duplicate announcement records

===show/dup_spots===
*show/dup_spots - Show duplicate spot records

===show/dx===
*show/dx - Interrogate the spot database
If you just type SHOW/DX you will get the last so many spots (sysop configurable, but usually 10). In addition you can add any number of these commands in very nearly any order to the basic SHOW/DX command, they are:
on <band> - eg 160m 20m 2m 23cm 6mm
on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
on <from>/<to> - eg 1000/4000 14000-30000 (in Khz) <from>-<to>
<number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
<prefix> - for a spotted callsign beginning with <prefix>
*<suffix> - for a spotted callsign ending in <suffix>
*<string>* - for a spotted callsign containing <string>
day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
info <text> - any spots containing <text> in the info or remarks
by <call> - any spots spotted by <call> (spotter <call> is the same).
qsl - this automatically looks for any qsl info on the call held in the spot database.
iota [<iota>] - If the iota island number is missing it will look for the string iota and anything which looks like an iota island number. If you specify then it will look for that island.
qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2 You can also use this with the 'by' keyword so eg by W dxcc
real or rt - Format the output the same as for real time spots. The formats are deliberately different (so you can tell one sort from the other). This is useful for some logging programs that can't cope with normal sh/dx output. An alias of SHOW/FDX is available.
filter - Filter the spots, before output, with the user's spot filter. An alias of SHOW/MYDX is available.
zone <zones> - look for spots in the cq zone (or zones) specified. zones are numbers separated by commas.
by_zone <zones> - look for spots spotted by people in the cq zone specified.
itu <itus> - look for spots in the itu zone (or zones) specified itu zones are numbers separated by commas.
by_itu <itus> - look for spots spotted by people in the itu zone specified.
state <list> - look for spots in the US state (or states) specified The list is two letter state codes separated by commas.
by_state <list> - look for spots spotted by people in the US state specified.
e.g.
SH/DX 9m0
SH/DX on 20m info iota
SH/DX 9a on vhf day 30
SH/DX rf1p qsl
SH/DX iota
SH/DX iota eu-064
SH/DX qra jn86
SH/DX dxcc oq2
SH/DX dxcc oq2 by w dxcc
SH/DX zone 4,5,6
SH/DX by_zone 4,5,6
SH/DX state in,oh
SH/DX by_state in,oh

===show/dxcc <prefix>===
*show/dxcc <prefix> - Interrogate the spot database by country
This command takes the <prefix> (which can be a full or partial callsign if desired), looks up which internal country number it is and then displays all the spots as per SH/DX for that country. This is now an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this command. e.g.
SH/DXCC G SH/DXCC W on 20m iota
This can be done with the SHOW/DX command like this:
SH/DX dxcc g
SH/DX dxcc w on 20m iota
This is an alias for: SH/DX dxcc

===show/dxqsl <callsign>===
*show/dxqsl <callsign> - Show any QSL info gathered from spots
The node collects information from the comment fields in spots (things like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database. This command allows you to interrogate that database and if the callsign is found will display the manager(s) that people have spotted. This information is NOT reliable, but it is normally reasonably accurate if it is spotted enough times. For example:
sh/dxqsl 4k9w
You can check the raw input spots yourself with:
sh/dx 4k9w qsl
This gives you more background information.

===show/dxstats [days] [date]===
*show/dxstats [days] [date] - Show the DX Statistics
Show the total DX spots for the last <days> no of days (default is 31), starting from a <date> (default: today).

===show/external_ip===
*show/external_ip - Show the external IP set/detected for the node and local terminal masquerade

===show/fdx===
*show/fdx - Show the DX data in realtime format.
Normally SHOW/DX outputs spot data in a different format to the realtime data. This is a deliberate policy (so you can tell the difference between the two). Some logging programs cannot handle this so SHOW/FDX outputs historical data in real time format. This is an alias for: SHOW/DX real

===show/files [<file area> [<string>]]===
*show/files [<file area> [<string>]] - List the contents of a file area
SHOW/FILES on its own will show you a list of the various file areas available on the system. To see the contents of a particular file area type:
SH/FILES <file area>
where <file area> is the name of the file area you want to see the contents of. You can also use shell globbing characters like '*' and '?' in a string to see a selection of files in a file area eg:
SH/FILES bulletins arld*
See also TYPE - to see the contents of a file.

===show/filter===
*show/filter - Show the contents of all the filters you have set
Show the contents of all the filters that are set. This command displays all the filters set - for all the various categories.

===show/hfstats [days] [date]===
*show/hfstats [days] [date] - Show the HF DX Statistics
Show the HF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a <date> (default: today).

===show/hftable [days] [date] [prefix ...]===
*show/hftable [days] [date] [prefix ...] - Show the HF DX Spotter Table
Show the HF DX Spotter table for the list of prefixes for the last <days> no of days (default is 31), starting from a <date> (default: today). If there are no prefixes then it will show the table for your country. Remember that some countries have more than one "DXCC country" in them (eg G :-), to show them (assuming you are not in G already which is specially treated in the code) you must list all the relevant prefixes
sh/hftable g gm gd gi gj gw gu
Note that the prefixes are converted into country codes so you don't have to list all possible prefixes for each country. If you want more or less days than the default simply include the number you require:
sh/hftable 20 pa
If you want to start at a different day, simply add the date in some recognizable form:
sh/hftable 2 25nov02
sh/hftable 2 25-nov-02
sh/hftable 2 021125
sh/hftable 2 25/11/02
This will show the stats for your DXCC for that CQWW contest weekend. You can specify either prefixes or full callsigns (so you can see how you did against all your mates). You can also say 'all' which will then print the worldwide statistics.
sh/hftable all

===show/hops <call> [ann|spots|route|wcy|wwv]===
*show/hops <call> [ann|spots|route|wcy|wwv] - Show the hop counts for a node
This command shows the hop counts set up for a node. You can specify which category you want to see. If you leave the category out then all the categories will be listed.

===show/isolate===
*show/isolate - Show list of ISOLATED nodes

===show/lockout <prefix>|all===
*show/lockout <prefix>|all - Show the list of locked out or excluded callsigns

===show/log [<callsign>]===
*show/log [<callsign>] - Show excerpts from the system log
This command outputs a short section of the system log. On its own it will output a general logfile. With the optional callsign it will show output from the log associated with that callsign.

===show/moon [ndays] [<prefix>|<callsign>]===
*show/moon [ndays] [<prefix>|<callsign>] - Show Moon rise and set times
Show the Moon rise and set times for a (list of) prefixes or callsigns, together with the azimuth and elevation of the sun currently at those locations. If you don't specify any prefixes or callsigns, it will show the times for your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), together with the current azimuth and elevation. In addition, it will show the illuminated fraction of the moons disk. If all else fails it will show the Moonrise and set times for the node that you are connected to. For example:
SH/MOON SH/MOON G1TLH W5UN
You can also use this command to see into the past or the future, so if you want to see yesterday's times then do:
SH/MOON -1
or in three days time:
SH/MOON +3 W9
Up to 366 days can be checked both in the past and in the future. Please note that the rise and set times are given as the UTC times of rise and set on the requested UTC day.

===show/muf <prefix> [<hours>][long]===
*show/muf <prefix> [<hours>][long] - Show the likely propagation to a prefix
This command allow you to estimate the likelihood of you contacting a station with the prefix you have specified. The output assumes a modest power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD). The result predicts the most likely operating frequencies and signal levels for high frequency (shortwave) radio propagation paths on specified days of the year and hours of the day. It is most useful for paths between 250 km and 6000 km, but can be used with reduced accuracy for paths shorter or longer than this. The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and used to predict the MUF given the predicted flux, day of the year, hour of the day and geographic coordinates of the transmitter and receiver. This routine is reasonably accurate for the purposes here, with a claimed RMS error of 3.8 MHz, but much smaller and less complex than the programs used by major shortwave broadcasting organizations, such as the Voice of America. The command will display some header information detailing its assumptions, together with the locations, latitude and longitudes and bearings. It will then show UTC (UT), local time at the other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path(Zen) and the likely signal strengths. Then for each frequency for which the system thinks there is a likelihood of a circuit it prints a value. The value is currently a likely S meter reading based on the conventional 6dB / S point scale. If the value has a '+' appended it means that it is 1/2 an S point stronger. If the value is proceeded by an 'm' it means that there is likely to be much fading and by an 's' that the signal is likely to be noisy. By default SHOW/MUF will show the next two hours worth of data. You can specify anything up to 24 hours worth of data by appending the no of hours required after the prefix. For example:
SH/MUF W
produces:
RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms Location Lat / Long Azim East Dereham, Norfolk 52 41 N 0 57 E 47 United-States-W 43 0 N 87 54 W 299 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0 18 23 11.5 -35 mS0+ mS2 S3 19 0 11.2 -41 mS0+ mS2 S3
indicating that you will have weak, fading circuits on top band and 80m but usable signals on 40m (about S3). inputting:
SH/MUF W 24
will get you the above display, but with the next 24 hours worth of propagation data.
SH/MUF W L 24
SH/MUF W 24 Long
Gives you an estimate of the long path propagation characteristics. It should be noted that the figures will probably not be very useful, nor terrible accurate, but it is included for completeness.

===show/mydx===
*show/mydx - Show the DX data filtered with your spot filter.
SHOW/DX potentially shows all the spots available in the system. Using SHOW/MYDX will, instead, filter the available spots using any spot filter that you have set, first. This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow you to customize the spots that you receive. So if you have said: ACC/SPOT on hf Doing a SHOW/MYDX will now only, ever, show HF spots. All the other options on SH/DX can still be used.

===show/newconfiguration [<node>]===
*show/newconfiguration [<node>] - Show all the nodes and users visible
This command allows you to see all the users that can be seen and the nodes to which they are connected. This command produces essentially the same information as SHOW/CONFIGURATION except that it shows all the duplication of any routes that might be present. It also uses a different format which may not take up quite as much space if you don't have any loops. BE WARNED: the list that is returned can be VERY long!

===show/newconfiguration/node===
*show/newconfiguration/node - Show all the nodes connected locally
Show all the nodes connected to this node in the new format.

===show/node [<callsign> ...]===
*show/node [<callsign> ...] - Show the type and version number of nodes
Show the type and version (if connected) of the nodes specified on the command line. If no callsigns are specified then a sorted list of all the non-user callsigns known to the system will be displayed.

===show/prefix <callsign>===
*show/prefix <callsign> - Interrogate the prefix database
This command takes the <callsign> (which can be a full or partial callsign or a prefix), looks up which internal country number it is and then displays all the relevant prefixes for that country together with the internal country no, the CQ and ITU regions. See also SHOW/DXCC.

===show/program===
*show/program - Show the locations of all the included program modules
Show the name and location where every program module was load from. This is useful for checking where you think you have loaded a .pm file from.

===show/qra <lat> <long>===
*show/qra <lat> <long> - Convert lat/long to a QRA Grid locator
This is a multipurpose command that allows you either to calculate the distance and bearing between two locators or (if only one locator is given on the command line) the distance and bearing from your station to the locator. For example:
SH/QRA IO92Q
SH/QRA JN06 IN73
The first example will show the distance and bearing to the locator from yourself, the second example will calculate the distance and bearing from the first locator to the second. You can use 4 or 6 character locators. It is also possible to convert a latitude and longitude to a locator by using this command with a latitude and longitude as an argument, for example:
SH/QRA 52 41 N 0 58 E

===show/qra <locator> [<locator>]===
*show/qra <locator> [<locator>] - Show distance between QRA Grid locators

===show/qrz <callsign>===
*show/qrz <callsign> - Show any callbook details on a callsign
This command queries the QRZ callbook server on the internet and returns any information available for that callsign. This service is provided for users of this software by http://www.qrz.com See also SHOW/WM7D for an alternative.

===show/registered [<prefix>]===
*show/registered [<prefix>] - Show the registered users

===show/route <callsign> ...===
*show/route <callsign> ... - Show the route to the callsign
This command allows you to see to which node the callsigns specified are connected. It is a sort of inverse sh/config.
sh/route n2tly

===show/satellite <name> [<hours> <interval>]===
*show/satellite <name> [<hours> <interval>] - Show tracking data
Show the tracking data from your location to the satellite of your choice from now on for the next few hours. If you use this command without a satellite name it will display a list of all the satellites known currently to the system. If you give a name then you can obtain tracking data of all the passes that start and finish 5 degrees below the horizon. As default it will give information for the next three hours for every five minute period. You can alter the number of hours and the step size, within certain limits. Each pass in a period is separated with a row of '-----' characters. So for example:
SH/SAT AO-10
SH/SAT FENGYUN1 12 2

===show/startup===
*show/startup - View your own startup script
View the contents of a startup script created with SET/STARTUP.

===show/startup <call>===
*show/startup <call> - View a user startup script

===show/station all [<regex>]===
*show/station all [<regex>] - Show list of users in the system

===show/station [<callsign> ..]===
*show/station [<callsign> ..] - Show information about a callsign
Show the information known about a callsign and whether (and where) that callsign is connected to the cluster.
SH/ST G1TLH
If no callsign is given then show the information for yourself.

===show/sun [ndays] [<prefix>|<callsign>]===
*show/sun [ndays] [<prefix>|<callsign>] - Show sun rise and set times
Show the sun rise and set times for a (list of) prefixes or callsigns, together with the azimuth and elevation of the sun currently at those locations. If you don't specify any prefixes or callsigns, it will show the times for your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), together with the current azimuth and elevation. If all else fails it will show the sunrise and set times for the node that you are connected to. For example:
SH/SUN
SH/SUN G1TLH K9CW ZS
You can also use this command to see into the past or the future, so if you want to see yesterday's times then do:
SH/SUN -1
or in three days time:
SH/SUN +3 W9
Up to 366 days can be checked both in the past and in the future. Please note that the rise and set times are given as the UTC times of rise and set on the requested UTC day.

===show/time [<prefix>|<callsign>]===
*show/time [<prefix>|<callsign>] - Show the local time
If no prefixes or callsigns are given then this command returns the local time and UTC as the computer has it right now. If you give some prefixes then it will show UTC and UTC + the local offset (not including DST) at the prefixes or callsigns that you specify.

===show/usdb [call ..]===
*show/usdb [call ..] - Show information held on the FCC Call database
Show the City and State of a Callsign held on the FCC database if his is being run on this system, eg:
sh/usdb k1xx

===show/vhfstats [days] [date]===
*show/vhfstats [days] [date] - Show the VHF DX Statistics
Show the VHF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a date (default: today).

===show/vhftable [days] [date] [prefix ...]===
*show/vhftable [days] [date] [prefix ...] - Show the VHF DX Spotter Table
Show the VHF DX Spotter table for the list of prefixes for the last <days> no of days (default is 31), starting from a date (default: today). If there are no prefixes then it will show the table for your country. Remember that some countries have more than one "DXCC country" in them (eg G :-), to show them (assuming you are not in G already which is specially treated in the code) you must list all the relevant prefixes:
sh/vhftable g gm gd gi gj gw gu
Note that the prefixes are converted into country codes so you don't have to list all possible prefixes for each country. If you want more or less days than the default simply include the number you require:
sh/vhftable 20 pa
If you want to start at a different day, simply add the date in some recognizable form:
sh/vhftable 2 25nov02
sh/vhftable 2 25-nov-02
sh/vhftable 2 021125
sh/vhftable 2 25/11/02
This will show the stats for your DXCC for that CQWW contest weekend. You can specify either prefixes or full callsigns (so you can see how you did against all your mates). You can also say 'all' which will then print the worldwide statistics.
sh/vhftable all

===show/wcy===
*show/wcy - Show last 10 WCY broadcasts

===show/wcy <n>===
show/wcy <n> - Show last <n> WCY broadcasts
Display the most recent WCY information that has been received by the system.

===show/wm7d <callsign>===
*show/wm7d <callsign> - Show callbook details on a US callsigns
This command queries the WM7D callbook server on the internet and returns any information available for that US callsign. This service is provided for users of this software by http://www.wm7d.net. See also SHOW/QRZ.

===show/wwv===
*show/wwv - Show last 10 WWV broadcasts

===show/wwv <n>===
*show/wwv <n> - Show last <n> WWV broadcasts
Display the most recent WWV information that has been received by the system.

==SHUTDOWN==
===shutdown===
shutdown - Shutdown the cluster
Shutdown the cluster and disconnect all the users

==SPOOF==
===spoof <call> <command>===
*spoof <call> <command> - Do a command as though you are another user
This command is provided so that sysops can set a user's parameters without me having to write a special 'sysop' version for every user command. It allows you to pretend that you are doing the command as the user you specify.eg:
SPOOF G1TLH set/name Dirk
SPOOF G1TLH set/qra JO02LQ

==STAT==
===stat/channel [<callsign>]===
*stat/channel [<callsign>] - Show the status of a channel on the cluster
Show the internal status of the channel object either for the channel that you are on or else for the callsign that you asked for. Only the fields that are defined (in perl term) will be displayed.

===stat/db <dbname>===
*stat/db <dbname> - Show the status of a database
Show the internal status of a database descriptor. Depending on your privilege level you will see more or less information. This command is unlikely to be of much use to anyone other than a sysop.

===stat/msg===
*stat/msg - Show the status of the message system

===stat/msg <msgno>===
*stat/msg <msgno> - Show the status of a message
This command shows the internal status of a message and includes information such as to whom it has been forwarded, its size, origin etc etc. If no message number is given then the status of the message system is displayed.

===stat/route_node <callsign>===
*stat/route_node <callsign> - Show the data in a Route::Node object

===stat/route_node all===
*stat/route_node all - Show list of all Route::Node objects

===stat/route_user <callsign>===
*stat/route_user <callsign> - Show the data in a Route::User object

===stat/route_user all===
*stat/route_user all - Show list of all Route::User objects

===stat/user [<callsign>]===
*stat/user [<callsign>] - Show the full status of a user
Shows the full contents of a user record including all the secret flags and stuff. Only the fields that are defined (in perl term) will be displayed.

==SYSOP==
===sysop===
sysop - Regain your privileges if you login remotely
The system automatically reduces your privilege level to that of anormal user if you login in remotely. This command allows you to regain your normal privilege level. It uses the normal system: five numbers are returned that are indexes into the character array that is your assigned password (see SET/PASSWORD). The indexes start from zero. You are expected to return a string which contains the characters required in the correct order. You may intersperse those characters with others to obscure your reply for any watchers. For example (and these values are for explanation :-):
password = 012345678901234567890123456789 > sysop 22 10 15 17 3
you type:
aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
They will all match. If there is no password you will still be offered numbers but nothing will happen when you input a string. Any match is case sensitive.

==TALK==
===talk <call> > <node> [<text>]===
*talk <call> > <node> [<text>] - Send a text message to another station via a node
Send a short message to any other station that is visible on the cluster system. You can send it to anyone you can see with a SHOW/CONFIGURATION command, they don't have to be connected locally. The second form of TALK is used when other cluster nodes are connected with restricted information. This usually means that they don't send the user information usually associated with logging on and off the cluster. If you know that G3JNB is likely to be present on GB7TLH, but you can only see GB7TLH in the SH/C list but with no users, then you would use the second form of the talk message. If you want to have a ragchew with someone you can leave the text message out and the system will go into 'Talk' mode. What this means is that a short message is sent to the recipient telling them that you are in a 'Talking' frame of mind and then you just type - everything you send will go to the station that you asked for. All the usual announcements, spots and so on will still come out on your terminal. If you want to do something (such as send a spot) you precede the normal command with a '/' character, eg:
/DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
To leave talk mode type:
/EX
If you are in 'Talk' mode, there is an extension to the '/' command which allows you to send the output to all the people you are talking to. You do with the '//' command. For example:
//sh/hftable
will send the hftable as you have it to all the people you are currently talking to.

===talk <call> [<text>]===
*talk <call> [<text>] - Send a text message to another station

==TYPE==
===type <filearea>/<name>===
*type <filearea>/<name> - Look at the contents of a file in one of the file areas
Type out the contents of a file in a file area. So, for example, in file area 'bulletins' you want to look at file 'arld051' you would enter:
TYPE bulletins/arld051
See also SHOW/FILES to see what file areas are available and a list of content.

==UNCATCHUP==
===uncatchup <node call> all|[msgno> ...]===
*uncatchup <node call> all|[msgno> ...] - Unmark a message as sent
When you send messages the fact that you have forwarded it to another node is remembered so that it isn't sent again. When you have a new partner node and you add their callsign to your /spider/msg/forward.pl file, all outstanding non-private messages will be forwarded to them. This may well be ALL the non-private messages. You can prevent this by using these commands:
catchup GB7DJK all
catchup GB7DJK 300 301 302 303 500-510
and to undo what you have just done:
uncatchup GB7DJK all
uncatchup GB7DJK 300 301 302 303 500-510
which will arrange for them to be forward candidates again. Order is not important.

==UNSET==
===unset/announce===
unset/announce - Stop announce messages coming out on your terminal

===unset/anntalk===
*unset/anntalk - Stop talk like announce messages on your terminal
The announce system on legacy cluster nodes is used as a talk substitute because the network is so poorly connected. If you:
unset/anntalk
you will suppress several of these announces, you may miss the odd useful one as well, but you would probably miss them anyway in the welter of useless ones.
set/anntalk
allows you to see them again. This is the default.

===unset/baddx <call>..===
*unset/baddx <call>.. - Propagate a dx spot with this callsign again
Setting a word as 'baddx' will prevent spots with that word in the 'spotted' field (as in: DX 14001.1 FR0G) of a DX spot from going any further. They will not be displayed and they will not be sent onto other nodes. The word must be written in full, no wild cards are allowed eg:
set/baddx FORSALE VIDEO FR0G
To allow a word again, use the following command ...
unset/baddx VIDEO

===unset/badnode <call>..===
*unset/badnode <call>.. - Allow spots from this node again
Setting a callsign as a 'badnode' will prevent spots from that node going any further. They will not be displayed and they will not be sent onto other nodes. The call must be a full eg:
set/badnode K1TTT
will stop anything from K1TTT. If you want SSIDs as well then you must enter them specifically.
unset/badnode K1TTT
will allow spots from him again. Use with extreme care. This command may well be superseded by FILTERing.

===unset/badspotter <call>..===
*unset/badspotter <call>.. - Allow spots from this callsign again
Setting a callsign as a 'badspotter' will prevent spots from this callsign going any further. They will not be displayed and they will not be sent onto other nodes. The call must be written in full, no wild cards are allowed eg:
set/badspotter VE2STN
will stop anything from VE2STN. This command will automatically stop spots from this user, regardless of whether or which SSID he uses. DO NOT USE SSIDs in the callsign, just use the callsign as above or below.
unset/badspotter VE2STN
will allow spots from him again. Use with extreme care. This command may well be superseded by FILTERing.

===unset/badword <word>..===
*unset/badword <word>.. - Propagate things with this word again
Setting a word as a 'badword' will prevent things like spots, announces or talks with this word in the the text part from going any further. They will not be displayed and they will not be sent onto other nodes. The word must be written in full, no wild cards are allowed eg:
set/badword annihilate annihilated annihilation
will stop anything with these words in the text.
unset/badword annihilated
will allow text with this word again.

===unset/beep===
*unset/beep - Stop beeps for DX and other messages on your terminal

===unset/debug <name>===
*unset/debug <name> - Remove a debug level from the debug set
You can choose to log several different levels. The levels are
chan state msg cron connect
You can show what levels you are logging with SHOW/DEBUG

===unset/dx===
*unset/dx - Stop DX messages coming out on your terminal

===unset/dxcq===
*unset/dxcq - Stop CQ Zones on the end of DX announcements
Display both the Spotter's and the Spotted's CQ Zone on the end of a DX announcement (there is just enough room). Some user programs cannot cope with this. The Spotter's CQ is on the RHS of the time, the Spotted's CQ is on the LHS. Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE. Do a STAT/USER to see which flags you have set if you are confused.

===unset/dxgrid===
*unset/dxgrid - Stop QRA Grid Squares on the end of DX announcements
A standard feature which is enabled in version 1.43 and above is that if the spotter's grid square is known it is output on the end of a DX announcement (there is just enough room). Some user programs cannot cope with this. You can use this command to reset (or set)this feature. Conflicts with: SET/DXCQ, SET/DXITU. Do a STAT/USER to see which flags you have set if you are confused.

===unset/dxitu===
*unset/dxitu - Stop ITU Zones on the end of DX announcements
Display both the Spotter's and the Spotted's ITU Zone on the end of a DX announcement (there is just enough room). Some user programs cannot cope with this. The Spotter's ITU is on the RHS of the time, the Spotted's ITU is on the LHS. Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE. Do a STAT/USER to see which flags you have set if you are confused.

===unset/echo===
*unset/echo - Stop the cluster echoing your input
If you are connected via a telnet session, different implementations of telnet handle echo differently depending on whether you are connected via port 23 or some other port. You can use this command to change the setting appropriately. The setting is stored in your user profile. YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.

===unset/email===
*unset/email - Stop personal msgs being forwarded by email
If any personal messages come in for your callsign then you can use these commands to control whether they are forwarded onto your email address. To enable the forwarding do something like:
SET/EMAIL mike.tubby@somewhere.com
You can have more than one email address (each one separated by a space). Emails are forwarded to all the email addresses you specify. You can disable forwarding by:
UNSET/EMAIL

===unset/here===
*unset/here - Tell the system you are absent from your terminal

===unset/hops <call> ann|spots|route|wwv|wcy===
*unset/hops <call> ann|spots|route|wwv|wcy - Unset hop count
Set the hop count for a particular type of broadcast for a node. This command allows you to set up special hop counts for a node for currently: announce, spots, wwv and wcy broadcasts.eg:
set/hops gb7djk ann 10
set/hops gb7mbc spots 20
Set SHOW/HOPS for information on what is already set. This commandcreates a filter and works in conjunction with the filter system. You can unset the hops with command UNSET/HOPS. For example:
unset/hops gb7djk ann
unset/hops gb7mbc spots

===unset/isolate===
*unset/isolate - Stop Isolation of a node from the rest of the network
Remove isolation from a node - SET/ISOLATE

===unset/lockout <call>===
*unset/lockout <call> - Allow a callsign to connect to the cluster

===unset/logininfo===
*unset/logininfo - No longer inform when a station logs in/out locally

===unset/password <call> ...===
*unset/password <call> ... - Delete (remove) a user's password
This command allows the sysop to completely delete and remove a password for a user.

===unset/privilege===
*unset/privilege - Remove any privilege for this session
You can use this command to 'protect' this session from unauthorized use. If you want to get your normal privilege back you will need to either logout and login again (if you are on a console) or use the SYSOP command.

===unset/prompt===
*unset/prompt - Set your prompt back to default
This command will set your user prompt to the string that you say. The point of this command to enable a user to interface to programs that are looking for a specific prompt (or else you just want a different prompt).
SET/PROMPT clx >
There are some substitutions that can be added to the prompt:
%C - callsign [which will have ( and ) around it if not here]
%D - date
%T - time
%M - cluster 'mycall'
The standard prompt is defined as:
SET/PROMPT %C de %M %D %T dxspider >
UNSET/PROMPT will undo the SET/PROMPT command and set your prompt back to normal.

===unset/register <call> ...===
*unset/register <call> ... - Mark a user as not registered
Registration is a concept that you can switch on by executing the
set/var $main::regreq = 1
command (usually in your startup file). If a user is NOT registered then, firstly, instead of the normal motd file (/spider/data/motd) being sent to the user at startup, the user is sent the motd_nor file instead. Secondly, the non-registered user only has READ-ONLY access to the node. The non-registered user cannot use DX, ANN etc. The only exception to this is that a non-registered user can TALK or SEND messages to the sysop.

===unset/startup===
*unset/startup - Remove your own startup script
You can remove your startup script with UNSET/STARTUP.

===unset/startup <call>===
*unset/startup <call> - Remove a user startup script

===unset/talk===
*unset/talk - Stop TALK messages coming out on your terminal

===unset/usstate===
*unset/usstate - Stop US State info on the end of DX announcements
If the spotter's or spotted's US State is known it is output on the end of a DX announcement (there is just enough room). A spotter's state will appear on the RHS of the time (like SET/DXGRID) and the spotted's state will appear on the LHS of thetime field. Any information found will override any locator information from SET/DXGRID. Some user programs cannot cope with this. You can use this command to reset (or set) this feature. Conflicts with: SET/DXCQ, SET/DXITU. Do a STAT/USER to see which flags you have set if you are confused.

===unset/wcy===
*unset/wcy - Stop WCY messages coming out on your terminal

===unset/wwv===
*unset/wwv - Stop WWV messages coming out on your terminal

===unset/wx===
*unset/wx - Stop WX messages coming out on your terminal

==WHO==
===who===
*who - Show who is physically connected
This is a quick listing that shows which callsigns are connected and what sort of connection they have.

==WX==
===wx <text>===
*wx <text> - Send a weather message to local users

===wx full <text>===
*wx full <text> - Send a weather message to all cluster users

===wx sysop <text>===
*wx sysop <text> - Send a weather message to other clusters only
Weather messages can sometimes be useful if you are experiencing an extreme that may indicate enhanced conditions.

DXSpider Debug Commands and Levels

2025-04-04T21:02:06Z

G0TRT:

===General Information===

The debug commands, or levels, are set and unset through the console, this gives the sysop control on the messages that are logged in the debug files.

====Levels====

* badip - for logging bad ip address
* chan
* connect - for logging connect messages
* cron
* msg
* nologchan - for logging (or not) the channel traffic
* pc11 - for logging PC11 messages
* progress
* spotdup
* state

====Examples====

At the console:

To enable the logging of PC11 messages
set/debug pc11

To unset the default of not logging channels
unset/debug nologchan

DXSpider Debug Commands and Levels

2025-04-04T20:53:03Z

G0TRT: Start point

===General Information===

The debug commands are set and unset through the console, this gives the sysop control on the messages that are logged in the debug files.

DXSpider Sysop Command Reference

2025-04-04T20:50:49Z

G0TRT: /* debug */

==ACCEPT==
* '''accept''' set a filter to accept something
* Create a filter to accept something. There are 2 types of filter, accept and reject. See ''Help Filtering'' for more info.

===accept/announce <call> [input] [0-9] <pattern>===
* '''accept/announce''' <call> [input] [0-9] <pattern> - Announce filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
accept/ann by G,M,2
accept/ann input node_default by G,M,2
accept/ann user_default by G,M,2

===accept/announce [0-9] <pattern>===
*accept/announce [0-9] <pattern> - Set an 'accept' filter line for announce
Create an 'accept this announce' line for a filter. An accept filter line means that if the announce matches this filter it is passed onto the user. See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
info <string> - eg: iota or qsl
by <prefixes> - eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> - eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,NH
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states>
channel <prefixes> wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX
some examples:
acc/ann dest 6MUK
acc/ann 2 by_zone 14,15,16
(this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
or
acc/ann by G,M,2
for american states
acc/ann by_state va,nh,ri,nh
You can use the tag 'all' to accept everything eg:
acc/ann all
but this probably for advanced users...

===accept/route <call> [0-9] <pattern>===
*accept/route <call> [0-9] <pattern> - Set an 'accept' filter line for routing
Create an 'accept this routing PC Protocol' line for a filter. An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter it is passed thru that interface. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:
call <prefixes>
the callsign of the thingy
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,NH
origin <prefixes>
really the interface it came in on
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,NH
some examples:
acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
you can now use 'by' as a synonym for 'call' so:
by = call by_dxcc = call_dxcc
you can use the tag 'all' to accept everything eg:
acc/route all

===accept/spots <call> [input] [0-9] <pattern>===
*accept/spots <call> [input] [0-9] <pattern> - Spot filter sysop version
This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:
accept/spot db0sue-7 1 by_zone 14,15,16
accept/spot node_default all
set/hops node_default 10
accept/spot user_default by G,M,2

===accept/spots [0-9] <pattern>===
*accept/spots [0-9] <pattern> - Set an 'accept' filter line for spots
Create an 'accept this spot' line for a filter. An accept filter line means that if the spot matches this filter it ispassed onto the user. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on <range> same as 'freq'
call <prefixes> eg: G,PA,HB9
info <string> eg: iota or qsl
by <prefixes>
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states> eg: VA,NH,RI,ME
origin <prefixes>
channel <prefixes>
'call' means the callsign that has spotted 'by' whoever. For frequencies, you can use any of the band names defined in SHOW/BANDS and you can use a sub-band name like: cw, rtty, data, ssb -thus: hf/ssb. You can also just have a simple range like: 0/30000 -this is more efficient than saying simply: freq HF (but don't get too hung up about that)some examples:
acc/spot 1 on hf/cw
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
You can use the tag 'all' to accept everything, eg:
acc/spot 3 all
for US states
acc/spots by_state VA,NH,RI,MA,ME
but this probably for advanced users...

===accept/wcy <call> [input] [0-9] <pattern>===
*accept/wcy <call> [input] [0-9] <pattern> - WCY filter sysop version
This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:
accept/wcy node_default all set/hops node_default 10

===accept/wcy [0-9] <pattern>===
*accept/wcy [0-9] <pattern> - set an 'accept' WCY filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them).This command is really provided for future use. See HELP FILTER for information.

===accept/wwv <call> [input] [0-9] <pattern>===
*accept/wwv <call> [input] [0-9] <pattern> - WWV filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
accept/wwv db0sue-7 1 by_zone 4
accept/wwv node_default all set/hops node_default 10
accept/wwv user_default by W,K

===accept/wwv [0-9] <pattern>===
*accept/wwv [0-9] <pattern> - set an 'accept' WWV filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
for example:
accept/wwv by_zone 4
is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). See HELP FILTER for information.

==ANNOUNCE==
===announce <text>===
*announce <text> - Send an announcement to LOCAL users only
<text> is the text of the announcement you wish to broadcast

===announce full <text>===
*announce full <text> - Send an announcement cluster wide
This will send your announcement cluster wide

===announce sysop <text>===
*announce sysop <text> - Send an announcement to Sysops only

==APROPOS==
===apropos <string>===
*apropos <string> - Search help database for <string>
Search the help database for <string> (it isn't case sensitive), and print the names of all the commands that may be relevant.

==BLANK==
===blank [<string>] [<nn>]===
*blank [<string>] [<nn>] - Print nn (default 1) blank lines (or strings)
In its basic form this command prints one or more blank lines. However if you pass it a string it will replicate the string for the width of the screen (default 80) and then print that one or more times, so:
blank 2
prints two blank lines
blank -
prints a row of - characters once.
blank abc
prints 'abcabcabcabcabcabc....'This is really only of any use in a script file and you can print a maximum of 9 lines.

==BYE==
===bye===
*bye - Exit from the cluster
This will disconnect you from the cluster

==CATCHUP==
===catchup <node call> all|[<msgno> ...]===
*catchup <node call> all|[<msgno> ...] - Mark a message as sent

==CHAT==
===chat <group> <text>===
*chat <group> <text> - Chat or Conference to a group
It is now possible to JOIN a group and have network wide conferencing to that group. DXSpider does not (and probably will not) implement the AK1A conference mode as this seems very limiting, is hardly used and doesn't seem to work too well anyway. This system uses the existing ANN system and is compatible with both other DXSpider nodes and AK1A clusters (they use ANN/<group>). You can be a member of as many "groups" as you want. To join a group type:
JOIN FOC (where FOC is the group name)
To leave a group type:
LEAVE FOC
You can see which groups you are in by typing:
STAT/USER
and you can see whether your mate is in the group, if he connects to the same node as you, by typing:
STAT/USER g1tlh
To send a message to a group type:
CHAT FOC hello everyone
or
CH #9000 hello I am back
See also JOIN, LEAVE, SHOW/CHAT

==CLEAR==
===clear/announce <callsign> [input] [0-9|all]===
*clear/announce <callsign> [input] [0-9|all] - Clear a announce filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/announce [1|all]===
*clear/announce [1|all] - Clear a announce filter line
This command allows you to clear (remove) a line in a announce filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

===clear/route <callsign> [input] [0-9|all]===
*clear/route <callsign> [input] [0-9|all] - Clear a route filter line
A sysop can clear an input or normal output filter for a user or then ode_default or user_default.

===clear/route [1|all]===
*clear/route [1|all] - Clear a route filter line
This command allows you to clear (remove) a line in a route filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

===clear/spots <callsign> [input] [0-9|all]===
*clear/spots <callsign> [input] [0-9|all] - Clear a spot filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/spots [0-9|all]===
*clear/spots [0-9|all] - Clear a spot filter line
This command allows you to clear (remove) a line in a spot filter or to remove the whole filter. If you have a filter:
acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
and you say:
clear/spot 1
you will be left with:
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
If you do:
clear/spot all
the filter will be completely removed.

===clear/wcy <callsign> [input] [0-9|all]===
*clear/wcy <callsign> [input] [0-9|all] - Clear a WCY filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/wcy [1|all]===
*clear/wcy [1|all] - Clear a WCY filter line
This command allows you to clear (remove) a line in a WCY filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

===clear/wwv <callsign> [input] [0-9|all]===
*clear/wwv <callsign> [input] [0-9|all] - Clear a WWV filter line
A sysop can clear an input or normal output filter for a user or the node_default or user_default.

===clear/wwv [1|all]===
clear/wwv [1|all] - Clear a WWV filter line
This command allows you to clear (remove) a line in a WWV filter or to remove the whole filter. See CLEAR/SPOTS for a more detailed explanation.

==CONNECT==
===connect <callsign>===
*connect <callsign> - Start a connection to another DX Cluster
Start a connection process that will culminate in a new connection to the DX cluster <callsign>. This process creates a new 'client' process which will use the script in /spider/connect/<callsign> to effect the 'chat' exchange necessary to traverse the network(s) to logon to the cluster <callsign>.

==DBAVAIL==
===dbavail===
*dbavail - Show a list of all the Databases in the system
Title says it all really, this command lists all the databases defined in the system. It is also aliased to SHOW/COMMAND.

==DBCREATE==
===dbcreate <name>===
*dbcreate <name> - Create a database entry

===dbcreate <name> chain <name> [<name>..]===
*dbcreate <name> chain <name> [<name>..] - Create a chained database entry

===dbcreate <name> cmd <dxspider command>===
*dbcreate <name> cmd <dxspider command> - make a local command available as a DB
DBCREATE allows you to define a database in the system. It doesn't actually create anything, just defines it. The databases that are created are simple DB_File hash databases, they are therefore already 'indexed'. You can define a local database with the first form of the command eg:
DBCREATE oblast
You can also chain databases with the addition of the 'chain' keyword. This will search each database one after the other. A typical example is:
DBCREATE sdx_qsl chain sql_ad
No checking is done to see if the any of the chained databases exist, in fact it is usually better to do the above statement first then do each of the chained databases. Databases can exist offsite. To define a database that lives on another node do:
DBCREATE buckmaster remote gb7dxc
Remote databases cannot be chained; however, the last database in a a chain can be a remote database eg:
DBCREATE qsl chain gb7dxc
To see what databases have been defined do:
DBAVAIL (or it will have been aliased to SHOW/COMMAND)
It would be normal for you to add an entry into your local Aliases file to allow people to use the 'SHOW/<dbname>' style syntax. So you would need to add a line like:
's' => [ .. .. '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', .. .. ],
to allow
SH/BUCK g1tlh
to work as they may be used to.You can also make local commands available as 'pseudo' databases. Youcan therefore make spider special commands available as a database. Iimagine that this will be primarily useful for remote access from legacy nodes. For example:-
DBCREATE dxqsl cmd show/dxqsl
You also use one of these databases in a chain. This may be useful locally. See DBIMPORT for the importing of existing AK1A format data to databases. See DBSHOW for generic database enquiry

===dbcreate <name> remote <node>===
*dbcreate <name> remote <node> - Create a remote database entry

==DBIMPORT==
===dbimport <dbname> <filename>===
*dbimport <dbname> <filename> - Import AK1A data into a database
If you want to import or update data in bulk to a database you can use this command. It will either create or update entries into an existing database. For example:
DBIMPORT oblast /tmp/OBLAST.FUL
will import the standard OBLAST database that comes with AK1A into the oblast database held locally.

==DBREMOVE==
===dbremove <dbname>===
*dbremove <dbname> - Delete a database
DBREMOVE will completely remove a database entry and also delete any datafile that is associated with it. There is no warning, no comeback, no safety net. For example:
DBREMOVE oblast
will remove the oblast database from the system and it will also remove the associated data file. I repeat: There is no warning, no comeback, no safety net. You have been warned.

==DBSHOW==
===dbshow <dbname> <key>===
*dbshow <dbname> <key> - Display an entry, if it exists, in a database
This is the generic user interface to the database to the database system. It is expected that the sysop will add an entry to the local Aliases file so that users can use the more familiar AK1A style of enquiry such as:
SH/BUCK G1TLH
but if he hasn't and the database really does exist (use DBAVAIL or SHOW/COMMAND to find out) you can do the same thing with:
DBSHOW buck G1TLH

==DEBUG==
===debug===
*debug - Set the cluster program into debug mode
Executing this command will only have an effect if you are running the cluster in debug mode i.e.
perl -d cluster.pl
It will interrupt the cluster just after the debug command has finished.

The full debug command set is on the [[Debug commands|debug commands]] page

==DELETE==
===delete/usdb <callsign> ...===
*delete/usdb <callsign> ... - Delete this user from the US State Database
This command will completely remove a one or more callsigns from the US States database. There is NO SECOND CHANCE. It goes without saying that you should use this command CAREFULLY! Note that these callsigns may be re-instated by any weekly updates from the FCC.

===delete/user <callsign> ...===
*delete/user <callsign> ... - Delete this user from the User Database
This command will completely remove a one or more users from the database. There is NO SECOND CHANCE. It goes without saying that you should use this command CAREFULLY!

==DEMONSTRATE==
===demonstrate <call> <command>===
*demonstrate <call> <command> - Demonstrate a command to another user
This command is provided so that sysops can demonstrate commands to other users. It runs a command as though that user had typed it in and then sends the output to that user, together with the command that caused it.
DEMO g7brn sh/dx iota oc209
DEMO g1tlh set/here
Note that this command is similar to SPOOF and will have the same side effects. Commands are run at the privilege of the user which is being demonstrated to.

==DIRECTORY==
===directory===
*directory - List messages

===directory <from>-<to>===
*directory <from>-<to> - List messages <from> message <to> message
List the messages in the messages directory. If there is a 'p' one space after the message number then it is a personal message. If there is a '-' between the message number and the 'p' then this indicates that the message has been read. You can use shell escape characters such as '*' and '?' in the <call>fields. You can combine some of the various directory commands together eg:
DIR TO G1TLH 5
or
DIR SUBJECT IOTA 200-250
You can abbreviate all the commands to one letter and use ak1a syntax:
DIR/T G1* 10
DIR/S QSL 10-100 5

===directory <nn>===
*directory <nn> - List last <nn> messages

===directory all===
*directory all - List all messages

===directory from <call>===
*directory from <call> - List all messages from <call>

===directory new===
*directory new - List all new messages

===directory own===
*directory own - List your own messages

===directory subject <string>===
*directory subject <string> - List all messages with <string> in subject

===directory to <call>===
*directory to <call> - List all messages to <call>

===directory- ===
directory-
Sysops can see all users' messages.

==DISCONNECT==
===disconnect <call> [<call> ...]===
*disconnect <call> [<call> ...] - Disconnect a user or cluster
Disconnect any <call> connected locally

==DX==
===dx [by <call>] <freq> <call> <remarks>===
dx [by <call>] <freq> <call> <remarks> - Send a DX spot
This is how you send a DX Spot to other users. You can, in fact, now enter the <freq> and the <call> either way round.
DX FR0G 144.600
DX 144.600 FR0G
DX 144600 FR0G
will all give the same result. You can add some remarks to the end of the command and they will be added to the spot.
DX FR0G 144600 this is a test
You can credit someone else by saying:
DX by G1TLH FR0G 144.600 he isn't on the cluster
The <freq> is compared against the available bands set up in the cluster. See SHOW/BANDS for more information.

==ECHO==
===echo <line>===
echo <line> - Echo the line to the output
This command is useful in scripts and so forth for printing the line that you give to the command to the output. You can use this in user_default scripts and the SAVE command for titling and so forth. The script will interpret certain standard "escape" sequences as follows:
\t - becomes a TAB character (0x09 in ascii)
\a - becomes a BEEP character (0x07 in ascii)
\n - prints a new line
So the following example:
echo GB7DJK is a dxcluster
produces:
GB7DJK is a dxcluster
on the output. You don't need a \n on the end of the line you want to send.

==EXPORT==
===export <msgno> <filename>===
*export <msgno> <filename> - Export a message to a file
Export a message to a file. This command can only be executed on a local console with a fully privileged user. The file produced will be in a form ready to be imported back into the cluster by placing it in the import directory (/spider/msg/import).This command cannot overwrite an existing file. This is to provide some measure of security. Any files written will owned by the same user as the main cluster, otherwise you can put the new files anywhere the cluster can access. For example:
EXPORT 2345 /tmp/a

===export_users [<filename>]===
*export_users [<filename>] - Export the users database to ascii
Export the users database to a file in ascii format. If no file name is given then it will export the file to /spider/data/user_asc. If the file already exists it will be renamed to <filename>.o. In fact up to 5 generations of the file can be kept each one with an extra 'o' on the suffix. BE WARNED: this will write to any file you have write access to. No check is made on the filename (if any) that you specify.

==FILTERING==
===filtering...===
*filtering... - Filtering things in DXSpider
There are a number of things you can filter in the DXSpider system. They all use the same general mechanism. In general terms you can create a 'reject' or an 'accept' filter which can have up to 10 lines in it. You do this using, for example:
accept/spots .....
reject/spots .....
where ..... are the specific commands for that type of filter. There are filters for spots, wwv, announce, wcy and (for sysops) connects. See each different accept or reject command reference for more details. There is also a command to clear out one or more lines in a filter and one to show you what you have set. They are:
clear/spots 1
clear/spots all
and
show/filter
There is clear/xxxx command for each type of filter. For now we are going to use spots for the examples, but you can apply the principles to all types of filter. There are two main types of filter 'accept' or 'reject'; which you use depends entirely on how you look at the world and what is least writing to achieve what you want. Each filter has 10 lines (of any length) which are tried in order. If a line matches then the action you have specified is taken (ie reject means ignore it and accept means gimme it). The important thing to remember is that if you specify a 'reject' filter (all the lines in it say 'reject/spots' (for instance)) then if a spot comes in that doesn't match any of the lines then you will get it BUT if you specify an 'accept' filter then any spots that don't match are dumped. For example if I have a one line accept filter:
accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
then automatically you will ONLY get VHF spots from or to CQ zones 1415 and 16. If you set a reject filter like:
reject/spots on hf/cw
Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA and will work it even on CW then you could say:
reject/spots on hf/cw and not info iota
But in that case you might only be interested in iota and say:
accept/spots not on hf/cw or info iota
which is exactly the same. You should choose one or the other until you are comfortable with the way it works. Yes, you can mix them (actually you can have an accept AND a reject on the same line) but don't try this at home until you can analyze the results that you get without ringing up the sysop for help. Another useful addition now is filtering by US state
accept/spots by_state VA,NH,RI,ME
You can arrange your filter lines into logical units, either for your own understanding or simply convenience. I have one set frequently:
reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
What this does is to ignore all HF CW spots (being a class B I can't read any CW and couldn't possibly be interested in HF :-) and also rejects any spots on VHF which don't either originate or spot someone in Europe. This is an example where you would use the line number (1 and 2 in this case), if you leave the digit out, the system assumes '1'. Digits'0'-'9' are available. You can leave the word 'and' out if you want, it is implied. You can use any number of brackets to make the 'expression' as you want it. There are things called precedence rules working here which mean that you will NEED brackets in a situation like line 2 because, without it, will assume:
(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
annoying, but that is the way it is. If you use OR - use brackets. Whilst we are here CASE is not important. 'And BY_Zone' is just 'and by_zone'. If you want to alter your filter you can just redefine one or more lines of it or clear out one line. For example:
reject/spots 1 on hf/ssb
or
clear/spots 1
To remove the filter in its entirty:
clear/spots all
There are similar CLEAR commands for the other filters:
clear/announce
clear/wcy
clear/wwv
ADVANCED USERS: Once you are happy with the results you get, you may like to experiment. my example that filters hf/cw spots and accepts vhf/uhf spots from EU can be written with a mixed filter, eg:
rej/spot on hf/cw acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
each filter slot actually has a 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE the accept slot. It was mentioned earlier that after a reject test that doesn't match, the default for following tests is 'accept', the reverse is true for 'accept'. In the example what happens is that the reject is executed first, any non hf/cw spot is passed to the accept line, which lets thru everything else on HF. The next filter line lets through just VHF/UHF spots from EU.

==FORWARD==
===forward/latlong <node_call>===
*forward/latlong <node_call> - Send latitude and longitude information to another cluster
This command sends all the latitude and longitude information that your cluster is holding against callsigns. One advantage of receiving this information is that more locator information is held by you. This means that more locators are given on the DX line assuming you have SET/DXGRID enabled. This could be a LOT of information though, so it is not recommended on slow links.

===forward/opernam <call>===
*forward/opernam <call> - Send out information on this <call> to all clusters
This command sends out any information held in the user file which can be broadcast in PC41 protocol packets. This information is Name, QTH, Locationand Homenode. PC41s are only sent for the information that is available.

==FTx==
===enable/autoftx===
*enable/autoftx - Enable detected automatically generated FTx spots to be output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

===enable/ftx===
*enable/ftx - Enable FTx spots to be output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

===disable/autoftx===
*disable/autoftx - Disable detected automatically generated FTx spots from being output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

===disable/ftx===
*disable/ftx - Disable FTx spots from being output on the screen
To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

==HELP==
===help===
help - The HELP Command
HELP is available for a number of commands. The syntax is:
HELP <cmd>
Where <cmd> is the name of the command you want help on. All commands can be abbreviated, so SHOW/DX can be abbreviated to SH/DX, ANNOUNCE can be shortened to AN and so on. Look at the APROPOS <string> command which will search the help database for the <string> you specify and give you a list of likely commands to look at with HELP.

==INIT==
===init <node>===
*init <node> - Re-initialize a link to an AK1A compatible node
This command attempts to re-initialize a link to a (usually) AK1A node that has got confused, usually by a protocol loop of some kind. It may work - but you usually will be better off simply disconnecting it (or better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your node>). Best of luck - you will need it.

==JOIN==
===join <group>===
*join <group> - Join a chat or conference group
JOIN allows you to join a network wide conference group. To join a group (called FOC in this case) type:
JOIN FOC
See also CHAT, LEAVE, SHOW/CHAT

==KILL==
===kill===
*kill
As a sysop you can kill any message on the system.

===kill <from msgno>-<to msgno>===
*kill <from msgno>-<to msgno> - Delete a range of messages

===kill <from>-<to>===
*kill <from>-<to> - Remove a range of messages from the system

===kill <msgno> [<msgno..]===
*kill <msgno> [<msgno..] - Delete a message from the local system

===kill <msgno> [<msgno> ...]===
*kill <msgno> [<msgno> ...] - Remove or erase a message from the system
You can get rid of any message to or originating from your callsign using this command. You can remove more than one message at a time.

===kill expunge <msgno> [<msgno..]===
*kill expunge <msgno> [<msgno..] - Expunge a message
Deleting a message using the normal KILL commands only marks that message for deletion. The actual deletion only happens later (usually two days later). The KILL EXPUNGE command causes the message to be truly deleted more or less immediately. It otherwise is used in the same way as the KILL command.

===kill from <call>===
*kill from <call> - Remove all messages from a callsign

===kill full <msgno> [<msgno..]===
*kill full <msgno> [<msgno..] - Delete a message from the whole cluster
Delete a message from the local system. You will only be able to delete messages that you have originated or been sent (unless you are the sysop).
KILL 1234-1255
Will delete all the messages that you own between msgnos 1234 and 1255.
KILL from g1tlh
will delete all the messages from g1tlh (if you are g1tlh). Similarly:
KILL to g1tlh
will delete all messages to g1tlh.
KILL FULL 1234
will delete a message (usually a 'bulletin') from the whole cluster system. This uses the subject field, so any messages that have exactly thesame subject will be deleted. Beware!

===kill full <msgno> [<msgno]===
*kill full <msgno> [<msgno] - Remove a message from the entire cluster
Remove this message from the entire cluster system as well as your node.

===kill to <call>===
*kill to <call> - Remove all messages to a callsign

===kill from <regex>===
*kill from <regex> - Delete messages FROM a callsign or pattern

===kill to <regex>===
*kill to <regex> - Delete messages TO a callsign or pattern

==LEAVE==
===leave <group>===
*leave <group> - Leave a chat or conference group
LEAVE allows you to leave a network wide conference group. To leave agroup (called FOC in this case) type:
LEAVE FOC
See also CHAT, JOIN, SHOW/CHAT

==LINKS==
===links===
*links - Show which nodes is physically connected
This is a quick listing that shows which links are connected and some information about them. See WHO for a list of all connections.

==LOAD==
===load/aliases===
*load/aliases - Reload the command alias table
Reload the /spider/cmd/Aliases file after you have edited it. You will need to do this if you change this file whilst the cluster is running in order for the changes to take effect.

===load/badmsg===
*load/badmsg - Reload the bad msg table
Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst the cluster is running. This table contains a number of perl regular expressions which are searched for in the fields targeted of each message. If any of them match then that message is immediately deleted on receipt.

===load/badwords===
*load/badwords - Reload the bad words table
Reload the /spider/data/badwords file if you have changed it manually whilst the cluster is running. This file contains a list of words which, if found on certain text portions of PC protocol, will cause those protocol frames to be rejected. It will all put out a message if any of these words are used on the announce, dx and talk commands. The words can be one or more on a line, lines starting with '#' are ignored.

===load/bands===
*load/bands - Reload the band limits table
Reload the /spider/data/bands.pl file if you have changed it manually whilst the cluster is running.

===load/cmd_cache===
*load/cmd_cache - Reload the automatic command cache
Normally, if you change a command file in the cmd or local_cmd tree it will automatically be picked up by the cluster program. Sometimes it can get confused if you are doing a lot of moving commands about or delete a command in the local_cmd tree and want to use the normal one again. Execute this command to reset everything back to the state it was just after a cluster restart.

===load/forward===
*load/forward - Reload the msg forwarding routing table
Reload the /spider/msg/forward.pl file if you have changed it manually whilst the cluster is running.

===load/keps===
*load/keps - Load new keps data

===load/keps [nn]===
*load/keps [nn] - Load new keps data from message
If there is no message number then reload the current Keps data from the Keps.pm data file. You create this file by running
/spider/perl/convkeps.pl <filename>
on a file containing NASA 2 line keps as a message issued by AMSAT. If there is a message number, then it will take the message, run convkeps.pl on it and then load the data, all in one step. These messages are sent to ALL by GB7DJK (and others) from time to time.

===load/messages===
*load/messages - Reload the system messages file
If you change the /spider/perl/Messages file (usually whilst fiddling/writing new commands) you can have them take effect during a cluster session by executing this command. You need to do this if get something like :
unknown message 'xxxx' in lang 'en'

===load/prefixes===
*load/prefixes - Reload the prefix table
Reload the /spider/data/prefix_data.pl file if you have changed it manually whilst the cluster is running.

==MERGE==
===merge <node> [<no spots>/<no wwv>]===
*merge <node> [<no spots>/<no wwv>] - Ask for the latest spots and WWV
MERGE allows you to bring your spot and wwv database up to date. By default it will request the last 10 spots and 5 WWVs from the node you select. The node must be connected locally. You can request any number of spots or wwv and although they will be appended to your databases they will not duplicate any that have recently been added (the last 2 days for spots and last month for WWV data).

==MSG==
===msg <cmd> <msgno> [data ... ]===
*msg <cmd> <msgno> [data ... ] - Alter various message parameters
Alter message parameters like To, From, Subject, whether private or bulletin or return receipt (RR) is required or whether to keep this message from timing out.
MSG TO <msgno> <call> - change TO callsign to <call>
MSG FRom <msgno> <call> - change FROM callsign to <call>
MSG PRrivate <msgno> - set private flag
MSG NOPRrivate <msgno> - unset private flag
MSG RR <msgno> - set RR flag
MSG NORR <msgno> - unset RR flag
MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
MSG NOKEep <msgno> - unset the keep flag
MSG SUbject <msgno> <new> - change the subject to <new>
MSG WAittime <msgno> - remove any waitting time for this message
MSG NOREad <msgno> - mark message as unread
MSG REad <msgno> - mark message as read
MSG QUeue - queue any outstanding bulletins
MSG QUeue 1 - queue any outstanding private messages
You can look at the status of a message by using:
STAT/MSG <msgno>
This will display more information on the message than DIR does.

==PC==
===pc <call> <text>===
*pc <call> <text> - Send arbitrary text to a connected callsign
Send some arbitrary text to a locally connected callsign. No processing is done on the text. This command allows you to send PC Protocol to unstick things if problems arise (messages get stuck etc). eg:
pc gb7djk PC33^GB7TLH^GB7DJK^400^
or
pc G1TLH Try doing that properly!!!
Send any text you like to the callsign requested. This is used mainly to send PC protocol to connected nodes either for testing or to unstick things. You can also use in the same way as a talk command to a connected user but without any processing, added of "from <blah> to <blah" or whatever.

==PING==
===ping <node call>===
*ping <node call> - Check the link quality between nodes
This command allows you to send a frame to another cluster node on the network and get a return frame. The time it takes to do this is a good indication of the quality of the link. The actual time it takes is output to the console in seconds. Any visible cluster node can be PINGed.

==RCMD==
===rcmd <node call> <cmd>===
*rcmd <node call> <cmd> - Send a command to another DX Cluster
This command allows you to send nearly any command to another DX Cluster node that is connected to the system. Whether you get any output is dependent on a) whether the other system knows that the node callsign of this cluster is in fact a node b) whether the other system is allowing RCMDs from this node and c) whether you have permission to send this command at all.

==READ==
===read===
*read - Read the next unread personal message addressed to you

===read <msgno>===
*read <msgno> - Read the specified message
You can read any messages that are sent as 'non-personal' and also any message either sent by or sent to your callsign.

===read-===
*read-
As a sysop you may read any message on the system

==REJECT==
===reject===
*reject - Set a filter to reject something
Create a filter to reject something. There are 2 types of filter, accept and reject. See HELP FILTERING for more info.

===reject/announce <call> [input] [0-9] <pattern>===
*reject/announce <call> [input] [0-9] <pattern> - Announce filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/ann by G,M,2
reject/ann input node_default by G,M,2
reject/ann user_default by G,M,2

===reject/announce [0-9] <pattern>===
*reject/announce [0-9] <pattern> - Set a 'reject' filter line for announce
Create an 'reject this announce' line for a filter. A reject filter line means that if the announce matches this filter it is passed onto the user. See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
info <string> eg: iota or qsl
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states> eg: VA,NH,RI,ME
channel <prefixes>
wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX
some examples:
rej/ann by_zone 14,15,16 and not by G,M,2
You can use the tag 'all' to reject everything eg:
rej/ann all
but this probably for advanced users...

===reject/route <call> [0-9] <pattern>===
*reject/route <call> [0-9] <pattern> - Set an 'reject' filter line for routing
Create an 'reject this routing PC Protocol' line for a filter. An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter it is NOT passed thru that interface. See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
call <prefixes> the callsign of the thingy
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,ME
origin <prefixes>
really the interface it came in on
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
origin_state <states> eg: VA,NH,RI,ME
some examples:
rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
You can use the tag 'all' to reject everything eg:
rej/route all (equiv to [very] restricted mode)
as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.

===reject/spots <call> [input] [0-9] <pattern>===
*reject/spots <call> [input] [0-9] <pattern> - Spot filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/spot db0sue-7 1 by_zone 14,15,16
reject/spot node_default all set/hops node_default 10
reject/spot user_default by G,M,2

===reject/spots [0-9] <pattern>===
*reject/spots [0-9] <pattern> - Set a 'reject' filter line for spots
Create a 'reject this spot' line for a filter. A reject filter line means that if the spot matches this filter it is dumped (not passed on). See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on. You can use any of the following things in this line:
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on <range> same as 'freq'
call <prefixes> eg: G,PA,HB9i
nfo <string> eg: iota or qsl
by <prefixes>
call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <prefixes or numbers> or: G,GM,GW
call_zone <prefixes or numbers>
call_state <states> eg: VA,NH,RI,ME
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
by_state <states> eg: VA,NH,RI,ME
origin <prefixes>
channel <prefixes>
'call' means the callsign that has spotted 'by' whoever. For frequencies, you can use any of the band names defined in SHOW/BANDS and you can use a sub-band name like: cw, rtty, data, ssb -thus: hf/ssb. You can also just have a simple range like: 0/30000 -this is more efficient than saying simply: on HF (but don't get too hung up about that)some examples:
rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
You can use the tag 'all' to reject everything eg:
rej/spot 3 all
but this probably for advanced users...

===reject/wcy <call> [input] [0-9] <pattern>===
*reject/wcy <call> [input] [0-9] <pattern> - WCY filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/wcy gb7djk all

===reject/wcy [0-9] <pattern>===
reject/wcy [0-9] <pattern> - set a 'reject' WCY filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them). This command is really provided for future use. See HELP FILTER for information.

===reject/wwv <call> [input] [0-9] <pattern>===
*reject/wwv <call> [input] [0-9] <pattern> - WWV filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:
reject/wwv db0sue-7 1 by_zone 4
reject/wwv node_default all
reject/wwv user_default by W

===reject/wwv [0-9] <pattern>===
*reject/wwv [0-9] <pattern> - set a 'reject' WWV filter
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
origin_itu <prefixes or numbers> or: G,GM,GW
origin_zone <prefixes or numbers>
by_dxcc <prefixes or numbers>
by_itu <prefixes or numbers>
by_zone <prefixes or numbers>
channel <prefixes>
for example
reject/wwv by_zone 14,15,16
is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). See HELP FILTER for information.

==REPLY==
===reply===
*reply - Reply (privately) to the last message that you have read

===reply <msgno>===
*reply <msgno> - Reply (privately) to the specified message

===reply b <msgno>===
*reply b <msgno> - Reply as a Bulletin to the specified message

===reply noprivate <msgno>===
*reply noprivate <msgno> - Reply as a Bulletin to the specified message

===reply rr <msgno>===
*reply rr <msgno> - Reply to the specified message with read receipt
You can reply to a message and the subject will automatically have "Re:" inserted in front of it, if it isn't already present. You can also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B that you can use with the SEND command (see SEND for further details)

==SAVE==
===save [-d -t -a] <filename> "<cmd>" [...]===
*save [-d -t -a] <filename> "<cmd>" [...] Save command output to a file
This sysop only command allows you to save the output of one or more commands to a file. For example:
save /spider/packclus/dxstats show/dxstat
will save the output of the normal command "show/dxstat" to the file "dxstats" in the files area. You can have some extra flags to the save which will either date stamp or time stamp or both the filename so:
save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
save -t /tmp/a <cmd> creates /tmp/a_2301Z
save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
The -a flag means append to the file instead of overwriting it. You can have more than one command on the line, to do this you MUST enclose each command in double quotes (") eg:
save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
or
save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
You can only write into places that the cluster has permission for (which is that of the "sysop" user [which had BETTER NOT BE "root"]), you will need to create any directories you want to put stuff in beforehand as well. It is likely that you will want to run these commands in a crontab type situation. You would do that something like:
0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
Note that you still enclose each command with (") characters but you must enclose the entire save command in (') characters. Now in fact, this can be varied if you know what you are doing. See the admin manual for more details.

==SEND==
===send <call> [<call> ...]===
*send <call> [<call> ...] - Send a message to one or more callsigns

===send copy <msgno> <call>===
send copy <msgno> <call> - Send a copy of a message to someone

===send noprivate <call>===
*send noprivate <call> - Send a message to all stations
All the SEND commands will create a message which will be sent either to an individual callsign or to one of the 'bulletin' addresses. SEND <call> on its own acts as though you had typed SEND PRIVATE, that is it will mark the message as personal and send it to the cluster node that that callsign is connected to. If the <call> you have specified is in fact a known bulletin category on your node (eg: ALL) then the message should automatically become a bulletin. You can have more than one callsign in all of the SEND commands. You can have multiple qualifiers so that you can have for example:
SEND RR COPY 123 PRIVATE G1TLH G0RDI
which should send a copy of message 123 to G1TLH and G0RDI and you will receive a read receipt when they have read the message. SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak). SP is an alias for SEND PRIVATE. The system will ask you for a subject. Conventionally this should be no longer than 29 characters for compatibility. Most modern cluster software should accept more. You will now be prompted to start entering your text. You finish the message by entering '/EX' on a new line. For instance:
... bye then Jim 73 Dirk /ex
If you have started a message and you don't want to keep it then you can abandon the message with '/ABORT' on a new line, like:
line 1 line 2 oh I just can't be bothered with this /abort
If you abort the message it will NOT be sent. When you are entering the text of your message, most normal output (such as DX announcements and so on are suppressed and stored for latter display(up to 20 such lines are stored, as new ones come along, so the oldest lines are dropped). Also, you can enter normal commands commands (and get the output immediately) whilst in the middle of a message. You do this by typing the command preceded by a '/' character on a new line, so:
/dx g1tlh 144010 strong signal
Will issue a dx announcement to the rest of the cluster. Also, you can add the output of a command to your message by preceding the command with '//', thus :
//sh/vhftable
This will show YOU the output from SH/VHFTABLE and also store it in the message. You can carry on with the message until you are ready to send it.

===send private <call>===
*send private <call> - Send a personal message

===send rr <call>===
*send rr <call> - Send a message and ask for a read receipt

==SET==
===set/address <your address>===
*set/address <your address> - Record your postal address

===set/announce===
*set/announce - Allow announce messages to come out on your terminal

===set/anntalk===
*set/anntalk - Allow talk like announce messages on your terminal

===set/arcluster <call> [<call>..]===
*set/arcluster <call> [<call>..] - Make the callsign an AR-Cluster node

===set/baddx <call>..===
*set/baddx <call>.. - Stop callsigns in a dx spot being propagated

===set/badnode <call>..===
*set/badnode <call>.. - Stop spots from this node being propagated

===set/badspotter <call>..===
*set/badspotter <call>.. - Stop spots from this callsign being propagated

===set/badword <word>..===
*set/badword <word>.. - Stop things with this word being propagated

===set/bbs <call> [<call>..]===
*set/bbs <call> [<call>..] - Make the callsign a BBS

===set/beep===
*set/beep - Add a beep to DX and other messages on your terminal

===set/clx <call> [<call>..]===
*set/clx <call> [<call>..] - Make the callsign an CLX node

===set/debug <name>===
*set/debug <name> - Add a debug level to the debug set

===set/dx===
*set/dx - Allow DX messages to come out on your terminal

===set/dxcq===
*set/dxcq - Show CQ Zones on the end of DX announcements

===set/dxgrid===
*set/dxgrid - Allow QRA Grid Squares on the end of DX announcements

===set/dxitu===
*set/dxitu - Show ITU Zones on the end of DX announcements

===set/dxnet <call> [<call>..]===
*set/dxnet <call> [<call>..] - Make the callsign an DXNet node

===set/echo===
*set/echo - Make the cluster echo your input

===set/email <email> ...===
*set/email <email> ... - Set email address(es) and forward your personals

===set/external_ip <external_ip>===
*set/external_ip - Set the external IPv4 address for the node and the local terminal masquerade automatically with best effort.

===set/here===
*set/here - Tell the system you are present at your terminal

===set/homenode <node>===
*set/homenode <node> - Set your normal cluster callsign
Tell the cluster system where you normally connect to. Any Messages sent to you will normally find their way there should you not be connected.eg:
SET/HOMENODE gb7djk

===set/hops <call> ann|spots|route|wwv|wcy <n>===
*set/hops <call> ann|spots|route|wwv|wcy <n> - Set hop count

===set/isolate===
*set/isolate - Isolate a node from the rest of the network
Connect a node to your system in such a way that you are a full protocol member of its network and can see all spots on it, but nothing either leaks out from it nor goes back into from the rest of the nodes connected to you. You can potentially connect several nodes in this way.

===set/language <lang>===
*set/language <lang> - Set the language you want to use
You can select the language that you want the cluster to use. Currently the languages available are en (English), de (German), es (Spanish),Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).

===set/location <lat & long>===
*set/location <lat & long> - Set your latitude and longitude

===set/lockout <call>===
*set/lockout <call> - Stop a callsign connecting to the cluster

===set/logininfo===
*set/logininfo - Inform when a station logs in/out locally

===set/name <your name>===
*set/name <your name> - Set your name
Tell the system what your name is eg:
SET/NAME Dirk

===set/node <call> [<call>..]===
*set/node <call> [<call>..] - Make the callsign an AK1A cluster
Tell the system that the call(s) are to be treated as AK1A cluster and fed PC Protocol rather normal user commands.

===set/obscount <count> <call>===
*set/obscount <count> <call> - Set the 'pump-up' obscelence PING counter
From 1.35 onwards neighboring nodes are pinged at regular intervals (see SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up' counter which is decremented on every outgoing ping and then reset to the 'obscount' value on every incoming ping. The default value of this parameter is 2. What this means is that a neighbouring node will be pinged twice at (default) 300 second intervals and if no reply has been heard just before what would be the third attempt, that node is disconnected. If a ping is heard then the obscount is reset to the full value. Using default values, if a node has not responded to a ping within 15 minutes, it is disconnected. You can set this parameter between 1 and 9. It is STRONGLY recommended that you don't change the default.

===set/page <lines per page>===
*set/page <lines per page> - Set the lines per page
Tell the system how many lines you wish on a page when the number of line of output from a command is more than this. The default is 20. Setting it explicitly to 0 will disable paging.
SET/PAGE 30 SET/PAGE 0
The setting is stored in your user profile.

===set/password===
*set/password - Set your own password
This command only works for a 'telnet' user (currently). It will only work if you have a password already set. This initial password can only be set by the sysop. When you execute this command it will ask you for your old password, then ask you to type in your new password twice (to make sure you get it right). You may or may not see the data echoed on the screen as you type, depending on the type of telnet client you have.

===set/password <callsign> <string>===
*set/password <callsign> <string> - Set a users password
The password for a user can only be set by a full sysop. The string can contain any characters. The way this field is used depends on context. If it is being used in the SYSOP command context then you are offered 5 random numbers and you have to supply the corresponding letters. This is now mainly for ax25 connections. If it is being used on incoming telnet connections then, if a password is set or the:
set/var $main::passwdreq = 1
command is executed in the startup script, then a password prompt is given after the normal 'login:' prompt.

===set/pinginterval <time> <nodecall>===
*set/pinginterval <time> <nodecall> - Set ping time to neighbouring nodes
As from release 1.35 all neighbouring nodes are pinged at regular intervals in order to determine the rolling quality of the link and, in future, to affect routing decisions. The default interval is 300 secs or 5 minutes. You can use this command to set a different interval. Please don't. But if you do the value you enter is treated as minutes up 30 and seconds for numbers greater than that. This is used also to help determine when a link is down at the far end(as certain cluster software doesn't always notice), see SET/OBSCOUNT for more information. If you must change it (and it may be useful for internet connected nodes on dynamic IP addresses that go away after a set time of usage) the time can be specified as:
5 which if less than 30 is converted to minutes otherwise is taken as the no of seconds between pings.
120s 120 seconds
5m 5 minutes
1h 1 hour
Please be aware that this causes traffic to occur on the link, setting this value too low may annoy your neighbours beyond the point of endurance! You can switch this off by setting it to 0.

===set/privilege <n> <call> [<call..]===
*set/privilege <n> <call> [<call..] - Set privilege level on a call
Set the privilege level on a callsign. The privilege levels that pertain to commands are as default:
0 - normal user
1 - allow remote nodes normal user RCMDs
5 - various privileged commands (including shutdown, but not disconnect), the normal level for another node.
8 - more privileged commands (including disconnect)
9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS LEVEL.
If you are a sysop and you come in as a normal user on a remote connection your privilege will automatically be set to 0.

===set/prompt <string>===
*set/prompt <string> - Set your prompt to <string>

===set/qra <locator>===
*set/qra <locator> - Set your QRA Grid locator
Tell the system what your QRA (or Maidenhead) locator is. If you have not done a SET/LOCATION then your latitude and longitude will be set roughly correctly (assuming your locator is correct ;-). For example:
SET/QRA JO02LQ

===set/qth <your qth>===
*set/qth <your qth> - Set your QTH
Tell the system where you are. For example:
SET/QTH East Dereham, Norfolk

===set/register <call> ...===
set/register <call> ... - Mark a user as registered

===set/spider <call> [<call>..]===
*set/spider <call> [<call>..] - Make the callsign an DXSpider node
Tell the system that the call(s) are to be treated as DXSpider node and fed new style DX Protocol rather normal user commands.

===set/startup===
*set/startup - Create your own startup script
Create a startup script of DXSpider commands which will be executed every time that you login into this node. You can only input the whole script afresh, it is not possible to 'edit' it. Inputting a new script is just like typing in a message using SEND. To finish inputting type: /EX on a newline, to abandon the script type: /ABORT. You may find the (curiously named) command BLANK useful to break up the output. If you simply want a blank line, it is easier to input one or more spaces and press the <return> key. See UNSET/STARTUP to remove a script.

===set/startup <call>===
*set/startup <call> - Create a user startup script

===set/sys_location <lat & long>===
*set/sys_location <lat & long> - Set your cluster latitude and longitude
In order to get accurate headings and such like you must tell the system what your latitude and longitude is. If you have not yet done a SET/QRA then this command will set your QRA locator for you. For example:
SET/LOCATION 52 22 N 0 57 E

===set/sys_qra <locator>===
*set/sys_qra <locator> - Set your cluster QRA Grid locator

===set/talk===
*set/talk - Allow TALK messages to come out on your terminal

===set/usdb <call> <state> <city>===
*set/usdb <call> <state> <city> - add/update a US DB callsign
This command allows you to add or alter a callsign in the US state database. Use with extreme caution. Anything you do here will be overwritten by any weekly updates that affect this callsign
set/usdb g1tlh nh downtown rindge
see also DELETE/USDB

===set/usstate===
*set/usstate - Allow US State info on the end of DX announcements

===set/wcy===
*set/wcy - Allow WCY messages to come out on your terminal

===set/wwv===
*set/wwv - Allow WWV messages to come out on your terminal

===set/wx===
*set/wx - Allow WX messages to come out on your terminal

==SHOW==
===show/baddx===
*show/baddx - Show all the bad dx calls in the system
Display all the bad dx callsigns in the system, see SET/BADDX for more information.

===show/badnode===
*show/badnode - Show all the bad nodes in the system
Display all the bad node callsigns in the system, see SET/BADNODE for more information.

===show/badspotter===
*show/badspotter - Show all the bad spotters in the system
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER for more information.

===show/badword===
*show/badword - Show all the bad words in the system
Display all the bad words in the system, see SET/BADWORD for more information.

===show/chat [<group>] [<lines>]===
*show/chat [<group>] [<lines>] - Show any chat or conferencing
This command allows you to see any chat or conferencing that has occurred whilst you were away. SHOW/CHAT on its own will show data for all groups. If you use a group name then it will show only chat for that group.

===show/configuration [<node>]===
*show/configuration [<node>] - Show all the nodes and users visible
This command allows you to see all the users that can be seen and the nodes to which they are connected. This command is normally abbreviated to: sh/c. Normally, the list returned will be just for the nodes from your country (because the list otherwise will be very long).
SH/C ALL
will produce a complete list of all nodes. BE WARNED: the list that is returned can be VERY long. It is possible to supply a node or part of a prefix and you will get a list of the users for that node or list of nodes starting with that prefix.
SH/C GB7DJK
SH/C SK

===show/configuration/node===
*show/configuration/node - Show all the nodes connected locally
Show all the nodes connected to this node.

===show/connect===
*show/connect - Show all the active connections
This command shows information on all the active connections known to the node. This command gives slightly more information than WHO.

===show/contest <year and month>===
*show/contest <year and month> - Show all the contests for a month
Show all known contests which are maintained at http://www.sk3bg.se/contest/ for a particular month or year. The format is reasonably flexible. For example:
SH/CONTEST sep2003
SH/CONTEST 03 march

===show/date [<prefix>|<callsign>]===
*show/date [<prefix>|<callsign>] - Show the local time
This is very nearly the same as SHOW/TIME, the only difference the format of the date string if no arguments are given. If no prefixes or callsigns are given then this command returns the local time and UTC as the computer has it right now. If you give some prefixes then it will show UTC and UTC + the local offset (not including DST) at the prefixes or callsigns that you specify.

===show/db0sdx <callsign>===
*show/db0sdx <callsign> - Show QSL information from DB0SDX database
This command queries the DB0SDX QSL server on the internet and returns any information available for that callsign. This service is provided for users of this software by http://www.qslinfo.de. See also SHOW/QRZ, SHOW/WM7D.

===show/debug===
*show/debug - Show what levels of debug information you are logging

===show/dup_ann===
*show/dup_ann - Show duplicate announcement records

===show/dup_spots===
*show/dup_spots - Show duplicate spot records

===show/dx===
*show/dx - Interrogate the spot database
If you just type SHOW/DX you will get the last so many spots (sysop configurable, but usually 10). In addition you can add any number of these commands in very nearly any order to the basic SHOW/DX command, they are:
on <band> - eg 160m 20m 2m 23cm 6mm
on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
on <from>/<to> - eg 1000/4000 14000-30000 (in Khz) <from>-<to>
<number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
<prefix> - for a spotted callsign beginning with <prefix>
*<suffix> - for a spotted callsign ending in <suffix>
*<string>* - for a spotted callsign containing <string>
day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
info <text> - any spots containing <text> in the info or remarks
by <call> - any spots spotted by <call> (spotter <call> is the same).
qsl - this automatically looks for any qsl info on the call held in the spot database.
iota [<iota>] - If the iota island number is missing it will look for the string iota and anything which looks like an iota island number. If you specify then it will look for that island.
qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2 You can also use this with the 'by' keyword so eg by W dxcc
real or rt - Format the output the same as for real time spots. The formats are deliberately different (so you can tell one sort from the other). This is useful for some logging programs that can't cope with normal sh/dx output. An alias of SHOW/FDX is available.
filter - Filter the spots, before output, with the user's spot filter. An alias of SHOW/MYDX is available.
zone <zones> - look for spots in the cq zone (or zones) specified. zones are numbers separated by commas.
by_zone <zones> - look for spots spotted by people in the cq zone specified.
itu <itus> - look for spots in the itu zone (or zones) specified itu zones are numbers separated by commas.
by_itu <itus> - look for spots spotted by people in the itu zone specified.
state <list> - look for spots in the US state (or states) specified The list is two letter state codes separated by commas.
by_state <list> - look for spots spotted by people in the US state specified.
e.g.
SH/DX 9m0
SH/DX on 20m info iota
SH/DX 9a on vhf day 30
SH/DX rf1p qsl
SH/DX iota
SH/DX iota eu-064
SH/DX qra jn86
SH/DX dxcc oq2
SH/DX dxcc oq2 by w dxcc
SH/DX zone 4,5,6
SH/DX by_zone 4,5,6
SH/DX state in,oh
SH/DX by_state in,oh

===show/dxcc <prefix>===
*show/dxcc <prefix> - Interrogate the spot database by country
This command takes the <prefix> (which can be a full or partial callsign if desired), looks up which internal country number it is and then displays all the spots as per SH/DX for that country. This is now an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this command. e.g.
SH/DXCC G SH/DXCC W on 20m iota
This can be done with the SHOW/DX command like this:
SH/DX dxcc g
SH/DX dxcc w on 20m iota
This is an alias for: SH/DX dxcc

===show/dxqsl <callsign>===
*show/dxqsl <callsign> - Show any QSL info gathered from spots
The node collects information from the comment fields in spots (things like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database. This command allows you to interrogate that database and if the callsign is found will display the manager(s) that people have spotted. This information is NOT reliable, but it is normally reasonably accurate if it is spotted enough times. For example:
sh/dxqsl 4k9w
You can check the raw input spots yourself with:
sh/dx 4k9w qsl
This gives you more background information.

===show/dxstats [days] [date]===
*show/dxstats [days] [date] - Show the DX Statistics
Show the total DX spots for the last <days> no of days (default is 31), starting from a <date> (default: today).

===show/external_ip===
*show/external_ip - Show the external IP set/detected for the node and local terminal masquerade

===show/fdx===
*show/fdx - Show the DX data in realtime format.
Normally SHOW/DX outputs spot data in a different format to the realtime data. This is a deliberate policy (so you can tell the difference between the two). Some logging programs cannot handle this so SHOW/FDX outputs historical data in real time format. This is an alias for: SHOW/DX real

===show/files [<file area> [<string>]]===
*show/files [<file area> [<string>]] - List the contents of a file area
SHOW/FILES on its own will show you a list of the various file areas available on the system. To see the contents of a particular file area type:
SH/FILES <file area>
where <file area> is the name of the file area you want to see the contents of. You can also use shell globbing characters like '*' and '?' in a string to see a selection of files in a file area eg:
SH/FILES bulletins arld*
See also TYPE - to see the contents of a file.

===show/filter===
*show/filter - Show the contents of all the filters you have set
Show the contents of all the filters that are set. This command displays all the filters set - for all the various categories.

===show/hfstats [days] [date]===
*show/hfstats [days] [date] - Show the HF DX Statistics
Show the HF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a <date> (default: today).

===show/hftable [days] [date] [prefix ...]===
*show/hftable [days] [date] [prefix ...] - Show the HF DX Spotter Table
Show the HF DX Spotter table for the list of prefixes for the last <days> no of days (default is 31), starting from a <date> (default: today). If there are no prefixes then it will show the table for your country. Remember that some countries have more than one "DXCC country" in them (eg G :-), to show them (assuming you are not in G already which is specially treated in the code) you must list all the relevant prefixes
sh/hftable g gm gd gi gj gw gu
Note that the prefixes are converted into country codes so you don't have to list all possible prefixes for each country. If you want more or less days than the default simply include the number you require:
sh/hftable 20 pa
If you want to start at a different day, simply add the date in some recognizable form:
sh/hftable 2 25nov02
sh/hftable 2 25-nov-02
sh/hftable 2 021125
sh/hftable 2 25/11/02
This will show the stats for your DXCC for that CQWW contest weekend. You can specify either prefixes or full callsigns (so you can see how you did against all your mates). You can also say 'all' which will then print the worldwide statistics.
sh/hftable all

===show/hops <call> [ann|spots|route|wcy|wwv]===
*show/hops <call> [ann|spots|route|wcy|wwv] - Show the hop counts for a node
This command shows the hop counts set up for a node. You can specify which category you want to see. If you leave the category out then all the categories will be listed.

===show/isolate===
*show/isolate - Show list of ISOLATED nodes

===show/lockout <prefix>|all===
*show/lockout <prefix>|all - Show the list of locked out or excluded callsigns

===show/log [<callsign>]===
*show/log [<callsign>] - Show excerpts from the system log
This command outputs a short section of the system log. On its own it will output a general logfile. With the optional callsign it will show output from the log associated with that callsign.

===show/moon [ndays] [<prefix>|<callsign>]===
*show/moon [ndays] [<prefix>|<callsign>] - Show Moon rise and set times
Show the Moon rise and set times for a (list of) prefixes or callsigns, together with the azimuth and elevation of the sun currently at those locations. If you don't specify any prefixes or callsigns, it will show the times for your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), together with the current azimuth and elevation. In addition, it will show the illuminated fraction of the moons disk. If all else fails it will show the Moonrise and set times for the node that you are connected to. For example:
SH/MOON SH/MOON G1TLH W5UN
You can also use this command to see into the past or the future, so if you want to see yesterday's times then do:
SH/MOON -1
or in three days time:
SH/MOON +3 W9
Up to 366 days can be checked both in the past and in the future. Please note that the rise and set times are given as the UTC times of rise and set on the requested UTC day.

===show/muf <prefix> [<hours>][long]===
*show/muf <prefix> [<hours>][long] - Show the likely propagation to a prefix
This command allow you to estimate the likelihood of you contacting a station with the prefix you have specified. The output assumes a modest power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD). The result predicts the most likely operating frequencies and signal levels for high frequency (shortwave) radio propagation paths on specified days of the year and hours of the day. It is most useful for paths between 250 km and 6000 km, but can be used with reduced accuracy for paths shorter or longer than this. The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and used to predict the MUF given the predicted flux, day of the year, hour of the day and geographic coordinates of the transmitter and receiver. This routine is reasonably accurate for the purposes here, with a claimed RMS error of 3.8 MHz, but much smaller and less complex than the programs used by major shortwave broadcasting organizations, such as the Voice of America. The command will display some header information detailing its assumptions, together with the locations, latitude and longitudes and bearings. It will then show UTC (UT), local time at the other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path(Zen) and the likely signal strengths. Then for each frequency for which the system thinks there is a likelihood of a circuit it prints a value. The value is currently a likely S meter reading based on the conventional 6dB / S point scale. If the value has a '+' appended it means that it is 1/2 an S point stronger. If the value is proceeded by an 'm' it means that there is likely to be much fading and by an 's' that the signal is likely to be noisy. By default SHOW/MUF will show the next two hours worth of data. You can specify anything up to 24 hours worth of data by appending the no of hours required after the prefix. For example:
SH/MUF W
produces:
RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms Location Lat / Long Azim East Dereham, Norfolk 52 41 N 0 57 E 47 United-States-W 43 0 N 87 54 W 299 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0 18 23 11.5 -35 mS0+ mS2 S3 19 0 11.2 -41 mS0+ mS2 S3
indicating that you will have weak, fading circuits on top band and 80m but usable signals on 40m (about S3). inputting:
SH/MUF W 24
will get you the above display, but with the next 24 hours worth of propagation data.
SH/MUF W L 24
SH/MUF W 24 Long
Gives you an estimate of the long path propagation characteristics. It should be noted that the figures will probably not be very useful, nor terrible accurate, but it is included for completeness.

===show/mydx===
*show/mydx - Show the DX data filtered with your spot filter.
SHOW/DX potentially shows all the spots available in the system. Using SHOW/MYDX will, instead, filter the available spots using any spot filter that you have set, first. This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow you to customize the spots that you receive. So if you have said: ACC/SPOT on hf Doing a SHOW/MYDX will now only, ever, show HF spots. All the other options on SH/DX can still be used.

===show/newconfiguration [<node>]===
*show/newconfiguration [<node>] - Show all the nodes and users visible
This command allows you to see all the users that can be seen and the nodes to which they are connected. This command produces essentially the same information as SHOW/CONFIGURATION except that it shows all the duplication of any routes that might be present. It also uses a different format which may not take up quite as much space if you don't have any loops. BE WARNED: the list that is returned can be VERY long!

===show/newconfiguration/node===
*show/newconfiguration/node - Show all the nodes connected locally
Show all the nodes connected to this node in the new format.

===show/node [<callsign> ...]===
*show/node [<callsign> ...] - Show the type and version number of nodes
Show the type and version (if connected) of the nodes specified on the command line. If no callsigns are specified then a sorted list of all the non-user callsigns known to the system will be displayed.

===show/prefix <callsign>===
*show/prefix <callsign> - Interrogate the prefix database
This command takes the <callsign> (which can be a full or partial callsign or a prefix), looks up which internal country number it is and then displays all the relevant prefixes for that country together with the internal country no, the CQ and ITU regions. See also SHOW/DXCC.

===show/program===
*show/program - Show the locations of all the included program modules
Show the name and location where every program module was load from. This is useful for checking where you think you have loaded a .pm file from.

===show/qra <lat> <long>===
*show/qra <lat> <long> - Convert lat/long to a QRA Grid locator
This is a multipurpose command that allows you either to calculate the distance and bearing between two locators or (if only one locator is given on the command line) the distance and bearing from your station to the locator. For example:
SH/QRA IO92Q
SH/QRA JN06 IN73
The first example will show the distance and bearing to the locator from yourself, the second example will calculate the distance and bearing from the first locator to the second. You can use 4 or 6 character locators. It is also possible to convert a latitude and longitude to a locator by using this command with a latitude and longitude as an argument, for example:
SH/QRA 52 41 N 0 58 E

===show/qra <locator> [<locator>]===
*show/qra <locator> [<locator>] - Show distance between QRA Grid locators

===show/qrz <callsign>===
*show/qrz <callsign> - Show any callbook details on a callsign
This command queries the QRZ callbook server on the internet and returns any information available for that callsign. This service is provided for users of this software by http://www.qrz.com See also SHOW/WM7D for an alternative.

===show/registered [<prefix>]===
*show/registered [<prefix>] - Show the registered users

===show/route <callsign> ...===
*show/route <callsign> ... - Show the route to the callsign
This command allows you to see to which node the callsigns specified are connected. It is a sort of inverse sh/config.
sh/route n2tly

===show/satellite <name> [<hours> <interval>]===
*show/satellite <name> [<hours> <interval>] - Show tracking data
Show the tracking data from your location to the satellite of your choice from now on for the next few hours. If you use this command without a satellite name it will display a list of all the satellites known currently to the system. If you give a name then you can obtain tracking data of all the passes that start and finish 5 degrees below the horizon. As default it will give information for the next three hours for every five minute period. You can alter the number of hours and the step size, within certain limits. Each pass in a period is separated with a row of '-----' characters. So for example:
SH/SAT AO-10
SH/SAT FENGYUN1 12 2

===show/startup===
*show/startup - View your own startup script
View the contents of a startup script created with SET/STARTUP.

===show/startup <call>===
*show/startup <call> - View a user startup script

===show/station all [<regex>]===
*show/station all [<regex>] - Show list of users in the system

===show/station [<callsign> ..]===
*show/station [<callsign> ..] - Show information about a callsign
Show the information known about a callsign and whether (and where) that callsign is connected to the cluster.
SH/ST G1TLH
If no callsign is given then show the information for yourself.

===show/sun [ndays] [<prefix>|<callsign>]===
*show/sun [ndays] [<prefix>|<callsign>] - Show sun rise and set times
Show the sun rise and set times for a (list of) prefixes or callsigns, together with the azimuth and elevation of the sun currently at those locations. If you don't specify any prefixes or callsigns, it will show the times for your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), together with the current azimuth and elevation. If all else fails it will show the sunrise and set times for the node that you are connected to. For example:
SH/SUN
SH/SUN G1TLH K9CW ZS
You can also use this command to see into the past or the future, so if you want to see yesterday's times then do:
SH/SUN -1
or in three days time:
SH/SUN +3 W9
Up to 366 days can be checked both in the past and in the future. Please note that the rise and set times are given as the UTC times of rise and set on the requested UTC day.

===show/time [<prefix>|<callsign>]===
*show/time [<prefix>|<callsign>] - Show the local time
If no prefixes or callsigns are given then this command returns the local time and UTC as the computer has it right now. If you give some prefixes then it will show UTC and UTC + the local offset (not including DST) at the prefixes or callsigns that you specify.

===show/usdb [call ..]===
*show/usdb [call ..] - Show information held on the FCC Call database
Show the City and State of a Callsign held on the FCC database if his is being run on this system, eg:
sh/usdb k1xx

===show/vhfstats [days] [date]===
*show/vhfstats [days] [date] - Show the VHF DX Statistics
Show the VHF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a date (default: today).

===show/vhftable [days] [date] [prefix ...]===
*show/vhftable [days] [date] [prefix ...] - Show the VHF DX Spotter Table
Show the VHF DX Spotter table for the list of prefixes for the last <days> no of days (default is 31), starting from a date (default: today). If there are no prefixes then it will show the table for your country. Remember that some countries have more than one "DXCC country" in them (eg G :-), to show them (assuming you are not in G already which is specially treated in the code) you must list all the relevant prefixes:
sh/vhftable g gm gd gi gj gw gu
Note that the prefixes are converted into country codes so you don't have to list all possible prefixes for each country. If you want more or less days than the default simply include the number you require:
sh/vhftable 20 pa
If you want to start at a different day, simply add the date in some recognizable form:
sh/vhftable 2 25nov02
sh/vhftable 2 25-nov-02
sh/vhftable 2 021125
sh/vhftable 2 25/11/02
This will show the stats for your DXCC for that CQWW contest weekend. You can specify either prefixes or full callsigns (so you can see how you did against all your mates). You can also say 'all' which will then print the worldwide statistics.
sh/vhftable all

===show/wcy===
*show/wcy - Show last 10 WCY broadcasts

===show/wcy <n>===
show/wcy <n> - Show last <n> WCY broadcasts
Display the most recent WCY information that has been received by the system.

===show/wm7d <callsign>===
*show/wm7d <callsign> - Show callbook details on a US callsigns
This command queries the WM7D callbook server on the internet and returns any information available for that US callsign. This service is provided for users of this software by http://www.wm7d.net. See also SHOW/QRZ.

===show/wwv===
*show/wwv - Show last 10 WWV broadcasts

===show/wwv <n>===
*show/wwv <n> - Show last <n> WWV broadcasts
Display the most recent WWV information that has been received by the system.

==SHUTDOWN==
===shutdown===
shutdown - Shutdown the cluster
Shutdown the cluster and disconnect all the users

==SPOOF==
===spoof <call> <command>===
*spoof <call> <command> - Do a command as though you are another user
This command is provided so that sysops can set a user's parameters without me having to write a special 'sysop' version for every user command. It allows you to pretend that you are doing the command as the user you specify.eg:
SPOOF G1TLH set/name Dirk
SPOOF G1TLH set/qra JO02LQ

==STAT==
===stat/channel [<callsign>]===
*stat/channel [<callsign>] - Show the status of a channel on the cluster
Show the internal status of the channel object either for the channel that you are on or else for the callsign that you asked for. Only the fields that are defined (in perl term) will be displayed.

===stat/db <dbname>===
*stat/db <dbname> - Show the status of a database
Show the internal status of a database descriptor. Depending on your privilege level you will see more or less information. This command is unlikely to be of much use to anyone other than a sysop.

===stat/msg===
*stat/msg - Show the status of the message system

===stat/msg <msgno>===
*stat/msg <msgno> - Show the status of a message
This command shows the internal status of a message and includes information such as to whom it has been forwarded, its size, origin etc etc. If no message number is given then the status of the message system is displayed.

===stat/route_node <callsign>===
*stat/route_node <callsign> - Show the data in a Route::Node object

===stat/route_node all===
*stat/route_node all - Show list of all Route::Node objects

===stat/route_user <callsign>===
*stat/route_user <callsign> - Show the data in a Route::User object

===stat/route_user all===
*stat/route_user all - Show list of all Route::User objects

===stat/user [<callsign>]===
*stat/user [<callsign>] - Show the full status of a user
Shows the full contents of a user record including all the secret flags and stuff. Only the fields that are defined (in perl term) will be displayed.

==SYSOP==
===sysop===
sysop - Regain your privileges if you login remotely
The system automatically reduces your privilege level to that of anormal user if you login in remotely. This command allows you to regain your normal privilege level. It uses the normal system: five numbers are returned that are indexes into the character array that is your assigned password (see SET/PASSWORD). The indexes start from zero. You are expected to return a string which contains the characters required in the correct order. You may intersperse those characters with others to obscure your reply for any watchers. For example (and these values are for explanation :-):
password = 012345678901234567890123456789 > sysop 22 10 15 17 3
you type:
aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
They will all match. If there is no password you will still be offered numbers but nothing will happen when you input a string. Any match is case sensitive.

==TALK==
===talk <call> > <node> [<text>]===
*talk <call> > <node> [<text>] - Send a text message to another station via a node
Send a short message to any other station that is visible on the cluster system. You can send it to anyone you can see with a SHOW/CONFIGURATION command, they don't have to be connected locally. The second form of TALK is used when other cluster nodes are connected with restricted information. This usually means that they don't send the user information usually associated with logging on and off the cluster. If you know that G3JNB is likely to be present on GB7TLH, but you can only see GB7TLH in the SH/C list but with no users, then you would use the second form of the talk message. If you want to have a ragchew with someone you can leave the text message out and the system will go into 'Talk' mode. What this means is that a short message is sent to the recipient telling them that you are in a 'Talking' frame of mind and then you just type - everything you send will go to the station that you asked for. All the usual announcements, spots and so on will still come out on your terminal. If you want to do something (such as send a spot) you precede the normal command with a '/' character, eg:
/DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
To leave talk mode type:
/EX
If you are in 'Talk' mode, there is an extension to the '/' command which allows you to send the output to all the people you are talking to. You do with the '//' command. For example:
//sh/hftable
will send the hftable as you have it to all the people you are currently talking to.

===talk <call> [<text>]===
*talk <call> [<text>] - Send a text message to another station

==TYPE==
===type <filearea>/<name>===
*type <filearea>/<name> - Look at the contents of a file in one of the file areas
Type out the contents of a file in a file area. So, for example, in file area 'bulletins' you want to look at file 'arld051' you would enter:
TYPE bulletins/arld051
See also SHOW/FILES to see what file areas are available and a list of content.

==UNCATCHUP==
===uncatchup <node call> all|[msgno> ...]===
*uncatchup <node call> all|[msgno> ...] - Unmark a message as sent
When you send messages the fact that you have forwarded it to another node is remembered so that it isn't sent again. When you have a new partner node and you add their callsign to your /spider/msg/forward.pl file, all outstanding non-private messages will be forwarded to them. This may well be ALL the non-private messages. You can prevent this by using these commands:
catchup GB7DJK all
catchup GB7DJK 300 301 302 303 500-510
and to undo what you have just done:
uncatchup GB7DJK all
uncatchup GB7DJK 300 301 302 303 500-510
which will arrange for them to be forward candidates again. Order is not important.

==UNSET==
===unset/announce===
unset/announce - Stop announce messages coming out on your terminal

===unset/anntalk===
*unset/anntalk - Stop talk like announce messages on your terminal
The announce system on legacy cluster nodes is used as a talk substitute because the network is so poorly connected. If you:
unset/anntalk
you will suppress several of these announces, you may miss the odd useful one as well, but you would probably miss them anyway in the welter of useless ones.
set/anntalk
allows you to see them again. This is the default.

===unset/baddx <call>..===
*unset/baddx <call>.. - Propagate a dx spot with this callsign again
Setting a word as 'baddx' will prevent spots with that word in the 'spotted' field (as in: DX 14001.1 FR0G) of a DX spot from going any further. They will not be displayed and they will not be sent onto other nodes. The word must be written in full, no wild cards are allowed eg:
set/baddx FORSALE VIDEO FR0G
To allow a word again, use the following command ...
unset/baddx VIDEO

===unset/badnode <call>..===
*unset/badnode <call>.. - Allow spots from this node again
Setting a callsign as a 'badnode' will prevent spots from that node going any further. They will not be displayed and they will not be sent onto other nodes. The call must be a full eg:
set/badnode K1TTT
will stop anything from K1TTT. If you want SSIDs as well then you must enter them specifically.
unset/badnode K1TTT
will allow spots from him again. Use with extreme care. This command may well be superseded by FILTERing.

===unset/badspotter <call>..===
*unset/badspotter <call>.. - Allow spots from this callsign again
Setting a callsign as a 'badspotter' will prevent spots from this callsign going any further. They will not be displayed and they will not be sent onto other nodes. The call must be written in full, no wild cards are allowed eg:
set/badspotter VE2STN
will stop anything from VE2STN. This command will automatically stop spots from this user, regardless of whether or which SSID he uses. DO NOT USE SSIDs in the callsign, just use the callsign as above or below.
unset/badspotter VE2STN
will allow spots from him again. Use with extreme care. This command may well be superseded by FILTERing.

===unset/badword <word>..===
*unset/badword <word>.. - Propagate things with this word again
Setting a word as a 'badword' will prevent things like spots, announces or talks with this word in the the text part from going any further. They will not be displayed and they will not be sent onto other nodes. The word must be written in full, no wild cards are allowed eg:
set/badword annihilate annihilated annihilation
will stop anything with these words in the text.
unset/badword annihilated
will allow text with this word again.

===unset/beep===
*unset/beep - Stop beeps for DX and other messages on your terminal

===unset/debug <name>===
*unset/debug <name> - Remove a debug level from the debug set
You can choose to log several different levels. The levels are
chan state msg cron connect
You can show what levels you are logging with SHOW/DEBUG

===unset/dx===
*unset/dx - Stop DX messages coming out on your terminal

===unset/dxcq===
*unset/dxcq - Stop CQ Zones on the end of DX announcements
Display both the Spotter's and the Spotted's CQ Zone on the end of a DX announcement (there is just enough room). Some user programs cannot cope with this. The Spotter's CQ is on the RHS of the time, the Spotted's CQ is on the LHS. Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE. Do a STAT/USER to see which flags you have set if you are confused.

===unset/dxgrid===
*unset/dxgrid - Stop QRA Grid Squares on the end of DX announcements
A standard feature which is enabled in version 1.43 and above is that if the spotter's grid square is known it is output on the end of a DX announcement (there is just enough room). Some user programs cannot cope with this. You can use this command to reset (or set)this feature. Conflicts with: SET/DXCQ, SET/DXITU. Do a STAT/USER to see which flags you have set if you are confused.

===unset/dxitu===
*unset/dxitu - Stop ITU Zones on the end of DX announcements
Display both the Spotter's and the Spotted's ITU Zone on the end of a DX announcement (there is just enough room). Some user programs cannot cope with this. The Spotter's ITU is on the RHS of the time, the Spotted's ITU is on the LHS. Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE. Do a STAT/USER to see which flags you have set if you are confused.

===unset/echo===
*unset/echo - Stop the cluster echoing your input
If you are connected via a telnet session, different implementations of telnet handle echo differently depending on whether you are connected via port 23 or some other port. You can use this command to change the setting appropriately. The setting is stored in your user profile. YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.

===unset/email===
*unset/email - Stop personal msgs being forwarded by email
If any personal messages come in for your callsign then you can use these commands to control whether they are forwarded onto your email address. To enable the forwarding do something like:
SET/EMAIL mike.tubby@somewhere.com
You can have more than one email address (each one separated by a space). Emails are forwarded to all the email addresses you specify. You can disable forwarding by:
UNSET/EMAIL

===unset/here===
*unset/here - Tell the system you are absent from your terminal

===unset/hops <call> ann|spots|route|wwv|wcy===
*unset/hops <call> ann|spots|route|wwv|wcy - Unset hop count
Set the hop count for a particular type of broadcast for a node. This command allows you to set up special hop counts for a node for currently: announce, spots, wwv and wcy broadcasts.eg:
set/hops gb7djk ann 10
set/hops gb7mbc spots 20
Set SHOW/HOPS for information on what is already set. This commandcreates a filter and works in conjunction with the filter system. You can unset the hops with command UNSET/HOPS. For example:
unset/hops gb7djk ann
unset/hops gb7mbc spots

===unset/isolate===
*unset/isolate - Stop Isolation of a node from the rest of the network
Remove isolation from a node - SET/ISOLATE

===unset/lockout <call>===
*unset/lockout <call> - Allow a callsign to connect to the cluster

===unset/logininfo===
*unset/logininfo - No longer inform when a station logs in/out locally

===unset/password <call> ...===
*unset/password <call> ... - Delete (remove) a user's password
This command allows the sysop to completely delete and remove a password for a user.

===unset/privilege===
*unset/privilege - Remove any privilege for this session
You can use this command to 'protect' this session from unauthorized use. If you want to get your normal privilege back you will need to either logout and login again (if you are on a console) or use the SYSOP command.

===unset/prompt===
*unset/prompt - Set your prompt back to default
This command will set your user prompt to the string that you say. The point of this command to enable a user to interface to programs that are looking for a specific prompt (or else you just want a different prompt).
SET/PROMPT clx >
There are some substitutions that can be added to the prompt:
%C - callsign [which will have ( and ) around it if not here]
%D - date
%T - time
%M - cluster 'mycall'
The standard prompt is defined as:
SET/PROMPT %C de %M %D %T dxspider >
UNSET/PROMPT will undo the SET/PROMPT command and set your prompt back to normal.

===unset/register <call> ...===
*unset/register <call> ... - Mark a user as not registered
Registration is a concept that you can switch on by executing the
set/var $main::regreq = 1
command (usually in your startup file). If a user is NOT registered then, firstly, instead of the normal motd file (/spider/data/motd) being sent to the user at startup, the user is sent the motd_nor file instead. Secondly, the non-registered user only has READ-ONLY access to the node. The non-registered user cannot use DX, ANN etc. The only exception to this is that a non-registered user can TALK or SEND messages to the sysop.

===unset/startup===
*unset/startup - Remove your own startup script
You can remove your startup script with UNSET/STARTUP.

===unset/startup <call>===
*unset/startup <call> - Remove a user startup script

===unset/talk===
*unset/talk - Stop TALK messages coming out on your terminal

===unset/usstate===
*unset/usstate - Stop US State info on the end of DX announcements
If the spotter's or spotted's US State is known it is output on the end of a DX announcement (there is just enough room). A spotter's state will appear on the RHS of the time (like SET/DXGRID) and the spotted's state will appear on the LHS of thetime field. Any information found will override any locator information from SET/DXGRID. Some user programs cannot cope with this. You can use this command to reset (or set) this feature. Conflicts with: SET/DXCQ, SET/DXITU. Do a STAT/USER to see which flags you have set if you are confused.

===unset/wcy===
*unset/wcy - Stop WCY messages coming out on your terminal

===unset/wwv===
*unset/wwv - Stop WWV messages coming out on your terminal

===unset/wx===
*unset/wx - Stop WX messages coming out on your terminal

==WHO==
===who===
*who - Show who is physically connected
This is a quick listing that shows which callsigns are connected and what sort of connection they have.

==WX==
===wx <text>===
*wx <text> - Send a weather message to local users

===wx full <text>===
*wx full <text> - Send a weather message to all cluster users

===wx sysop <text>===
*wx sysop <text> - Send a weather message to other clusters only
Weather messages can sometimes be useful if you are experiencing an extreme that may indicate enhanced conditions.

The crontab file

2025-04-04T14:57:10Z

G0TRT: Added some crontab links and the set/external_ip job

==General Information==

Crontab is a tool for setting up cron jobs to automatically run scripts and commands at a predefined time. [https://linuxhandbook.com/crontab/ Details] and [https://crontab.guru/ tools] are useful for those new to cron. The following relates to all versions of DXSpider and is not platform related.

===The crontab file===

====Check for, and establish connections====

Login as 'sysop' and create a file in /spider/local_cmd called crontab. Edit it with your favourite editor and add a line like this (I have included a comment)

# Establish connections
# check every 10 minutes to see if gb7xxx is connected and if not, start a connect job going
0,10,20,30,40,50 * * * * start_connect('gb7xxx') unless connected('gb7xxx')

The callsign involved will be the callsign of the cluster node you are going to connect to. This will now check every 10 minutes to see if gb7xxx is connected, if it is then nothing will be done. If it is not, then a connect attempt will be started.

====Keep DXspider up-to-date with the latest version====

# Check for update using EA3CV's update utilities each night prior to update
30 22 * * * spawn('cd /spider/local_cmd; wget -q https://raw.githubusercontent.com/EA3CV/dxspider_info/main/check_build.pl -O /spider/local_cmd/check_build.pl')
32 22 * * * spawn('cd /spider/local_cmd; wget -q https://raw.githubusercontent.com/EA3CV/dxspider_info/main/undo_newbuild.pl -O /spider/local_cmd/undo_newbuild.pl')
35 22 * * * run_cmd('load/cmd')
#
# Check for updates on weekdays at 23:35 and 03:07, avoiding contest times at weekends. Y 5 is yes to backups, and keep 5 of them.
35 23 * * 1,2,3,4,5 run_cmd("check_build Y 5")
07 03 * * 1,2,3,4,5 run_cmd("check_build Y 5")

====Set your dynamic external ip address====

#Check your dynamic external IP address and change it in dxspider if needed
00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('set/external_ip')

The crontab file

2025-04-03T13:53:16Z

G0TRT: Added EA3CV's update utility.

==General Information==

The following relates to all versions of DXSpider and is not platform related.

===The crontab file===

====Check for, and establish connections====

Login as 'sysop' and create a file in /spider/local_cmd called crontab. Edit it with your favourite editor and add a line like this (I have included a comment)

# Establish connections
# check every 10 minutes to see if gb7xxx is connected and if not, start a connect job going
0,10,20,30,40,50 * * * * start_connect('gb7xxx') unless connected('gb7xxx')

The callsign involved will be the callsign of the cluster node you are going to connect to. This will now check every 10 minutes to see if gb7xxx is connected, if it is then nothing will be done. If it is not, then a connect attempt will be started.

====Keep DXspider up-to-date with the latest version====

# Check for update using EA3CV's update utilities each night prior to update
30 22 * * * spawn('cd /spider/local_cmd; wget -q https://raw.githubusercontent.com/EA3CV/dxspider_info/main/check_build.pl -O /spider/local_cmd/check_build.pl')
32 22 * * * spawn('cd /spider/local_cmd; wget -q https://raw.githubusercontent.com/EA3CV/dxspider_info/main/undo_newbuild.pl -O /spider/local_cmd/undo_newbuild.pl')
35 22 * * * run_cmd('load/cmd')
#
# Check for updates on weekdays at 23:35 and 03:07, avoiding contest times at weekends. Y 5 is yes to backups, and keep 5 of them.
35 23 * * 1,2,3,4,5 run_cmd("check_build Y 5")
07 03 * * 1,2,3,4,5 run_cmd("check_build Y 5")

Hints, tips and common questions

2025-03-12T15:21:04Z

G0TRT:

==Hints, tips and common questions==

'''Q. These commands seem very long! Can I shorten them?
'''
Of course you can and the usual abbreviations work. If you are unsure, try it.

'''Q. I am not sure if this command is correct. Can I cause any harm if I try it?'''

Do not be afraid to try a command to see if it will work, at the worst you will get an error message. If you require any help on a command, just type help followed by the command you want help on.
Look at the "DXSpider Command Reference" section to see what help can be found.

'''Q. How should I use the announce command?'''

With respect. Use the command by all means, but please only use the "full" extension if absolutely necessary. It can create a LOT of messages passing between clusters.

'''Q. I like to be working in the shack while logged into the cluster but I can't be looking at the screen all the time. How can I be alerted when anything happens?'''

Use the SET/BEEP command. You can find information on this in the "DXSpider Command Reference" section.

'''Q. I got disconnected from the cluster and now I can't log back in again. What is wrong?'''

Probably the cluster thinks you are still logged on and will not let you reconnect using the same call to prevent loops. Try logging on again adding an ssid to your callsign as DXSpider treats G0YLM and G0YLM-1 as different users.

'''Q. How do I know if I have got the latest version of this user manual?'''

The latest and greatest will always be on the Website. It will also be included with every release of DXSpider. As always, if unsure, ask your sysop what version number is the latest.

'''Q. Where are the recent changes to DXSpider listed?'''

Changes can be viewed either by using the git log command in the spider/ directory or by reading the Changes file, also in the spider/ directory.

Hints, tips and common questions

2025-03-12T15:20:04Z

G0TRT: Added Q. Where are the recent changes to DXSpider listed?

==Hints, tips and common questions==

'''Q. These commands seem very long! Can I shorten them?
'''
Of course you can and the usual abbreviations work. If you are
unsure, try it.

'''Q. I am not sure if this command is correct. Can I cause any harm if I try it?'''

Do not be afraid to try a command to see if it will work, at the
worst you will get an error message. If you require any help on a
command, just type help followed by the command you want help on.
Look at the "DXSpider Command Reference" section to see what help can
be found.

'''Q. How should I use the announce command?'''

With respect. Use the command by all means, but please only use the
"full" extension if absolutely necessary. It can create a LOT of
messages passing between clusters.

'''Q. I like to be working in the shack while logged into the cluster but I can't be looking at the screen all the time. How can I be alerted when anything happens?'''

Use the SET/BEEP command. You can find information on this in the
"DXSpider Command Reference" section.

'''Q. I got disconnected from the cluster and now I can't log back in again. What is wrong?'''

Probably the cluster thinks you are still logged on and will not let
you reconnect using the same call to prevent loops. Try logging on
again adding an ssid to your callsign as DXSpider treats G0YLM and
G0YLM-1 as different users.

'''Q. How do I know if I have got the latest version of this user manual?'''

The latest and greatest will always be on the Website. It will also
be included with every release of DXSpider. As always, if unsure, ask
your sysop what version number is the latest.

'''Q. Where are the recent changes to DXSpider listed?'''

Changes can be viewed either by using the git log command in the spider/ directory or by reading the Changes file, also in the spider/ directory.

DXSpider PC Packet Cluster Protocol

2025-03-11T06:18:14Z

G0TRT: Added PC93 breakdown

{| class="wikitable"
|+ Legacy Protocols
|-
! Topic !! Protocol
|-
| Talk mode || PC10^from-user^to-user^msg^bell-flag^ ^from-node^~
PC10^from-user^route-via-node^msg^bell-flag^to-user^origin-node^~
|-
| DX info || PC11^DXfreq^DXcall^date^time^comment-txt^user-rprt^origin-node^hops^~
|-
| Announcement || PC12^from-user^route-to-node^msg^sysop-flg^origin-node^wx-flg^hops^~
|-
| Stn into CONF || PC13^user^hops^
|-
| Stn out of CONF || PC14^user^hops^
|-
| Conference Mode || PC15^from-user^msg^hops^~
|-
| PC user add || PC16^node^user talk-mode here^user talk-mode here^...^hops^
|-
| PC user delete || PC17^user^node^hops^
|-
| PC initialization: RequestInit || PC18^cluster info^ver^
|-
| PC initialization: NodeAdd || PC19^here^node^talk^ver^...^hops^
|-
| PC initialization: InitDone || PC20^
|-
| PC initialization: NodeDelete || PC21^node^reason^hops^
|-
| PC initialization: PCDone || PC22^
|-
| WWV info || PC23^date^hour^SFI^A^K^forecast^logger^origin-node^hops^~
|-
| Here status info || PC24^user^here^hops^
|-
| DX/WWV merge req || PC25^route-to-node^route-from-node^DX-cnt^WWV-cnt^
|-
| Merge DX info || PC26^DXfreq^DXcall^date^time^comment-txt^spotter^origin-node^ ^~
|-
| Merge WWV info || PC27^date^hour^SFI^A^K^forecast^logger^origin-node^ ^~
|-
| PC Mail: SendSubject || PC28^route-to-node^route-from-node^to-user^from-user^date^time^private-flg^subject^bbs^no-lines^rr-flg^via-node^origin-node^~
|-
| PC Mail: SendText || PC29^route-to-node^route-from-node^stream-no^text^~
|-
| PC Mail: AckSubject || PC30^route-to-node^route-from-node^stream-no^
|-
| PC Mail: AckText || PC31^route-to-node^route-from-node^stream-no^
|-
| PC Mail: CompleteText || PC32^route-to-node^route-from-node^stream-no^
|-
| PC Mail: AckCompleteText || PC33^route-to-node^route-from-node^stream-no^
|-
| Remote commands: Command || PC34^route-to-node^route-from-node^cmd^~
|-
| Remote commands: Response || PC35^route-to-node^route-from-node^cmd-resp^~
|-
| Remote commands: Show Command || PC36^route-to-node^route-from-node^cmd^~
|-
| Remote commands: Needs db update || PC37^route-to-node^route-from-node^user^stream-no^cmd^~
|-
| PC initialization: Connected nodes || PC38^node,node,...^~
|-
| NodeDelete w/Discon || PC39^node^reason^
|-
| PC file forward || PC40^route-to-node^route-from-node^filename^bulletin^linecnt^
|-
| User info || PC41^user^type^info^hops^~
|-
| Forwarding abort || PC42^route-to-node^route-from-node^stream-no^
|-
| Remote DB request || PC44^route-to-node^route-from-node^stream-no^qualifier^key^user^
|-
| Remote DB response || PC45^route-to-node^route-from-node^stream-no^info^~
|-
| Remote DB complete || PC46^route-to-node^route-from-node^stream-no^
|-
| Remote DB update || PC47^route-to-node^route-from-node^user^qualifier^key^stream-no^
|-
| Remote userDB req || PC48^route-to-node^route-from-node^stream-no^qualifier^key^user^
|-
| Bulletin delete || PC49^from-user^subject^hops^
|-
| Local User count || PC50^node^user-count^hops^
|-
| Ping || PC51^route-to-node^route-from-node^ping-flag^
|-
| WCY Info || PC73^date^hour^SFI^A^K^ExpK^R^SA^GMF^Aurora^logger^origin-node^hops^
|}

{| class="wikitable"
|+ New protocols
|-
! Topic !! Protocol !! Description
|-
| DX Info || PC61^DXfreq^DXcall^date^time^comment-txt^user-rprt^origin-node^user-ip^hops^~ || P61 is a replacement for PC11 originating with Lee Sawkins, VE7CC. PC61 differs by allowing several significant digits after the frequency decimal. All other fields are the same, except for an added originating user IP address. The user IP can be IPv4 or IPv6.
|-
| General Info || PC9x^<node call>^<seconds since last midnight>^ || <seconds since last midnight> is the number of seconds since the beginning of "today" UTC. It *MUST* be unique and increase with each sentence. It can therefore be a decimal number. The idea being that if the next sentence is sent in the same second as the last one, then you append (for instance) '.01' on the end. If there is an other one: .02 etc. But you add any number of decimal points (eg '.1' or '.001') you like. Look at gen_pc9x_t in DXProtHandle.pm for an example.

At midnight, they all go back to 0.
|-
| Routing || PC92^GB7TLH^78031^C^5GB7TLH:5457^1G1TLH-2:XX.XX.XX.XX^5GB7DJK^H99^ || See breakdown below
|-
| Talk/Announce/WX || PC93^<node call>^<timestamp>^<to>^<from>^<via>^<text>[^<onode>][^<IPaddr>]^H99 || See breakdown below
|}
'''PC92 - Routing'''

The biggest change is that nodes only (ever) send their configuration (using a PC92) and the configuration of any *directly connected* "traditionally routing" nodes (TNODES) (ie still using PC16,17,19,21). The config stored of any TNODES is limited only to the local users on those nodes. Anything else is kept as hints, but is not transmitted onward, neither to other PC9x nodes nor other TNODES. The only configuration that other TNODES will see are the composite of all the PC92 nodes's configs + any other locally connected TNODES.

PC92 Nodes periodically output their configuration. Failure to receive a config after 3 update periods will cause that node's config to be erased (and the changes to be propagated to any connected TNODEs). Think OSPF.

All PC9x sentences contain a timestamp and the originating node call. This allows any of these sentences to be deduplicated and deliberate loops (for routing and new other functions) will allow things to continue to work as only "new" PC9x sentences will be processed.

All PC9x sentences are passed onto neighbouring PC9x unaltered apart from a decremented hop count.

Breakdown

Ex. PC92^GB7TLH^78031^C^5GB7TLH:5457^1G1TLH-2:XX.XX.XX.XX^5GB7DJK^H99^

GB7TLH - Originating Node

78031 - Timestamp - seconds since midnight

'C' current configuration record

'A' records add nodes or users

'D' records delete nodes or users.

'K' keep alive records

5GB7TLH:5457 ---.

|

5 is a bit map which is made up like this:-

Bit 1 - here/not here

Bit 2 - external, traditional PC protocol node

Bit 4 - Node

1 - User/here

4 - Node/not here - here flag is unset

5 - Node/here

7 - Traditional PC node/here

GB7TLH is the callsign

<nowiki>:</nowiki>5457 is the version number, other fields may be tacked on

The first slot after the 'C', 'A' or 'D', is always reserved for the node call. This slot may be empty (as in ...^A^^1G1TLH^... as opposed to ..^A^5GB7TLH^1G1TLH^..) if the node is the same as the node call after PC92. Any software must be able to cope with this empty slot.

The remaining payload...

Bitmap/Call/:IPaddress

Ex. 1G1TLH-2:XX.XX.XX.XX

<nowiki>*</nowiki>Note: the IP address may not always be present at this time.

H99 - hopcount

Note that DXSpider converts PC16/17/19/21 from *directly* connected PC only nodes into PC92 that look like:-

PC92^GB7TLH^78042^C^7GB7DJK-1:5453^1G1TLH-1^H99^

This means that GB7TLH has PC node GB7DJK-1 with user G1TLH-1 attached to it.

The principle being used here is similar to protocols like OSPF. A node *only* sends records that either come from it or PC nodes that it is "responsible" for. Nodes do *not* splurge out their local view of the network to cause even more confusion...

'K' Record Examples - Keep Alive

GB7DJK PC92^GB7TLH^82234^K^5GB7TLH:5457:568^3^1^H99^

|

build number -------------------'

WR3D PC92^GB7TLH^82744^K^7GB7DJK-1:5453^1^1^H99^

The first for the main PC9X handling node and the second for an attached Legacy PC protocol node. The two fields at the end are <no of nodes> and <no of users> respectively. You should note the similarity of this and the traditional PC50.

'''PC93 - Talk/Announce/WX'''

PC93^<node call>^<timestamp>^<to>^<from>^<via>^<text>[^<onode>][^<IPaddr>]^H99

NOTES:

* any ^ characters in <text> MUST be converted to %5E

* <to> can be a callsign (a talk), if I can route to it, I treat it as a talk.

WX (for weather).

SYSOP (sysop announcements).

<string> which is not recognised as a callsign by pattern recognition and is taken as a CHAT group (eg: LOGGER, #9000).

* (announce/full).

* <from> is the from users callsign

* <via> constrains whether it goes via a particular node set to * for now.

* <onode> is optional and is used when passing PC93s o.b.o non-PC9x handling nodes. Not currently used.

This is an announce:

PC93^IZ7AUH-6^79200^*^IZ7AUH-6^*^IZ7AUH-6 DX CLUSTER -> dx.iz7auh.net port 8000^^XX.XX.XX.XX^H97^

This a talk:

PC93^GB7TLH^81701^WR3D-2^G1TLH-2^*^wot?^H98^

This is a Chat message:

PC93^GB7TLH^81745^#9000^G1TLH-2^*^#48 anybody on?^H96^

Note that for backwards compatibility all chat <text> sections have a serial number #1->#999 + a space added to it. The first chat message sent after restart should be a random no in that range. This is designed to defeat any de-duping on announces.

DXSpider PC Packet Cluster Protocol

2025-03-11T06:13:19Z

G0TRT: