2 # please put your help in in alphabetical order
4 # a string search is done in the command field (case is ignored)
5 # and all commands matching the asked for command are printed out
7 # the order of the fields in each header is
8 # privilege, command, Description
9 # if the command ends in a - then that line isn't printed, but any
10 # subsequent lines are
12 # Comment lines are indented before printing
14 === 0^ACCEPT/ANNOUNCE [0-9] <pattern>^Set an 'accept' filter line for announce
15 Create an 'accept this announce' line for a filter.
17 An accept filter line means that if the announce matches this filter it is
18 passed onto the user. See HELP FILTERING for more info. Please read this
19 to understand how filters work - it will save a lot of grief later on.
21 You can use any of the following things in this line:-
23 info <string> eg: iota or qsl
24 by <prefixes> eg: G,M,2
26 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
27 origin_itu <prefixes or numbers> or: G,GM,GW
28 origin_zone <prefixes or numbers>
29 by_dxcc <prefixes or numbers>
30 by_itu <prefixes or numbers>
31 by_zone <prefixes or numbers>
33 wx 1 filter WX announces
34 dest <prefixes> eg: 6MUK,WDX (distros)
39 acc/ann 2 by_zone 14,15,16
40 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
44 You can use the tag 'all' to accept everything eg:
48 but this probably for advanced users...
50 === 8^ACCEPT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
51 This version allows a sysop to set a filter for a callsign as well as the
52 default for nodes and users eg:-
55 accept/ann input node_default by G,M,2
56 accept/ann user_default by G,M,2
58 === 8^ACCEPT/ROUTE <call> [0-9] <pattern>^Set an 'accept' filter line for routing
59 Create an 'accept this routing PC Protocol' line for a filter.
61 An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
62 it is passed thru that interface. See HELP FILTERING for more info. Please read this
63 to understand how filters work - it will save a lot of grief later on.
65 You can use any of the following things in this line:-
67 call <prefixes> the callsign of the thingy
68 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
69 call_itu <prefixes or numbers> or: G,GM,GW
70 call_zone <prefixes or numbers>
71 origin <prefixes> really the interface it came in on
72 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
73 origin_itu <prefixes or numbers> or: G,GM,GW
74 origin_zone <prefixes or numbers>
78 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
79 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
81 You can use the tag 'all' to accept everything eg:
86 === 0^ACCEPT/SPOTS [0-9] <pattern>^Set an 'accept' filter line for spots
87 Create an 'accept this spot' line for a filter.
89 An accept filter line means that if the spot matches this filter it is
90 passed onto the user. See HELP FILTERING for more info. Please read this
91 to understand how filters work - it will save a lot of grief later on.
93 You can use any of the following things in this line:-
95 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
96 on <range> same as 'freq'
97 call <prefixes> eg: G,PA,HB9
98 info <string> eg: iota or qsl
100 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
101 call_itu <prefixes or numbers> or: G,GM,GW
102 call_zone <prefixes or numbers>
103 by_dxcc <prefixes or numbers>
104 by_itu <prefixes or numbers>
105 by_zone <prefixes or numbers>
109 For frequencies, you can use any of the band names defined in
110 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
111 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
112 this is more efficient than saying simply: freq HF (but don't get
113 too hung up about that)
118 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
120 You can use the tag 'all' to accept everything, eg:
124 but this probably for advanced users...
127 === 8^ACCEPT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
128 This version allows a sysop to set a filter for a callsign as well as the
129 default for nodes and users eg:-
131 accept/spot db0sue-7 1 by_zone 14,15,16
132 accept/spot node_default all
133 set/hops node_default 10
135 accept/spot user_default by G,M,2
137 === 0^ACCEPT/WCY [0-9] <pattern>^set an 'accept' WCY filter
138 It is unlikely that you will want to do this, but if you do then you can
139 filter on the following fields:-
141 by <prefixes> eg: G,M,2
143 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
144 origin_itu <prefixes or numbers> or: G,GM,GW
145 origin_zone <prefixes or numbers>
146 by_dxcc <prefixes or numbers>
147 by_itu <prefixes or numbers>
148 by_zone <prefixes or numbers>
151 There are no examples because WCY Broadcasts only come from one place and
152 you either want them or not (see UNSET/WCY if you don't want them).
154 This command is really provided for future use.
156 See HELP FILTER for information.
158 === 8^ACCEPT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
159 This version allows a sysop to set a filter for a callsign as well as the
160 default for nodes and users eg:-
162 accept/wcy node_default all
163 set/hops node_default 10
165 === 0^ACCEPT/WWV [0-9] <pattern>^set an 'accept' WWV filter
166 It is unlikely that you will want to do this, but if you do then you can
167 filter on the following fields:-
169 by <prefixes> eg: G,M,2
171 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
172 origin_itu <prefixes or numbers> or: G,GM,GW
173 origin_zone <prefixes or numbers>
174 by_dxcc <prefixes or numbers>
175 by_itu <prefixes or numbers>
176 by_zone <prefixes or numbers>
183 is probably the only useful thing to do (which will only show WWV broadcasts
184 by stations in the US).
186 See HELP FILTER for information.
188 === 8^ACCEPT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
189 This version allows a sysop to set a filter for a callsign as well as the
190 default for nodes and users eg:-
192 accept/wwv db0sue-7 1 by_zone 4
193 accept/wwv node_default all
194 set/hops node_default 10
196 accept/wwv user_default by W,K
198 === 0^ANNOUNCE <text>^Send an announcement to LOCAL users only
199 <text> is the text of the announcement you wish to broadcast
201 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
202 This will send your announcement cluster wide
204 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
206 === 0^APROPOS <string>^Search help database for <string>
207 Search the help database for <string> (it isn't case sensitive), and print
208 the names of all the commands that may be relevant.
210 === 0^BLANK [<string>] [<nn>]^Print nn (default 1) blank lines (or strings)
211 In its basic form this command prints one or more blank lines. However if
212 you pass it a string it will replicate the string for the width of the
213 screen (default 80) and then print that one or more times, so:
217 prints two blank lines
221 prints a row of - characters once.
225 prints 'abcabcabcabcabcabc....'
227 This is really only of any use in a script file and you can print a maximum
230 === 0^BYE^Exit from the cluster
231 This will disconnect you from the cluster
233 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
234 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
235 When you send messages the fact that you have forwarded it to another node
236 is remembered so that it isn't sent again. When you have a new partner
237 node and you add their callsign to your /spider/msg/forward.pl file, all
238 outstanding non-private messages will be forwarded to them. This may well
239 be ALL the non-private messages. You can prevent this by using these
243 catchup GB7DJK 300 301 302 303 500-510
245 and to undo what you have just done:-
248 uncatchup GB7DJK 300 301 302 303 500-510
250 which will arrange for them to be forward candidates again.
252 Order is not important.
254 === 0^CLEAR/ANNOUNCE [1|all]^Clear a announce filter line
255 This command allows you to clear (remove) a line in a annouce filter or to
256 remove the whole filter.
258 see CLEAR/SPOTS for a more detailed explanation.
260 === 8^CLEAR/ANNOUNCE [input] <callsign> [0-9|all]^Clear a announce filter line
261 A sysop can clear an input or normal output filter for a user or the
262 node_default or user_default.
264 === 0^CLEAR/ROUTE [1|all]^Clear a route filter line
265 This command allows you to clear (remove) a line in a route filter or to
266 remove the whole filter.
268 see CLEAR/SPOTS for a more detailed explanation.
270 === 8^CLEAR/ROUTE [input] <callsign> [0-9|all]^Clear a route filter line
271 A sysop can clear an input or normal output filter for a user or the
272 node_default or user_default.
274 === 0^CLEAR/SPOTS [0-9|all]^Clear a spot filter line
275 This command allows you to clear (remove) a line in a spot filter or to
276 remove the whole filter.
278 If you have a filter:-
281 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
287 you will be left with:-
289 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
295 the filter will be completely removed.
297 === 8^CLEAR/SPOTS [input] <callsign> [0-9|all]^Clear a spot filter line
298 A sysop can clear an input or normal output filter for a user or the
299 node_default or user_default.
301 === 0^CLEAR/WCY [1|all]^Clear a WCY filter line
302 This command allows you to clear (remove) a line in a WCY filter or to
303 remove the whole filter.
305 see CLEAR/SPOTS for a more detailed explanation.
307 === 8^CLEAR/WCY [input] <callsign> [0-9|all]^Clear a WCY filter line
308 A sysop can clear an input or normal output filter for a user or the
309 node_default or user_default.
311 === 0^CLEAR/WWV [1|all]^Clear a WWV filter line
312 This command allows you to clear (remove) a line in a WWV filter or to
313 remove the whole filter.
315 see CLEAR/SPOTS for a more detailed explanation.
317 === 8^CLEAR/WWV [input] <callsign> [0-9|all]^Clear a WWV filter line
318 A sysop can clear an input or normal output filter for a user or the
319 node_default or user_default.
321 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
322 Start a connection process that will culminate in a new connection to the
323 DX cluster <callsign>. This process creates a new 'client' process which will
324 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
325 necessary to traverse the network(s) to logon to the cluster <callsign>.
327 === 9^DELETE/USER <callsign> ...^Delete this user from the User Database
328 This command will completely remove a one or more users from the database.
330 There is NO SECOND CHANCE.
332 It goes without saying that you should use this command CAREFULLY!
334 === 0^DBAVAIL^Show a list of all the Databases in the system
335 Title says it all really, this command lists all the databases defined
336 in the system. It is also aliased to SHOW/COMMAND.
338 === 9^DBCREATE <name>^Create a database entry
339 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
340 === 9^DBCREATE <name> remote <node>^Create a remote database entry
341 DBCREATE allows you to define a database in the system. It doesn't actually
342 create anything, just defines it.
344 The databases that are created are simple DB_File hash databases, they are
345 therefore already 'indexed'.
347 You can define a local database with the first form of the command eg:
351 You can also chain databases with the addition of the 'chain' keyword.
352 This will search each database one after the other. A typical example
355 DBCREATE sdx_qsl chain sql_ad
357 No checking is done to see if the any of the chained databases exist, in
358 fact it is usually better to do the above staement first then do each of
359 the chained databases.
361 Databases can exist offsite. To define a database that lives on another
364 DBCREATE buckmaster remote gb7dxc
366 Remote databases cannot be chained; however, the last database in a
367 a chain can be a remote database eg:
369 DBCREATE qsl chain gb7dxc
371 To see what databases have been defined do:
373 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
375 It would be normal for you to add an entry into your local Aliases file
376 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
377 need to add a line like:-
382 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
391 to work as they may be used to.
393 See DBIMPORT for the importing of existing AK1A format data to databases.
394 See DBSHOW for generic database enquiry
396 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
397 If you want to import or update data in bulk to a database you can use
398 this command. It will either create or update entries into an existing
399 database. For example:-
401 DBIMPORT oblast /tmp/OBLAST.FUL
403 will import the standard OBLAST database that comes with AK1A into the
404 oblast database held locally.
406 === 9^DBREMOVE <dbname>^Delete a database
407 DBREMOVE will completely remove a database entry and also delete any data
408 file that is associated with it.
410 There is no warning, no comeback, no safety net.
416 will remove the oblast database from the system and it will also remove
417 the associated datafile.
421 There is no warning, no comeback, no safety net.
423 You have been warned.
425 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
426 This is the generic user interface to the database to the database system.
427 It is expected that the sysop will add an entry to the local Aliases file
428 so that users can use the more familiar AK1A style of enquiry such as:
432 but if he hasn't and the database really does exist (use DBAVAIL or
433 SHOW/COMMAND to find out) you can do the same thing with:
437 === 9^DEBUG^Set the cluster program into debug mode
438 Executing this command will only have an effect if you are running the cluster
443 It will interrupt the cluster just after the debug command has finished.
445 === 0^DIRECTORY^List messages
446 === 0^DIRECTORY ALL^List all messages
447 === 0^DIRECTORY OWN^List your own messages
448 === 0^DIRECTORY NEW^List all new messages
449 === 0^DIRECTORY TO <call>^List all messages to <call>
450 === 0^DIRECTORY FROM <call>^List all messages from <call>
451 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
452 === 0^DIRECTORY <nn>^List last <nn> messages
453 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
454 List the messages in the messages directory.
456 If there is a 'p' one space after the message number then it is a
457 personal message. If there is a '-' between the message number and the
458 'p' then this indicates that the message has been read.
460 You can use shell escape characters such as '*' and '?' in the <call>
463 You can combine some of the various directory commands together eg:-
467 DIR SUBJECT IOTA 200-250
469 You can abbreviate all the commands to one letter and use ak1a syntax:-
475 Sysops can see all users' messages.
477 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
478 Disconnect any <call> connected locally
480 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
481 This is how you send a DX Spot to other users. You can, in fact, now
482 enter the <freq> and the <call> either way round.
488 will all give the same result. You can add some remarks to the end
489 of the command and they will be added to the spot.
491 DX FR0G 144600 this is a test
493 You can credit someone else by saying:-
495 DX by G1TLH FR0G 144.600 he isn't on the cluster
497 The <freq> is compared against the available bands set up in the
498 cluster. See SHOW/BANDS for more information.
500 === 0^ECHO <line>^Echo the line to the output
501 This command is useful in scripts and so forth for printing the
502 line that you give to the command to the output. You can use this
503 in user_default scripts and the SAVE command for titling and so forth
505 The script will interpret certain standard "escape" sequences as follows:-
507 \t - becomes a TAB character (0x09 in ascii)
508 \a - becomes a BEEP character (0x07 in ascii)
509 \n - prints a new line
511 So the following example:-
513 echo GB7DJK is a dxcluster
517 GB7DJK is a dxcluster
519 on the output. You don't need a \n on the end of the line you want to send.
521 A more complex example:-
523 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
533 === 9^EXPORT <msgno> <filename>^Export a message to a file
534 Export a message to a file. This command can only be executed on a local
535 console with a fully privileged user. The file produced will be in a form
536 ready to be imported back into the cluster by placing it in the import
537 directory (/spider/msg/import).
539 This command cannot overwrite an existing file. This is to provide some
540 measure of security. Any files written will owned by the same user as the
541 main cluster, otherwise you can put the new files anywhere the cluster can
542 access. For example:-
546 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
547 Export the users database to a file in ascii format. If no filename
548 is given then it will export the file to /spider/data/user_asc.
550 If the file already exists it will be renamed to <filename>.o. In fact
551 up to 5 generations of the file can be kept each one with an extra 'o' on the
554 BE WARNED: this will write to any file you have write access to. No check is
555 made on the filename (if any) that you specify.
557 === 0^FILTERING...^Filtering things in DXSpider
558 There are a number of things you can filter in the DXSpider system. They
559 all use the same general mechanism.
561 In general terms you can create a 'reject' or an 'accept' filter which
562 can have up to 10 lines in it. You do this using, for example:-
567 where ..... are the specific commands for that type of filter. There
568 are filters for spots, wwv, announce, wcy and (for sysops)
569 connects. See each different accept or reject command reference for
572 There is also a command to clear out one or more lines in a filter and
573 one to show you what you have set. They are:-
582 There is clear/xxxx command for each type of filter.
584 For now we are going to use spots for the examples, but you can apply
585 the principles to all types of filter.
587 There are two main types of filter 'accept' or 'reject'; which you use
588 depends entirely on how you look at the world and what is least
589 writing to achieve what you want. Each filter has 10 lines (of any
590 length) which are tried in order. If a line matches then the action
591 you have specified is taken (ie reject means ignore it and accept
594 The important thing to remember is that if you specify a 'reject'
595 filter (all the lines in it say 'reject/spots' (for instance) then if
596 a spot comes in that doesn't match any of the lines then you will get
597 it BUT if you specify an 'accept' filter then any spots that don't
598 match are dumped. For example if I have a one line accept filter:-
600 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
602 then automatically you will ONLY get VHF spots from or to CQ zones 14
603 15 and 16. If you set a reject filter like:
605 reject/spots on hf/cw
607 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
608 and will work it even on CW then you could say:-
610 reject/spots on hf/cw and not info iota
612 But in that case you might only be interested in iota and say:-
614 accept/spots not on hf/cw or info iota
616 which is exactly the same. You should choose one or the other until
617 you are confortable with the way it works. Yes, you can mix them
618 (actually you can have an accept AND a reject on the same line) but
619 don't try this at home until you can analyse the results that you get
620 without ringing up the sysop for help.
622 You can arrange your filter lines into logical units, either for your
623 own understanding or simply convenience. I have one set frequently:-
625 reject/spots 1 on hf/cw
626 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
628 What this does is to ignore all HF CW spots (being a class B I can't
629 read any CW and couldn't possibly be interested in HF :-) and also
630 rejects any spots on VHF which don't either originate or spot someone
633 This is an exmaple where you would use the line number (1 and 2 in
634 this case), if you leave the digit out, the system assumes '1'. Digits
635 '0'-'9' are available.
637 You can leave the word 'and' out if you want, it is implied. You can
638 use any number of brackets to make the 'expression' as you want
639 it. There are things called precedence rules working here which mean
640 that you will NEED brackets in a situation like line 2 because,
641 without it, will assume:-
643 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
645 annoying, but that is the way it is. If you use OR - use
646 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
649 If you want to alter your filter you can just redefine one or more
650 lines of it or clear out one line. For example:-
652 reject/spots 1 on hf/ssb
658 To remove the filter in its entirty:-
662 There are similar CLEAR commands for the other filters:-
670 Once you are happy with the results you get, you may like to experiment.
672 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
673 can be written with a mixed filter, eg:
677 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
679 each filter slot actually has a 'reject' slot and an 'accept'
680 slot. The reject slot is executed BEFORE the accept slot.
682 It was mentioned earlier that after a reject test that doesn't match,
683 the default for following tests is 'accept', the reverse is true for
684 'accept'. In the example what happens is that the reject is executed
685 first, any non hf/cw spot is passed to the accept line, which lets
686 thru everything else on HF.
688 The next filter line lets through just VHF/UHF spots from EU.
690 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
691 This command sends all the latitude and longitude information that your
692 cluster is holding against callsigns. One advantage of recieving this
693 information is that more locator information is held by you. This
694 means that more locators are given on the DX line assuming you have
695 SET/DXGRID enabled. This could be a LOT of information though, so
696 it is not recommended on slow links.
698 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
699 This command sends out any information held in the user file which can
700 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
701 and Homenode. PC41s are only sent for the information that is available.
703 === 0^HELP^The HELP Command
704 HELP is available for a number of commands. The syntax is:-
708 Where <cmd> is the name of the command you want help on.
710 All commands can be abbreviated, so SHOW/DX can be abbreviated
711 to SH/DX, ANNOUNCE can be shortened to AN and so on.
713 Look at the APROPOS <string> command which will search the help database
714 for the <string> you specify and give you a list of likely commands
715 to look at with HELP.
717 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
718 This command attempts to re-initialise a link to a (usually) AK1A node
719 that has got confused, usually by a protocol loop of some kind. It may
720 work - but you usually will be better off simply disconnecting it (or
721 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
724 Best of luck - you will need it.
726 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
727 === 0^KILL <from msgno>-<to msgno>^Delete a range of messages
728 === 0^KILL from <regex>^Delete messages FROM a callsign or pattern
729 === 0^KILL to <regex>^Delete messages TO a callsign or pattern
730 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
731 Delete a message from the local system. You will only be able to
732 delete messages that you have originated or been sent (unless you are
737 Will delete all the messages that you own between msgnos 1234 and 1255.
741 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
745 will delete all messages to g1tlh.
749 will delete a message (usually a 'bulletin') from the whole cluster system.
751 This uses the subject field, so any messages that have exactly the
752 same subject will be deleted. Beware!
754 === 6^KILL EXPunge <msgno> [<msgno..]^Expunge a message
755 Deleting a message using the normal KILL commands only marks that message
756 for deletion. The actual deletion only happens later (usually two days later).
758 The KILL EXPUNGE command causes the message to be truly deleted more or less
761 It otherwise is used in the same way as the KILL command.
763 === 0^LINKS^Show which nodes is physically connected
764 This is a quick listing that shows which links are connected and
765 some information about them. See WHO for a list of all connections.
767 === 9^LOAD/ALIASES^Reload the command alias table
768 Reload the /spider/cmd/Aliases file after you have editted it. You
769 will need to do this if you change this file whilst the cluster is
770 running in order for the changes to take effect.
772 === 9^LOAD/BANDS^Reload the band limits table
773 Reload the /spider/data/bands.pl file if you have changed it manually whilst
774 the cluster is running.
776 === 9^LOAD/BADMSG^Reload the bad msg table
777 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
778 the cluster is running. This table contains a number of perl regular
779 expressions which are searched for in the fields targetted of each message.
780 If any of them match then that message is immediately deleted on receipt.
782 === 9^LOAD/BADWORDS^Reload the bad words table
783 Reload the /spider/data/badwords file if you have changed it manually whilst
784 the cluster is running. This file contains a list of words which, if found
785 on certain text portions of PC protocol, will cause those protocol frames
786 to be rejected. It will all put out a message if any of these words are
787 used on the announce, dx and talk commands. The words can be one or
788 more on a line, lines starting with '#' are ignored.
790 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
791 Normally, if you change a command file in the cmd or local_cmd tree it
792 will automatially be picked up by the cluster program. Sometimes it
793 can get confused if you are doing a lot of moving commands about or
794 delete a command in the local_cmd tree and want to use the normal one
795 again. Execute this command to reset everything back to the state it
796 was just after a cluster restart.
798 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
799 Reload the /spider/msg/forward.pl file if you have changed it
800 manually whilst the cluster is running.
802 === 5^LOAD/KEPS^Load new keps data
803 === 5^LOAD/KEPS [nn]^Load new keps data from message
804 If there is no message number then reload the current Keps data from
805 the Keps.pm data file. You create this file by running
807 /spider/perl/convkeps.pl <filename>
809 on a file containing NASA 2 line keps as a message issued by AMSAT.
811 If there is a message number, then it will take the message, run
812 convkeps.pl on it and then load the data, all in one step.
814 These messages are sent to ALL by GB7DJK (and others) from time to time.
816 === 9^LOAD/MESSAGES^Reload the system messages file
817 If you change the /spider/perl/Messages file (usually whilst
818 fiddling/writing new commands) you can have them take effect during a
819 cluster session by executing this command. You need to do this if get
822 unknown message 'xxxx' in lang 'en'
824 === 9^LOAD/PREFIXES^Reload the prefix table
825 Reload the /spider/data/prefix_data.pl file if you have changed it
826 manually whilst the cluster is running.
828 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
829 MERGE allows you to bring your spot and wwv database up to date. By default
830 it will request the last 10 spots and 5 WWVs from the node you select. The
831 node must be connected locally.
833 You can request any number of spots or wwv and although they will be appended
834 to your databases they will not duplicate any that have recently been added
835 (the last 2 days for spots and last month for WWV data).
837 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
838 Alter message parameters like To, From, Subject, whether private or bulletin
839 or return receipt (RR) is required or whether to keep this message from timing
842 MSG TO <msgno> <call> - change TO callsign to <call>
843 MSG FRom <msgno> <call> - change FROM callsign to <call>
844 MSG PRrivate <msgno> - set private flag
845 MSG NOPRrivate <msgno> - unset private flag
846 MSG RR <msgno> - set RR flag
847 MSG NORR <msgno> - unset RR flag
848 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
849 MSG NOKEep <msgno> - unset the keep flag
850 MSG SUbject <msgno> <new> - change the subject to <new>
851 MSG WAittime <msgno> - remove any waitting time for this message
852 MSG NOREad <msgno> - mark message as unread
853 MSG REad <msgno> - mark message as read
854 MSG QUeue - queue any outstanding bulletins
855 MSG QUeue 1 - queue any outstanding private messages
857 You can look at the status of a message by using:-
861 This will display more information on the message than DIR does.
863 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
864 Send some arbitrary text to a locally connected callsign. No
865 processing is done on the text. This command allows you to send PC
866 Protocol to unstick things if problems arise (messages get stuck
869 pc gb7djk PC33^GB7TLH^GB7DJK^400^
871 pc G1TLH Try doing that properly!!!
873 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
874 You can get rid of any message to or originating from your callsign using
875 this command. You can remove more than one message at a time.
877 === 5^KILL <from>-<to>^Remove a range of messages from the system
878 === 5^KILL FROM <call>^Remove all messages from a callsign
879 === 5^KILL TO <call>^Remove all messages to a callsign
880 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
881 Remove this message from the entire cluster system as well as your node.
884 As a sysop you can kill any message on the system.
886 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
887 Send any text you like to the callsign requested. This is used mainly to send
888 PC protocol to connected nodes either for testing or to unstick things.
890 You can also use in the same way as a talk command to a connected user but
891 without any processing, added of "from <blah> to <blah" or whatever.
893 === 1^PING <node call>^Check the link quality between nodes
894 This command allows you to send a frame to another cluster node on
895 the network and get a return frame. The time it takes to do this
896 is a good indication of the quality of the link. The actual time
897 it takes is output to the console in seconds.
898 Any visible cluster node can be PINGed.
900 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
901 This command allows you to send nearly any command to another DX Cluster
902 node that is connected to the system.
904 Whether you get any output is dependant on a) whether the other system knows
905 that the node callsign of this cluster is in fact a node b) whether the
906 other system is allowing RCMDs from this node and c) whether you have
907 permission to send this command at all.
909 === 0^READ^Read the next unread personal message addressed to you
910 === 0^READ <msgno>^Read the specified message
911 You can read any messages that are sent as 'non-personal' and also any
912 message either sent by or sent to your callsign.
915 As a sysop you may read any message on the system
917 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
918 Create an 'reject this announce' line for a filter.
920 A reject filter line means that if the announce matches this filter it is
921 passed onto the user. See HELP FILTERING for more info. Please read this
922 to understand how filters work - it will save a lot of grief later on.
924 You can use any of the following things in this line:-
926 info <string> eg: iota or qsl
927 by <prefixes> eg: G,M,2
929 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
930 origin_itu <prefixes or numbers> or: G,GM,GW
931 origin_zone <prefixes or numbers>
932 by_dxcc <prefixes or numbers>
933 by_itu <prefixes or numbers>
934 by_zone <prefixes or numbers>
936 wx 1 filter WX announces
937 dest <prefixes> eg: 6MUK,WDX (distros)
941 rej/ann by_zone 14,15,16 and not by G,M,2
943 You can use the tag 'all' to reject everything eg:
947 but this probably for advanced users...
949 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
950 This version allows a sysop to set a filter for a callsign as well as the
951 default for nodes and users eg:-
954 reject/ann input node_default by G,M,2
955 reject/ann user_default by G,M,2
957 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
958 Create a 'reject this spot' line for a filter.
960 A reject filter line means that if the spot matches this filter it is
961 dumped (not passed on). See HELP FILTERING for more info. Please read this
962 to understand how filters work - it will save a lot of grief later on.
964 You can use any of the following things in this line:-
966 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
967 on <range> same as 'freq'
968 call <prefixes> eg: G,PA,HB9
969 info <string> eg: iota or qsl
971 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
972 call_itu <prefixes or numbers> or: G,GM,GW
973 call_zone <prefixes or numbers>
974 by_dxcc <prefixes or numbers>
975 by_itu <prefixes or numbers>
976 by_zone <prefixes or numbers>
980 For frequencies, you can use any of the band names defined in
981 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
982 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
983 this is more efficient than saying simply: on HF (but don't get
984 too hung up about that)
989 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
991 You can use the tag 'all' to reject everything eg:
995 but this probably for advanced users...
997 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
998 Create an 'reject this routing PC Protocol' line for a filter.
1000 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1001 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
1002 read this to understand how filters work - it will save a lot of grief later on.
1004 You can use any of the following things in this line:-
1006 call <prefixes> the callsign of the thingy
1007 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1008 call_itu <prefixes or numbers> or: G,GM,GW
1009 call_zone <prefixes or numbers>
1010 origin <prefixes> really the interface it came in on
1011 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1012 origin_itu <prefixes or numbers> or: G,GM,GW
1013 origin_zone <prefixes or numbers>
1017 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
1019 You can use the tag 'all' to reject everything eg:
1021 rej/route all (equiv to [very] restricted mode)
1023 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
1024 This version allows a sysop to set a filter for a callsign as well as the
1025 default for nodes and users eg:-
1027 reject/spot db0sue-7 1 by_zone 14,15,16
1028 reject/spot node_default all
1029 set/hops node_default 10
1031 reject/spot user_default by G,M,2
1033 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
1034 It is unlikely that you will want to do this, but if you do then you can
1035 filter on the following fields:-
1037 by <prefixes> eg: G,M,2
1039 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1040 origin_itu <prefixes or numbers> or: G,GM,GW
1041 origin_zone <prefixes or numbers>
1042 by_dxcc <prefixes or numbers>
1043 by_itu <prefixes or numbers>
1044 by_zone <prefixes or numbers>
1047 There are no examples because WCY Broadcasts only come from one place and
1048 you either want them or not (see UNSET/WCY if you don't want them).
1050 This command is really provided for future use.
1052 See HELP FILTER for information.
1054 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
1055 This version allows a sysop to set a filter for a callsign as well as the
1056 default for nodes and users eg:-
1058 reject/wcy gb7djk all
1060 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
1061 It is unlikely that you will want to do this, but if you do then you can
1062 filter on the following fields:-
1064 by <prefixes> eg: G,M,2
1066 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1067 origin_itu <prefixes or numbers> or: G,GM,GW
1068 origin_zone <prefixes or numbers>
1069 by_dxcc <prefixes or numbers>
1070 by_itu <prefixes or numbers>
1071 by_zone <prefixes or numbers>
1076 reject/wwv by_zone 14,15,16
1078 is probably the only useful thing to do (which will only show WWV broadcasts
1079 by stations in the US).
1081 See HELP FILTER for information.
1083 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
1084 This version allows a sysop to set a filter for a callsign as well as the
1085 default for nodes and users eg:-
1087 reject/wwv db0sue-7 1 by_zone 4
1088 reject/wwv node_default all
1090 reject/wwv user_default by W
1092 === 0^REPLY^Reply (privately) to the last message that you have read
1093 === 0^REPLY <msgno>^Reply (privately) to the specified message
1094 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
1095 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
1096 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
1097 You can reply to a message and the subject will automatically have
1098 "Re:" inserted in front of it, if it isn't already present.
1100 You can also use all the extra qualifiers such as RR, PRIVATE,
1101 NOPRIVATE, B that you can use with the SEND command (see SEND
1102 for further details)
1104 === 9^SAVE [-d -t -a] <filename> "<cmd>" [...]^Save command output to a file
1105 This sysop only cammand allows you to save the output of one or more
1106 commands to a file. For example:-
1108 save /spider/packclus/dxstats show/dxstat
1110 will save the output of the normal command "show/dxstat" to the file
1111 "dxstats" in the files area.
1113 You can have some extra flags to the save which will either
1114 date stamp or time stamp or both the filename so:-
1116 save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
1117 save -t /tmp/a <cmd> creates /tmp/a_2301Z
1118 save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
1120 The -a flag means append to the file instead of overwriting it.
1122 You can have more than one command on the line, to do this you MUST
1123 enclose each command in double quotes (") eg:-
1125 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
1129 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
1131 You can only write into places that the cluster has permission for (which
1132 is that of the "sysop" user [which had BETTER NOT BE "root"]), you will
1133 need to create any directories you want to put stuff in beforehand as well.
1135 It is likely that you will want to run these commands in a crontab type
1136 situation. You would do that something like:-
1138 0 0 * * * run_cmd('save /tmp/dxstats echo "DXStat Table", "sh/dxstats"')
1140 Note that you still enclose each command with (") characters but you must
1141 enclose the entire save command in (') characters.
1143 Now in fact, this can be varied if you know what you are doing. See the
1144 admin manual for more details.
1146 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
1147 === 0^SEND RR <call>^Send a message and ask for a read receipt
1148 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
1149 === 0^SEND PRIVATE <call>^Send a personal message
1150 === 0^SEND NOPRIVATE <call>^Send a message to all stations
1151 All the SEND commands will create a message which will be sent either to
1152 an individual callsign or to one of the 'bulletin' addresses.
1154 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1155 it will mark the message as personal and send it to the cluster node that
1156 that callsign is connected to. If the <call> you have specified is in fact
1157 a known bulletin category on your node (eg: ALL) then the message should
1158 automatically become a bulletin.
1160 You can have more than one callsign in all of the SEND commands.
1162 You can have multiple qualifiers so that you can have for example:-
1164 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1166 which should send a copy of message 123 to G1TLH and G0RDI and you will
1167 receive a read receipt when they have read the message.
1169 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1170 SP is an alias for SEND PRIVATE
1172 The system will ask you for a subject. Conventionally this should be
1173 no longer than 29 characters for compatibility. Most modern cluster
1174 software should accept more.
1176 You will now be prompted to start entering your text.
1178 You finish the message by entering '/EX' on a new line. For instance:
1185 If you have started a message and you don't want to keep it then you
1186 can abandon the message with '/ABORT' on a new line, like:-
1190 oh I just can't be bothered with this
1193 If you abort the message it will NOT be sent.
1195 When you are entering the text of your message, most normal output (such
1196 as DX announcements and so on are suppressed and stored for latter display
1197 (upto 20 such lines are stored, as new ones come along, so the oldest
1200 Also, you can enter normal commands commands (and get the output
1201 immediately) whilst in the middle of a message. You do this by typing
1202 the command preceeded by a '/' character on a new line, so:-
1204 /dx g1tlh 144010 strong signal
1206 Will issue a dx annoucement to the rest of the cluster.
1208 Also, you can add the output of a command to your message by preceeding
1209 the command with '//', thus :-
1213 This will show YOU the output from SH/VHFTABLE and also store it in the
1216 You can carry on with the message until you are ready to send it.
1217 === 0^SET/ADDRESS <your address>^Record your postal address
1219 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
1220 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
1222 === 0^SET/ANNTALK^Allow talk like announce messages on your terminal
1223 === 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal
1224 The announce system on legacy cluster nodes is used as a talk
1225 substitute because the network is so poorly connected. If you:
1229 you will suppress several of these announces, you may miss the odd
1230 useful one as well, but you would probably miss them anyway in the
1231 welter of useless ones.
1235 allows you to see them again. This is the default.
1237 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
1239 === 8^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
1240 === 8^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
1241 Setting a word as 'baddx' will prevent spots with that word in the
1242 'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
1243 further. They will not be displayed and they will not be sent onto
1246 The word must be written in full, no wild cards are allowed eg:-
1248 set/baddx FORSALE VIDEO FR0G
1250 To allow a word again, use the following command ...
1254 === 8^SET/BADNODE <call>..^Stop spots from this node being propagated
1255 === 8^UNSET/BADNODE <call>..^Allow spots from this node again
1256 Setting a callsign as a 'badnode' will prevent spots from that node
1257 going any further. They will not be displayed and they will not be
1258 sent onto other nodes.
1260 The call must be a full eg:-
1264 will stop anything from K1TTT. If you want SSIDs as well then you must
1265 enter them specifically.
1269 will allow spots from him again.
1271 Use with extreme care. This command may well be superceeded by FILTERing.
1273 === 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1274 === 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1275 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1276 going any further. They will not be displayed and they will not be
1277 sent onto other nodes.
1279 The call must be written in full, no wild cards are allowed eg:-
1281 set/badspotter VE2STN
1283 will stop anything from VE2STN. If you want SSIDs as well then you must
1284 enter them specifically.
1286 unset/badspotter VE2STN
1288 will allow spots from him again.
1290 Use with extreme care. This command may well be superceded by FILTERing.
1292 === 8^SET/BADWORD <word>..^Stop things with this word being propagated
1293 === 8^UNSET/BADWORD <word>..^Propagate things with this word again
1294 Setting a word as a 'badword' will prevent things like spots,
1295 announces or talks with this word in the the text part from going any
1296 further. They will not be displayed and they will not be sent onto
1299 The word must be written in full, no wild cards are allowed eg:-
1301 set/badword annihilate annihilated annihilation
1303 will stop anything with these words in the text.
1305 unset/badword annihilated
1307 will allow text with this word again.
1309 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1310 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1312 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1314 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1316 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1317 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1318 You can choose to log several different levels. The levels are
1326 You can show what levels you are logging with SHOW/DEBUG
1328 === 0^SET/DX^Allow DX messages to come out on your terminal
1329 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1331 === 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements
1332 === 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements
1333 A standard feature which is enabled in version 1.43 and above is
1334 that if the spotter's grid square is known it is output on the end
1335 of a DX announcement (there is just enough room). Some user programs
1336 cannot cope with this. You can use this command to reset (or set)
1339 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1341 === 0^SET/ECHO^Make the cluster echo your input
1342 === 0^UNSET/ECHO^Stop the cluster echoing your input
1343 If you are connected via a telnet session, different implimentations
1344 of telnet handle echo differently depending on whether you are
1345 connected via port 23 or some other port. You can use this command
1346 to change the setting appropriately.
1348 The setting is stored in your user profile.
1350 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1352 === 0^SET/EMAIL <email> ...^Set email address(es) and forward your personals
1353 === 0^UNSET/EMAIL^Stop personal msgs being forwarded by email
1354 If any personal messages come in for your callsign then you can use
1355 these commands to control whether they are forwarded onto your email
1356 address. To enable the forwarding do something like:-
1358 SET/EMAIL mike.tubby@somewhere.com
1360 You can have more than one email address (each one separated by a space).
1361 Emails are forwarded to all the email addresses you specify.
1363 You can disable forwarding by:-
1367 === 0^SET/HERE^Tell the system you are present at your terminal
1368 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1370 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1371 Tell the cluster system where you normally connect to. Any Messages sent
1372 to you will normally find their way there should you not be connected.
1376 === 8^SET/HOPS <call> ann|spots|route|wwv|wcy <n>^Set hop count
1377 === 8^UNSET/HOPS <call> ann|spots|route|wwv|wcy^Unset hop count
1378 Set the hop count for a particular type of broadcast for a node.
1380 This command allows you to set up special hop counts for a node
1381 for currently: announce, spots, wwv and wcy broadcasts.
1384 set/hops gb7djk ann 10
1385 set/hops gb7mbc spots 20
1387 Set SHOW/HOPS for information on what is already set. This command
1388 creates a filter and works in conjunction with the filter system.
1390 You can unset the hops with command UNSET/HOPS. For example:-
1392 unset/hops gb7djk ann
1393 unset/hops gb7mbc spots
1396 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1397 Connect a node to your system in such a way that you are a full protocol
1398 member of its network and can see all spots on it, but nothing either leaks
1399 out from it nor goes back into from the rest of the nodes connected to you.
1401 You can potentially connect several nodes in this way.
1403 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1404 Remove isolation from a node - SET/ISOLATE
1406 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1407 You can select the language that you want the cluster to use. Currently
1408 the languages available are en (English), de (German), es (Spanish)
1411 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1412 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1413 In order to get accurate headings and such like you must tell the system
1414 what your latitude and longitude is. If you have not yet done a SET/QRA
1415 then this command will set your QRA locator for you. For example:-
1416 SET/LOCATION 52 22 N 0 57 E
1418 === 0^SET/LOGININFO^Inform when a station logs in locally
1419 === 0^UNSET/LOGININFO^Inform when a station logs out locally
1421 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1422 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1424 === 0^SET/NAME <your name>^Set your name
1425 Tell the system what your name is eg:-
1428 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1429 Tell the system that the call(s) are to be treated as AK1A cluster and
1430 fed PC Protocol rather normal user commands.
1432 === 8^SET/OBSCOUNT <count> <nodecall>^Set the 'pump-up' obscelence counter
1433 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1434 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1435 counter which is decremented on every outgoing ping and then reset to
1436 the 'obscount' value on every incoming ping. The default value of this
1439 What this means is that a neighbouring node will be pinged twice at
1440 (default) 300 second intervals and if no reply has been heard just before
1441 what would be the third attempt, that node is disconnected.
1443 If a ping is heard then the obscount is reset to the full value. Using
1444 default values, if a node has not responded to a ping within 15 minutes,
1447 You can set this parameter between 1 and 9.
1449 It is STRONGLY recommended that you don't change the default.
1451 === 0^SET/PAGE <lines per page>^Set the lines per page
1452 Tell the system how many lines you wish on a page when the number of line
1453 of output from a command is more than this. The default is 20. Setting it
1454 explicitly to 0 will disable paging.
1458 The setting is stored in your user profile.
1460 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1461 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1462 in order to determine the rolling quality of the link and, in future, to
1463 affect routing decisions. The default interval is 300 secs or 5 minutes.
1465 You can use this command to set a different interval. Please don't.
1467 But if you do the value you enter is treated as minutes up 30 and seconds
1468 for numbers greater than that.
1470 This is used also to help determine when a link is down at the far end
1471 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1472 for more information.
1474 If you must change it (and it may be useful for internet connected nodes
1475 on dynamic IP addresses that go away after a set time of usage) the time
1476 can be specified as:-
1478 5 which if less than 30 is converted to minutes otherwise is
1479 taken as the no of seconds between pings.
1484 Please be aware that this causes traffic to occur on the link, setting
1485 this value too low may annoy your neighbours beyond the point of
1488 You can switch this off by setting it to 0.
1490 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1491 Set the privilege level on a callsign. The privilege levels that pertain
1492 to commands are as default:-
1494 1 - allow remote nodes normal user RCMDs
1495 5 - various privileged commands (including shutdown, but not disc-
1496 connect), the normal level for another node.
1497 8 - more privileged commands (including disconnect)
1498 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1500 If you are a sysop and you come in as a normal user on a remote connection
1501 your privilege will automatically be set to 0.
1503 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1504 You can use this command to 'protect' this session from unauthorised
1505 use. If you want to get your normal privilege back you will need to
1506 either logout and login again (if you are on a console) or use the
1509 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1510 The password for a user can only be set by a full sysop. The string
1511 can contain any characters.
1513 The way this field is used depends on context. If it is being used in
1514 the SYSOP command context then you are offered 5 random numbers and you
1515 have to supply the corresponding letters. This is now mainly for ax25
1518 If it is being used on incoming telnet connections then, if a password
1521 set/var $main::passwdreq = 1
1523 command is executed in the startup script, then a password prompt is
1524 given after the normal 'login: ' prompt.
1526 === 0^SET/PASSWORD^Set your own password
1527 This command only works for a 'telnet' user (currently). It will
1528 only work if you have a password already set. This initial password
1529 can only be set by the sysop.
1531 When you execute this command it will ask you for your old password,
1532 then ask you to type in your new password twice (to make sure you
1533 get it right). You may or may not see the data echoed on the screen
1534 as you type, depending on the type of telnet client you have.
1536 === 9^UNSET/PASSWORD <call> ...^Delete (remove) a user's password
1537 This command allows the sysop to completely delete and remove a
1538 password for a user.
1540 === 0^SET/PROMPT <string>^Set your prompt to <string>
1541 === 0^UNSET/PROMPT^Set your prompt back to default
1542 This command will set your user prompt to exactly the string that you
1543 say. The point of this command to enable a user to interface to programs
1544 that are looking for a specific prompt (or else you just want a different
1549 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to
1552 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1553 Tell the system that the call(s) are to be treated as DXSpider node and
1554 fed new style DX Protocol rather normal user commands.
1556 === 9^SET/SYS_QRA <locator>^Set your cluster QRA Grid locator
1557 === 0^SET/QRA <locator>^Set your QRA Grid locator
1558 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1559 done a SET/LOCATION then your latitude and longitude will be set roughly
1560 correctly (assuming your locator is correct ;-). For example:-
1563 === 0^SET/QTH <your qth>^Set your QTH
1564 Tell the system where you are. For example:-
1565 SET/QTH East Dereham, Norfolk
1567 === 9^SET/REGISTER <call> ...^Mark a user as registered
1568 === 9^UNSET/REGISTER <call> ...^Mark a user as not registered
1569 Registration is a concept that you can switch on by executing the
1571 set/var $main::regreq = 1
1573 command (usually in your startup file)
1575 If a user is NOT registered then, firstly, instead of the normal
1576 motd file (/spider/data/motd) being sent to the user at startup, the
1577 user is sent the motd_nor file instead. Secondly, the non registered
1578 user only has READ-ONLY access to the node. The non-registered user
1579 cannot use DX, ANN etc.
1581 The only exception to this is that a non-registered user can TALK or
1582 SEND messages to the sysop.
1584 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1585 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1587 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1588 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1590 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1591 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1593 === 0^SET/WX^Allow WX messages to come out on your terminal
1594 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1596 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1597 Display all the bad dx callsigns in the system, see SET/BADDX
1598 for more information.
1600 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1601 Display all the bad node callsigns in the system, see SET/BADNODE
1602 for more information.
1604 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1605 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1606 for more information.
1608 === 1^SHOW/BADWORD^Show all the bad words in the system
1609 Display all the bad words in the system, see SET/BADWORD
1610 for more information.
1612 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
1613 This command allows you to see all the users that can be seen
1614 and the nodes to which they are connected.
1616 This command is normally abbreviated to: sh/c
1618 BE WARNED: the list that is returned can be VERY long
1620 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
1621 Show all the nodes connected to this node.
1623 === 1^SHOW/CONNECT^Show all the active connections
1624 This command shows information on all the active connections known to
1625 the node. This command gives slightly more information than WHO.
1627 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
1628 This is very nearly the same as SHOW/TIME, the only difference the format
1629 of the date string if no arguments are given.
1631 If no prefixes or callsigns are given then this command returns the local
1632 time and UTC as the computer has it right now. If you give some prefixes
1633 then it will show UTC and UTC + the local offset (not including DST) at
1634 the prefixes or callsigns that you specify.
1636 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
1638 === 0^SHOW/DX^Interrogate the spot database
1639 If you just type SHOW/DX you will get the last so many spots
1640 (sysop configurable, but usually 10).
1642 In addition you can add any number of these commands in very nearly
1643 any order to the basic SHOW/DX command, they are:-
1645 on <band> - eg 160m 20m 2m 23cm 6mm
1646 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1647 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
1650 <number> - the number of spots you want
1651 <from>-<to> - <from> spot no <to> spot no in the selected list
1654 <prefix> - for a spotted callsign beginning with <prefix>
1655 *<suffix> - for a spotted callsign ending in <suffix>
1656 *<string>* - for a spotted callsign containing <string>
1658 day <number> - starting <number> days ago
1659 day <from>-<to> - <from> days <to> days ago
1662 info <text> - any spots containing <text> in the info or remarks
1664 by <call> - any spots spotted by <call> (spotter <call> is the
1667 qsl - this automatically looks for any qsl info on the call
1668 held in the spot database.
1670 iota [<iota>] - If the iota island number is missing it will look for
1671 the string iota and anything which looks like an iota
1672 island number. If you specify then it will look for
1675 qra [<locator>] - this will look for the specific locator if you specify
1676 one or else anything that looks like a locator.
1678 dxcc - treat the prefix as a 'country' and look for spots
1679 from that country regardless of actual prefix.
1682 You can also use this with the 'by' keyword so
1688 SH/DX on 20m info iota
1689 SH/DX 9a on vhf day 30
1695 SH/DX dxcc oq2 by w dxcc
1697 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
1698 This command takes the <prefix> (which can be a full or partial
1699 callsign if desired), looks up which internal country number it is
1700 and then displays all the spots as per SH/DX for that country.
1702 This is now an alias for 'SHOW/DX DXCC'
1704 The options for SHOW/DX also apply to this command.
1708 SH/DXCC W on 20m iota
1710 This can be done with the SHOW/DX command like this:-
1713 SH/DX dxcc w on 20m iota
1715 === 0^SHOW/DXSTATS^Show the DX Statistics for last 31 days
1716 Show the total DX spots for the last 31 days
1718 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
1719 SHOW/FILES on its own will show you a list of the various fileareas
1720 available on the system. To see the contents of a particular file
1723 where <filearea> is the name of the filearea you want to see the
1726 You can also use shell globbing characters like '*' and '?' in a
1727 string to see a selection of files in a filearea eg:-
1728 SH/FILES bulletins arld*
1730 See also TYPE - to see the contents of a file.
1732 === 0^SHOW/FILTER^Show the contents of all the filters you have set
1733 Show the contents of all the filters that are set. This command displays
1734 all the filters set - for all the various categories.
1736 === 0^SHOW/HFSTATS^Show the HF DX Statistics for last 31 days
1737 Show the HF DX spots breakdown by band for the last 31 days
1739 === 0^SHOW/HFTABLE^Show the HF DX Spotter Table for your country
1740 Show the HF DX Spotter table for your country for the last 31 days
1742 === 8^SHOW/HOPS <call> [ann|spots|route|wcy|wwv]^Show the hop counts for a node
1743 This command shows the hop counts set up for a node. You can specify
1744 which category you want to see. If you leave the category out then
1745 all the categories will be listed.
1747 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
1749 === 9^SHOW/LOCKOUT <prefix>|ALL^Show the list of locked out or excluded callsigns
1751 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
1752 This command outputs a short section of the system log. On its own
1753 it will output a general logfile. With the optional callsign it will
1754 show output from the log associated with that callsign.
1756 === 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
1757 Show the Moon rise and set times for a (list of) prefixes or callsigns,
1758 together with the azimuth and elevation of the sun currently at those
1761 If you don't specify any prefixes or callsigns, it will show the times for
1762 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1763 together with the current azimuth and elevation.
1765 In addition, it will show the gain or loss dB relative to the nominal
1766 distance of 385,000Km due to the ellipsoidal nature of the orbit.
1768 If all else fails it will show the Moonrise and set times for the node
1769 that you are connected to.
1776 You can also use this command to see into the past or the future, so
1777 if you want to see yesterday's times then do:-
1781 or in three days time:-
1785 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
1786 This command allow you to estimate the likelihood of you contacting
1787 a station with the prefix you have specified. The output assumes a modest
1788 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
1790 The result predicts the most likely operating frequencies and signal
1791 levels for high frequency (shortwave) radio propagation paths on
1792 specified days of the year and hours of the day. It is most useful for
1793 paths between 250 km and 6000 km, but can be used with reduced accuracy
1794 for paths shorter or longer than this.
1796 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1797 used to predict the MUF given the predicted flux, day of the year,
1798 hour of the day and geographic coordinates of the transmitter and
1799 receiver. This routine is reasonably accurate for the purposes here,
1800 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1801 than the programs used by major shortwave broadcasting organizations,
1802 such as the Voice of America.
1804 The command will display some header information detailing its
1805 assumptions, together with the locations, latitude and longitudes and
1806 bearings. It will then show UTC (UT), local time at the other end
1807 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1808 (Zen) and the likely signal strengths. Then for each frequency for which
1809 the system thinks there is a likelihood of a circuit it prints a value.
1811 The value is currently a likely S meter reading based on the conventional
1812 6dB / S point scale. If the value has a '+' appended it means that it is
1813 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1814 there is likely to be much fading and by an 's' that the signal is likely
1817 By default SHOW/MUF will show the next two hours worth of data. You
1818 can specify anything up to 24 hours worth of data by appending the no of
1819 hours required after the prefix. For example:-
1825 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1826 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1827 Location Lat / Long Azim
1828 East Dereham, Norfolk 52 41 N 0 57 E 47
1829 United-States-W 43 0 N 87 54 W 299
1830 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1831 18 23 11.5 -35 mS0+ mS2 S3
1832 19 0 11.2 -41 mS0+ mS2 S3
1834 indicating that you will have weak, fading circuits on top band and
1835 80m but usable signals on 40m (about S3).
1841 will get you the above display, but with the next 24 hours worth of
1847 Gives you an estimate of the long path propagation characterics. It
1848 should be noted that the figures will probably not be very useful, nor
1849 terrible accurate, but it is included for completeness.
1851 === 0^SHOW/NEWCONFIGURATION [<node>]^Show all the nodes and users visible
1852 This command allows you to see all the users that can be seen
1853 and the nodes to which they are connected.
1855 This command produces essentially the same information as
1856 SHOW/CONFIGURATION except that it shows all the duplication of
1857 any routes that might be present It also uses a different format
1858 which may not take up quite as much space if you don't have any
1861 BE WARNED: the list that is returned can be VERY long
1863 === 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally
1864 Show all the nodes connected to this node in the new format.
1866 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
1867 Show the type and version (if connected) of the nodes specified on the
1868 command line. If no callsigns are specified then a sorted list of all
1869 the non-user callsigns known to the system will be displayed.
1871 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
1872 This command takes the <callsign> (which can be a full or partial
1873 callsign or a prefix), looks up which internal country number
1874 it is and then displays all the relevant prefixes for that country
1875 together with the internal country no, the CQ and ITU regions.
1879 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
1880 Show the name and location where every program module was load from. This
1881 is useful for checking where you think you have loaded a .pm file from.
1883 === 0^SHOW/QRA <locator> [<locator>]^Show distance between QRA Grid locators
1884 === 0^SHOW/QRA <lat> <long>^Convert lat/long to a QRA Grid locator
1885 This is a multipurpose command that allows you either to calculate the
1886 distance and bearing between two locators or (if only one locator is
1887 given on the command line) the distance and beraing from your station
1888 to the locator. For example:-
1893 The first example will show the distance and bearing to the locator from
1894 yourself, the second example will calculate the distance and bearing from
1895 the first locator to the second. You can use 4 or 6 character locators.
1897 It is also possible to convert a latitude and longitude to a locator by
1898 using this command with a latitude and longitude as an argument, for
1901 SH/QRA 52 41 N 0 58 E
1903 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
1904 This command queries the QRZ callbook server on the internet
1905 and returns any information available for that callsign. This service
1906 is provided for users of this software by http://www.qrz.com
1908 === 9^SHOW/REGISTERED [<prefix>]^Show the registered users
1910 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
1911 This command allows you to see to which node the callsigns specified are
1912 connected. It is a sort of inverse sh/config.
1916 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
1917 Show the tracking data from your location to the satellite of your choice
1918 from now on for the next few hours.
1920 If you use this command without a satellite name it will display a list
1921 of all the satellites known currently to the system.
1923 If you give a name then you can obtain tracking data of all the passes
1924 that start and finish 5 degrees below the horizon. As default it will
1925 give information for the next three hours for every five minute period.
1927 You can alter the number of hours and the step size, within certain
1930 Each pass in a period is separated with a row of '-----' characters
1935 SH/SAT FENGYUN1 12 2
1937 === 6^SHOW/STATION ALL [<regex>]^Show list of users in the system
1938 === 0^SHOW/STATION [<callsign> ..]^Show information about a callsign
1939 Show the information known about a callsign and whether (and where)
1940 that callsign is connected to the cluster.
1944 If no callsign is given then show the information for yourself.
1946 === 0^SHOW/SUN [+/- days][<prefix>|<callsign>]^Show sun rise and set times
1947 Show the sun rise and set times for a (list of) prefixes or callsigns,
1948 together with the azimuth and elevation of the sun currently at those
1951 If you don't specify any prefixes or callsigns, it will show the times for
1952 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1953 together with the current azimuth and elevation.
1955 If all else fails it will show the sunrise and set times for the node
1956 that you are connected to.
1961 SH/SUN G1TLH K9CW ZS
1963 You can also use this command to see into the past or the future, so
1964 if you want to see yesterday's times then do:-
1968 or in three days time:-
1972 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
1973 If no prefixes or callsigns are given then this command returns the local
1974 time and UTC as the computer has it right now. If you give some prefixes
1975 then it will show UTC and UTC + the local offset (not including DST) at
1976 the prefixes or callsigns that you specify.
1978 === 0^SHOW/VHFSTATS^Show the VHF DX Statistics for last 31 days
1979 Show the VHF DX spots breakdown by band for the last 31 days
1981 === 0^SHOW/VHFTABLE^Show the VHF DX Spotter Table for your country
1982 Show the VHF DX Spotter table for your country for the last 31 days
1984 === 0^SHOW/WCY^Show last 10 WCY broadcasts
1985 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
1986 Display the most recent WCY information that has been received by the system
1988 === 0^SHOW/WWV^Show last 10 WWV broadcasts
1989 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
1990 Display the most recent WWV information that has been received by the system
1992 === 5^SHUTDOWN^Shutdown the cluster
1993 Shutdown the cluster and disconnect all the users
1995 === 9^SPOOF <call> <command>^Do a command as though you are another user
1996 This command is provided so that sysops can set a user's parameters without
1997 me having to write a special 'sysop' version for every user command. It
1998 allows you to pretend that you are doing the command as the user you specify.
2002 SPOOF G1TLH set/name Dirk
2003 SPOOF G1TLH set/qra JO02LQ
2005 === 5^STAT/DB <dbname>^Show the status of a database
2006 Show the internal status of a database descriptor.
2008 Depending on your privilege level you will see more or less information.
2009 This command is unlikely to be of much use to anyone other than a sysop.
2011 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
2012 Show the internal status of the channel object either for the channel that
2013 you are on or else for the callsign that you asked for.
2015 Only the fields that are defined (in perl term) will be displayed.
2017 === 1^STAT/MSG^Show the status of the message system
2018 === 1^STAT/MSG <msgno>^Show the status of a message
2019 This command shows the internal status of a message and includes information
2020 such as to whom it has been forwarded, its size, origin etc etc.
2022 If no message number is given then the status of the message system is
2025 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
2026 === 5^STAT/ROUTE_NODE all^Show list of all Route::Node objects
2028 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
2029 === 5^STAT/ROUTE_USER all^Show list of all Route::User objects
2031 === 5^STAT/USER [<callsign>]^Show the full status of a user
2032 Shows the full contents of a user record including all the secret flags
2035 Only the fields that are defined (in perl term) will be displayed.
2037 === 0^SYSOP^Regain your privileges if you login remotely
2038 The system automatically reduces your privilege level to that of a
2039 normal user if you login in remotely. This command allows you to
2040 regain your normal privilege level. It uses the normal system: five
2041 numbers are returned that are indexes into the character array that is
2042 your assigned password (see SET/PASSWORD). The indexes start from
2045 You are expected to return a string which contains the characters
2046 required in the correct order. You may intersperse those characters
2047 with others to obscure your reply for any watchers. For example (and
2048 these values are for explanation :-):
2050 password = 012345678901234567890123456789
2054 aa2bbbb0ccc5ddd7xxx3n
2058 They will all match. If there is no password you will still be offered
2059 numbers but nothing will happen when you input a string. Any match is
2062 === 0^TALK <call> [<text>]^Send a text message to another station
2063 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
2064 Send a short message to any other station that is visible on the cluster
2065 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2066 command, they don't have to be connected locally.
2068 The second form of TALK is used when other cluster nodes are connected
2069 with restricted information. This usually means that they don't send
2070 the user information usually associated with logging on and off the cluster.
2072 If you know that G3JNB is likely to be present on GB7TLH, but you can only
2073 see GB7TLH in the SH/C list but with no users, then you would use the
2074 second form of the talk message.
2076 If you want to have a ragchew with someone you can leave the text message
2077 out and the system will go into 'Talk' mode. What this means is that a
2078 short message is sent to the recipient telling them that you are in a
2079 'Talking' frame of mind and then you just type - everything you send will
2080 go to the station that you asked for.
2082 All the usual announcements, spots and so on will still come out on your
2085 If you want to do something (such as send a spot) you preceed the normal
2086 command with a '/' character, eg:-
2088 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2091 To leave talk mode type:
2095 If you are in 'Talk' mode, there is an extention to the '/' command which
2096 allows you to send the output to all the people you are talking to. You do
2097 with the '//' command. For example:-
2101 will send the hftable as you have it to all the people you are currently
2104 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
2105 Type out the contents of a file in a filearea. So, for example, in
2106 filearea 'bulletins' you want to look at file 'arld051' you would
2108 TYPE bulletins/arld051
2110 See also SHOW/FILES to see what fileareas are available and a
2113 === 0^WHO^Show who is physically connected
2114 This is a quick listing that shows which callsigns are connected and
2115 what sort of connection they have
2117 === 0^WX <text>^Send a weather message to local users
2118 === 0^WX FULL <text>^Send a weather message to all cluster users
2119 === 5^WX SYSOP <text>^Send a weather message to other clusters only
2120 Weather messages can sometimes be useful if you are experiencing an extreme
2121 that may indicate enhanced conditions