The DXSpider Administration Manual v1.50: Routing and Filtering

-Below is a complete list of commands available from the cluster prompt. -Most maintenance tasks are automatic but there are some commands that are useful -for a sysop. These are listed below in alphabetical order. The number in -brackets following the command name is the permissions level needed to use -the command - -accept/announce (0) - -

--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 FILTERS 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 eg: iota or qsl - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - wx 1 filter WX announces - dest eg: 6MUK,WDX (distros) - - -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 - - -This filter would only allow announces that were posted buy UK stations. -You can use the tag 'all' to accept everything eg: - - - acc/ann all - - -but this probably for advanced users... - -accept/announce (extended for sysops) (8) - -

--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/route (8) - -

--accept/route <call> [0-9] <pattern> Set an 'accept' filter line for routing - - -

-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 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 the callsign of the thingy - call_dxcc eg: 61,62 (from eg: sh/pre G) - call_itu - call_zone - origin really the interface it came in on - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - - -

-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 use the tag 'all' to accept everything eg: - - - acc/route all - - -accept/spots (0) - -

-An accept filter line means that if the spot matches this filter it is -passed onto the user. See HELP FILTERS for more info. Please read this -to understand how filters work - it will save a lot of grief later on. - -Please read the following section carefully. Though it looks similar, -reformatting, corrections, and hopefully clarifications have been added. - -You can use any of the following things in this line:- - - -Filters for the station being spotted: - call - call G --> G1AAA, GJ2BBB, GU3CCC, etc will be spotted - call K --> K1XX, K1XXX will be spotted - W1XX, W1XXX will NOT be spotted - call PA --> PA3EZL will be spotted - PB2FG will NOT be spotted - - call_dxcc - call_dxcc G --> G1AAA will be spotted - GU1AAA will NOT be spotted (different country) - call_dxcc K --> K1XX, W1XX will be spotted (same country) - call_dxcc 139 --> PA3EZL and PB2FG will be spotted - - call_itu - call_zone - -Filters for the callsign of the station doing the spotting: - by - by G --> spots from G1AAA, GJ2BBB, GU3CCC, etc will be spotted - by K --> spots from K1XX, K1XXX will be spotted - spots from W1XX, W1XXX will NOT be spotted - - by_dxcc - by_dxcc G --> spots from G1AAA will be spotted - spots from GU1AAA will NOT be spotted (different -country) - by_dxcc K --> spots from K1XX, W1XX will be spotted (same country) - by_dxcc 139 --> spots from PA3EZL or PB2FG will be spotted - - by_itu - by_zone - -Filters for the callsign of the "node" doing the spotting: - origin - origin K --> spots from a node starting with K will be spotted - spots from a node starting with KK will NOT be spotted - spots from a node starting with W will NOT be spotted - -Filters for the callsign of the connected node or user (channel) doing the spotting: - channel - channel W1HR --> spots from the connected node W1HR will be spotted - channel K1QX --> spots from the connected user K1QX will be spotted - - info eg: iota or qsl - freq eg: 0/30000 or hf or hf/cw or 6m,4m,2m - on same as 'freq' - - - -

-For frequencies, you can use any of the band names defined in -SHOW/BANDS and you can use a subband 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 - - -but this probably for advanced users... - -accept/spots (extended for sysops) (8) - -

-This version allows a sysop to set a filter for a callsign as well as the -default 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/wcy (0) - -

-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/wcy (extended for sysops) (8) - -

-This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- - - - accept/wcy node_default all - set/hops node_default 10 - - -accept/wwv (0) - -

-It is unlikely that you will want to do this, but if you do then you can -filter on the following fields:- - - - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - - -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. - -accept/wwv (extended for sysops) (8) - -

-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 - - -announce (0) - -

-Send an announcement to LOCAL users only, where <text> is the text -of the announcement you wish to broadcast. If you do not wish to receive -announces, use the set/noannounce command. Any announces made by -a sysop will override set/noannounce. - -announce full (0) - -

-This command will send your announcement across the whole cluster -network. - - -announce sysop (5) - -

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

-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 -commmands:- - - - 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. - -clear/announce (8) - -

--clear/announce <callsign> [input] [0-9|all] Clear an announce filter line - - -

-A sysop can clear an input or normal output filter for a user or the -node_default or user_default. - -clear/route (8) - -

-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. - -A sysop can clear an input or normal output filter for a user or the -node_default or user_default. - -clear/spots (0) - -

-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/spots (extended for sysops) (8) - -

-A sysop can clear an input or normal output filter for a user or the -node_default or user_default. - -clear/wcy (0) - -

-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/wcy (extended for sysops) (8) - -

-A sysop can clear an input or normal output filter for a user or the -node_default or user_default. - -clear/wwv (0) - -

-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. - -clear/wwv (extended for sysops) (8) - -

-A sysop can clear an input or normal output filter for a user or the -node_default or user_default. - -connect (5) - -

-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 (0) - -

-The title says it all really, this command lists all the databases defined -in the system. It is also aliased to SHOW/COMMAND. - -dbcreate (9) - -

--dbcreate <name> Create a database entry -dbcreate <name> chain <name> [<name>..] Create a -chained database entry -dbcreate <name> remote <node> Create a remote database -entry - - -

-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. - -See DBIMPORT for the importing of existing AK1A format data to databases. -See DBSHOW for generic database enquiry - -dbimport (9) - -

-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 (9) - -

-DBREMOVE will completely remove a database entry and also delete any data -file 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 datafile. - -I repeat: - -There is no warning, no comeback, no safety net. - -You have been warned. - -dbshow (0) - -

-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 (9) - -

-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. - -delete/user (9) - -

-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 (9) - -

-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 (0) - -

--directory List messages -directory all List all messages -directory own List your own messages -directory new List all new messages -directory to <call> List all messages to <call> -directory from <call> List all messages from <call> -directory subject <string> List all messages with <string> -in subject -directory <nn> List last <nn> messages -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 (extended for sysops) (5) - -

-Works just like the user command except that sysops can see ALL messages. - -disconnect (8) - -

-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. - -export (9) - -

-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 (9) - -

-Export the users database to a file in ascii format. If no filename -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 (0) - -

-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 14 -15 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 confortable 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 analyse the results that you get -without ringing up the sysop for help. - -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 exmaple 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/latlong (8) - -

--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 recieving 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/opername (1) - -

--forward/opername <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, Location -and Homenode. PC41s are only sent for the information that is available. - -help (0) - -

-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 (5) - -

-This command attempts to re-initialise 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. - -kill (0) - -

-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 (5) - -

--kill <msgno> [<msgno> ...] Remove or erase a message from -the system -kill from <call> Remove all messages from a callsign -kill to <call> Remove all messages to a callsign - - -

-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. - -As a sysop you can kill any message on the system. - -kill full (5) - -

-Delete a message (usually a 'bulletin') from the whole cluster system. - -This uses the subject field, so any messages that have exactly the same subject -will be deleted. Beware! - -kill/expunge (6) - -

-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. - - -links (0) - -

-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/aliases (9) - -

-Reload the /spider/cmd/Aliases file after you have editted 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 (9) - -

-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 targetted of each message. -If any of them match then that message is immediately deleted on receipt. - -load/badwords (9) - -

-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 (9) - -

-Reload the /spider/data/bands.pl file if you have changed it manually whilst -the cluster is running. - -load/cmd_cache (9) - -

-Normally, if you change a command file in the cmd or local_cmd tree it will -automatially 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 (9) - -

--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/messages (9) - -

-If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne -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 (9) - -

-Reload the /spider/data/prefix_data.pl file if you have changed it manually -whilst the cluster is running. - -merge (5) - -

-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 (9) - -

-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 - change TO callsign to - MSG FRom - change FROM callsign to - MSG PRrivate - set private flag - MSG NOPRrivate - unset private flag - MSG RR - set RR flag - MSG NORR - unset RR flag - MSG KEep - set the keep flag (message won't be deleted ever) - MSG NOKEep - unset the keep flag - MSG SUbject - change the subject to - MSG WAittime - remove any waitting time for this message - MSG NOREad - mark message as unread - MSG REad - 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 (8) - -

-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^ - -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. - - pc G1TLH Try doing that properly!!! - -ping (1) - -

-his 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 (1) - -

-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 dependant 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 (0) - -

--read Read the next unread personal message addressed to you -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 (extended for sysops) (5) - -

-Create an 'reject this announce' line for a filter. - -An reject filter line means that if the announce matches this filter it is -passed onto the user. See HELP FILTERS 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 eg: iota or qsl - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - wx 1 filter WX announces - dest eg: 6MUK,WDX (distros) - - -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/announce (extended for sysops) (8) - -

--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/route (8) - -

--reject/route <call> [0-9] <pattern> Set an 'reject' filter line for routing - - -

-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 the callsign of the thingy - call_dxcc eg: 61,62 (from eg: sh/pre G) - call_itu - call_zone - origin really the interface it came in on - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - - -

-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) - - -reject/spots (0) - -

-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 FILTERS 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 eg: 0/30000 or hf or hf/cw or 6m,4m,2m - on same as 'freq' - call eg: G,PA,HB9 - info eg: iota or qsl - by - call_dxcc eg: 61,62 (from eg: sh/pre G) - call_itu - call_zone - by_dxcc - by_itu - by_zone - origin - channel - - -For frequencies, you can use any of the band names defined in -SHOW/BANDS and you can use a subband 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/spots (extended for sysops) (8) - -

--reject/spots <call> [input] [0-9] <pattern> - Reject 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/wcy (0) - -

-It is unlikely that you will want to do this, but if you do then you can -filter on the following fields:- - - - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - - -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/wcy (extended for sysops) (8) - -

--reject/wcy <call> [input] [0-9] <pattern> - WCY reject 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/wwv (0) - -

-It is unlikely that you will want to do this, but if you do then you can -filter on the following fields:- - - - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - - -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. - -reject/wwv (extended for sysops) (8) - -

--reject/wwv <call> [input] [0-9] <pattern> - WWV reject 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 - - -reply (0) - -

--reply Reply (privately) to the last message that you have read -reply <msgno> Reply (privately) to the specified message -reply B <msgno> Reply as a Bulletin to the specified message -reply NOPrivate <msgno> Reply as a Bulletin to the specified -message -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) - -send (0) - -

--send <call> [<call> ...] Send a message to -one or more callsigns -send RR <call> Send a message and ask for a read receipt -send COPY <msgno> <call> Send a copy of a message -to someone -send PRIVATE <call> Send a personal message -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. - -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 - -set/address (0) - -

--set/arcluster <node_call> [<node_call> ...] Make -the node_call an AR-Cluster type node - - -

--set/baddx <call> Stop words we do not wish to see in the callsign field -of a dx spot being propagated - - -

-Setting a word as 'baddx' will prevent spots with that word in the callsign -field 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 wriiten 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 - - -set/badnode (6) - -

--set/badnode <node_call> Stop spots from this node_call -being propagated - - -

-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 can be a full or partial call (or a prefix), eg:- - - - set/badnode K1TTT - - -will stop anything from K1TTT (including any SSID's) - - - unset/badnode K1TTT - - -will allow spots from him again. - -Use with extreme care. This command may well be superceded by FILTERing. - -set/badspotter (8) - -

-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. If you want SSIDs as well then you must -enter them specifically. - - - unset/badspotter VE2STN - - -will allow spots from him again. - -Use with extreme care. This command may well be superceded by FILTERing. - -set/badword (8) - -

-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. - - -set/beep (0) - -

--set/clx <node_call> [<node_call> ...] Make -the node_call a CLX type node - - -

-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 the show/debug -command. - -You can remove a debug level with unset/debug <name> - -set/dx (0) - -

-Some logging programs do not like the additional information at -the end of a DX spot. If this is the case, use the unset/dxgrid -command to remove the grid squares. - -set/dxnet (5) - -

--set/dxnet <node_call> [<node_call> ...] Make -the node_call a DXNet type node - - -

-If you are connected via a telnet session, different implimentations -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. - -You can remove the echo with the unset/echo command - -The setting is stored in your user profile. - -YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25. - -set/email (0) - -

--set/email <email_address> Set email address(es) and forward your personals - - -

-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 - -set/here (0) - -

-Let others on the cluster know you are here by only displaying your -callsign. If you are away from your terminal you can use the unset/here -command to let people know you are away. This simply puts brackets -around your callsign to indicate you are not available. - -set/homenode (0) - -

-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 (8) - -

-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 command -creates a filter and works in conjunction with the filter system. - -set/isolate (9) - -

-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. - -You can see which nodes are isolated with the show/isolate (1) command. - -You can remove the isolation with the command unset/isolate. - -set/language (0) - -

-You can select the language that you want the cluster to use. Currently -the languages available are en (English) and nl (Dutch). - -set/location (0) - -

-You can set your latitude and longitude manually or alternatively use the -set/qra command which will do the conversion for you. - - - set/location 54 04 N 2 02 E - - - -set/sys_location (9) - -

-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/logininfo (0) - -

-Show users and nodes when they log in and out of the local cluster. You -can stop these messages by using the unset/logininfo command. - - -set/lockout (9) - -

-You can show who is locked out with the show/lockout command. -To allow the user to connect again, use the unset/lockout command. - -set/name (0) - -

-Tell the cluster what your name is, eg:- - - - set/name Dirk - - -set/node (9) - -

-Tell the system that the call(s) are to be treated as AK1A cluster and -fed PC Protocol rather normal user commands. - -From version 1.41 you can also set the following types of cluster - - - set/spider - set/dxnet - set/clx - set/arcluster - - -To see what your nodes are set to, use the show/nodes command. - -set/obscount (9) - -

--set/obscount <count> <node call> Set the 'pump-up' -obsolescence counter - - -

-From version 1.35 onwards neighbouring 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. - -set/page (0) - -

-Tell the system how many lines you wish on a page when the number of lines -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 (0) - -

-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 (9) - -

-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. - -The command "unset/password" is provided to allow a sysop to remove a -users password completely in case a user forgets or loses their password. - -set/pinginterval (9) - -

-set/pinginterval <time> <node call> Set the ping time -to neighbouring nodes - - -

-As from version 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 60 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. - -set/privilege (9) - -

--set/privilege <n> <call> [<call> ...] Set the -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 disc- - connect), 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/spider (5) - -

--set/spider <node_call> [<node_call> ...] Make -the node_call a DXSpider type node - - -

-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 (0) - -

-Tell the system where your are. For example:- - - - set/qth East Dereham, Norfolk - - -set/register (9) - -

-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. - -To unset a user use the 'unset/register' command - -set/talk (0) - -

-Allow talk messages to arrive at your console. You can switch off -talks with the unset/talk command. - -set/wcy (0) - -

-Allow WCY information to be seen at your console. You can switch off -WCY messages with the unset/wcy command. - -set/wwv (0) - -

-Allow WWV information to be seen at your console. You can switch off -WWV messages with the unset/wwv command. - -set/wx (0) - -

-Allow WX information to be seen at your console. You can switch off -WX messages with the unset/wx command. - -show/baddx (1) - -

-Display all the bad dx callsigns in the system, see SET/BADDX -for more information. - -show/badnode (6) - -

-Display all the bad node callsigns in the system, see SET/BADNODE -for more information. - -show/badspotter (1) - -

-Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER -for more information. - -show/badword (1) - -

-Display all the bad words in the system, see SET/BADWORD -for more information. - -show/configuration (0) - -

-This command allows you to see all the users that can be seen -and the nodes to which they are connected. With the optional node, -you can specify a particular node to look at. - -This command is normally abbreviated to: sh/c - -BE WARNED: the list that is returned can be VERY long - -show/configuration/node (0) - -

-Show all the nodes connected locally and the nodes they have connected. - -show/connect (1) - -

-This command shows information on all the active connections known to -the node. This command gives slightly more information than WHO. - -show/date (0) - -

-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/debug (9) - -

-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 options 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) - -<number> - the number of spots you want -<from>-<to> - <from> spot no <to> spot no in - the selected list - -<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 - -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. - - -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 - - -show/dxcc (0) - -

-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. - -The options for SHOW/DX also apply to this command. -e.g. - - - SH/DXCC G - SH/DXCC W on 20m info iota - - -sh/dxstats (0) - -

-SHOW/FILES on its own will show you a list of the various fileareas -available on the system. To see the contents of a particular file -area type:- - - - SH/FILES <filearea> - - -where <filearea> is the name of the filearea 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 filearea eg:- - - - SH/FILES bulletins arld* - - -See also TYPE - to see the contents of a file. - -show/filter (0) - -

-Show the contents of all the filters that are set by you. This command -displays all the filters set - for all the various categories. - -show/filter (extended for sysops) (5) - -

-Show the HF DX spots breakdown by band for the last 31 days - -show/hftable (0) - -

-Show the HF DX Spotter table for your country for the last 31 days - -show/hops (8) - -

--show/hops <node_call> [ann|spots|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 (1) - -

-Show a list of callsigns that have been excluded (locked out) of the -cluster locally with the set/lockout command - -show/log (8) - -

-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 (0) - -

-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 gain or loss dB relative to the nominal -distance of 385,000Km due to the ellipsoidal nature of the orbit. - -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 - - -show/muf (0) - -

--show/muf <prefix> [<hours>][long] Show -the likely propagation to <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 preceeded 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 characterics. It -should be noted that the figures will probably not be very useful, nor -terrible accurate, but it is included for completeness. - -show/newconfiguration (0) - -

-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 (0) - -

-Show all the nodes connected to this node in the new format. - -show/node (1) - -

--show/node [<node_call> ...] 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 (0) - -

-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 (5) - -

-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 (0) - -

--show/qra <locator> [<locator>] Show the distance -between locators -show/qra <lat> <long> Convert latitude and longitude to -a 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 beraing from your station -to the locator. For example:- - - -SH/QRA IO92QL -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/qrz (0) - -

-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 - -show/registered (9) - -

--show/registered [<prefix>[ Show the registered users - - -show/route (0) - -

-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 (0) - -

--show/satellite <name> [<hours> <interval>] -Show satellite 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/sun (0) - -

-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 - - -show/time (0) - -

-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/vhfstats (0) - -

-Show the VHF DX spots breakdown by band for the last 31 days - -show/vhftable (0) - -

-Show the VHF DX Spotter table for your country for the last 31 days - -show/wcy (0) - -

--show/wcy Show the last 10 WCY broadcasts -show/wcy <n> Show the last <n> WCY broadcasts - - -

-Display the most recent WCY information that has been received by the system - -show/wwv (0) - -

--show/wwv Show the last 10 WWV broadcasts -show/wwv <n> Show the last <n> WWV broadcasts - - -

-Display the most recent WWV information that has been received by the system - - -shutdown (5) - -

-Shutdown the cluster and disconnect all the users. If you have Spider -set to respawn in /etc/inittab it will of course restart. - -spoof (9) - -

-This is a very simple yet powerful command for the sysop. It allows you to -issue commands as if you were a different user. This is very useful for the -kind of things that users seem to always get wrong.. like home_node for -example. - -stat/db (5) - -

-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/channel (5) - -

-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/msg (5) - -

-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 (5) - -

--stat/route_node <callsign> Show the data in a Route::Node object - - -stat/route_user (5) - -

--stat/route_user <callsign> Show the data in a Route::User object - - -stat/user (5) - -

-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 (0) - -

-The system automatically reduces your privilege level to that of a -normal 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 (0) - -

--talk <callsign> Enter talk mode with <callsign> -talk <callsign> <text> Send a text message to <callsign> -talk <callsign> > <node_call> [<text>] -Send a text message to <callsign> via <node_call> - - -

-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 - - -type (0) - -

-Type out the contents of a file in a filearea. So, for example, in -filearea 'bulletins' you want to look at file 'arld051' you would -enter:- - - - TYPE bulletins/arld051 - - -See also SHOW/FILES to see what fileareas are available and a -list of content. - -who (0) - -

-This is a quick listing that shows which callsigns are connected and -what sort of connection they have - -wx (0) - -

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

-Weather messages can sometimes be useful if you are experiencing an extreme -that may indicate enhanced conditions - -wx (enhanced for sysops) (5) - -

-Send a weather message only to other cluster nodes and not to general users. - - - diff --git a/sgml/adminmanual_en.sgml b/sgml/adminmanual_en.sgml new file mode 100644 index 00000000..eff06a86 --- /dev/null +++ b/sgml/adminmanual_en.sgml @@ -0,0 +1,5341 @@ + + +

+ + + +The DXSpider Administration Manual v1.50 +Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and +Charlie Carroll, K1XX, (k1xx@ptcnh.net) +February 2003 revision 0.3 + + +A reference for SysOps of the DXSpider DXCluster program. + + + + + + + +Routing and Filtering + +Introduction + +

+From DXSpider version 1.48, major changes were introduced to the way +node connections are treated. This is part of an ongoing process to +remove problems with loops and to enable talk and other functions to +propagate across the whole of the worldwide cluster network. In fact, +in a Spider network, it would be useful, perhaps even necessary to +have loops. This would give real resilience to the network, meaning +that if a link dropped, the information flow would simply come in and +go out via a different route. Of course, we do not have a complete +network of Spider nodes, there are other programs out there. Some of +these do not have any protection from loops. Certainly AK1A does not +handle loops well at all. It is therefore necessary to have some form +of protection for these nodes. + +

+In fact DXSpider has had a simple system for some time which is called +isolation. This is similar to what in other systems such as +clx, is called passive mode. A more detailed explanation +of isolation is given further below. This system is still available +and, for simple networks, is probably all that you need. + +

+The new functionality introduced in version 1.48 allows filtering the node +and user protocol frames on a "per interface" basis. We call this +route filtering. This is used instead of +isolation. + +

+What this really means is that you can control more or less completely +which user and node management PC protocol frames pass to each of your +partner nodes. You can also limit what comes into your node from your +partners. It is even possible to control the settings that your partner +node has for the routing information that it sends to you +(using the rcmd command). + +Route Filters + +

+Initially when route filters were being tested we generated a +"default" filter. Unfortunately it quickly became apparent that this +might suit the UK cluster network but didn't really fit anybody else. +However using a default filter is an appropriate thing to do. How, is +explained further on. + +

+The first thing that you must do is determine whether you need to use +route filtering at all. If you are a "normal" node with two or +three partners and you arranged in an "official" non-looping tree type +network, then you do not need to do route filtering and you will +feel a lot better for not getting involved. If you are successfully using +isolation then you also probably don't need to use route filtering. + +

+To put it simply, you should not mix Isolation and Route Filtering. It +will work, of sorts, but you will not get the expected results. If you +are using Isolation sucessfully at the moment, do not get involved in +Route Filtering unless you have a good supply of aspirin! Once you have +started down the road of Route Filtering, do not use Isolation either. +Use one or the other, not both. + +

+You will only require this functionality if you are "well-connected". What +that means is that you are connected to several different parts of (say) +the EU cluster and, at the same time, also connected to two or three places +in the US which, in turn are connected back to the EU. This is called a +"loop" and if you are seriously looped then you need filtering. + +

+I should at this stage give a little bit of background on filters. All +the filters in Spider work in basically the same way. You can either +accept or reject various options in order to create the filter rules +you wish to achieve. Some filters are user settable, others can only +be altered by the sysop. Route filtering can only be done by the sysop. + +

+Anyway, without further discouragement, let me start the process +of explanation. + +The node_default filter + +

+All normal systems should have a default routing filter and it should +usually be set to send only the normal, unlooped, view of your +"national" network. Here in the UK that means nodes from the UK and +Eire, in EU it is more complex as the networks there grew up in a more +intertwined way. + +

+The generic commands are:- + + +reject/route node_default <filter_option> + +or + +accept/route node_default <filter_option> + + +where filter_option is one of the following ... + + +call <prefixes> +call_dxcc <numbers> +call_itu <numbers> +call_zone <numbers> +channel <prefixes> +channel_dxcc <numbers> +channel_itu <numbers> +channel_zone <numbers> + + +Please be careful if you alter this setting, it will affect +ALL your links! Remember, this is a default +filter for node connections, not a per link default. + +

+For the default routing filter then you have two real choices: either +a "national" view or the "safe" option of only your own +callsign. Examples of each (for my node: GB7DJK) are:- + + +acc/route node_default call_dxcc 61,38 +acc/route node_default call gb7djk + + +GB7DJK uses the first of these. The DXCC countries can be obtained from the +show/prefix command. + +

+The example filters shown control output TO all your +partner nodes unless they have a specific filter applied to them (see +next section). + +

+It is also possible to control the incoming routing +information that you are prepared to accept FROM your partner +nodes. The reason this is necessary is to make sure that stuff like +mail, pings and similar commands a) go down the correct links and b) +don't loop around excessively. Again using GB7DJK as an example a typical +default input filter would be something like: + + +rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38 + + +What this does is accept node and user information for our national +network from nodes that are in our national network, but rejects such +information from anyone else. Although it doesn't explicitly say so, +by implication, any other node information (not from the UK and Eire) +is accepted. + +

+As I imagine it will take a little while to get one's head around all of +this you can study the effect of any rules that you try by watching the +debug output after having done:- + + +set/debug filter + + +After you have got tired of that, to put it back the way it was:- + + +unset/debug filter + + +General route filtering + +

+Exactly the same rules apply for general route filtering. You would +use either an accept filter or a reject filter like this ... + + +reject/route <node_call> <filter_option> + +or + +accept/route <node_call> <filter_option> + + +

+Here are some examples of route filters ... + + +rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes) +rej/route all (equiv to [very] restricted mode) +acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) +acc/route gb7djk call gb7djk (equiv to SET/ISOLATE) + + +In practice you will either be opening the default filter out for a +partner by defining a specific filter for that callsign:- + + +acc/route gb7baa all +acc/route gb7baa input all + + +or restricting it quite a lot, in fact making it very nearly like an +isolated node, like this:- + + +acc/route pi4ehv-8 call gb7djk +rej/route pi4ehv-8 input call_dxcc 61,38 + + +This last example takes everything except UK and Eire from PI4EHV-8 +but only sends him my local configuration (just a PC19 for GB7DJK and +PC16s for my local users). + +

+It is possible to write much more complex rules, there are up +to 10 accept/reject pairs per callsign per filter. For more information +see the next section. + + +General filter rules + +

+Upto v1.44 it was not possible for the user to set their own filters. From +v1.45 though that has all changed. It is now possible to set filters for just +about anything you wish. If you have just updated from an older version of +DXSpider you will need to update your new filters. You do not need to do +anything with your old filters, they will be renamed as you update. + +

+There are 3 basic commands involved in setting and manipulating filters. These +are accept, reject and clear. First we will look +generally at filtering. 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. They are ... + + +clear/spots 1 +clear/spots all + + +There is clear/xxxx command for each type of filter. + +

+and you can check that your filters have worked by the command ... + + +show/filter + + +

+For now we are going to use spots for the examples, but you can apply the same +principles to all types of filter. + +Types of filter + +

+There are two main types of filter, accept or reject. You +can use either to achieve the result you want dependent on your own preference +and which is more simple to do. It is pointless writing 8 lines of reject +filters when 1 accept filter would do the same thing! 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 take it) + +

+If you specify reject filters, then any lines that arrive that match the filter +will be dumped but all else will be accepted. If you use an accept filter, +then ONLY the lines in the filter will be accepted and all else will be dumped. +For example if you have a single line accept filter ... + + +accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16) + + +then you will ONLY get VHF spots from or to CQ zones +14, 15 and 16. + +

+If you set a reject filter like this ... + + +reject/spots on hf/cw + + +Then you will get everything EXCEPT HF CW spots. You could make this +single filter even more flexible. For example, if you are interested in IOTA +and will work it even on CW even though normally you are not interested in +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 achieves exactly the same thing. You should choose one or the other +until you are comfortable with the way it works. You can mix them if you +wish (actually you can have an accept AND a reject on the same line) but +don't attempt this until you are sure you know what you are doing! + +

+You can arrange your filter lines into logical units, either for your own +understanding or simply convenience. Here is an example ... + + +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 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 a line number (1 and 2 in this case), if +you leave the digit out, the system assumes '1'. Digits '0'-'9' are available. +This make it easier to see just what filters you have set. It also makes it +more simple to remove individual filters, during a contest for example. + +

+You will notice in the above example that the second line has brackets. Look +at the line logically. You can see there are 2 separate sections to it. We +are saying reject spots that are VHF or above APART from those in +zones 14, 15 and 16 (either spotted there or originated there). If you did +not have the brackets to separate the 2 sections, then Spider would read it +logically from the front and see a different expression entirely ... + + +(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16 + + +The simple way to remember this is, if you use OR - use brackets. Whilst we are +here CASE is not important. 'And BY_Zone' is just the same as 'and by_zone'. + +As mentioned earlier, setting several filters can be more flexible than +simply setting one complex one. Doing it in this way means that if you want +to alter your filter you can just redefine or remove one or more lines of it or +one line. For example ... + + +reject/spots 1 on hf/ssb + + +would redefine our earlier example, or + + +clear/spots 1 + + +To remove all the filter lines in the spot filter ... + + +clear/spots all + + +Filter options + +

+You can filter in several different ways. The options are listed in the +various helpfiles for accept, reject and filter. + +Default filters + +

+Sometimes all that is needed is a general rule for node connects. This can +be done with a node_default filter. This rule will always be followed, even +if the link is isolated, unless another filter is set specifically. Default +rules can be set for nodes and users. They can be set for spots, announces, +WWV and WCY. They can also be used for hops. An example might look like +this ... + + +accept/spot node_default by_zone 14,15,16,20,33 +set/hops node_default spot 50 + + +This filter is for spots only, you could set others for announce, WWV and WCY. +This filter would work for ALL nodes unless a specific filter is written to +override it for a particular node. You can also set a user_default should +you require. It is important to note that default filters should be +considered to be "connected". By this I mean that should you override the +default filter for spots, you need to add a rule for the hops for spots also. + +Advanced filtering + +

+Once you are happy with the results you get, you may like to experiment. + +

+The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU +can be written with a mixed filter, for example ... + + +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) + + +Note that the first filter has not been specified with a number. This will +automatically be assumed to be number 1. In this case, we have said reject all +HF spots in the CW section of the bands but accept all others at HF. Also +accept anything in VHF and above spotted in or by operators in the zones +14, 15 and 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 through everything else on HF. The next filter line +lets through just VHF/UHF spots from EU. + +Basic hop control + +

+In /spider/data you will find a file called hop_table.pl. This is the file +that controls your hop count settings. It has a set of default hops on the +various PC frames and also a set for each node you want to alter the hops for. +You may be happy with the default settings of course, but this powerful tool +can help to protect and improve the network. The file will look something +like this ... + + +# +# hop table construction +# + +package DXProt; + +# default hopcount to use +$def_hopcount = 5; + +# some variable hop counts based on message type +%hopcount = +( + 11 => 10, + 16 => 10, + 17 => 10, + 19 => 10, + 21 => 10, +); + + +# the per node hop control thingy + + +%nodehops = +( + GB7ADX => { 11 => 8, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + + GB7UDX => { 11 => 8, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + GB7BAA => { + 11 => 5, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, +); + + +

+Each set of hops is contained within a pair of curly braces and contains a +series of PC frame types. PC11 for example is a DX spot. The figures here +are not exhaustive but should give you a good idea of how the file works. + +

+SHould any of the nodecalls include an ssid, it is important to wrap the +whole call in single quotes, like this ... + + + 'DB0FHF-15' => { + 11 => 5, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + + +If you do not do this, you will get errors and the file will not work as +expected. + +

+You can alter this file at any time, including whilst the cluster is running. +If you alter the file during runtime, the command load/hops will +bring your changes into effect. + +Hop Control on Specific Nodes + +

You can set a callsign specific hop count for any of the standard filter +options so:- + + +set/hops gb7djk spot 4 +set/hops node_default route 10 +set/hops gb7baa wcy 5 + + +all work on their specific area of the protocol. + +

+The set/hops command overrides any hops that you have set otherwise. + +

+You can show what hops have been set using the show/hops command. + +Isolating networks + +

+It is possible to isolate networks from each other on a "gateway" node using the + set/isolate <node_call> command. + +

+The effect of this is to partition an isolated network completely from another +node connected to your node. Your node will appear on and otherwise behave +normally on every network to which you are connected, but data from an isolated +network will not cross onto any other network or vice versa. However all the +spot, announce and WWV traffic and personal messages will still be handled +locally (because you are a real node on all connected networks), that is locally +connected users will appear on all networks and will be able to access and +receive information from all networks transparently. All routed messages will +be sent as normal, so if a user on one network knows that you are a gateway for +another network, he can still still send a talk/announce etc message via your +node and it will be routed across. + +

+If you use isolate on a node connection you will continue to receive +all information from the isolated partner, however you will not pass +any information back to the isolated node. There are times when you +would like to forward only spots across a link (maybe during a contest +for example). To do this, isolate the node in the normal way and use +an acc/spot >call< all filter to override the isolate. + +Other filters + +Filtering Mail + +

+In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename +this to badmsg.pl and edit the file. The original looks something like this .... + + + +# the list of regexes for messages that we won't store having +# received them (bear in mind that we must receive them fully before +# we can bin them) + + +# The format of each line is as follows + +# type source pattern +# P/B/F T/F/O/S regex + +# type: P - private, B - bulletin (msg), F - file (ak1a bull) +# source: T - to field, F - from field, O - origin, S - subject +# pattern: a perl regex on the field requested + +# Currently only type B and P msgs are affected by this code. +# +# The list is read from the top down, the first pattern that matches +# causes the action to be taken. + +# The pattern can be undef or 0 in which case it will always be selected +# for the action specified + + + +package DXMsg; + +@badmsg = ( +'B', 'T', 'SALE', +'B', 'T', 'WANTED', +'B', 'S', 'WANTED', +'B', 'S', 'SALE', +'B', 'S', 'WTB', +'B', 'S', 'WTS', +'B', 'T', 'FS', +); + + +

+I think this is fairly self explanatory. It is simply a list of subject +headers that we do not want to pass on to either the users of the cluster or +the other cluster nodes that we are linked to. This is usually because of +rules and regulations pertaining to items for sale etc in a particular country. + + +Filtering words from text fields in Announce, Talk and DX spots + +

+From version 1.48 onwards the interface to this has changed. You can now +use the commands set/badword to add words that you are not prepared +to see on the cluster, unset/badword to allow that word again and +show/badword to list the words that you have set. + +

+If you have a previous /spider/data/badwords, the first time you start +the node, it will read and convert this file to the new commands. The old style +file will then be removed. + +Stopping (possibly bad) DX Spots from Nodes or Spotters + +

+There are a number of commands that control whether a spot progresses +any further by regarding it as "bad" in some way. + +

+A DX Spot has a number of fields which can be checked to see whether they +contain "bad" values, they are: the DX callsign itself, the Spotter and +the Originating Node. + +

+There are a set of commands which allow the sysop to control whether a +spot continues:- + + +set/baddx +set/badspotter +set/badnode + + +These work in the same as the set/badword command, you can add +any words or callsigns or whatever to the appropriate database. For +example, to stop a spot from a particular node you do: + + +set/badnode gb7djk gb7dxc + + +a bad spotter: + + +set/badspotter b0mb p1rat nocall + + +and some bad dx: + + +set/baddx video wsjt + + +You can remove a word using the appropriate unset command +(unset/baddx, unset/badspotter, unset/badnode) or list them +using one of show/baddx, show/badspotter and +show/badnode. + +Mail + +

+DXSpider deals seamlessly with standard AK1A type mail. It supports both +personal and bulletin mail and the sysop has additional commands to ensure +that mail gets to where it is meant. DXSpider will send mail almost +immediately, assuming that the target is on line. However, only one +mail message is dealt with at any one time. If a mail message is already +being sent or recieved, then the new message will be queued until it has +finished. + +The cluster mail is automatically deleted after 30 days unless the sysop +sets the "keep" flag using the msg command. + +Personal mail + +

+Personal mail is sent using the sp command. This is actually the +default method of sending mail and so a simple s for send will do. +A full list of the send commands and options is in the command set +section, so I will not duplicate them here. + +Bulletin mail + +

+Bulletin mail is sent by using the sb command. This is one of the +most common mistakes users make when sending mail. They send a bulletin +mail with s or sp instead of sb and of course +the message never leaves the cluster. This can be rectified by the sysop +by using the msg command. + +

Bulletin addresses can be set using the Forward.pl file. + +Forward.pl + +

+DXSpider receives all and any mail sent to it without any alterations needed +in files. Because personal and bulletin mail are treated differently, there +is no need for a list of accepted bulletin addresses. It is necessary, however, +to tell the program which links accept which bulletins. For example, it is +pointless sending bulletins addresses to "UK" to any links other than UK +ones. The file that does this is called forward.pl and lives in /spider/msg. +At default, like other spider files it is named forward.pl.issue. Rename it +to forward.pl and edit the file to match your requirements. +The format is below ... + + +# +# this is an example message forwarding file for the system +# +# The format of each line is as follows +# +# type to/from/at pattern action destinations +# P/B/F T/F/A regex I/F [ call [, call ...] ] +# +# type: P - private, B - bulletin (msg), F - file (ak1a bull) +# to/from/at: T - to field, F - from field, A - home bbs, O - origin +# pattern: a perl regex on the field requested +# action: I - ignore, F - forward +# destinations: a reference to an array containing node callsigns +# +# if it is non-private and isn't in here then it won't get forwarded +# +# Currently only type B msgs are affected by this code. +# +# The list is read from the top down, the first pattern that matches +# causes the action to be taken. +# +# The pattern can be undef or 0 in which case it will always be selected +# for the action specified +# +# If the BBS list is undef or 0 and the action is 'F' (and it matches the +# pattern) then it will always be forwarded to every node that doesn't have +# it (I strongly recommend you don't use this unless you REALLY mean it, if +# you allow a new link with this on EVERY bull will be forwarded immediately +# on first connection) +# + +package DXMsg; + +@forward = ( +'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ], +'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ], +'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ], +'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +); + + +Simply insert a bulletin address and state in the brackets where you wish +that mail to go. For example, you can see here that mail sent to "UK" will +only be sent to the UK links and not to PA4AB-14. + +

+To force the cluster to reread the file use load/forward + +

+NB: If a user tries to send mail to a bulletin address that does not exist +in this file, they will get an error. + +The msg command + +

+The msg command is a very powerful and flexible tool for the +sysop. It allows the sysop to alter to and from fields and make other +changes to manage the cluster mail. + +Here is a full list of the various options ... + + + MSG TO - change TO callsign to + MSG FRom - change FROM callsign to + MSG PRrivate - set private flag + MSG NOPRrivate - unset private flag + MSG RR - set RR flag + MSG NORR - unset RR flag + MSG KEep - set the keep flag (message won't be deleted ever) + MSG NOKEep - unset the keep flag + MSG SUbject - change the subject to + MSG WAittime - remove any waiting time for this message + MSG NOREad - mark message as unread + MSG REad - mark message as read + MSG QUeue - queue any outstanding bulletins + MSG QUeue 1 - queue any outstanding private messages + + +These commands are simply typed from within the cluster as the sysop user. + +Message status + +

+You can check on a message from within the cluster by using the command +stat/msg. This will give you additional information on the +message number including which nodes have received it, which node it +was received from and when etc. Here is an example of the output of +the command ... + + +G0VGS de GB7MBC 28-Jan-2001 1308Z > +stat/msg 6869 + From: GB7DJK + Msg Time: 26-Jan-2001 1302Z + Msgno: 6869 + Origin: GB7DJK + Size: 8012 + Subject: AMSAT 2line KEPS 01025.AMSAT + To: UK +Got it Nodes: GB7BAA, GB7ADX + Private: 0 +Read Confirm: 0 + Times read: 0 +G0VGS de GB7MBC 28-Jan-2001 1308Z > + + +Filtering mail + +

+This is described in the section on Other filters so I will not +duplicate it here. + +Distribution lists + +

+Distribution lists are simply a list of users to send certain types of +mail to. An example of this is mail you only wish to send to other +sysops. In /spider/msg there is a directory called distro. You +put any distibution lists in here. For example, here is a file called +SYSOP.pl that caters for the UK sysops. + + +qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX + GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH + GB7DXK GB7DXI GB7DXS) + + +Any mail sent to "sysop" would only be sent to the callsigns in this list. + +BBS interface + +

+Spider provides a simple BBS interface. No input is required from the sysop +of the cluster at all. The BBS simply sets the cluster as a BBS and pushes +any required mail to the cluster. No mail can flow from Spider to the BBS, +the interface is one-way. + +

+Please be careful not to flood the cluster network with unnecessary mail. +Make sure you only send mail to the clusters that want it by using the +Forward.pl file very carefully. + +Scripts + +

+From 1.48 onwards it will become increasingly possible to control DXSpider's +operation with scripts of various kinds. + +

+The directory /spider/scripts is where it all happens and is used for several +things. Firstly it contains a file called startup that can be used to call +in any 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. Examples of this include how many +spots it is possible to get with the sh/dx command, whether you want +registration/passwords to be permanently on etc. An example file is shown +below and is included in the distribution as startup.issue. + + +# +# startup script example +# +# set maximum no of spots allowed to 100 +# set/var $Spot::maxspots = 100 +# +# Set registration on +# set/var $main::reqreg = 1 +# +# Set passwords on +# set/var $main::passwdreq = 1 +# + + +

+As usual, any text behind a # is treated as a comment and not read. To use +this file, simply rename it from startup.issue to startup. In our example +above there are three options. The first option is the amount of spots that +a user can request with the sh/dx command. Normally the default is +to give 10 spots unless the user specifies more. Without this line enabled, +the maximum a user can request is 100 spots. Depending on your link quality +you may wish to enable more or less by specifying the number. + +

+The other 2 options are dealt with more fully in the security section. + +

+Secondly, it is used to store the login scripts for users and nodes. Currently +this can only be done by the sysop but it is envisaged that eventually users will +be able to set their own. An example is included in the distibution but here is +a further example. + + +# +# G0FYD +# +blank + +sh/wwv 3 +blank + +sh/dx +blank + +t g0jhc You abt? +blank + + + +The lines in between commands can simply insert a blank line or a character +such as a + sign to make the output easier to read. Simply create this script +with your favourite editor and save it with the callsign of the user as the +filename. Filenames should always be in lower case. + +

+Commands can be inserted in the same way for nodes. A node may wish a series +of commands to be issued on login, such as a merge command for example. + +

+Thirdly, there are 2 default scripts for users and nodes who do not have a +specifically defined script. These are user_default and +node_default + +Databases + +

+Spider allows the creation of local or remote databases. It supports +chained databases, allowing several different databases to be scanned +with one simple command. Importing of databases is limited at present +to the standard AK1A databases such as OBLAST and the DB0SDX QSL +database but will expand with time. + +Creating databases + +

+Creating a database could not be more simple. All the commands are +sent from the cluster prompt as the sysop user. + +To create a database you use the command dbcreate. It can +be used in 3 different ways like so .. + + +dbcreate + + +To simply create a database locally, you just tell the command the +name of the database. This does not create the actual database, it +simply defines it to say that it exists. + + +dbcreate chain [...] + + +This creates a chained database entry. The first database will be +scanned, then the second, the third etc... + + +dbcreate remote + + +This creates a remote entry. the first name field is the database +name at the remote node, then the remote switch, then the actual +node_call of the remote node, for example... + + +dbcreate buckmaster remote gb7dxc + + +Remote databases cannot be chained, however, the last database in a +chain can be a remote database. + +Importing databases + +

+The only databases that Spider can currently import are the standard +AK1A databases such as OBLAST or the DB0SDX qsl and address database. +This will be added to with time. + +To import such a database, first put the file somewhere useful like /tmp +and then issue the following command ... + + +dbimport oblast /tmp/OBLAST.FUL + + +This will update the existing local oblast database or create it if +it does not exist. + +Checking available databases + +

+Once a database is created, you will want to check that it has been +added. To do this use the dbavail command. This will +output the available databases. For example ... + + +dbavail +DB Name Location Chain +qsl Local +buck GB7ADX +hftest GB7DXM +G0VGS de GB7MBC 3-Feb-2001 1925Z > + + +Looking up databases + +

+To look for information in a defined database, simply use the dbshow +command, for example ... + + +dbshow buckmaster G0YLM + + +will show the information for the callsign G0YLM from the buckmaster +database if it exists. To make things more standard for the users +you can add an entry in the Aliases file so that it looks like a standard +show command like this ... + + +'^sh\w*/buc', 'dbshow buckmaster', 'dbshow', + + +Now you can simply use show/buckmaster or an abreviation. + +Removing databases + +

+To delete an existing database you use the dbremove command. +For example ... + + +dbremove oblast + + +would remove the oblast database and its associated datafile from the +system. There are no warnings or recovery possible from this command. +If you remove a database it ceases to exist and would have to be created +from scratch if you still required it. + +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 show/files +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 +'$' says match the end exactly. This prevents unwanted and unintentional matches +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 convkeps.pl. 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 once you have followed a few +simple steps. First you need to get a user ID and password from qrz.com. +Simply go to the site and create one. Secondly 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. Many thanks to Fred Lloyd, the proprieter of + for allowing this access. + +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. + +Java Web applet + +

+In the spider tree will be a directory spider-web. This is a +neat little java web applet that can be run from a website. The applet +must run on the same machine as the cluster. The included README file is +shown below. + +

+I should comment here that the applet is precompiled, that is, ready to go. +It was compiled using JDK1.3.1. If your version is earlier than this then it +may not work. Should that be the case you need to recompile or update your +JDK. To recompile do the following ... + + +cd /spider/spider-web +rm *.class +/usr/bin/javac spiderclient.java + + +

+I have used /usr/bin/javac as an example, your path to javac may be different. + + +Spider-WEB v0.6b + +Completely based on a clx web client written in Java by dl6dbh +(ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz) + +The webserver has to run on the same machine as your DxSpider software! + +It is assumed that you have Java installed. You need JDK1.3.1 at least. + +Installation instructions (Performed as root): + +Put all the files in the spider-web directory into a newly created directory +under the DocumentRoot of your websever for instance 'client'. In my case +this is: /home/httpd/html/client/ although ymmv. For Suse the correct +path should be /usr/local/httpd/htdocs/client/ for example. + +Move spider.cgi to the cgi-bin directory of your webserver, in my case that is +/home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be +/usr/local/httpd/cgi-bin/ for example. + +Change the permissions of the files to ensure they are correct, obviously you +will need to use the correct path the the files according to your system: + +chmod 755 /home/httpd/html/cgi-bin/spider.cgi +chmod -R 755 /home/httpd/html/client/ + +By default the spider.cgi script should pick up your hostname (As long as this +is set correctly). If it does not or your hostname differs from the name that +you attach to the public address that you are using, then edit spider.cgi : + +# Uncomment and set the hostname manually here if the above fails. +# $HOSTNAME = "gb7mbc.spoo.org" ; +$PORT = "8000" ; + +'HOSTNAME' is the hostname of your cluster. + +'PORT' is the portnumber that you use to connect to your DxSpider via +telnet (see Listeners.pm) + +NOTE: If you can start the console but cannot connect to the cluster from it, +then it is possible that the machine you are on cannot resolve the hostname of +your cluster machine. If this is the case, you need to set your hostname +manually as above. + +You also need to set the $NODECALL variable. This prints the name of your +choosing (probably your cluster callsign) on the html page. + +You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi + + +Web based statistics + +

+From version 1.50, you can use the freeware software MRTG to produce +really nice graphical statistics on your web site. For an example +try . + +

+The following should help you get it all working. + +

+First you need to download the latest version of MRTG from . +You will also need the following files.. + + +libpng-1.0.14.tar.gz +zlib-1.1.4.tar.gz +gd-1.8.3.tar.gz + + +Login to your machine as the root user, put all the downloaded files +in /usr/local/src/ (or wherever you prefer) and untar and compile them. +All the information to compile and install these sources come with them. +After compilation and installation, you will find MRTG in /usr/local/mrtg-2. + +

+Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to +/spider/html/mrtg/ + +

+You now need to make 2 symbolic links like below... + + +ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg +ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2 + + +

+Now login to the cluster with your sysop callsign and run the command +"mrtg all". + +

Now you are nearly there! Login as the sysop user and change to the +/spider/html/mrtg/ directory. Now run the command indexmaker as +shown below... + + +indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg + + +Changing the callsign for your own cluster callsign of course! + +

+And finally you need to login as the root user and create one last +symbolic link. Where this points will depend on where your html +documents are kept. For RedHat systems you use... + + +ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg + + +and for SuSE systems... + + +ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg + + +If you now point your browser to your website as below it should all +be happening! + + +http://www.xxx.xxx/mrtg/stats.html + + +Of course, to get the stats to update, you need to add some information +in the spider crontab file as below... + + +# 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. + +Security + +

+From version 1.49 DXSpider has some additional security features. These +are not by any means meant to be exhaustive, however they do afford some +security against piracy. These two new features can be used independently +of each other or in concert to tighten the security. + +Registration + +

+The basic principle of registration is simple. If a user is not registered +by the sysop, then they have read-only access to the cluster. The only +thing they can actually send is a talk or a message to the sysop. In +order for them to be able to spot, send announces or talks etc the sysop +must register them with the set/register command, like this ... + + +set/register g0vgs + + +The user g0vgs can now fully use the cluster. In order to enable +registration, you can issue the command ... + + +set/var $main::reqreg = 1 + + +Any users that are not registered will now see the motd_nor file rather +than the motd file as discussed in the Information, files and useful +programs section. + +

+Entering this line at the prompt will only last for the time the cluster +is running of course and would not be present on a restart. To make the +change permanent, add the above line to /spider/scripts/startup. To +read more on the startup file, see the section on Information, files +and useful programs. + +

+To unregister a user use unset/register and to show the list +of registered users, use the command show/register. + +Passwords + +

+At the moment, passwords only affect users who login to a DXSpider +cluster node via telnet. If a user requires a password, they can +either set it themselves or have the sysop enter it for them by using +the set/password command. Any users who already have passwords, +such as remote sysops, will be asked for their passwords automatically +by the cluster. Using passwords in this way means that the user has a +choice on whether to have a password or not. To force the use of +passwords at login, issue the command ... + + +set/var $main::passwdreq = 1 + + +at the cluster prompt. This can also be added to the /spider/scripts/startup +file as above to make the change permanent. + +

+Of course, if you do this you will have to assign a password for each of +your users. If you were asking them to register, it is anticipated that +you would ask them to send you a message both to ask to be registered and +to give you the password they wish to use. + +

+Should a user forget their password, it can be reset by the sysop by +first removing the existing password and then setting a new one like so ... + + +unset/password g0vgs +set/password g0vgs new_password + + +CVS + +CVS from a Linux platform + +

+CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held +at . This means +that it is possible to update your DXSpider installation to the latest +sources by using a few simple commands. A graphical interface to CVS for +Windows is explained in the next section. + +

+Please be aware that if you update your system using CVS, it is possible that +you could be running code that is very beta and not fully tested. There is +a possibility that it could be unstable. + +

+I am of course assuming that you have a machine with both DXSpider and +Internet access running. + +

+BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR +ENTIRE SPIDER TREE!! + +

+Assuming you are connected to the Internet, you need to login to the +CVS repository and then update your Spider source. There are several +steps which are listed below ... + +

+First login as the user sysop. Next you need to connect to the CVS +repository. You do this with the command below ... + + +cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login + + +You will get a password prompt. Simply hit return here and your machine should +return to a normal linux prompt. + +

+What happens next depends on whether you have an existing installation that +you want to update with the latest and greatest or whether you just want +to see what is there and/or run it on a new machine for testing. + +If you are installing Spider from CVS then change directory to /home/sysop + +If you are wanting to update Spider then cd to /tmp + +

+The next step will create a brand new 'spider' directory in your current +directory. + + +cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider + + +This command is all on one line. + +

+Hopefully your screen should show you downloading files. The -z3 simply compresses +the download to improve speed. +When this has finished, you will have exactly the same as if you had untarred a full +tarball PLUS some extra directories and files that CVS needs to do the magic that +it does. + +

+Now if you are doing a new installation, that's it. Carry on as if you have +just downloaded and untarred the lastest tarball. + +

+If you want to upgrade your current installation then do this ... + + +tar cvfz /tmp/s.tgz spider +cd / +tar xvfzp /tmp/s.tgz + + +This is assuming you downloaded to the /tmp directory of course. + +

+NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions +correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU????? + +Remember to recompile the C client (cd /spider/src; make) + +

+At this point the files have been upgraded. You can (usually) restart the cluster +in your own time. However, if you attempt to use any new commands or features +expect it to be fatal! At least your cluster will have been restarted then so it +will be too late to worry about it! + +

+Now the magic part! From now on when you want to update, simply connect to the +Internet and then, as the user sysop ... + + +cd /spider +cvs -z3 update -d + + +and your files will be updated. As above, remember to recompile the "C" client +if it has been updated (CVS will tell you) and restart if any of the perl scripts +have been altered or added, again, CVS will tell you. + +

+You will find any changes documented in the /spider/Changes file. + +CVS from a Windows platform + +

+After the initial setup, an update to your DXSpider software is no more than a couple +of clicks away. This section is intended to explain and illustrate the use of the +WinCVS application to update your DXSpider software. The current stable version of +WinCVS is Ver. 1.2. You can get this software at: + + + +Pick your download mirror and then install WinCVS after the download is complete. + +In this next section I have included a series of links to .jpg files to take advantage of the +picture and 1000 words equivalency. The .jpg files are in the C:\spider\html directory. If +someone using a Linux system is reading this section from boredom, the files are in +/home/sysop/spider/html. One aside, a Linux user can also get a copy of gcvs and do your updates +graphically as opposed to from the command line. The following descriptions are almost identical +between WinCvs and gcvs. The following screen shots have duplicate links, depending upon whether +you are viewing this information under the Windows or Linux operating system. + +When WinCVS is installed, running, and you are connected to the internet, the initial screen looks like: + + + +If you want, you can also look at these .jpg files with another viewer that might provide some +better clarity to the image. On the left is the directory tree for your hard disk. Notice that +the spider directory has a gray highlight. + +To start configuring WinCVS, click on Admin at the top of the screen and then Preferences. This +should get you: + + + +In the top line for CVSROOT, enter: + +anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login + + +and select + +"passwd" file on the cvs server + + +for Authentication on the General tab. + +Next, move to the right to the Ports tab. + + + +In here, check the box on the second line down for the "pserver" port. Enter a port number of 2401. + +Finally, go to the WinCvs tab all the way to the right. + + + +Enter Notepad as the viewer to open files. For the HOME folder, put "C:\spider" and click OK +because the configuration is now complete. + +You are now ready to upgrade your copy of DXSpider. Click on the greyed Spider folder +shown in the directory tree on the left of the WinCVS display. Two things should happen. The Spider +folder will be selected and the greyed-out arrow located just below the word Query in the top line will +turn to solid green. + +For anyone using gcvs under Linux, the green arrow is located on the extreme left of the display, +under the word File. A gcvs screen looks like: + + + +Click on the now green arrow to start the download process. An Update Settings box will be displayed +to which you can simply say OK. + + + +For future reference, the Update Settings box is the place where you can enter information to revert +to a prior version of DXSpider. Information on reverting to a Before Date is contained in the WinCVS +manual. + +After a short period of time, a series of file names will scroll by in the lower pane of the WinCVS +window. Eventually you should see + +*****CVS exited normally with code 0***** + + +appear in the lower pane. You're done. The updated files are in place ready for you to stop and then +restart your DXSpider. After the restart, you're running with the latest version of DXSpider. + + + +To paraphrase from the CVS section... Now the magic part! From now on when you want to update, simply +connect to the Internet and start WinCVS. + +Click on the greyed-out Spider directory in the left screen +Click on the green down arrow +Click OK on the Update Settings dialog box +Restart your Spider software + + +The DXSpider command set + + +accept (0) + +

++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> (8) + +

++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> (0) + +

++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 (distros) + + +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> (8) + +

++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 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,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 + + +and so on + +You can use the tag 'all' to accept everything eg: + + + acc/route all + + +accept/spots <call> [input] [0-9] <pattern> (8) + +

++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 the +default 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> (0) + +

++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 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:- + + + 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 subband 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> (8) + +

++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 the +default for nodes and users eg:- + + + accept/wcy node_default all + set/hops node_default 10 + + +accept/wcy [0-9] <pattern> (0) + +

++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> (8) + +

++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> (0) + +

++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 <text> (0) + +

++announce <text> Send an announcement to LOCAL users only + + +

+<text> is the text of the announcement you wish to broadcast +announce full <text> (0) + +

++announce full <text> Send an announcement cluster wide + + +

+This will send your announcement cluster wide +announce sysop <text> (5) + +

++announce sysop <text> Send an announcement to Sysops only + + +

+apropos <string> (0) + +

++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 [<string>] [<nn>] (0) + +

++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 (0) + +

++bye Exit from the cluster + + +

+This will disconnect you from the cluster +catchup <node call> all|[<msgno> ...] (5) + +

++catchup <node call> all|[<msgno> ...] Mark a message as sent + + +

+clear/announce <callsign> [input] [0-9|all] (8) + +

++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] (0) + +

++clear/announce [1|all] Clear a announce filter line + + +

+This command allows you to clear (remove) a line in a annouce filter or to +remove the whole filter. + +see CLEAR/SPOTS for a more detailed explanation. +clear/route <callsign> [input] [0-9|all] (8) + +

++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 the +node_default or user_default. +clear/route [1|all] (0) + +

++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] (8) + +

++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] (0) + +

++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] (8) + +

++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] (0) + +

++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] (8) + +

++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] (0) + +

++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 <callsign> (5) + +

++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 (0) + +

++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. +dbshow <dbname> <key> (0) + +

++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 + + +directory (0) + +

++directory List messages + + +

+directory <from>-<to> (0) + +

++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> (0) + +

++directory <nn> List last <nn> messages + + +

+directory all (0) + +

++directory all List all messages + + +

+directory from <call> (0) + +

++directory from <call> List all messages from <call> + + +

+directory new (0) + +

++directory new List all new messages + + +

+directory own (0) + +

++directory own List your own messages + + +

+directory subject <string> (0) + +

++directory subject <string> List all messages with <string> in subject + + +

+directory to <call> (0) + +

++directory to <call> List all messages to <call> + + +

+directory- (5) + +

++directory- + + +

+Sysops can see all users' messages. +disconnect <call> [<call> ...] (8) + +

++disconnect <call> [<call> ...] Disconnect a user or cluster + + +

+Disconnect any <call> connected locally +dx [by <call>] <freq> <call> <remarks> (0) + +

++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 <line> (0) + +

++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. + +A more complex example:- + + + echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard + + +produces:- + + + GB7DJK + g1tlh Dirk + g3xvf Richard + + +on the output. + +filtering... (0) + +

++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 14 +15 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 confortable 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 analyse 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 exmaple 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/latlong <node_call> (8) + +

++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 recieving 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> (1) + +

++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, Location +and Homenode. PC41s are only sent for the information that is available. + +help (0) + +

++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 <node> (5) + +

++init <node> Re-initialise a link to an AK1A compatible node + + +

+This command attempts to re-initialise 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. + +kill (5) + +

++kill + + +

+As a sysop you can kill any message on the system. +kill <from msgno>-<to msgno> (0) + +

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

+kill <from>-<to> (5) + +

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

+kill <msgno> [<msgno..] (0) + +

++kill <msgno> [<msgno..] Delete a message from the local system + + +

+kill <msgno> [<msgno> ...] (0) + +

++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..] (6) + +

++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> (5) + +

++kill from <call> Remove all messages from a callsign + + +

+kill full <msgno> [<msgno..] (5) + +

++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 the +same subject will be deleted. Beware! +kill full <msgno> [<msgno] (5) + +

++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> (5) + +

++kill to <call> Remove all messages to a callsign + + +

+kill from <regex> (0) + +

++kill from <regex> Delete messages FROM a callsign or pattern + + +

+kill to <regex> (0) + +

++kill to <regex> Delete messages TO a callsign or pattern + + +

+links (0) + +

++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/keps (5) + +

++load/keps Load new keps data + + +

+load/keps [nn] (5) + +

++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. +merge <node> [<no spots>/<no wwv>] (5) + +

++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). +pc <call> <text> (8) + +

++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 <node call> (1) + +

++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 <node call> <cmd> (1) + +

++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 dependant 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 (0) + +

++read Read the next unread personal message addressed to you + + +

+read <msgno> (0) + +

++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- (5) + +

++read- + + +

+As a sysop you may read any message on the system +reject (0) + +

++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> (8) + +

++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> (0) + +

++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 (distros) + + +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> (8) + +

++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> (8) + +

++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> (0) + +

++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,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 subband 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> (8) + +

++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> (0) + +

++reject/wcy [0-9] <pattern> set a 'reject' WCY filter + + +

++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> (0) + +

++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 (0) + +

++reply Reply (privately) to the last message that you have read + + +

+reply <msgno> (0) + +

++reply <msgno> Reply (privately) to the specified message + + +

+reply b <msgno> (0) + +

++reply b <msgno> Reply as a Bulletin to the specified message + + +

+reply noprivate <msgno> (0) + +

++reply noprivate <msgno> Reply as a Bulletin to the specified message + + +

+reply rr <msgno> (0) + +

++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) +send <call> [<call> ...] (0) + +

++send <call> [<call> ...] Send a message to one or more callsigns + + +

+send copy <msgno> <call> (0) + +

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

+send noprivate <call> (0) + +

++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 +(upto 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 preceeded by a '/' character on a new line, so:- + + + /dx g1tlh 144010 strong signal + + +Will issue a dx annoucement to the rest of the cluster. + +Also, you can add the output of a command to your message by preceeding +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> (0) + +

++send private <call> Send a personal message + + +

+send rr <call> (0) + +

++send rr <call> Send a message and ask for a read receipt + + +

+set/address <your address> (0) + +

++set/address <your address> Record your postal address + + +

+set/announce (0) + +

++set/announce Allow announce messages to come out on your terminal + + +

+set/anntalk (0) + +

++set/anntalk Allow talk like announce messages on your terminal + + +

+set/arcluster <call> [<call>..] (5) + +

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

+set/baddx <call>.. (8) + +

++set/baddx <call>.. Stop callsigns in a dx spot being propagated + + +

+set/badnode <call>.. (8) + +

++set/badnode <call>.. Stop spots from this node being propagated + + +

+set/badspotter <call>.. (8) + +

++set/badspotter <call>.. Stop spots from this callsign being propagated + + +

+set/badword <word>.. (8) + +

++set/badword <word>.. Stop things with this word being propagated + + +

+set/bbs <call> [<call>..] (5) + +

++set/bbs <call> [<call>..] Make the callsign a BBS + + +

+set/beep (0) + +

++set/beep Add a beep to DX and other messages on your terminal + + +

+set/clx <call> [<call>..] (5) + +

++set/clx <call> [<call>..] Make the callsign an CLX node + + +

+set/dx (0) + +

++set/dx Allow DX messages to come out on your terminal + + +

+set/dxgrid (0) + +

++set/dxgrid Allow QRA Grid Squares on the end of DX announcements + + +

+set/dxnet <call> [<call>..] (5) + +

++set/dxnet <call> [<call>..] Make the callsign an DXNet node + + +

+set/echo (0) + +

++set/echo Make the cluster echo your input + + +

+set/email <email> ... (0) + +

++set/email <email> ... Set email address(es) and forward your personals + + +

+set/here (0) + +

++set/here Tell the system you are present at your terminal + + +

+set/homenode <node> (0) + +

++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> (8) + +

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

+set/language <lang> (0) + +

++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) +and nl (Dutch). +set/location <lat & long> (0) + +

++set/location <lat & long> Set your latitude and longitude + + +

+set/logininfo (0) + +

++set/logininfo Inform when a station logs in locally + + +

+set/name <your name> (0) + +

++set/name <your name> Set your name + + +

+Tell the system what your name is eg:- + + SET/NAME Dirk + + +set/node <call> [<call>..] (5) + +

++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> (8) + +

++set/obscount <count> <call> Set the 'pump-up' obscelence PING counter + + +

+From 1.35 onwards neighbouring 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> (0) + +

++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 (0) + +

++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/prompt <string> (0) + +

++set/prompt <string> Set your prompt to <string> + + +

+set/qra <locator> (0) + +

++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> (0) + +

++set/qth <your qth> Set your QTH + + +

+Tell the system where you are. For example:- + + SET/QTH East Dereham, Norfolk + + +set/spider <call> [<call>..] (5) + +

++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/talk (0) + +

++set/talk Allow TALK messages to come out on your terminal + + +

+set/wcy (0) + +

++set/wcy Allow WCY messages to come out on your terminal + + +

+set/wwv (0) + +

++set/wwv Allow WWV messages to come out on your terminal + + +

+set/wx (0) + +

++set/wx Allow WX messages to come out on your terminal + + +

+show/baddx (1) + +

++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 (1) + +

++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 (1) + +

++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 (1) + +

++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/configuration [<node>] (0) + +

++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 (0) + +

++show/configuration/node Show all the nodes connected locally + + +

+Show all the nodes connected to this node. +show/connect (1) + +

++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/date [<prefix>|<callsign>] (0) + +

++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/dx (0) + +

++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 + + + + 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 + + +show/dxcc <prefix> (0) + +

++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 + + +show/dxstats [days] [date] (0) + +

++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/files [<filearea> [<string>]] (0) + +

++show/files [<filearea> [<string>]] List the contents of a filearea + + +

+SHOW/FILES on its own will show you a list of the various fileareas +available on the system. To see the contents of a particular file +area type:- + + SH/FILES <filearea> + +where <filearea> is the name of the filearea 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 filearea eg:- + + SH/FILES bulletins arld* + + +See also TYPE - to see the contents of a file. +show/filter (0) + +

++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] (0) + +

++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 ...] (0) + +

++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] (8) + +

++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 (1) + +

++show/isolate Show list of ISOLATED nodes + + +

+show/log [<callsign>] (8) + +

++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>] (0) + +

++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 + + +Upto 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 UT times of rise and +set on the requested UT day. +show/muf <prefix> [<hours>][long] (0) + +

++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 preceeded 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). + +inputing:- + + + 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 characterics. It +should be noted that the figures will probably not be very useful, nor +terrible accurate, but it is included for completeness. +show/newconfiguration [<node>] (0) + +

++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 (0) + +

++show/newconfiguration/node Show all the nodes connected locally + + +

+Show all the nodes connected to this node in the new format. +show/node [<callsign> ...] (1) + +

++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> (0) + +

++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 (5) + +

++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> (0) + +

++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 beraing from your station +to the locator. For example:- + + + SH/QRA IO92QL + 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>] (0) + +

++show/qra <locator> [<locator>] Show distance between QRA Grid locators + + +

+show/qrz <callsign> (0) + +

++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 +show/route <callsign> ... (0) + +

++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>] (0) + +

++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/station all [<regex>] (6) + +

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

+show/station [<callsign> ..] (0) + +

++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>] (0) + +

++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 + + +Upto 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 UT times of rise +and set on the requested UT day. +show/time [<prefix>|<callsign>] (0) + +

++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 ..] (0) + +

++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] (0) + +

++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 ...] (0) + +

++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 (0) + +

++show/wcy Show last 10 WCY broadcasts + + +

+show/wcy <n> (0) + +

++show/wcy <n> Show last <n> WCY broadcasts + + +

+Display the most recent WCY information that has been received by the system +show/wwv (0) + +

++show/wwv Show last 10 WWV broadcasts + + +

+show/wwv <n> (0) + +

++show/wwv <n> Show last <n> WWV broadcasts + + +

+Display the most recent WWV information that has been received by the system +shutdown (5) + +

++shutdown Shutdown the cluster + + +

+Shutdown the cluster and disconnect all the users +stat/channel [<callsign>] (5) + +

++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> (5) + +

++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 (1) + +

++stat/msg Show the status of the message system + + +

+stat/msg <msgno> (1) + +

++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> (5) + +

++stat/route_node <callsign> Show the data in a Route::Node object + + +

+stat/route_node all (5) + +

++stat/route_node all Show list of all Route::Node objects + + +

+stat/route_user <callsign> (5) + +

++stat/route_user <callsign> Show the data in a Route::User object + + +

+stat/route_user all (5) + +

++stat/route_user all Show list of all Route::User objects + + +

+stat/user [<callsign>] (5) + +

++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 (0) + +

++sysop Regain your privileges if you login remotely + + +

+The system automatically reduces your privilege level to that of a +normal 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 <call> > <node> [<text>] (0) + +

++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 preceed 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 extention 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>] (0) + +

++talk <call> [<text>] Send a text message to another station + + +

+type <filearea>/<name> (0) + +

++type <filearea>/<name> Look at the contents of a file in one of the fileareas + + +

+Type out the contents of a file in a filearea. So, for example, in +filearea 'bulletins' you want to look at file 'arld051' you would +enter:- + + TYPE bulletins/arld051 + + +See also SHOW/FILES to see what fileareas are available and a +list of content. +uncatchup <node call> all|[msgno> ...] (5) + +

++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 +commmands:- + + + 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/announce (0) + +

++unset/announce Stop announce messages coming out on your terminal + + +

+unset/anntalk (0) + +

++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>.. (8) + +

++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>.. (8) + +

++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 superceeded by FILTERing. +unset/badspotter <call>.. (8) + +

++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 superceded by FILTERing. +unset/badword <word>.. (8) + +

++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 (0) + +

++unset/beep Stop beeps for DX and other messages on your terminal + + +

+unset/dx (0) + +

++unset/dx Stop DX messages coming out on your terminal + + +

+unset/dxgrid (0) + +

++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. +unset/echo (0) + +

++unset/echo Stop the cluster echoing your input + + +

+If you are connected via a telnet session, different implimentations +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 (0) + +

++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 (0) + +

++unset/here Tell the system you are absent from your terminal + + +

+unset/hops <call> ann|spots|route|wwv|wcy (8) + +

++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 command +creates 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/logininfo (0) + +

++unset/logininfo Inform when a station logs out locally + + +

+unset/privilege (0) + +

++unset/privilege Remove any privilege for this session + + +

+You can use this command to 'protect' this session from unauthorised +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 (0) + +

++unset/prompt Set your prompt back to default + + +

+This command will set your user prompt to exactly 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 +fixed prompt). + + + SET/PROMPT clx > + + +UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to +normal. +unset/talk (0) + +

++unset/talk Stop TALK messages coming out on your terminal + + +

+unset/wcy (0) + +

++unset/wcy Stop WCY messages coming out on your terminal + + +

+unset/wwv (0) + +

++unset/wwv Stop WWV messages coming out on your terminal + + +

+unset/wx (0) + +

++unset/wx Stop WX messages coming out on your terminal + + +

+who (0) + +

++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 <text> (0) + +

++wx <text> Send a weather message to local users + + +

+wx full <text> (0) + +

++wx full <text> Send a weather message to all cluster users + + +

+wx sysop <text> (5) + +

++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 DXSpider User Manual v1.50 +Ian Maude, G0VGS, (g0vgs@gb7mbc.net) +September 2002 revision 0.1 + + +A complete reference for users of the DXSpider DXCluster program. + + + + + + + +Introduction + +What is a DX Cluster? + +

+A DX Cluster is a packet node where DX chasers on any band or mode can +post rare or interesting stations that they have worked or heard. Of +course other people are doing the same thing too, so you can find new +DX as well as telling others about the stations you have worked. +Clusters tend to be linked to each other so that the amount of people +using them is increased, thereby increasing the amount of posted DX. +Other information can be found on clusters such as on-line call books, +mail etc. You can talk to other stations connected to the cluster +network too, in real time, whether at the node you are logged into or +on another node connected to the network. You can also use converse +mode, where several stations can talk to each other in the same way. +Of course, the DX is still posted to you all the while! + +So what is DXSpider? + +

+PacketCluster nodes have been around since roughly 1985. The original +PacketCluster idea came from Dick Newell, AK1A, and ran under DOS. +In about 1992 Dick stopped the development of the PacketCluster +software for amateur radio. Many systems are still using this +relatively old DOS software today. + +There are several new compatible cluster programs around now, +including DXSpider. DXSpider is a clone of PacketCluster software that runs +under several operating systems including Linux and Windows. Linux is fast +becoming the choice for amateur radio stations because of it's flexibility, +reliability and the lack of the memory limitations of DOS. Linux supports +multitasking and is also multiuser. It has support for AX25, ROSE, +NetROM and TCPIP built in, making it the ideal choice for amateur +radio. It is also totally free! + +DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an +exercise in perl programming. It has developed rapidly and today is a +very powerful cluster program. It was designed to be totally compatible +with the AK1A program, although several commands have been extended to +improve functionality. + +This manual is designed to help you become familiar with the commands +that DXSpider supports and to help you get the best from the program so +you can enjoy working that rare DX! As DXSpider is being improved all the +time, commands will be added as time goes by, so make sure you have +the most upto date version of this manual. The latest version will +always be included with the cluster program so if you are unsure, simply +ask your sysop. The manual will also be available on the wesite. + + +Logins and logouts. + +

+You might not think that there is a lot of point of including a +section on how to log in and out of DXSpider. However, you would be +suprised at the difficulties some people have in simply getting in +and out of the cluster! + +There are several ways a login might be achieved, dependant on how +the sysop has DXSpider configured. It is impossible for me to cover all +variations but here are the basic ones. + +AX25 logins. + +

+Simplicity itself. The usual CONNECT command will log you straight +into the cluster and you will not have to do anything else. +Obviously, you will have to connect to the correct callsign. Some +nodes use an SSID with their call so you would have to add that. + +Examples: + + +connect GB7MBC +connect GB7MBC-1 + + +Netrom logins. + +

+There are several possibilities here, dependant on how the sysop has +configured his system. If you are connecting via netrom then you are +most probably connecting from another station. Listing the nodes in +that station with the NODES command will tell you what callsign +or netrom alias to connect to. Then just issue the connect command +from there. It is possible that the netrom alias may connect you to +a node with an alias for the cluster, such as DXC. Just type this +and you will be connected. + +Example: + +connect MBCDX + + +Telnet logins. + +

+With telnet connections, the source callsign is not seen by DXSpider, so +you will be asked to login with your callsign. +To telnet to DXSpider, you would connect to a specific port. There is no +standard at the moment for a cluster telnet port but ask the sysop if +you are unsure. + +Example: + + +telnet gb7mbc 8000 + + +All the above are possible ways of connecting to a DXSpider cluster. You +may have some or all of these available to you. There may be one or +two additional ways to connect dependant on the network local to you. +However I am sure you get the idea. + +Logouts. + +

+Logging out can be done by simply issuing the standard BYE +command. + +You could also send a disconnect if you are using AX25, or a CLOSE +command if you are connected via telnet. +If you do not log out gracefully using one of the above commands, +you may find you are unable to get a full connect next time. This +may also happen if a netrom connection drops. You may get connected, +but nothing else will happen because the program thinks you are still +connected and will not let you connect twice under the same call. +However you could reconnect by adding a number to the end of your call, +for example G0YLM-2. +This can be done by either altering your MYCALL setting in the TNC or +by altering your program configuration. + + +Setting your personal details. + +

+Once logged in to the cluster, you should set your details so that +anybody who wishes to contact you can find out who and where you are. +There are four items to set, your name, qth, location and home node. +Setting these details also allows the use of the SHOW/HEADING and +SHOW/SUN commands from within the cluster. Unless you set your QTH +and location, these commands cannot function. +Once you have set your name, DXSpider will greet you with it next time +you login. Your QTH setting is where you live and it is a good idea +to add your locator to this as the location setting is converted to +latitude and longitude once inputted. You can actually set your location +in latitude/longitude or as a locator. Setting your home node will +tell the program where you wish mail to be sent to you. + +Examples: + + +set/name Ian +set/qth Morecambe, Lancashire IO84NB +set/location 48 34 n 12 12 e +set/qra IO84NB +set/home gb7mbc + + +Getting and posting DX. + +

+When all is said and done, this is the main function of a DX cluster. +In its simplest form you can just connect to the node and you will +start to receive DX spots almost immediately! You can check on +recent postings in either a general manner or on a particular band or +mode. You can even check DX by callsign or a fragment of a callsign. +Of course, once you get the hang of things, it is expected that you +start posting some yourself! After all, there would be no clusters +if people did not post DX and you get the added thrill of the hunt! + +Receiving DX. + +

+As we have already said, it is possible just to connect to the +cluster and you will receive spots automatically. However, you may +wish to check on spots just posted. Maybe you wish to see if a +particular band is open or if a certain callsign is active, perhaps a +DXpedition. The command to do this is SHOW/DX. Without any +other arguments, this command will output the last 10 spots +posted. It is possible to look at more than this, for example the +last 20 or 50 spots, by adding the number to the command. You can +make it even more specific by adding a band in either wavelength or +frequency, and/or any additional information such as QSL details. + +Examples: + + +show/dx +show/dx 5 +show/dx 20 + + +will show the last 10, 5 and 20 spots received by the cluster +respectively. + +Examples + + +show/dx on 20m +show/dx 10 on 20m +show/dx 20 on 20m + + +will show the last 5, 10 or 20 spots on 20 metres only. + +It is also possible to check for certain callsigns, or fragments of +callsigns in the same way. + +Examples: + + +show/dx g0vgs +show/dx 10 g0vgs + + +would show the last 5 or 10 dx spots containing the callsign g0vgs. + +

+You can check for DX by offset and also by specifying a comment to +search for. + +Examples: + + +show/dx 30-40 +show/dx 14000-14033 +show/dx iota + + +would show the spots that arrived between 30 and 40 spots ago and any +spots with the word iota in the comment field. The case of +the comment is not important. + +Checking DX posted on a certain day is possible too. All you have +to do here is to specify how many days ago it was like this ... + +Example: + + +show/dx day 30 + + +It is of course possible to specify multiple arguments. + +Example: + + +show/dx 20 prefix 9a on vhf day 30 + + +This would show the last 20 spots posted by or about calls with the prefix +9a on vhf 30 days ago. + +As you can see the SHOW/DX command is very flexible, so if you are +not sure whether something will work or not, try it and see! More +information can be found in the Command Set section. + +Posting DX. + +

+To post DX you use the DX command. The syntax is shown below. + +Example: + + +dx (frequency) (callsign) (remarks) + + +Where frequency is in kilohertz and the callsign is the callsign of +the station you have worked or heard, (ie not your own callsign!). +The remarks section allows you to add information like the operators +name or perhaps a location. Actually DXSpider will allow the frequency +and callsign fields to be entered in any order. + +Example: + + +dx 14004 pa3ezl OP Aurelio 599 + + +In fact, all the following will give the same result... + + +dx 14004 pa3ezl OP Aurelio 599 +dx pa3ezl 14004 OP Aurelio 599 +dx pa3ezl 14.004 OP Aurelio 599 + + +This posting, or callout as it is known, will be forwarded to all +other connected stations both at the cluster you are connected to and +other active clusters in the network. The callout will also be sent +to you as proof of receipt. + +Headings and propagation + +

+There are three commands in DXSpider to help you get the best DX possible. +These are SHOW/SUN, SHOW/MOON and +SHOW/HEADING. These commands will only work for you if you +have entered your personal details. They use your entered location as +a reference, so if you have not entered it or have entered it incorrectly +they will not return the correct information. + +Sun + +

+The SHOW/SUN command can be used in three different ways. It +can be used to show sunrise and sunset times for your own station, a +particular callsign or a prefix. + +Example: + + +show/sun + + +The output from this would look something like this .. + + +sh/sun +Location Rise Set Azim Elev +G0VGS Morecambe, Lancashire 07:08Z 17:39Z 205.3 24.1 + + + +sh/sun 5b4 + + +would look like this ... + + +sh/sun 5b4 +Location Rise Set Azim Elev +5B Cyprus-5B 04:23Z 15:40Z 244.0 18.8 + + +You can also specify multiple arguments like this ... + + +sh/sun gw4veq 5b4ab zs + + +and then the output would look like this ... + + +sh/sun gw4veq 5b4ab zs +Location Rise Set Azim Elev +GW4VEQ Brungwran, Isle of Anglesey IO 07:14Z 17:48Z 204.9 24.9 +5B Cyprus-5B 04:23Z 15:40Z 244.5 18.3 +ZS So-Africa-ZS1-ZS 04:31Z 17:28Z 289.9 41.3 +ZS So-Africa-ZS5-ZS 03:44Z 16:34Z 278.5 32.0 +ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0 + + +Moon + +

+The SHOW/MOON command works in the same way as the +SHOW/SUN command. This program however, calculates the +rise and set times of the moon for a prefix or callsign, together +with the current azimuth and elevation of the sun at these +locations. + +Example: + + +show/moon ea + + +The output from this command would look like this .. + + +sh/moon ea +Location Rise Set Azim Elev RGain dB +EA Spain-EA 08:15Z 20:09Z 257.2 9.5 -0.6 + + +You can see that the output is similar to the SHOW/SUN +command, with slightly different fields. + +Heading + +

+The SHOW/HEADING command works in the same way as the +SHOW/SUN and SHOW/MOON commands but outputs beam +headings for a specified callsign or prefix. Reciprocal beam headings +are also calculated. + +Example + + +show/heading zl + + +The output from this command would look like this .. + + +sh/heading zl +ZL New-Zealand-ZL1-ZL: 7 degs - dist: 11238 mi, 18087 km Reciprocal heading: 355 degs +ZL New-Zealand-ZL2-ZL: 9 degs - dist: 11540 mi, 18574 km Reciprocal heading: 353 degs +ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 345 degs +ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs + + +Announcements. + +Making announcements. + +

+Occasionally, you may wish to post something that does not fall into +the normal parameters for a DX callout. You may wish to tell +everybody connected that 10 FM is open for example, or ask if anyone +knows the QSL manager for a certain callsign etc. You can do this +using the ANNOUNCE command. + +Example: + + +announce 10 FM is open in IO84NB to europe. + + +That would let everyone know locally that this was the case, however +it would not be forwarded to other nodes connected. To send +announcements to other connected nodes as well, you would use the +FULL extension. + +Example: + + +announce full Anyone seen EA7WA today? + + +Be cautious in your use of announce full. There are many other tools +available to get the information you require and the judicious use of +this command is frowned upon as it creates a great deal of traffic +across the network. + +Listing announcements. + +

+You can list previous announcements in the standard format with the +SHOW command. As before you can list just the last 5 or as +many as you wish. + +Example: + + +show/announcements +show/announcements 10 + + +Nodes and users. + +

+You can check which nodes are connected in the network, who is +logged on locally, who is logged on at all the nodes or even +just one node in particular. This is handy if you wish to see whether +a friend is connected at the node they use. To see who is connected +to the nodes, the SHOW/CONFIGURATION command is used. + +Example: + + +show/configuration +show/configuration/nodes +show/configuration (node_call) +show/configuration (prefix) + + +The first of our three examples would output something like this, + + +sh/c +Node Callsigns +EI5TCR (7 users) +GB7ADX +GB7BAA G4FPV G8TIC +GB7BIG (GD0TEP) GD3UMW +GB7BPQ (G0INA) G0RCI G3AKU G3OCA +(GB7CDX) G3JNB G4ALR +GB7DJK G0FYD G0REK G1TLH G4PEL G4SOZ + G4TVR G7SQW K8AZ M0CTQ-1 MM1CXE-10 + ON7WP +GB7DXA G0RDI G8SJP +GB7DXC (G0HDB) G0WFK (G1FYC) G3KWK G3LME + G3OIL G4BGW G4FUJ (G4PDQ) GW7SMV +GB7DXE G1NNB +(GB7DXG) GU6EFB GU7DHI +GB7DXK G1NTW G3IBI G3NSM G3XAQ G4CUS + G4XQY G7GAN +GB7DXM G1EUC G3GAF G3LAS G4ZTR G8WXU + M0BCT M1EMF + + +You will notice that EI5TCR is showing only that it has 7 users and not +giving the actual callsigns. This means that this node is on a limited +protocol of some kind, probably because of a contest situation where +slow radio links can block up and fail if too much information is sent +between nodes. + +The second example would just show the nodes connected in the +network, like this, + + +sh/c/n +Node Callsigns +GB7BAA GB7BAA GB7BPQ (GB7CDX) GB7DJK GB7DXA + GB7DXC GB7DXE (GB7DXG) GB7DXK GB7DXL + GB7DXM GB7DXS GB7IPT GB7MRS GB7UJS + GB7YDX KL7G N2TLY (ON0DXK) +GB7BIG EI5TCR GB7ADX GB7BIG GB7UDX +GB7MBC +PA4AB-14 PA4AB-14 +PI4TUE-8 PI4TUE-8 + + +If we insert the node_call pi4tue-8 into the third example, then +this would be the output, + + +Node Callsigns +PI4TUE-8 9A1CMA-6 DF6PW DL4FAY DL4KAK DL4WF-2 + F5NOD-2 F5PAC IZ0CSR N6CR OH2BLD + ON1LVL-13 ON4CBT ON4CJP ON5DXL-14 ON7NQ + PA0RCT PA3DYS PA3FDO PA5KW-4 PI4TUE-9 + YT1XX + + +As you can see, only the users of the requested node are shown. + +You can also use a prefix to show only a group of nodes. For example +you may only wish to see who is connected to the nodes in the UK. To +do this simply use a prefix like this ... + + +show/configuration gb7 + + +To show the locally connected users, the SHOW/USERS command is +used + +Example: + + +show/users + + +The output of this command would look like this, + + +Callsigns connected to GB7MBC +G0JHC G0NEI G0VGS G0VGS-2 G0YLM +G3JAG G3OWO G3UEU + + +Talk mode. + +

+You can send a single comment or start a dedicated talk session to +another user by using the TALK command. + +

+Talk mode is used to send a one line comment or greeting to a +specific user connected either at your node or another in the +network. You can also enter into a dedicated talk session with +another user. Talks will be automatically forwarded to other nodes +if the station you are talking to is not connected locally. +You can find out who is connected by using the +SHOW/CONFIGURATION command, (described earlier). + +Examples: + + +talk g0rdi Having a good day Iain? + + +This example would send the line "Having a good day Iain?" to the +user g0rdi but would leave you in normal mode. + + +talk g0rdi +Entering Talkmode, /EX to end, / to run a command +Talk (G0RDI)> + + +As you can see, you can still run commands whilst in talk mode. +Simply prefix the command with a / like /sh/dx and you will get +the expected output. +If the user is connected to another node, you may have to use a +slightly extended version of the TALK command. + + +talk g0rdi > gb7djk + + +To exit talk mode, you issue the command /ex. + +Whilst in talk mode you will still receive DX spots. This means that +you can chat to a friend whilst working DX. + +Mail. + +

+You can send and receive both personal mail and bulletins with DXSpider +quite easily. + +The "directory" command. + +

+To list mail you would use the DIRECTORY command. On its +own, this command will output the last ten messages received by the +node, either to or from yourself or bulletins such as "DX" and "ALL". +As with other commands you can display more by specifying a number +with the command. You should be aware that Spider will accept +these commands by separating with either a slash or a space, so +dir new and dir/new work in the same way. + +Example: + + +directory +directory/20 +directory 20 + + +Of course most of the time you will only want to list new mail sent +to you personally since your last login. However you might also like +to check for general mail received by the node. In fact if there is +new mail for you, the cluster will tell you when you login. You will +also be informed if new mail arrives for you during the time you are +logged in. +Mail is not only sent to callsigns though. Mail can also be sent to +subjects like "all" or "local" or "dx" etc. You can treat these +bulletins in the same way as personal mail with the directory +command. + +Examples: + + +directory/new +directory/own +directory/own/10 +directory/all +directory/from + + +The last option will only show mail from a callsign if it was sent to +you personally or was sent as a bulletin. There are some additional +commands and these can be found in the DXSpider Command Reference section. + +Reading mail. + +

+The output of the DIRECTORY command could be something like +this. + + +dir + 20735 2 ALL GW7SMV 21-Feb 1204Z REC 9E1S QSL TDY 50Mhz.... + 20823 308 UK G0HDB 22-Feb 2334Z Help - which district code? + 20824 105 ALL W9AE 23-Feb 0349Z S0NY QSL address? + 20825 2 UK G0LRJ 23-Feb 0806Z QSL REC LZ2CJ/1.CARD NO-750. + 20858 2 ALL GW7SMV 24-Feb 0905Z REC S92DX QSL CARD TDY 50Mhz + 20921 200 ALL GM4FDM 27-Feb 2203Z Trip to VP8 + 20949 375 ALL K0MN 27-Feb 0428Z ST0P cards are gd @ ARRL + 20950 2 UK G0LRJ 28-Feb 0835Z QSL REC SV9/IZ0CKJ/P EU-187. + 20987 569 ALL GD0TEP 1-Mar 1733Z Portable contests + 21076 2 ALL G4AFJ 3-Mar 1743Z kh6nd/kh5 qsl received + 21184-p 599 GW4HAT G0VGS 4-Mar 1518Z Re: Time + + +The first column is the actual message number. If the message is a +personal one to you, you will see a letter 'p' after this number. If +the message has been read, there will be a '-' between the message +number and the 'p'. This only works for personal messages. The next +column shows the file size of the message. The third column shows the +address the message was sent to and the next column shows who sent it. +The rest is fairly self-explanatory. + +Reading a message is as simple as typing read, followed by the +message number that you wish to read. + +Example: + + +read 25 + + +will read message number 25. However the mail will be displayed in it's +entirety unless you specify a page length. You can set your page length +to any number you like and when the message reaches that number of lines +you will get a prompt giving you options. + +Example: + + +set/page 20 + + + +Sending mail. + +

+Sending mail is done in the time honoured way. First you specify +a recipient for the message, then you will be prompted for a subject. +Once you have done this you will be asked to type your message. +Please remember that there is no automatic word wrap, so unless you +are using a client that wraps lines automatically, remember to hit +return at the end of each line. + +Example: + + +send m0azm +Enter Subject (30 characters): +See you Thursday +Enter Message /EX to send or /ABORT to exit +Hi Ian, +Just a quick note to say that I can make Thursday after all. The +appointment I had has cancelled so we are go! +Cheers +Ian + + +At this point you can either hit return and enter /ex to send the +message or use /abort at any time to abort it. You can now display +the message in the normal way. There are several send options and +these are listed in the Command Set section. These include sending +mail to several recipients and asking for a return receipt. + + +Replying to mail. + +

+If mail is addressed to you or to a bulletin address, you can use the +REPLY command to reply to it. Using this command, the +subject will be automatically set for you as "Re: subject", whatever +the subject was. + +Example: + + +reply 2500 + + +Deleting mail + +

+To delete a message, you use the delete command. +You can only delete messages sent to or received by yourself. +Bulletins are dealt with automatically or by the sysop. + +Filtering (From version 1.45) + +General filter rules + +

+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. They are ... + + +clear/spots 1 +clear/spots all + + +There is clear/xxxx command for each type of filter. + +

+and you can check that your filters have worked by the command ... + + +show/filter + + +

+For now we are going to use spots for the examples, but you can apply the same +principles to all types of filter. + +Types of filter + +

+You can filter in several different ways. The options are listed in the +various helpfiles for accept, reject and filter. + +Advanced filtering + +

+Once you are happy with the results you get, you may like to experiment. + +

+The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU +can be written with a mixed filter, for example ... + + +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) + + +Note that the first filter has not been specified with a number. This +will automatically be assumed to be number 1. In this case, we have +said reject all HF spots in the CW section of the bands but accept +all others at HF. Also accept anything in VHF and above spotted in or +by operators in the zones 14, 15 and 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 through everything +else on HF. The next filter line lets through just VHF/UHF spots from EU. + + +Hints, tips and common questions. + +

+SET/BEEP command. You can find information +on this in the "DXSpider Command Reference" section. + +The DXSpider command reference + +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 [0-9] <pattern> + +

++accept/announce [0-9] <pattern> Set an 'accept' filter line for announce + + +

++accept/spots [0-9] <pattern> Set an 'accept' filter line for spots + + +

++accept/wcy [0-9] <pattern> set an 'accept' WCY filter + + +

++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 <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 +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 [<string>] [<nn>] + +

++blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings) + + +

++bye Exit from the cluster + + +

+This will disconnect you from the cluster +clear/announce [1|all] + +

++clear/announce [1|all] Clear a announce filter line + + +

+This command allows you to clear (remove) a line in a annouce filter or to +remove the whole filter. + +see CLEAR/SPOTS for a more detailed explanation. +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 [0-9|all] + +

++clear/spots [0-9|all] Clear a spot filter line + + +

++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 [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. +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. +dbshow <dbname> <key> + +

++dbshow <dbname> <key> Display an entry, if it exists, in a database + + +

++directory List messages + + +

+directory <from>-<to> + +

++directory <from>-<to> List messages <from> message <to> message + + +

++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> + + +

+dx [by <call>] <freq> <call> <remarks> + +

++dx [by <call>] <freq> <call> <remarks> Send a DX spot + + +

++echo <line> Echo the line to the output + + +

++filtering... Filtering things in DXSpider + + +

++help The HELP Command + + +

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

+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 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 + + +

+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. +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. +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 [0-9] <pattern> + +

++reject/announce [0-9] <pattern> Set a 'reject' filter line for announce + + +

++reject/spots [0-9] <pattern> Set a 'reject' filter line for spots + + +

++reject/wcy [0-9] <pattern> set a 'reject' WCY filter + + +

++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 (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 + + +

++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 + + +

++send private <call> Send a personal message + + +

+send rr <call> + +

++send rr <call> Send a message and ask for a read receipt + + +

+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/beep + +

++set/beep Add a beep to DX and other messages on your terminal + + +

+set/dx + +

++set/dx Allow DX messages to come out on your terminal + + +

+set/dxgrid + +

++set/dxgrid Allow QRA Grid Squares on the end of DX announcements + + +

+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/here + +

++set/here Tell the system you are present at your terminal + + +

+set/homenode <node> + +

++set/homenode <node> Set your normal cluster callsign + + +

++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) +and nl (Dutch). +set/location <lat & long> + +

++set/location <lat & long> Set your latitude and longitude + + +

+set/logininfo + +

++set/logininfo Inform when a station logs in locally + + +

+set/name <your name> + +

++set/name <your name> Set your name + + +

+Tell the system what your name is eg:- + + SET/NAME Dirk + + +set/page <lines per page> + +

++set/page <lines per page> Set the lines per page + + +

++set/password Set your own password + + +

++set/prompt <string> Set your prompt to <string> + + +

+set/qra <locator> + +

++set/qra <locator> Set your QRA Grid locator + + +

++set/qth <your qth> Set your QTH + + +

+Tell the system where you are. For example:- + + SET/QTH East Dereham, Norfolk + + +set/talk + +

++set/talk Allow TALK messages to come out on your terminal + + +

+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/configuration [<node>] + +

++show/configuration [<node>] Show all the nodes and users visible + + +

++show/configuration/node Show all the nodes connected locally + + +

+Show all the nodes connected to this node. +show/date [<prefix>|<callsign>] + +

++show/date [<prefix>|<callsign>] Show the local time + + +

++show/dx Interrogate the spot database + + +

++show/dxcc <prefix> Interrogate the spot database by country + + +

++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/files [<filearea> [<string>]] + +

++show/files [<filearea> [<string>]] List the contents of a filearea + + +

++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/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times + + +

++show/muf <prefix> [<hours>][long] Show the likely propagation to a prefix + + +

++show/newconfiguration [<node>] Show all the nodes and users visible + + +

++show/newconfiguration/node Show all the nodes connected locally + + +

+Show all the nodes connected to this node in the new format. +show/prefix <callsign> + +

++show/prefix <callsign> Interrogate the prefix database + + +

++show/qra <lat> <long> Convert lat/long to a QRA Grid locator + + +

++show/qra <locator> [<locator>] Show distance between QRA Grid locators + + +

+show/qrz <callsign> + +

++show/qrz <callsign> Show any callbook details on a 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/station [<callsign> ..] Show information about a callsign + + +

++show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times + + +

++show/time [<prefix>|<callsign>] Show the local time + + +

++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/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/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 +sysop + +

++sysop Regain your privileges if you login remotely + + +

++talk <call> > <node> [<text>] Send a text message to another station via a node + + +

++talk <call> [<text>] Send a text message to another station + + +

+type <filearea>/<name> + +

++type <filearea>/<name> Look at the contents of a file in one of the fileareas + + +

++unset/announce Stop announce messages coming out on your terminal + + +

+unset/anntalk + +

++unset/anntalk Stop talk like announce messages on your terminal + + +

++unset/beep Stop beeps for DX and other messages on your terminal + + +

+unset/dx + +

++unset/dx Stop DX messages coming out on your terminal + + +

+unset/dxgrid + +

++unset/dxgrid Stop QRA Grid Squares on the end of DX announcements + + +

++unset/echo Stop the cluster echoing your input + + +

++unset/email Stop personal msgs being forwarded by email + + +

++unset/here Tell the system you are absent from your terminal + + +

+unset/logininfo + +

++unset/logininfo Inform when a station logs out locally + + +

+unset/privilege + +

++unset/privilege Remove any privilege for this session + + +

++unset/prompt Set your prompt back to default + + +

++unset/talk Stop TALK messages coming out on your terminal + + +

+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 Show who is physically connected + + +

+This is a quick listing that shows which callsigns are connected and +what sort of connection they have +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 + + +

1. Routing and Filtering

1.1 Introduction +

1.2 Route Filters +

1.3 The node_default filter +

1.4 General route filtering +

1.5 General filter rules +

1.6 Types of filter +

1.7 Filter options +

1.8 Default filters +

1.9 Advanced filtering +

1.10 Basic hop control +

1.11 Hop Control on Specific Nodes +

1.12 Isolating networks +

10. CVS

10.1 CVS from a Linux platform +

10.2 CVS from a Windows platform +

11. The DXSpider command set

11.1 accept (0) +

11.2 accept/announce <call> [input] [0-9] <pattern> (8) +

11.3 accept/announce [0-9] <pattern> (0) +

11.4 accept/route <call> [0-9] <pattern> (8) +

11.5 accept/spots <call> [input] [0-9] <pattern> (8) +

11.6 accept/spots [0-9] <pattern> (0) +

11.7 accept/wcy <call> [input] [0-9] <pattern> (8) +

11.8 accept/wcy [0-9] <pattern> (0) +

11.9 accept/wwv <call> [input] [0-9] <pattern> (8) +

11.10 accept/wwv [0-9] <pattern> (0) +

11.11 announce <text> (0) +

11.12 announce full <text> (0) +

11.13 announce sysop <text> (5) +

11.14 apropos <string> (0) +

11.15 blank [<string>] [<nn>] (0) +

11.16 bye (0) +

11.17 catchup <node call> all|[<msgno> ...] (5) +

11.18 clear/announce <callsign> [input] [0-9|all] (8) +

11.19 clear/announce [1|all] (0) +

11.20 clear/route <callsign> [input] [0-9|all] (8) +

11.21 clear/route [1|all] (0) +

11.22 clear/spots <callsign> [input] [0-9|all] (8) +

11.23 clear/spots [0-9|all] (0) +

11.24 clear/wcy <callsign> [input] [0-9|all] (8) +

11.25 clear/wcy [1|all] (0) +

11.26 clear/wwv <callsign> [input] [0-9|all] (8) +

11.27 clear/wwv [1|all] (0) +

11.28 connect <callsign> (5) +

11.29 dbavail (0) +

11.30 dbshow <dbname> <key> (0) +

11.31 directory (0) +

11.32 directory <from>-<to> (0) +

11.33 directory <nn> (0) +

11.34 directory all (0) +

11.35 directory from <call> (0) +

11.36 directory new (0) +

11.37 directory own (0) +

11.38 directory subject <string> (0) +

11.39 directory to <call> (0) +

11.40 directory- (5) +

11.41 disconnect <call> [<call> ...] (8) +

11.42 dx [by <call>] <freq> <call> <remarks> (0) +

11.43 echo <line> (0) +

11.44 filtering... (0) +

11.45 forward/latlong <node_call> (8) +

11.46 forward/opernam <call> (1) +

11.47 help (0) +

11.48 init <node> (5) +

11.49 kill (5) +

11.50 kill <from msgno>-<to msgno> (0) +

11.51 kill <from>-<to> (5) +

11.52 kill <msgno> [<msgno..] (0) +

11.53 kill <msgno> [<msgno> ...] (0) +

11.54 kill expunge <msgno> [<msgno..] (6) +

11.55 kill from <call> (5) +

11.56 kill full <msgno> [<msgno..] (5) +

11.57 kill full <msgno> [<msgno] (5) +

11.58 kill to <call> (5) +

11.59 kill from <regex> (0) +

11.60 kill to <regex> (0) +

11.61 links (0) +

11.62 load/keps (5) +

11.63 load/keps [nn] (5) +