1 The DXSpider Installation and Administration Manual
2 Ian Maude, G0VGS, (ianmaude@btinternet.com)
3 Version 1.34 (Revision 1.01) April 2001
5 A reference for SysOps of the DXSpider DXCluster program.
6 ______________________________________________________________________
67 1. Installation (Original version by Iain Philipps, G0RDI)
71 1.3 Installing the software
72 1.4 Setting callsigns etc
73 1.5 Starting up for the first time
74 1.6 The Client program
76 2. Quick installation guide
80 3.1 Allowing ax25 connects from users
81 3.2 Allowing telnet connects from users
82 3.3 Setting up node connects
83 3.4 Connection scripts
84 3.5 Starting the connection
89 4.1 Autostarting the cluster
95 5.2 Isolating networks
97 6. Filtering (Old Style upto v1.44)
103 7. Filtering (New Style v1.45 and later)
105 7.1 General filter rules
109 7.5 Advanced filtering
114 8.2 Filtering DX callouts (Depricated)
115 8.3 Filtering words from text fields in Announce, Talk and DX spots
125 9.7 Distribution lists
130 10.1 Creating databases
131 10.2 Importing databases
132 10.3 Checking available databases
133 10.4 Looking up databases
134 10.5 Removing databases
136 11. Information, files and useful programs
139 11.2 Downtime message
140 11.3 Other text messages
141 11.4 The Aliases file
143 11.6 Updating kepler data
144 11.7 The QRZ callbook
148 13. The DXSpider command set
150 13.1 accept/announce (0)
151 13.2 accept/announce (extended for sysops) (8)
152 13.3 accept/spots (0)
153 13.4 accept/spots (extended for sysops) (8)
155 13.6 accept/wcy (extended for sysops) (8)
157 13.8 accept/wwv (extended for sysops) (8)
159 13.10 announce full (0)
160 13.11 announce sysop (5)
164 13.15 clear/spots (0)
173 13.24 directory (extended for sysops) (5)
177 13.28 export_users (9)
178 13.29 forward/latlong (8)
179 13.30 forward/opername (1)
186 13.37 load/aliases (9)
188 13.39 load/badmsg (9)
189 13.40 load/badwords (9)
191 13.42 load/cmd_cache (9)
192 13.43 load/forward (9)
193 13.44 load/messages (9)
194 13.45 load/prefixes (9)
201 13.52 read (extended for sysops) (5)
202 13.53 reject/announce
203 13.54 reject/announce (extended for sysops) (8)
204 13.55 reject/spots (0)
205 13.56 reject/spots (extended for sysops) (8)
207 13.58 reject/wcy (extended for sysops) (8)
209 13.60 reject/wwv (extended for sysops) (8)
212 13.63 set/address (0)
213 13.64 set/announce (0)
214 13.65 set/arcluster (5)
216 13.67 set/badnode (6)
217 13.68 set/badspotter (8)
226 13.77 set/homenode (0)
228 13.79 set/isolate (9)
229 13.80 set/language (0)
230 13.81 set/location (0)
231 13.82 set/sys_location (9)
232 13.83 set/logininfo (0)
233 13.84 set/lockout (9)
236 13.87 set/obscount (9)
238 13.89 set/password (9)
239 13.90 set/pinginterval (9)
240 13.91 set/privilege (9)
242 13.93 set/sys_qra (9)
249 13.100 show/baddx (1)
250 13.101 show/badnode (6)
251 13.102 show/badspotter (1)
253 13.104 show/debug (9)
256 13.107 show/files (0)
257 13.108 show/filter (0)
258 13.109 show/filter (extended for sysops) (5)
260 13.111 show/isolate (1)
261 13.112 show/lockout (9)
266 13.117 show/prefix (0)
267 13.118 show/program (5)
270 13.121 show/route (0)
271 13.122 show/satellite (0)
279 13.130 stat/channel (5)
287 13.138 wx (enhanced for sysops) (5)
290 ______________________________________________________________________
292 1
\b1.
\b. I
\bIn
\bns
\bst
\bta
\bal
\bll
\bla
\bat
\bti
\bio
\bon
\bn (
\b(O
\bOr
\bri
\big
\bgi
\bin
\bna
\bal
\bl v
\bve
\ber
\brs
\bsi
\bio
\bon
\bn b
\bby
\by I
\bIa
\bai
\bin
\bn P
\bPh
\bhi
\bil
\bli
\bip
\bpp
\bps
\bs,
\b, G
\bG0
\b0R
\bRD
\bDI
\bI)
\b)
294 1
\b1.
\b.1
\b1.
\b. I
\bIn
\bnt
\btr
\bro
\bod
\bdu
\buc
\bct
\bti
\bio
\bon
\bn
296 This section describes the installation of DX Spider v1.46 on a RedHat
297 Linux Distribution. Wherever possible I will try to include
298 differences for other distributions. I do not intend to try and cover
299 the installation of Linux or the setup of the AX25 utilities. If you
300 need help on this then read Iains original installation guide that
301 comes with the Spider distribution.
304 I am assuming a general knowledge of Linux and its commands. You
305 should know how to use _
\bt_
\ba_
\br and how to edit files using your favourite
309 The crucial ingredient for all of this is Perl. Earlier versions of
310 Spider required perl 5.004, however it is now _
\bS_
\bT_
\bR_
\bO_
\bN_
\bG_
\bL_
\bY recommended
311 that you use at least version 5.005_03 as this is the version being
312 used in the development of Spider.
315 In addition to the standard Red Hat distribution you will require the
316 following modules from http://www.cpan.org/CPAN.html ...
322 +
\bo Data-Dumper-2.10.tar.gz
324 +
\bo TimeDate-1.08.tar.gz
328 +
\bo Net-Telnet-3.02.tar.gz
331 +
\bo Curses-1.05.tar.gz
333 +
\bo Time-HiRes-01.20.tar.gz
337 _
\bD_
\bo get the latest versions of these packages and install them but use
338 the above list as the earliest versions usable.
341 1
\b1.
\b.2
\b2.
\b. P
\bPr
\bre
\bep
\bpa
\bar
\bra
\bat
\bti
\bio
\bon
\bn
343 I will assume that you have already downloaded the latest tarball of
344 the DXSpider software and are ready to install it. I am assuming
345 version 1.46 for this section but of course you would use the latest
349 Login as root and create a user to run the cluster under. _
\bU_
\bN_
\bD_
\bE_
\bR _
\bN_
\bO
350 _
\bC_
\bI_
\bR_
\bC_
\bU_
\bM_
\bS_
\bT_
\bA_
\bN_
\bC_
\bE_
\bS _
\bU_
\bS_
\bE _
\bR_
\bO_
\bO_
\bT _
\bA_
\bS _
\bT_
\bH_
\bI_
\bS _
\bU_
\bS_
\bE_
\bR_
\b!. I am going to use the name
351 _
\bs_
\by_
\bs_
\bo_
\bp. You can call it anything you wish. Depending on your security
352 requirements you may wish to use an existing user, however this is
364 Now set a password for the user ...
370 # Retype new UNIX password:
371 passwd: all authentication tokens updated successfully
377 1
\b1.
\b.3
\b3.
\b. I
\bIn
\bns
\bst
\bta
\bal
\bll
\bli
\bin
\bng
\bg t
\bth
\bhe
\be s
\bso
\bof
\bft
\btw
\bwa
\bar
\bre
\be
379 Now to unpack the DX Spider distribution, set symbolic links and group
380 permissions. Copy the tarball to /home/sysop and do the following.
385 # tar xvfz spider-1.46.tar.gz
386 # ln -s ~sysop/spider /spider
387 # groupadd -g 251 spider (or another number)
392 If you do not have the command _
\bg_
\br_
\bo_
\bu_
\bp_
\ba_
\bd_
\bd available to you simply add a
393 line in /etc/group by hand.
397 # vi /etc/group (or your favorite editor)
402 You also need to add some others to the group, including your own
403 callsign (this will be used as an alias) and root. The finished line
404 in /etc/group should look something like this
406 spider:x:251:sysop,g0vgs,root
409 The next step is to set the permissions on the Spider directory tree
414 # chown -R sysop.spider spider
415 # find . -type d -exec chmod 2775 {} \;
416 # find . -type f -exec chmod 775 {} \;
422 This last step allows various users of the group _
\bs_
\bp_
\bi_
\bd_
\be_
\br to have write
423 access to all the directories. This is not really needed just yet but
424 will be useful when web interfaces start to appear.
427 Finally, you need to fix the permissions on the ax25_call and
428 netrom_call programs. Check where they are with the _
\bl_
\bo_
\bc_
\ba_
\bt_
\be command
429 and alter the permissions with the _
\bc_
\bh_
\bm_
\bo_
\bd command like this ..
433 # chown root ax25_call netrom_call
434 # chmod 4775 ax25_call netrom_call
440 1
\b1.
\b.4
\b4.
\b. S
\bSe
\bet
\btt
\bti
\bin
\bng
\bg c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bns
\bs e
\bet
\btc
\bc
442 Now login to your machine as the user you created earlier. In my case
443 that user is called _
\bs_
\by_
\bs_
\bo_
\bp. Once logged in, issue the following
451 $ cp perl/DXVars.pm.issue local/DXVars.pm
453 $ vi DXVars.pm (or your favourite editor)
459 Using the distributed DXVars.pm as a a template, set your cluster
460 callsign, sysop callsign and other user info to suit your own
461 environment. Note that this a perl file which will be parsed and
462 executed as part of the cluster. If you get it wrong then perl will
463 complain when you start the cluster process. It is important only to
464 alter the text of any section. Some of the lines look a little odd.
465 Take this line for example ....
467 $myemail = "ianmaude\@btinternet.com";
470 There appears to be an extra slash in there. However this has to be
471 there for the file to work so leave it in.
474 P
\bPL
\bLE
\bEA
\bAS
\bSE
\bE U
\bUS
\bSE
\bE C
\bCA
\bAP
\bPI
\bIT
\bTA
\bAL
\bL L
\bLE
\bET
\bTT
\bTE
\bER
\bRS
\bS F
\bFO
\bOR
\bR C
\bCA
\bAL
\bLL
\bLS
\bSI
\bIG
\bGN
\bNS
\bS
477 DON'T alter any file in /spider/perl, they are overwritten with every
478 release. Any files or commands you place in /spider/local or
479 /spider/local_cmd will automagically be used in preference to the ones
480 in /spider/perl EVEN while the cluster is running!
483 Save the new file and change directory to ../perl ....
493 Now type the following command which creates the basic user file with
504 1
\b1.
\b.5
\b5.
\b. S
\bSt
\bta
\bar
\brt
\bti
\bin
\bng
\bg u
\bup
\bp f
\bfo
\bor
\br t
\bth
\bhe
\be f
\bfi
\bir
\brs
\bst
\bt t
\bti
\bim
\bme
\be
506 We can now bring spider up for the first time and see if all is well
507 or not! It should look something like this ...
512 DXSpider DX Cluster Version 1.46
513 Copyright (c) 1998 Dirk Koopman G1TLH
515 loading band data ...
516 loading user file system ...
517 starting listener ...
518 reading existing message headers
520 orft we jolly well go ...
526 If all is well then login on another term or console as _
\bs_
\by_
\bs_
\bo_
\bp and cd
527 to /spider/src. Now issue the following command ...
535 This should log you into the cluster as the sysop under the alias
536 callsign we set earlier. In this case the callsign is G0VGS. The
537 cluster callsign is set in the DXVars.pm file in /spider/local. In
538 this case we will assume that this was set as GB7MBC. You should
539 therefore see this when you login ....
543 G0VGS de GB7MBC 19-Nov-1999 2150Z >
548 If you do, congratulations! If not, look over the instructions again,
549 you have probably missed something out. You can shut spider down
550 again with the command ....
560 and both the cluster and the client should return to Linux prompts.
563 1
\b1.
\b.6
\b6.
\b. T
\bTh
\bhe
\be C
\bCl
\bli
\bie
\ben
\bnt
\bt p
\bpr
\bro
\bog
\bgr
\bra
\bam
\bm
565 In earlier versions of Spider, all the processes were Perl scripts.
566 This was fine but with a lot of users your computer memory would soon
567 be used up. To combat this a new client was written in "C". This
568 client only works for _
\bi_
\bn_
\bc_
\bo_
\bm_
\bi_
\bn_
\bg connects at the moment. Before you can
569 use it though it has to be "made". CD to /spider/src and type _
\bm_
\ba_
\bk_
\be.
570 You should see the output on your screen and hopefully now have a
571 small C program called _
\bc_
\bl_
\bi_
\be_
\bn_
\bt. Leave it in this directory.
575 2
\b2.
\b. Q
\bQu
\bui
\bic
\bck
\bk i
\bin
\bns
\bst
\bta
\bal
\bll
\bla
\bat
\bti
\bio
\bon
\bn g
\bgu
\bui
\bid
\bde
\be
577 This section is designed for experienced Spider sysops who want to
578 install Spider from scratch. It is simply a check list of things that
579 need to be done without any explanations. The name in brackets at the
580 end of each line is the user that should be doing that process.
585 +
\bo Get the additional CPAN modules and install them (root)
587 +
\bo Create the "sysop" user and set a password (root)
589 +
\bo Put the Spider tarball in sysop and untar it (root)
591 +
\bo ln -s sysop/spider /spider (root)
593 +
\bo groupadd -g 251 spider (root)
595 +
\bo Add any more users you need to the group entry in /etc/group (root)
597 +
\bo Set the permissions on the spider tree (root)
599 +
\bo Fix permissions on ax25_call and netrom_call (root)
601 +
\bo Login as the sysop user
603 +
\bo cd to /spider (sysop)
605 +
\bo mkdir local (sysop)
607 +
\bo mkdir local_cmd (sysop)
609 +
\bo cp perl/DXVars.pm.issue local/DXVars.pm (sysop)
611 +
\bo cd to /spider/local and edit DXVars to set your details (sysop)
613 +
\bo cd ../perl (sysop)
615 +
\bo ./create_sysop.pl (sysop)
617 +
\bo ./cluster.pl (sysop)
619 Spider should now be running and you should be able to login using the
625 +
\bo Enter the correct line in ax25d.conf (root)
627 +
\bo Enter the correct line in /etc/services (root)
629 +
\bo Enter the correct line in /etc/inetd.conf (root)
631 +
\bo killall -HUP inetd (root)
633 Spider should now be able to accept logins via telnet, netrom and
639 +
\bo Start the cluster (sysop)
641 +
\bo set/node and type for links (sysop)
643 +
\bo Write any connect scripts (sysop)
645 +
\bo Edit /spider/crontab as required (sysop)
647 +
\bo Edit any other files as necessary (sysop)
649 +
\bo Set filters, hops and forwarding files (sysop)
653 +
\bo Enter the correct line in /etc/inittab (root)
656 3
\b3.
\b. C
\bCo
\bon
\bnf
\bfi
\big
\bgu
\bur
\bra
\bat
\bti
\bio
\bon
\bn
661 3
\b3.
\b.1
\b1.
\b. A
\bAl
\bll
\blo
\bow
\bwi
\bin
\bng
\bg a
\bax
\bx2
\b25
\b5 c
\bco
\bon
\bnn
\bne
\bec
\bct
\bts
\bs f
\bfr
\bro
\bom
\bm u
\bus
\bse
\ber
\brs
\bs
663 As stated previously, the aim of this document is not to tell you how
664 to configure Linux or the ax25 utilities. However, you do need to add
665 a line in your ax25d.conf to allow connections to DXSpider for your
666 users. For each interface that you wish to allow connections on, use
667 the following format ...
671 default * * * * * * - sysop /spider/src/client client %u ax25
676 or, if you wish your users to be able to use SSID's on their callsigns
681 default * * * * * * - sysop /spider/src/client client %s ax25
687 3
\b3.
\b.2
\b2.
\b. A
\bAl
\bll
\blo
\bow
\bwi
\bin
\bng
\bg t
\bte
\bel
\bln
\bne
\bet
\bt c
\bco
\bon
\bnn
\bne
\bec
\bct
\bts
\bs f
\bfr
\bro
\bom
\bm u
\bus
\bse
\ber
\brs
\bs
689 Allowing telnet connections is quite simple. Firstly you need to add
690 a line in /etc/services to allow connections to a port number, like
695 spdlogin 8000/tcp # spider anonymous login port
700 Then add a line in /etc/inetd.conf like this ....
704 spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
710 This needs to be added above the standard services such as ftp, telnet
711 etc. Once this is done, you need to restart inetd like this ....
722 Now login as _
\bs_
\by_
\bs_
\bo_
\bp and cd spider/src. You can test that spider is
723 accepting telnet logins by issuing the following command ....
727 ./client login telnet
732 You should get a login prompt and on issuing a callsign, you will be
733 given access to the cluster. Note, you will not get a password login.
734 There seems no good reason for a password prompt to be given so it is
738 Assuming all is well, then try a telnet from your linux console ....
742 telnet localhost 8000
748 You should now get the login prompt and be able to login as before.
751 3
\b3.
\b.3
\b3.
\b. S
\bSe
\bet
\btt
\bti
\bin
\bng
\bg u
\bup
\bp n
\bno
\bod
\bde
\be c
\bco
\bon
\bnn
\bne
\bec
\bct
\bts
\bs
753 In order to allow cluster node connections, spider needs to know that
754 the connecting callsign is a cluster node. This is the case whether
755 the connect is incoming or outgoing. In spider this is a simple task
756 and can be done in runtime.
759 Later versions of Spider can distinguish different software and treat
760 them differently. For example, the WCY beacon cannot be handles by
761 AK1A type nodes as AK1A does not know what to do with PC73. There are
762 4 different types of node at present and although they may not have
763 any major differences at the moment, it allows for compatibility. The
777 For now, we will assume that the cluster we are going to connect to is
781 Start up the cluster as you did before and login as the sysop with
782 client. The cluster node I am wanting to make a connection to is
783 GB7BAA but you would obviously use whatever callsign you required. At
793 The case does not matter as long as you have a version of DXSpider
794 later than 1.33. Earlier versions required the callsign to be in
798 That is now set, it is as simple as that. To prove it, login on yet
799 another console as sysop, cd to spider/src and issue the command ...
803 ./client gb7baa (using the callsign you set as a node)
809 You should get an initialisation string from DXSpider like this ...
819 If the callsign you just set up as a cluster node is for an incoming
820 connect, this is all that needs to be done. If the connection is to
821 be outgoing then a connection script needs to be written.
824 3
\b3.
\b.4
\b4.
\b. C
\bCo
\bon
\bnn
\bne
\bec
\bct
\bti
\bio
\bon
\bn s
\bsc
\bcr
\bri
\bip
\bpt
\bts
\bs
826 Because DXSpider operates under Linux, connections can be made using
827 just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all
828 possible examples. Connect scripts live in the /spider/connect
829 directory and are simple ascii files. Writing a script for
830 connections is therefore relatively simple.
833 The connect scripts consist of lines which start with the following
834 keywords or symbols:-
859 # All lines starting with a # are ignored, as are completely
862 timeout timeout followed by a number is the number of seconds to wait for a
863 command to complete. If there is no timeout specified in the script
864 then the default is 60 seconds.
866 abort abort is a regular expression containing one or more strings to look
867 for to abort a connection. This is a perl regular expression and is
868 executed ignoring case.
870 connect connect followed by ax25 or telnet and some type dependent
871 information. In the case of a telnet connection, there can be up to
873 The first is the ip address or hostname of the computer you wish to
874 connect to and the second is the port number you want to use (this
875 can be left out if it is a normal telnet session).
876 In the case of an ax25 session then this would normally be a call to
877 ax25_call or netrom_call as in the example above. It is your
878 responsibility to get your node and other ax25 parameters to work
879 before going down this route!
881 ' line in a chat type script. The words/phrases normally come in pairs,
882 either can be empty. Each line reads input from the connection until
883 it sees the string (or perl regular expression) contained in the
884 left hand string. If the left hand string is empty then it doesn't
885 read or wait for anything. The comparison is done ignoring case.
886 When the left hand string has found what it is looking for (if it is)
887 then the right hand string is sent to the connection.
888 This process is repeated for every line of chat script.
890 client client starts the connection, put the arguments you would want here
891 if you were starting the client program manually. You only need this
892 if the script has a different name to the callsign you are trying to
893 connect to (i.e. you have a script called other which actually
894 connects to GB7DJK-1 [instead of a script called gb7djk-1]).
899 There are many possible ways to configure the script but here are two
900 examples, one for a NETRom/AX25 connect and one for tcp/ip.
905 abort (Busy|Sorry|Fail)
906 # don't forget to chmod 4775 netrom_call!
907 connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
908 # you can leave this out if you call the script 'gb7dxm'
919 connect telnet dirkl.tobit.co.uk
920 # tell GB7DJK-1 that it is connected to GB7DJK
921 # you can leave this out if you call this script 'gb7djk'
925 Both these examples assume that everything is set up properly at the
926 other end. You will find other examples in the /spider/examples
930 3
\b3.
\b.5
\b5.
\b. S
\bSt
\bta
\bar
\brt
\bti
\bin
\bng
\bg t
\bth
\bhe
\be c
\bco
\bon
\bnn
\bne
\bec
\bct
\bti
\bio
\bon
\bn
932 You start the connection, from within a sysop enabled cluster login,
933 by typing in the word _
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt followed by a script name like this ....
937 G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1
938 connection to GB7DJK-1 started
939 G0VGS de GB7MBC 13-Dec-1998 2043Z >
944 This will start a connection using the script called _
\bg_
\bb_
\b7_
\bd_
\bj_
\bk_
\b-_
\b1. You
945 can follow the connection by watching the term or console from where
946 you started _
\bc_
\bl_
\bu_
\bs_
\bt_
\be_
\br_
\b._
\bp_
\bl. You should see something like this ...
950 <- D G1TLH connect gb7djk-1
951 -> D G1TLH connection to GB7DJK-1 started
952 -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
954 CONNECT sort: telnet command: dirkl.tobit.co.uk
955 CHAT "login" -> "gb7djk"
957 Red Hat Linux release 5.1 (Manhattan)
958 Kernel 2.0.35 on an i586
962 CHAT "word" -> "gb7djk"
964 received "Password: "
966 Connected to GB7DJK-1, starting normal protocol
969 GB7DJK-1 channel func state 0 -> init
971 <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1
972 <- D GB7DJK-1 PC38^GB7DJK-1^~
973 <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime
981 With later versions of Spider there is a set/login command for users.
982 This tells them when a user or node logs in or out. If you do not add
983 a line to your scripts after the final line (or before the client line
984 which should always be last if needed) then the login/logout
985 information will be sent to users _
\bb_
\be_
\bf_
\bo_
\br_
\be the login actually completes.
986 This means if a node is unreachable, it will continue sending logins
987 and logouts to users even though it is not actually connecting. To
988 avoid this use the following line ...
991 In a script, this might look like ...
996 abort (Busy|Sorry|Fail)
997 connect telnet mary 3000
1003 3
\b3.
\b.6
\b6.
\b. T
\bTe
\bel
\bln
\bne
\bet
\bt e
\bec
\bch
\bho
\bo
1005 Cluster links in particular suffer greatly from the presence of telnet
1006 echo. This is caused by the telnet negotiation itself and can create
1007 at worst severe loops. At best it creates unnecessary bandwidth and
1008 large logfiles! There are things that can be done to limit this
1009 problem but will not always work dependent on the route taken to
1013 Telnet echo itself should only be a problem if the connection is being
1014 made to the telnet port (23). This port uses special rules that
1015 include echo negotiation. If the connection is to a different port,
1016 such as 8000, this negotiation does not happen and therefore no echo
1020 Sometimes it is not possible to make a direct connection to another
1021 node and this can cause problems. There is a way of trying to
1022 suppress the telnet echo but this will not always work, unfortunately
1023 it is difficult to be more specific. Here is an example of what I
1029 abort (Busy|Sorry|Fail)
1030 connect telnet mary.lancs.ac.uk
1035 So, the first connection is made by Spider. This is fine as Spider
1036 uses the Net_Telnet script from within perl. This actually uses TCP
1037 rather than TELNET so no negotiation will be done on the first
1038 connection. Once connected to mary.lancs.ac.uk, the command is sent
1039 to suppress echo. Now a telnet is made to a cluster node that is
1040 accepting connections on port 23. The problem with this link is that
1041 the negotiation is made by the remote machine, therefore you have no
1042 control over it. The chances are that this link will create echo and
1043 there will be no way you can stop it.
1047 4
\b4.
\b. A
\bAu
\but
\bto
\bom
\bma
\bat
\bti
\bin
\bng
\bg t
\bth
\bhi
\bin
\bng
\bgs
\bs
1049 Ok, you should now have DXSpider running nicely and allowing connects
1050 by cluster nodes or users. However, it has to be shutdown and
1051 restarted manually and if connection scripts fail they have to be
1052 started again manually too, not much use if you are not at the
1053 console! So, in this section we will automate both. Firstly starting
1057 4
\b4.
\b.1
\b1.
\b. A
\bAu
\but
\bto
\bos
\bst
\bta
\bar
\brt
\bti
\bin
\bng
\bg t
\bth
\bhe
\be c
\bcl
\blu
\bus
\bst
\bte
\ber
\br
1059 This is not only a way to start the cluster automatically, it also
1060 works as a watchdog, checking the sanity of DXSpider and respawning it
1061 should it crash for any reason. Before doing the following, shutdown
1062 the cluster as you did earlier.
1065 Login as root and bring up the /etc/inittab file in your favourite
1066 editor. Add the following lines to the file near the end ...
1070 ##Start DXSpider on bootup and respawn it should it crash
1071 DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
1077 This line works fine for RedHat distributions. It is also fine for
1078 SuSE up to 7.0. From Suse 7.1 you need to add runlevels 2 and 5 like
1083 DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
1089 The line required for Slackware distributions is slightly different.
1090 My thanks to Aurelio, PA3EZL for this information.
1094 DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7
1100 This will automatically start DXSpider on tty7 (ALT-F7) on bootup and
1101 restart it should it crash for any reason.
1104 As root type the command _
\bt_
\be_
\bl_
\bi_
\bn_
\bi_
\bt _
\bq. DXSpider should start up
1105 immediately. You will see the output on tty7 and if you login as
1106 _
\bs_
\by_
\bs_
\bo_
\bp you should find everything running nicely.
1109 So far so good, now to automate script connections...
1112 4
\b4.
\b.2
\b2.
\b. T
\bTh
\bhe
\be c
\bcr
\bro
\bon
\bnt
\bta
\bab
\bb f
\bfi
\bil
\ble
\be
1114 Login as _
\bs_
\by_
\bs_
\bo_
\bp and create a file in /spider/local_cmd called crontab.
1115 Edit it with your favourite editor and add a line like this (I have
1123 # check every 10 minutes to see if gb7xxx is connected and if not
1124 # start a connect job going
1126 0,10,20,30,40,50 * * * * start_connect('gb7xxx') if !connected('gb7xxx')
1132 The callsign involved will be the callsign of the cluster node you are
1133 going to connect to. This will now check every 10 minutes to see if
1134 gb7xxx is connected, if it is then nothing will be done. If it is
1135 not, then a connect attempt will be started.
1138 There are probably lots of other things you could use this crontab
1139 file for. If you want to know more about it, look at the DXSpider
1140 website at the cron page where it is explained more fully.
1143 5
\b5.
\b. H
\bHo
\bop
\bp c
\bco
\bon
\bnt
\btr
\bro
\bol
\bl
1145 Starting with version 1.13 there is simple hop control available on a
1146 per node basis. Also it is possible to isolate a network completely so
1147 that you get all the benefits of being on that network, but can't pass
1148 on information from it to any other networks you may be connected to
1152 5
\b5.
\b.1
\b1.
\b. B
\bBa
\bas
\bsi
\bic
\bc h
\bho
\bop
\bp c
\bco
\bon
\bnt
\btr
\bro
\bol
\bl
1154 In /spider/data you will find a file called hop_table.pl. This is the
1155 file that controls your hop count settings. It has a set of default
1156 hops on the various PC frames and also a set for each node you want to
1157 alter the hops for. You may be happy with the default settings of
1158 course, but this powerful tool can help to protect and improve the
1159 network. The file will look something like this ...
1190 # hop table construction
1195 # default hopcount to use
1198 # some variable hop counts based on message type
1209 # the per node hop control thingy
1214 GB7ADX => { 11 => 8,
1222 GB7UDX => { 11 => 8,
1243 Each set of hops is contained within a pair of curly braces and
1244 contains a series of PC frame types. PC11 for example is a DX spot.
1245 The figures here are not exhaustive but should give you a good idea of
1249 You can alter this file at any time, including whilst the cluster is
1250 running. If you alter the file during runtime, the command _
\bl_
\bo_
\ba_
\bd_
\b/_
\bh_
\bo_
\bp_
\bs
1251 will bring your changes into effect.
1255 5
\b5.
\b.2
\b2.
\b. I
\bIs
\bso
\bol
\bla
\bat
\bti
\bin
\bng
\bg n
\bne
\bet
\btw
\bwo
\bor
\brk
\bks
\bs
1257 It is possible to isolate networks from each other on a "gateway" node
1258 using the _
\bs_
\be_
\bt_
\b/_
\bi_
\bs_
\bo_
\bl_
\ba_
\bt_
\be _
\b<_
\bn_
\bo_
\bd_
\be_
\b__
\bc_
\ba_
\bl_
\bl_
\b> command.
1261 The effect of this is to partition an isolated network completely from
1262 another nodes connected to your node. Your node will appear on and
1263 otherwise behave normally on every network to which you are connected,
1264 but data from an isolated network will not cross onto any other
1265 network or vice versa. However all the spot, announce and WWV traffic
1266 and personal messages will still be handled locally (because you are a
1267 real node on all connected networks), that is locally connected users
1268 will appear on all networks and will be able to access and receive
1269 information from all networks transparently. All routed messages will
1270 be sent as normal, so if a user on one network knows that you are a
1271 gateway for another network, he can still still send a talk/announce
1272 etc message via your node and it will be routed across.
1275 The only limitation currently is that non-private messages cannot be
1276 passed down isolated links regardless of whether they are generated
1277 locally. This will change when the bulletin routing facility is added.
1280 If you use isolate on a node connection you will continue to receive
1281 all information from the isolated partner, however you will not pass
1282 any information back to the isolated node. There are times when you
1283 would like to forward only spots across a link (maybe during a contest
1284 for example). To do this, isolate the node in the normal way and put
1285 in a filter in the /spider/filter/spots directory to override the
1286 isolate. This filter can be very simple and consists of just one line
1292 [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count
1299 There is a lot more on filtering in the next section.
1302 6
\b6.
\b. F
\bFi
\bil
\blt
\bte
\ber
\bri
\bin
\bng
\bg (
\b(O
\bOl
\bld
\bd S
\bSt
\bty
\byl
\ble
\be u
\bup
\bpt
\bto
\bo v
\bv1
\b1.
\b.4
\b44
\b4)
\b)
1304 Filters can be set for spots, announcements and WWV. You will find
1305 the directories for these under /spider/filter. You will find some
1306 examples in the directories with the suffix _
\b._
\bi_
\bs_
\bs_
\bu_
\be. There are two
1307 types of filter, one for incoming information and one for outgoing
1308 information. Outgoing filters are in the form _
\bC_
\bA_
\bL_
\bL_
\bS_
\bI_
\bG_
\bN_
\b._
\bp_
\bl and
1309 incoming filters are in the form _
\bi_
\bn_
\b__
\bC_
\bA_
\bL_
\bL_
\bS_
\bI_
\bG_
\bN_
\b._
\bp_
\bl. Filters can be set
1310 for both nodes and users.
1313 All filters work in basically the same way. There are several
1314 elements delimited by commas. There can be many lines in the filter
1315 and they are read from the top by the program. When writing a filter
1316 you need to think carefully about just what you want to achieve. You
1317 are either going to write a filter to _
\ba_
\bc_
\bc_
\be_
\bp_
\bt or to _
\br_
\be_
\bj_
\be_
\bc_
\bt. Think of a
1318 filter as having 2 main elements. For a reject filter, you would have
1319 a line or multiple lines rejecting the things you do not wish to
1320 receive and then a default line accepting everything else that is not
1321 included in the filter. Likewise, for an accept filter, you would
1322 have a line or multiple lines accepting the things you wish to receive
1323 and a default line rejecting everthing else.
1326 In the example below, a user requires a filter that would only return
1327 SSB spots posted in Europe on the HF bands. This is achieved by first
1328 rejecting the CW section of each HF band and rejecting all of VHF, UHF
1329 etc based on frequency. Secondly, a filter rule is set based on CQ
1330 zones to only accept spots posted in Europe. Lastly, a default filter
1331 rule is set to reject anything outside the filter.
1336 [ 0, 0, 'r', # reject all CW spots
1346 30000.0, 49000000000.0,
1348 [ 1, 11, 'n', [ 14, 15, 16, 20, 33, ], 15 ], #accept EU
1349 [ 0, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
1356 The actual elements of each filter are described more fully in the
1360 6
\b6.
\b.1
\b1.
\b. S
\bSp
\bpo
\bot
\bts
\bs
1362 The elements of the Spot filter are ....
1366 [action, field_no, sort, possible_values, hops]
1372 There are 3 elements here to look at. Firstly, the action element.
1373 This is very simple and only 2 possible states exist, accept (1) or
1377 The second element is the field_no. There are 13 possiblities to
1378 choose from here ....
1389 2 = date in unix format
1392 5 = spotted dxcc country
1393 6 = spotter's dxcc country
1399 12 = callsign of the channel on which the spot has appeared
1405 The third element tells us what to expect in the fourth element.
1406 There are 4 possibilities ....
1410 n - numeric list of numbers e.g. [ 1,2,3 ]
1411 r - ranges of pairs of numbers e.g. between 2 and 4 or 10 to 17 - [ 2,4, 10,17 ]
1412 a - an alphanumeric regex
1413 d - the default rule
1419 The fifth element is simply the hops to set in this filter. This
1420 would only be used if the filter was for a node of course and
1421 overrides the hop count in hop_table.pl.
1424 So, let's look at an example spot filter. It does not matter in the
1425 example who the filter is to be used for. So, what do we need in the
1426 filter? We need to filter the spots the user/node requires and also
1427 set a default rule for anything else outside the filter. Below is a
1428 simple filter that stops spots arriving from outside Europe.
1433 [ 0, 4, 'a', '^(K|N|A|W|VE|VA|J)'], # 0 = drop, 'a' = alphanumeric
1434 [ 1, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
1441 So the filter is wrapped in between a pair of square brackets. This
1442 tells Spider to look in between these limits. Then each line is
1443 contained within its own square brackets and ends with a comma. Lets
1444 look carefully at the first line. The first element is 0 (drop).
1445 Therefore anything we put on this line will not be accepted. The next
1446 element is 4. This means we are filtering by the spotter. The third
1447 element is the letter "a" which tells the program to expect an
1448 alphanumeric expression in the fourth element. The fourth element is
1449 a list of letters separated by the pipe symbol.
1453 What this line does is tell the program to drop any spots posted by
1454 anyone in the USA, Canada or Japan.
1457 The second line is the default rule for anything else. The "d" tells
1458 us this and the line simply reads... accept anything else.
1461 You can add as many lines as you need to complete the filter but if
1462 there are several lines of the same type it is neater to enclose them
1463 all as one line. An example of this is where specific bands are set.
1464 We could write this like this ....
1468 [ 0,0,'r',[1800.0, 2000.0], 1],
1469 [ 0,0,'r',[10100.0, 10150.0], 1],
1470 [ 0,0,'r',[14000.0, 14350.0], 1],
1471 [ 0,0,'r',[18000.0, 18200.0], 1],
1477 But the line below achieves the same thing and is more efficient ....
1483 1800.0, 2000.0, # top band
1484 10100.0, 10150.0, # WARC
1485 14000.0, 14350.0, # 20m
1486 18000.0, 18200.0, # WARC
1494 6
\b6.
\b.2
\b2.
\b. A
\bAn
\bnn
\bno
\bou
\bun
\bnc
\bce
\bem
\bme
\ben
\bnt
\bts
\bs
1499 # This is an example announce or filter allowing only West EU announces
1501 # The element list is:-
1502 # 0 - callsign of announcer
1503 # 1 - destination * = all, <callsign> = routed to the node
1505 # 3 - * - sysop, <some text> - special list eg 6MUK, ' ', normal announce
1507 # 5 - 0 - announce, 1 - wx
1508 # 6 - channel callsign (the interface from which this spot came)
1511 [ 1, 0, 'a', '^(P[ABCDE]|DK0WCY|G|M|2|EI|F|ON)' ],
1519 In this example, only the prefixes listed will be allowed. It is
1520 possible to be quite specific. The Dutch prefix "P" is followed by
1521 several secondary identifiers which are allowed. So, in the example,
1522 "PA" or "PE" would be ok but not "PG". It is even possible to allow
1523 information from a single callsign. In the example this is DK0WCY, to
1524 allow the posting of his Aurora Beacon.
1527 6
\b6.
\b.3
\b3.
\b. W
\bWW
\bWV
\bV
1532 # This is an example WWV filter
1534 # The element list is:-
1535 # 0 - nominal unix date of spot (ie the day + hour:13)
1543 # 8 - incoming interface callsign
1545 # this one doesn't filter, it just sets the hop count to 6 and is
1546 # used mainly just to override any isolation from WWV coming from
1557 It should be noted that the filter will start to be used only once a
1558 user/node has logged out and back in again.
1560 I am not going to spend any more time on these filters now as they
1561 will become more "comprehensive" in the near future.
1564 7
\b7.
\b. F
\bFi
\bil
\blt
\bte
\ber
\bri
\bin
\bng
\bg (
\b(N
\bNe
\bew
\bw S
\bSt
\bty
\byl
\ble
\be v
\bv1
\b1.
\b.4
\b45
\b5 a
\ban
\bnd
\bd l
\bla
\bat
\bte
\ber
\br)
\b)
1566 7
\b7.
\b.1
\b1.
\b. G
\bGe
\ben
\bne
\ber
\bra
\bal
\bl f
\bfi
\bil
\blt
\bte
\ber
\br r
\bru
\bul
\ble
\bes
\bs
1568 Upto v1.44 it was not possible for the user to set their own filters.
1569 From v1.45 though that has all changed. It is now possible to set
1570 filters for just about anything you wish. If you have just updated
1571 from an older version of DXSpider you will need to update your new
1572 filters. You do not need to do anything with your old filters, they
1573 will be renamed as you update.
1576 There are 3 basic commands involved in setting and manipulating
1577 filters. These are _
\ba_
\bc_
\bc_
\be_
\bp_
\bt, _
\br_
\be_
\bj_
\be_
\bc_
\bt and _
\bc_
\bl_
\be_
\ba_
\br. First we will look
1578 generally at filtering. There are a number of things you can filter in
1579 the DXSpider system. They all use the same general mechanism.
1582 In general terms you can create a 'reject' or an 'accept' filter which
1583 can have up to 10 lines in it. You do this using, for example ...
1591 where ..... are the specific commands for that type of filter. There
1592 are filters for spots, wwv, announce, wcy and (for sysops) connects.
1593 See each different accept or reject command reference for more
1596 There is also a command to clear out one or more lines in a filter.
1607 There is clear/xxxx command for each type of filter.
1610 and you can check that your filters have worked by the command ...
1621 For now we are going to use spots for the examples, but you can apply
1622 the same principles to all types of filter.
1625 7
\b7.
\b.2
\b2.
\b. T
\bTy
\byp
\bpe
\bes
\bs o
\bof
\bf f
\bfi
\bil
\blt
\bte
\ber
\br
1627 There are two main types of filter, _
\ba_
\bc_
\bc_
\be_
\bp_
\bt or _
\br_
\be_
\bj_
\be_
\bc_
\bt. You can use
1628 either to achieve the result you want dependent on your own preference
1629 and which is more simple to do. It is pointless writing 8 lines of
1630 reject filters when 1 accept filter would do the same thing! Each
1631 filter has 10 lines (of any length) which are tried in order. If a
1632 line matches then the action you have specified is taken (ie reject
1633 means ignore it and accept means take it)
1636 If you specify reject filters, then any lines that arrive that match
1637 the filter will be dumped but all else will be accepted. If you use
1638 an accept filter, then ONLY the lines in the filter will be accepted
1639 and all else will be dumped. For example if you have a single line
1640 _
\ba_
\bc_
\bc_
\be_
\bp_
\bt filter ...
1644 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1649 then you will _
\bO_
\bN_
\bL_
\bY get VHF spots _
\bf_
\br_
\bo_
\bm or _
\bt_
\bo CQ zones 14, 15 and 16.
1651 If you set a reject filter like this ...
1655 reject/spots on hf/cw
1660 Then you will get everything _
\bE_
\bX_
\bC_
\bE_
\bP_
\bT HF CW spots. You could make this
1661 single filter even more flexible. For example, if you are interested
1662 in IOTA and will work it even on CW even though normally you are not
1663 interested in CW, then you could say ...
1667 reject/spots on hf/cw and not info iota
1672 But in that case you might only be interested in iota and say:-
1676 accept/spots not on hf/cw or info iota
1681 which achieves exactly the same thing. You should choose one or the
1682 other until you are comfortable with the way it works. You can mix
1683 them if you wish (actually you can have an accept AND a reject on the
1684 same line) but don't attempt this until you are sure you know what you
1688 You can arrange your filter lines into logical units, either for your
1689 own understanding or simply convenience. Here is an example ...
1693 reject/spots 1 on hf/cw
1694 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
1699 What this does is to ignore all HF CW spots and also rejects any spots
1700 on VHF which don't either originate or spot someone in Europe.
1703 This is an example where you would use a line number (1 and 2 in this
1704 case), if you leave the digit out, the system assumes '1'. Digits
1705 '0'-'9' are available. This make it easier to see just what filters
1706 you have set. It also makes it more simple to remove individual
1707 filters, during a contest for example.
1710 You will notice in the above example that the second line has
1711 brackets. Look at the line logically. You can see there are 2
1712 separate sections to it. We are saying reject spots that are VHF or
1713 above _
\bA_
\bP_
\bA_
\bR_
\bT from those in zones 14, 15 and 16 (either spotted there or
1714 originated there). If you did not have the brackets to separate the 2
1715 sections, then Spider would read it logically from the front and see a
1716 different expression entirely ...
1717 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
1722 The simple way to remember this is, if you use OR - use brackets.
1723 Whilst we are here CASE is not important. 'And BY_Zone' is just the
1724 same as 'and by_zone'.
1726 As mentioned earlier, setting several filters can be more flexible
1727 than simply setting one complex one. Doing it in this way means that
1728 if you want to alter your filter you can just redefine or remove one
1729 or more lines of it or one line. For example ...
1733 reject/spots 1 on hf/ssb
1738 would redefine our earlier example, or
1747 To remove all the filter lines in the spot filter ...
1757 7
\b7.
\b.3
\b3.
\b. F
\bFi
\bil
\blt
\bte
\ber
\br o
\bop
\bpt
\bti
\bio
\bon
\bns
\bs
1759 You can filter in several different ways. The options are listed in
1760 the various helpfiles for accept, reject and filter.
1763 7
\b7.
\b.4
\b4.
\b. D
\bDe
\bef
\bfa
\bau
\bul
\blt
\bt f
\bfi
\bil
\blt
\bte
\ber
\brs
\bs
1765 Sometimes all that is needed is a general rule for node connects.
1766 This can be done with a node_default filter. This rule will always be
1767 followed, even if the link is isolated, unless another filter is set
1768 specifically. Default rules can be set for nodes and users. They can
1769 be set for spots, announces, WWV and WCY. They can also be used for
1770 hops. An example might look like this ...
1774 accept/spot node_default by_zone 14,15,16,20,33
1775 set/hops node_default spot 50
1780 This filter is for spots only, you could set others for announce, WWV
1781 and WCY. This filter would work for ALL nodes unless a specific
1782 filter is written to override it for a particular node. You can also
1783 set a user_default should you require. It is important to note that
1784 default filters should be considered to be "connected". By this I
1785 mean that should you override the default filter for spots, you need
1786 to add a rule for the hops for spots also.
1789 7
\b7.
\b.5
\b5.
\b. A
\bAd
\bdv
\bva
\ban
\bnc
\bce
\bed
\bd f
\bfi
\bil
\blt
\bte
\ber
\bri
\bin
\bng
\bg
1791 Once you are happy with the results you get, you may like to
1795 The previous example that filters hf/cw spots and accepts vhf/uhf
1796 spots from EU can be written with a mixed filter, for example ...
1802 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
1807 Note that the first filter has not been specified with a number. This
1808 will automatically be assumed to be number 1. In this case, we have
1809 said _
\br_
\be_
\bj_
\be_
\bc_
\bt _
\ba_
\bl_
\bl _
\bH_
\bF _
\bs_
\bp_
\bo_
\bt_
\bs _
\bi_
\bn _
\bt_
\bh_
\be _
\bC_
\bW _
\bs_
\be_
\bc_
\bt_
\bi_
\bo_
\bn _
\bo_
\bf _
\bt_
\bh_
\be _
\bb_
\ba_
\bn_
\bd_
\bs _
\bb_
\bu_
\bt _
\ba_
\bc_
\bc_
\be_
\bp_
\bt _
\ba_
\bl_
\bl
1810 _
\bo_
\bt_
\bh_
\be_
\br_
\bs _
\ba_
\bt _
\bH_
\bF_
\b. _
\bA_
\bl_
\bs_
\bo _
\ba_
\bc_
\bc_
\be_
\bp_
\bt _
\ba_
\bn_
\by_
\bt_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bV_
\bH_
\bF _
\ba_
\bn_
\bd _
\ba_
\bb_
\bo_
\bv_
\be _
\bs_
\bp_
\bo_
\bt_
\bt_
\be_
\bd _
\bi_
\bn _
\bo_
\br _
\bb_
\by
1811 _
\bo_
\bp_
\be_
\br_
\ba_
\bt_
\bo_
\br_
\bs _
\bi_
\bn _
\bt_
\bh_
\be _
\bz_
\bo_
\bn_
\be_
\bs _
\b1_
\b4_
\b, _
\b1_
\b5 _
\ba_
\bn_
\bd _
\b1_
\b6. Each filter slot actually has a
1812 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
1816 It was mentioned earlier that after a reject test that doesn't match,
1817 the default for following tests is 'accept', the reverse is true for
1818 'accept'. In the example what happens is that the reject is executed
1819 first, any non hf/cw spot is passed to the accept line, which lets
1820 through everything else on HF. The next filter line lets through just
1821 VHF/UHF spots from EU.
1825 8
\b8.
\b. O
\bOt
\bth
\bhe
\ber
\br f
\bfi
\bil
\blt
\bte
\ber
\brs
\bs
1827 8
\b8.
\b.1
\b1.
\b. F
\bFi
\bil
\blt
\bte
\ber
\bri
\bin
\bng
\bg M
\bMa
\bai
\bil
\bl
1829 In the /spider/msg directory you will find a file called
1830 badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
1831 original looks something like this ....
1849 # the list of regexes for messages that we won't store having
1850 # received them (bear in mind that we must receive them fully before
1854 # The format of each line is as follows
1856 # type source pattern
1857 # P/B/F T/F/O/S regex
1859 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1860 # source: T - to field, F - from field, O - origin, S - subject
1861 # pattern: a perl regex on the field requested
1863 # Currently only type B and P msgs are affected by this code.
1865 # The list is read from the top down, the first pattern that matches
1866 # causes the action to be taken.
1868 # The pattern can be undef or 0 in which case it will always be selected
1869 # for the action specified
1882 I think this is fairly self explanatory. It is simply a list of
1883 subject headers that we do not want to pass on to either the users of
1884 the cluster or the other cluster nodes that we are linked to. This is
1885 usually because of rules and regulations pertaining to items for sale
1886 etc in a particular country.
1889 8
\b8.
\b.2
\b2.
\b. F
\bFi
\bil
\blt
\bte
\ber
\bri
\bin
\bng
\bg D
\bDX
\bX c
\bca
\bal
\bll
\blo
\bou
\but
\bts
\bs (
\b(D
\bDe
\bep
\bpr
\bri
\bic
\bca
\bat
\bte
\bed
\bd)
\b)
1891 _
\bF_
\br_
\bo_
\bm _
\bv_
\be_
\br_
\bs_
\bi_
\bo_
\bn _
\b1_
\b._
\b4_
\b7_
\b, _
\bt_
\bh_
\bi_
\bs _
\bm_
\be_
\bt_
\bh_
\bo_
\bd _
\bi_
\bs _
\br_
\be_
\bp_
\bl_
\ba_
\bc_
\be_
\bd _
\bb_
\by _
\bt_
\bh_
\be _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bs_
\be_
\bt_
\b/_
\bb_
\ba_
\bd_
\bd_
\bx
1894 In the same way as mail, there are some types of spot we do not wish
1895 to pass on to users or linked cluster nodes. In the /spider/data
1896 directory you will find a file called baddx.pl.issue. Rename this to
1897 baddx.pl and edit the file. The original looks like this ....
1915 # the list of dx spot addresses that we don't store and don't pass on
1938 Again, this is simply a list of names we do not want to see in the
1939 spotted field of a DX callout.
1943 8
\b8.
\b.3
\b3.
\b. F
\bFi
\bil
\blt
\bte
\ber
\bri
\bin
\bng
\bg w
\bwo
\bor
\brd
\bds
\bs f
\bfr
\bro
\bom
\bm t
\bte
\bex
\bxt
\bt f
\bfi
\bie
\bel
\bld
\bds
\bs i
\bin
\bn A
\bAn
\bnn
\bno
\bou
\bun
\bnc
\bce
\be,
\b, T
\bTa
\bal
\blk
\bk a
\ban
\bnd
\bd D
\bDX
\bX s
\bsp
\bpo
\bot
\bts
\bs
1945 Create a file in /spider/data called _
\bb_
\ba_
\bd_
\bw_
\bo_
\br_
\bd_
\bs. The format is quite
1946 simple. Lines beginning with # are ignored so comments can be added.
1947 An example file is below ...
1951 # Below is a list of words we do not wish to see on the cluster
1952 grunge grunged grunging
1953 splodge splodger splodging
1960 Multiple words can be used on the same line as shown. Obviously these
1961 are just examples :-)
1964 You can reload the file from the cluster prompt as sysop with
1968 9
\b9.
\b. M
\bMa
\bai
\bil
\bl
1970 DXSpider deals seamlessly with standard AK1A type mail. It supports
1971 both personal and bulletin mail and the sysop has additional commands
1972 to ensure that mail gets to where it is meant. DXSpider will send
1973 mail almost immediately, assuming that the target is on line.
1974 However, only one mail message is dealt with at any one time. If a
1975 mail message is already being sent or recieved, then the new message
1976 will be queued until it has finished.
1978 The cluster mail is automatically deleted after 30 days unless the
1979 sysop sets the "keep" flag using the _
\bm_
\bs_
\bg command.
1981 9
\b9.
\b.1
\b1.
\b. P
\bPe
\ber
\brs
\bso
\bon
\bna
\bal
\bl m
\bma
\bai
\bil
\bl
1983 Personal mail is sent using the _
\bs_
\bp command. This is actually the
1984 default method of sending mail and so a simple _
\bs for send will do. A
1985 full list of the send commands and options is in the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bs_
\be_
\bt
1986 section, so I will not duplicate them here.
1989 9
\b9.
\b.2
\b2.
\b. B
\bBu
\bul
\bll
\ble
\bet
\bti
\bin
\bn m
\bma
\bai
\bil
\bl
1991 Bulletin mail is sent by using the _
\bs_
\bb command. This is one of the
1992 most common mistakes users make when sending mail. They send a
1993 bulletin mail with _
\bs or _
\bs_
\bp instead of _
\bs_
\bb and of course the message
1994 never leaves the cluster. This can be rectified by the sysop by using
1995 the _
\bm_
\bs_
\bg command.
1998 Bulletin addresses can be set using the Forward.pl file.
2001 9
\b9.
\b.3
\b3.
\b. F
\bFo
\bor
\brw
\bwa
\bar
\brd
\bd.
\b.p
\bpl
\bl
2003 DXSpider receives all and any mail sent to it without any alterations
2004 needed in files. Because personal and bulletin mail are treated
2005 differently, there is no need for a list of accepted bulletin
2006 addresses. It is necessary, however, to tell the program which links
2007 accept which bulletins. For example, it is pointless sending
2008 bulletins addresses to "UK" to any links other than UK ones. The file
2009 that does this is called forward.pl and lives in /spider/msg. At
2010 default, like other spider files it is named forward.pl.issue. Rename
2011 it to forward.pl and edit the file to match your requirements. The
2048 # this is an example message forwarding file for the system
2050 # The format of each line is as follows
2052 # type to/from/at pattern action destinations
2053 # P/B/F T/F/A regex I/F [ call [, call ...] ]
2055 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
2056 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
2057 # pattern: a perl regex on the field requested
2058 # action: I - ignore, F - forward
2059 # destinations: a reference to an array containing node callsigns
2061 # if it is non-private and isn't in here then it won't get forwarded
2063 # Currently only type B msgs are affected by this code.
2065 # The list is read from the top down, the first pattern that matches
2066 # causes the action to be taken.
2068 # The pattern can be undef or 0 in which case it will always be selected
2069 # for the action specified
2071 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
2072 # pattern) then it will always be forwarded to every node that doesn't have
2073 # it (I strongly recommend you don't use this unless you REALLY mean it, if
2074 # you allow a new link with this on EVERY bull will be forwarded immediately
2075 # on first connection)
2086 Simply insert a bulletin address and state in the brackets where you
2087 wish that mail to go. For example, you can see here that mail sent to
2088 "UK" will only be sent to the UK links and not to PA4AB-14.
2091 To force the cluster to reread the file use load/forward
2095 9
\b9.
\b.4
\b4.
\b. T
\bTh
\bhe
\be m
\bms
\bsg
\bg c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
2097 The _
\bm_
\bs_
\bg command is a very powerful and flexible tool for the sysop.
2098 It allows the sysop to alter to and from fields and make other changes
2099 to manage the cluster mail.
2101 Here is a full list of the various options ...
2113 MSG TO <msgno> <call> - change TO callsign to <call>
2114 MSG FRom <msgno> <call> - change FROM callsign to <call>
2115 MSG PRrivate <msgno> - set private flag
2116 MSG NOPRrivate <msgno> - unset private flag
2117 MSG RR <msgno> - set RR flag
2118 MSG NORR <msgno> - unset RR flag
2119 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
2120 MSG NOKEep <msgno> - unset the keep flag
2121 MSG SUbject <msgno> <new> - change the subject to <new>
2122 MSG WAittime <msgno> - remove any waiting time for this message
2123 MSG NOREad <msgno> - mark message as unread
2124 MSG REad <msgno> - mark message as read
2125 MSG QUeue - queue any outstanding bulletins
2126 MSG QUeue 1 - queue any outstanding private messages
2131 These commands are simply typed from within the cluster as the sysop
2135 9
\b9.
\b.5
\b5.
\b. M
\bMe
\bes
\bss
\bsa
\bag
\bge
\be s
\bst
\bta
\bat
\btu
\bus
\bs
2137 You can check on a message from within the cluster by using the
2138 command _
\bs_
\bt_
\ba_
\bt_
\b/_
\bm_
\bs_
\bg. This will give you additional information on the
2139 message number including which nodes have received it, which node it
2140 was received from and when etc. Here is an example of the output of
2145 G0VGS de GB7MBC 28-Jan-2001 1308Z >
2148 Msg Time: 26-Jan-2001 1302Z
2152 Subject: AMSAT 2line KEPS 01025.AMSAT
2154 Got it Nodes: GB7BAA, GB7ADX
2158 G0VGS de GB7MBC 28-Jan-2001 1308Z >
2164 9
\b9.
\b.6
\b6.
\b. F
\bFi
\bil
\blt
\bte
\ber
\bri
\bin
\bng
\bg m
\bma
\bai
\bil
\bl
2166 This is described in the section on _
\bO_
\bt_
\bh_
\be_
\br _
\bf_
\bi_
\bl_
\bt_
\be_
\br_
\bs so I will not
2170 9
\b9.
\b.7
\b7.
\b. D
\bDi
\bis
\bst
\btr
\bri
\bib
\bbu
\but
\bti
\bio
\bon
\bn l
\bli
\bis
\bst
\bts
\bs
2172 Distribution lists are simply a list of users to send certain types of
2173 mail to. An example of this is mail you only wish to send to other
2174 sysops. In /spider/msg there is a directory called _
\bd_
\bi_
\bs_
\bt_
\br_
\bo. You put
2175 any distibution lists in here. For example, here is a file called
2176 SYSOP.pl that caters for the UK sysops.
2179 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
2180 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
2181 GB7DXK GB7DXI GB7DXS)
2186 Any mail sent to "sysop" would only be sent to the callsigns in this
2190 9
\b9.
\b.8
\b8.
\b. B
\bBB
\bBS
\bS i
\bin
\bnt
\bte
\ber
\brf
\bfa
\bac
\bce
\be
2192 Spider provides a simple BBS interface. No input is required from the
2193 sysop of the cluster at all. The BBS simply sets the cluster as a BBS
2194 and pushes any required mail to the cluster. No mail can flow from
2195 Spider to the BBS, the interface is one-way.
2198 Please be careful not to flood the cluster network with unnecessary
2199 mail. Make sure you only send mail to the clusters that want it by
2200 using the Forward.pl file very carefully.
2203 1
\b10
\b0.
\b. D
\bDa
\bat
\bta
\bab
\bba
\bas
\bse
\bes
\bs
2205 Spider allows the creation of local or remote databases. It supports
2206 chained databases, allowing several different databases to be scanned
2207 with one simple command. Importing of databases is limited at present
2208 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
2209 database but will expand with time.
2212 1
\b10
\b0.
\b.1
\b1.
\b. C
\bCr
\bre
\bea
\bat
\bti
\bin
\bng
\bg d
\bda
\bat
\bta
\bab
\bba
\bas
\bse
\bes
\bs
2214 Creating a database could not be more simple. All the commands are
2215 sent from the cluster prompt as the _
\bs_
\by_
\bs_
\bo_
\bp user.
2217 To create a database you use the command _
\bd_
\bb_
\bc_
\br_
\be_
\ba_
\bt_
\be. It can be used in
2218 3 different ways like so ..
2227 To simply create a database locally, you just tell the command the
2228 name of the database. This does not create the actual database, it
2229 simply defines it to say that it exists.
2233 dbcreate <name> chain <name> [<name>...]
2238 This creates a chained database entry. The first database will be
2239 scanned, then the second, the third etc...
2243 dbcreate <name> remote <name>
2245 This creates a remote entry. the first name field is the database
2246 name at the remote node, then the remote switch, then the actual
2247 node_call of the remote node, for example...
2251 dbcreate buckmaster remote gb7dxc
2256 Remote databases cannot be chained, however, the last database in a
2257 chain can be a remote database.
2260 1
\b10
\b0.
\b.2
\b2.
\b. I
\bIm
\bmp
\bpo
\bor
\brt
\bti
\bin
\bng
\bg d
\bda
\bat
\bta
\bab
\bba
\bas
\bse
\bes
\bs
2262 The only databases that Spider can currently import are the standard
2263 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
2264 This will be added to with time.
2266 To import such a database, first put the file somewhere useful like
2267 /tmp and then issue the following command ...
2271 dbimport oblast /tmp/OBLAST.FUL
2276 This will update the existing local oblast database or create it if it
2280 1
\b10
\b0.
\b.3
\b3.
\b. C
\bCh
\bhe
\bec
\bck
\bki
\bin
\bng
\bg a
\bav
\bva
\bai
\bil
\bla
\bab
\bbl
\ble
\be d
\bda
\bat
\bta
\bab
\bba
\bas
\bse
\bes
\bs
2282 Once a database is created, you will want to check that it has been
2283 added. To do this use the _
\bd_
\bb_
\ba_
\bv_
\ba_
\bi_
\bl command. This will output the
2284 available databases. For example ...
2289 DB Name Location Chain
2293 G0VGS de GB7MBC 3-Feb-2001 1925Z >
2299 1
\b10
\b0.
\b.4
\b4.
\b. L
\bLo
\boo
\bok
\bki
\bin
\bng
\bg u
\bup
\bp d
\bda
\bat
\bta
\bab
\bba
\bas
\bse
\bes
\bs
2301 To look for information in a defined database, simply use the _
\bd_
\bb_
\bs_
\bh_
\bo_
\bw
2302 command, for example ...
2306 dbshow buckmaster G0YLM
2311 will show the information for the callsign G0YLM from the buckmaster
2312 database if it exists. To make things more standard for the users you
2313 can add an entry in the Aliases file so that it looks like a standard
2314 _
\bs_
\bh_
\bo_
\bw command like this ...
2322 Now you can simply use show/buckmaster or an abreviation.
2325 1
\b10
\b0.
\b.5
\b5.
\b. R
\bRe
\bem
\bmo
\bov
\bvi
\bin
\bng
\bg d
\bda
\bat
\bta
\bab
\bba
\bas
\bse
\bes
\bs
2327 To delete an existing database you use the _
\bd_
\bb_
\br_
\be_
\bm_
\bo_
\bv_
\be command. For
2337 would remove the oblast database and its associated datafile from the
2338 system. There are no warnings or recovery possible from this command.
2339 If you remove a database it ceases to exist and would have to be
2340 created from scratch if you still required it.
2343 1
\b11
\b1.
\b. I
\bIn
\bnf
\bfo
\bor
\brm
\bma
\bat
\bti
\bio
\bon
\bn,
\b, f
\bfi
\bil
\ble
\bes
\bs a
\ban
\bnd
\bd u
\bus
\bse
\bef
\bfu
\bul
\bl p
\bpr
\bro
\bog
\bgr
\bra
\bam
\bms
\bs
2345 1
\b11
\b1.
\b.1
\b1.
\b. M
\bMO
\bOT
\bTD
\bD
2347 One of the more important things a cluster sysop needs to do is to get
2348 information to his users. The simplest way to do this is to have a
2349 banner that is sent to the user on login. This is know as a "message
2350 of the day" or "motd". To set this up, simply create a file in
2351 /spider/data called motd and edit it to say whatever you want. It is
2352 purely a text file and will be sent automatically to anyone logging in
2356 1
\b11
\b1.
\b.2
\b2.
\b. D
\bDo
\bow
\bwn
\bnt
\bti
\bim
\bme
\be m
\bme
\bes
\bss
\bsa
\bag
\bge
\be
2358 If for any reason the cluster is down, maybe for upgrade or
2359 maintenance but the machine is still running, a message can be sent to
2360 the user advising them of the fact. This message lives in the
2361 /spider/data directory and is called "offline". Simply create the
2362 file and edit it to say whatever you wish. This file will be sent to
2363 a user attempting to log into the cluster when DXSpider is not
2367 1
\b11
\b1.
\b.3
\b3.
\b. O
\bOt
\bth
\bhe
\ber
\br t
\bte
\bex
\bxt
\bt m
\bme
\bes
\bss
\bsa
\bag
\bge
\bes
\bs
2369 You can set other text messages to be read by the user if they input
2370 the file name. This could be for news items or maybe information for
2371 new users. To set this up, make a directory under /spider called
2372 _
\bp_
\ba_
\bc_
\bk_
\bc_
\bl_
\bu_
\bs. Under this directory you can create files called _
\bn_
\be_
\bw_
\bs or
2373 _
\bn_
\be_
\bw_
\bu_
\bs_
\be_
\br for example. In fact you can create files with any names you
2374 like. These can be listed by the user with the command ....
2382 They can be read by the user by typing the command ....
2391 If the file they want to read is called _
\bn_
\be_
\bw_
\bs. You could also set an
2392 alias for this in the Alias file to allow them just to type _
\bn_
\be_
\bw_
\bs
2395 You can also store other information in this directory, either
2396 directly or nested under directories. One use for this would be to
2397 store DX bulletins such as the OPDX bulletins. These can be listed
2398 and read by the user. To keep things tidy, make a directory under
2399 /spider/packclus called _
\bb_
\bu_
\bl_
\bl_
\be_
\bt_
\bi_
\bn. Now copy any OPDX or similar
2400 bulletins into it. These can be listed by the user in the same way as
2401 above using the _
\bs_
\bh_
\bo_
\bw_
\b/_
\bf_
\bi_
\bl_
\be_
\bs command with an extension for the bulletin
2402 directory you have just created, like this ....
2412 An example would look like this ....
2417 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
2422 You can see that in the files area (basically the packclus directory)
2423 there is a file called _
\bn_
\be_
\bw_
\bs and a directory called _
\bb_
\bu_
\bl_
\bl_
\be_
\bt_
\bi_
\bn. You can
2424 also see that dates they were created. In the case of the file _
\bn_
\be_
\bw_
\bs,
2425 you can also see the time it was last modified, a good clue as to
2426 whether the file has been updated since you last read it. To read the
2427 file called _
\bn_
\be_
\bw_
\bs you would simply issue the command ....
2436 To look what is in the bulletin directory you issue the command ....
2444 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
2445 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
2446 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
2447 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
2448 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
2449 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
2450 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
2451 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
2452 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
2453 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
2454 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
2455 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
2456 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
2457 Press Enter to continue, A to abort (16 lines) >
2462 You can now read any file in this directory using the type command,
2467 type bulletin/opdx391
2468 Ohio/Penn DX Bulletin No. 391
2469 The Ohio/Penn Dx PacketCluster
2473 Editor Tedd Mirgliotta, KB8NW
2474 Provided by BARF-80 BBS Cleveland, Ohio
2475 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
2476 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
2477 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
2478 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
2479 Press Enter to continue, A to abort (508 lines) >
2484 The page length will of course depend on what you have it set to!
2487 1
\b11
\b1.
\b.4
\b4.
\b. T
\bTh
\bhe
\be A
\bAl
\bli
\bia
\bas
\bse
\bes
\bs f
\bfi
\bil
\ble
\be
2489 You will find a file in /spider/cmd/ called Aliases. First, copy this
2490 file to /spider/local_cmd/Aliases and edit this file. You will see
2491 something like this ...
2511 # provide some standard aliases for commands for terminally
2512 # helpless ak1a user (helpless in the sense that they never
2513 # read nor understand help files)
2515 # This file is automagically reloaded if its modification time is
2516 # later than the one stored in CmdAlias.pm
2518 # PLEASE make this file consistant with reality! (the patterns MUST
2519 # match the filenames!)
2521 # Don't alter this file, copy it into the local_cmd tree and modify it.
2522 # This file will be replaced everytime I issue a new release.
2524 # You only need to put aliases in here for commands that don't work as
2525 # you desire naturally, e.g sh/dx on its own just works as you expect
2526 # so you need not add it as an alias.
2534 '^\?', 'apropos', 'apropos',
2537 '^ann.*/full', 'announce full', 'announce',
2538 '^ann.*/sysop', 'announce sysop', 'announce',
2539 '^ann.*/(.*)$', 'announce $1', 'announce',
2546 '^del', 'kill', 'kill',
2547 '^del\w*/fu', 'kill full', 'kill',
2548 '^di\w*/a\w*', 'directory all', 'directory',
2549 '^di\w*/b\w*', 'directory bulletins', 'directory',
2550 '^di\w*/n\w*', 'directory new', 'directory',
2551 '^di\w*/o\w*', 'directory own', 'directory',
2552 '^di\w*/s\w*', 'directory subject', 'directory',
2553 '^di\w*/t\w*', 'directory to', 'directory',
2554 '^di\w*/f\w*', 'directory from', 'directory',
2555 '^di\w*/(\d+)', 'directory $1', 'directory',
2572 '^l$', 'directory', 'directory',
2573 '^ll$', 'directory', 'directory',
2574 '^ll/(\d+)', 'directory $1', 'directory',
2579 '^news', 'type news', 'type',
2589 '^r$', 'read', 'read',
2590 '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
2593 '^s/p$', 'send', 'send',
2594 '^sb$', 'send noprivate', 'send',
2595 '^set/home$', 'set/homenode', 'set/homenode',
2596 '^set/nobe', 'unset/beep', 'unset/beep',
2597 '^set/nohe', 'unset/here', 'unset/here',
2598 '^set/noan', 'unset/announce', 'unset/announce',
2599 '^set/nodx', 'unset/dx', 'unset/dx',
2600 '^set/nota', 'unset/talk', 'unset/talk',
2601 '^set/noww', 'unset/wwv', 'unset/wwv',
2602 '^set/nowx', 'unset/wx', 'unset/wx',
2603 '^sh$', 'show', 'show',
2604 '^sh\w*/buck', 'dbshow buck', 'dbshow',
2605 '^sh\w*/bu', 'show/files bulletins', 'show/files',
2606 '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
2607 '^sh\w*/c$', 'show/configuration', 'show/configuration',
2608 '^sh\w*/com', 'dbavail', 'dbavail',
2609 '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
2610 '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
2611 '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
2612 '^sh\w*/email', 'dbshow email', 'dbshow',
2613 '^sh\w*/hftest', 'dbshow hftest', 'dbshow',
2614 '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
2615 '^sh\w*/qsl', 'dbshow qsl', 'dbshow',
2616 '^sh\w*/tnc', 'who', 'who',
2617 '^sh\w*/up', 'show/cluster', 'show/cluster',
2618 '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
2619 '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
2620 '^sp$', 'send', 'send',
2624 '^ta$', 'talk', 'talk',
2625 '^t$', 'talk', 'talk',
2632 '^wx/full', 'wx full', 'wx',
2633 '^wx/sysop', 'wx sysop', 'wx',
2646 You can create aliases for commands at will. Beware though, these may
2647 not always turn out as you think. Care is needed and you need to test
2648 the results once you have set an alias.
2651 1
\b11
\b1.
\b.5
\b5.
\b. C
\bCo
\bon
\bns
\bso
\bol
\ble
\be.
\b.p
\bpl
\bl
2653 In later versions of Spider a simple console program is provided for
2654 the sysop. This has a type ahead buffer with line editing facilities
2655 and colour for spots, announces etc. To use this program, simply use
2656 console.pl instead of client.
2659 To edit the colours, copy /spider/perl/Console.pl to /spider/local and
2660 edit the file with your favourite editor.
2663 1
\b11
\b1.
\b.6
\b6.
\b. U
\bUp
\bpd
\bda
\bat
\bti
\bin
\bng
\bg k
\bke
\bep
\bpl
\ble
\ber
\br d
\bda
\bat
\bta
\ba
2665 Spider has a powerful and flexible show/satellite command. In order
2666 for this to be accurate, the kepler data has to be updated regularly.
2667 In general, this data is available as an email or via cluster mail.
2668 Updating it is simple. First you need to export the mail message as a
2669 file. You do this with the _
\be_
\bx_
\bp_
\bo_
\br_
\bt command from the cluster prompt as
2670 the sysop. For example ...
2674 export 5467 /spider/perl/keps.in
2679 would export message number 5467 as a file called keps.in in the
2680 /spider/perl directory.
2682 Now login to a VT as sysop and cd /spider/perl. There is a command in
2683 the perl directory called _
\bc_
\bo_
\bn_
\bv_
\bk_
\be_
\bp_
\bs_
\b._
\bp_
\bl. All we need to do now is
2684 convert the file like so ...
2688 ./convkeps.pl keps.in
2693 Now go back to the cluster and issue the command ...
2702 That is it! the kepler data has been updated.
2707 1
\b11
\b1.
\b.7
\b7.
\b. T
\bTh
\bhe
\be Q
\bQR
\bRZ
\bZ c
\bca
\bal
\bll
\blb
\bbo
\boo
\bok
\bk
2709 The command _
\bs_
\bh_
\b/_
\bq_
\br_
\bz will only work once you have followed a few simple
2710 steps. First you need to get a user ID and password from qrz.com.
2711 Simply go to the site and create one. Secondly you need to copy the
2712 file /spider/perl/Internet.pm to /spider/local and alter it to match
2713 your user ID and password. You also at this point need to set
2714 $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
2715 proprieter of qrz.com for allowing this access.
2718 1
\b12
\b2.
\b. C
\bCV
\bVS
\bS
2720 CVS stands for "Concurrent Versions System" and the CVS for DXSpider
2721 is held at Sourceforge. This means that it is possible to update your
2722 DXSpider installation to the latest sources by using a few simple
2726 THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST
2727 INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!! THIS
2728 MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!! YOU
2732 DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE
2736 I am of course assuming that you have a machine with both DXSpider and
2737 Internet access running.
2740 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
2741 ENTIRE SPIDER TREE!!
2744 Assuming you are connected to the Internet, you need to login to the
2745 CVS repository and then update your Spider source. There are several
2746 steps which are listed below ...
2749 First login as the user _
\bs_
\by_
\bs_
\bo_
\bp. Next you need to connect to the CVS
2750 repository. You do this with the command below ...
2753 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2757 You will get a password prompt. Simply hit return here and your
2758 machine should return to a normal linux prompt.
2761 What happens next depends on whether you have an existing installation
2762 that you want to update with the latest and greatest or whether you
2763 just want to see what is there and/or run it on a new machine for
2766 If you are installing Spider from CVS then change directory to
2769 If you are wanting to update Spider then cd to /tmp
2773 The next step will create a brand new 'spider' directory in your
2777 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
2781 This command is all on one line.
2784 Hopefully your screen should show you downloading files. The -z3
2785 simply compresses the download to improve speed. When this has
2786 finished, you will have exactly the same as if you had untarred a full
2787 tarball PLUS some extra directories and files that CVS needs to do the
2791 Now if you are doing a new installation, that's it. Carry on as if
2792 you have just downloaded and untarred the lastest tarball.
2795 If you want to upgrade your current installation then do this ...
2799 tar cvfz /tmp/s.tgz spider
2801 tar xvfzp /tmp/s.tgz
2806 This is assuming you downloaded to the /tmp directory of course.
2809 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
2810 permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
2813 Remember to recompile the C client (cd /spider/src; make)
2816 At this point the files have been upgraded. You can (usually) restart
2817 the cluster in your own time. However, if you attempt to use any new
2818 commands or features expect it to be fatal! At least your cluster
2819 will have been restarted then so it will be too late to worry about
2823 Now the magic part! From now on when you want to update, simply
2824 connect to the Internet and then, as the user _
\bs_
\by_
\bs_
\bo_
\bp ...
2834 and your files will be updated. As above, remember to recompile the
2835 "C" client if it has been updated (CVS will tell you) and restart if
2836 any of the perl scripts have been altered or added, again, CVS will
2839 You will find any changes documented in the /spider/Changes file.
2842 1
\b13
\b3.
\b. T
\bTh
\bhe
\be D
\bDX
\bXS
\bSp
\bpi
\bid
\bde
\ber
\br c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd s
\bse
\bet
\bt
2844 Below is a complete list of commands available from the cluster
2845 prompt. Most maintenance tasks are automatic but there are some
2846 commands that are useful for a sysop. These are listed below in
2847 alphabetical order. The number in brackets following the command name
2848 is the permissions level needed to use the command.
2851 1
\b13
\b3.
\b.1
\b1.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be (
\b(0
\b0)
\b)
2853 a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set an accept filter line for announce
2856 Create an 'accept this announce' line for a filter.
2858 An accept filter line means that if the announce matches this filter
2859 it is passed onto the user. See HELP FILTERS for more info. Please
2860 read this to understand how filters work - it will save a lot of grief
2863 You can use any of the following things in this line:-
2867 info <string> eg: iota or qsl
2868 by <prefixes> eg: G,M,2
2870 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2871 origin_itu <numbers>
2872 origin_zone <numbers>
2877 wx 1 filter WX announces
2878 dest <prefixes> eg: 6MUK,WDX (distros)
2888 acc/ann 2 by_zone 14,15,16
2889 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
2903 This filter would only allow announces that were posted buy UK
2904 stations. You can use the tag 'all' to accept everything eg:
2910 but this probably for advanced users...
2913 1
\b13
\b3.
\b.2
\b2.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be (
\b(e
\bex
\bxt
\bte
\ben
\bnd
\bde
\bed
\bd f
\bfo
\bor
\br s
\bsy
\bys
\bso
\bop
\bps
\bs)
\b) (
\b(8
\b8)
\b)
2915 a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[i
\bin
\bnp
\bpu
\but
\bt]
\b] [
\b[0
\b0-
\b-9
\b9]
\b]<
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Announce filter sysop
2919 This version allows a sysop to set a filter for a callsign as well as
2920 the default for nodes and users eg:-
2925 accept/ann input node_default by G,M,2
2926 accept/ann user_default by G,M,2
2932 1
\b13
\b3.
\b.3
\b3.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs (
\b(0
\b0)
\b)
2934 a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set an accept filter line for spots
2937 Create an 'accept this spot' line for a filter.
2940 An accept filter line means that if the spot matches this filter it is
2941 passed onto the user. See HELP FILTERS for more info. Please read this
2942 to understand how filters work - it will save a lot of grief later on.
2944 You can use any of the following things in this line:-
2948 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
2949 on <range> same as 'freq'
2950 call <prefixes> eg: G,PA,HB9
2951 info <string> eg: iota or qsl
2953 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2966 For frequencies, you can use any of the band names defined in
2967 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
2968 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
2969 this is more efficient than saying simply: freq HF (but don't get too
2976 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2981 You can use the tag 'all' to accept everything, eg:
2990 but this probably for advanced users...
2993 1
\b13
\b3.
\b.4
\b4.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs (
\b(e
\bex
\bxt
\bte
\ben
\bnd
\bde
\bed
\bd f
\bfo
\bor
\br s
\bsy
\bys
\bso
\bop
\bps
\bs)
\b) (
\b(8
\b8)
\b)
2995 a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[i
\bin
\bnp
\bpu
\but
\bt]
\b] [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Spot filter sysop version
2998 This version allows a sysop to set a filter for a callsign as well as
2999 the default for nodes and users eg:-
3003 accept/spot db0sue-7 1 by_zone 14,15,16
3004 accept/spot node_default all
3005 set/hops node_default 10
3007 accept/spot user_default by G,M,2
3013 1
\b13
\b3.
\b.5
\b5.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bwc
\bcy
\by (
\b(0
\b0)
\b)
3015 a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bwc
\bcy
\by [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> set an accept WCY filter
3018 It is unlikely that you will want to do this, but if you do then you
3019 can filter on the following fields:-
3023 by <prefixes> eg: G,M,2
3025 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3026 origin_itu <numbers>
3027 origin_zone <numbers>
3037 There are no examples because WCY Broadcasts only come from one place
3038 and you either want them or not (see UNSET/WCY if you don't want
3041 This command is really provided for future use.
3043 See HELP FILTER for information.
3046 1
\b13
\b3.
\b.6
\b6.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bwc
\bcy
\by (
\b(e
\bex
\bxt
\bte
\ben
\bnd
\bde
\bed
\bd f
\bfo
\bor
\br s
\bsy
\bys
\bso
\bop
\bps
\bs)
\b) (
\b(8
\b8)
\b)
3048 a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bwc
\bcy
\by <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[i
\bin
\bnp
\bpu
\but
\bt]
\b] [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> WCY filter sysop version
3051 This version allows a sysop to set a filter for a callsign as well as
3052 the default for nodes and users eg:-
3056 accept/wcy node_default all
3057 set/hops node_default 10
3063 1
\b13
\b3.
\b.7
\b7.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bww
\bwv
\bv (
\b(0
\b0)
\b)
3065 a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bww
\bwv
\bv [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set an accept WWV filter
3068 It is unlikely that you will want to do this, but if you do then you
3069 can filter on the following fields:-
3073 by <prefixes> eg: G,M,2
3075 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3076 origin_itu <numbers>
3077 origin_zone <numbers>
3090 accept/wwv by_zone 4
3095 is probably the only useful thing to do (which will only show WWV
3096 broadcasts by stations in the US).
3098 See HELP FILTER for information.
3103 1
\b13
\b3.
\b.8
\b8.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bww
\bwv
\bv (
\b(e
\bex
\bxt
\bte
\ben
\bnd
\bde
\bed
\bd f
\bfo
\bor
\br s
\bsy
\bys
\bso
\bop
\bps
\bs)
\b) (
\b(8
\b8)
\b)
3105 a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bww
\bwv
\bv <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[i
\bin
\bnp
\bpu
\but
\bt]
\b] [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> WWV filter sysop version
3108 This version allows a sysop to set a filter for a callsign as well as
3109 the default for nodes and users eg:-
3113 accept/wwv db0sue-7 1 by_zone 4
3114 accept/wwv node_default all
3115 set/hops node_default 10
3117 accept/wwv user_default by W,K
3123 1
\b13
\b3.
\b.9
\b9.
\b. a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be (
\b(0
\b0)
\b)
3125 a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send an announcement to local users
3128 Send an announcement to LOCAL users only, where <text> is the text of
3129 the announcement you wish to broadcast
3132 1
\b13
\b3.
\b.1
\b10
\b0.
\b. a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be f
\bfu
\bul
\bll
\bl (
\b(0
\b0)
\b)
3134 a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be f
\bfu
\bul
\bll
\bl <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send an announcement cluster wide
3137 This command will send your announcement across the whole cluster
3142 1
\b13
\b3.
\b.1
\b11
\b1.
\b. a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be s
\bsy
\bys
\bso
\bop
\bp (
\b(5
\b5)
\b)
3144 a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be s
\bsy
\bys
\bso
\bop
\bp <
\b<t
\bte
\bex
\bxt
\bt>
\b>
3147 Send an announcement to Sysops only
3150 1
\b13
\b3.
\b.1
\b12
\b2.
\b. a
\bap
\bpr
\bro
\bop
\bpo
\bos
\bs (
\b(0
\b0)
\b)
3152 a
\bap
\bpr
\bro
\bop
\bpo
\bos
\bs <
\b<s
\bst
\btr
\bri
\bin
\bng
\bg>
\b> Search the help database
3155 Search the help database for <string> (it isn't case sensitive), and
3156 print the names of all the commands that may be relevant.
3159 1
\b13
\b3.
\b.1
\b13
\b3.
\b. b
\bby
\bye
\be (
\b(0
\b0)
\b)
3161 b
\bby
\bye
\be Exit from the cluster
3164 This will disconnect you from the cluster
3169 1
\b13
\b3.
\b.1
\b14
\b4.
\b. c
\bca
\bat
\btc
\bch
\bhu
\bup
\bp (
\b(5
\b5)
\b)
3171 c
\bca
\bat
\btc
\bch
\bhu
\bup
\bp <
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> A
\bAl
\bll
\bl|
\b|[
\b[<
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> .
\b..
\b..
\b.]
\b] Mark a message as sent
3174 When you send messages the fact that you have forwarded it to another
3175 node is remembered so that it isn't sent again. When you have a new
3176 partner node and you add their callsign to your /spider/msg/forward.pl
3177 file, all outstanding non-private messages will be forwarded to them.
3178 This may well be ALL the non-private messages. You can prevent this by
3179 using these commmands:-
3184 catchup GB7DJK 300 301 302 303 500-510
3189 and to undo what you have just done:-
3193 uncatchup GB7DJK all
3194 uncatchup GB7DJK 300 301 302 303 500-510
3199 which will arrange for them to be forward candidates again.
3201 Order is not important.
3204 1
\b13
\b3.
\b.1
\b15
\b5.
\b. c
\bcl
\ble
\bea
\bar
\br/
\b/s
\bsp
\bpo
\bot
\bts
\bs (
\b(0
\b0)
\b)
3206 c
\bcl
\ble
\bea
\bar
\br/
\b/s
\bsp
\bpo
\bot
\bts
\bs [
\b[1
\b1|
\b|a
\bal
\bll
\bl]
\b] Clear a spot filter line
3209 This command allows you to clear (remove) a line in a spot filter or
3210 to remove the whole filter.
3212 If you have a filter:-
3217 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
3231 you will be left with:-
3235 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
3249 the filter will be completely removed.
3253 1
\b13
\b3.
\b.1
\b16
\b6.
\b. c
\bco
\bon
\bnn
\bne
\bec
\bct
\bt (
\b(5
\b5)
\b)
3255 c
\bco
\bon
\bnn
\bne
\bec
\bct
\bt <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> Start a connection to another DX Cluster
3258 Start a connection process that will culminate in a new connection to
3259 the DX cluster <callsign>. This process creates a new 'client' process
3260 which will use the script in /spider/connect/<callsign> to effect the
3261 'chat' exchange necessary to traverse the network(s) to logon to the
3265 1
\b13
\b3.
\b.1
\b17
\b7.
\b. d
\bdb
\bba
\bav
\bva
\bai
\bil
\bl (
\b(0
\b0)
\b)
3267 d
\bdb
\bba
\bav
\bva
\bai
\bil
\bl Show a list of all the databases in the system
3270 The title says it all really, this command lists all the databases
3271 defined in the system. It is also aliased to SHOW/COMMAND.
3274 1
\b13
\b3.
\b.1
\b18
\b8.
\b. d
\bdb
\bbc
\bcr
\bre
\bea
\bat
\bte
\be (
\b(9
\b9)
\b)
3276 d
\bdb
\bbc
\bcr
\bre
\bea
\bat
\bte
\be <
\b<n
\bna
\bam
\bme
\be>
\b> Create a database entry
3277 d
\bdb
\bbc
\bcr
\bre
\bea
\bat
\bte
\be <
\b<n
\bna
\bam
\bme
\be>
\b> c
\bch
\bha
\bai
\bin
\bn <
\b<n
\bna
\bam
\bme
\be>
\b> [
\b[<
\b<n
\bna
\bam
\bme
\be>
\b>.
\b..
\b.]
\b] Create a chained database
3279 d
\bdb
\bbc
\bcr
\bre
\bea
\bat
\bte
\be <
\b<n
\bna
\bam
\bme
\be>
\b> r
\bre
\bem
\bmo
\bot
\bte
\be <
\b<n
\bno
\bod
\bde
\be>
\b> Create a remote database entry
3282 DBCREATE allows you to define a database in the system. It doesn't
3283 actually create anything, just defines it.
3285 The databases that are created are simple DB_File hash databases, they
3286 are therefore already 'indexed'.
3288 You can define a local database with the first form of the command eg:
3292 You can also chain databases with the addition of the 'chain' keyword.
3293 This will search each database one after the other. A typical example
3296 DBCREATE sdx_qsl chain sql_ad
3298 No checking is done to see if the any of the chained databases exist,
3299 in fact it is usually better to do the above statement first then do
3300 each of the chained databases.
3301 Databases can exist offsite. To define a database that lives on
3304 DBCREATE buckmaster remote gb7dxc
3306 Remote databases cannot be chained; however, the last database in a a
3307 chain can be a remote database eg:
3309 DBCREATE qsl chain gb7dxc
3311 To see what databases have been defined do:
3313 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
3315 It would be normal for you to add an entry into your local Aliases
3316 file to allow people to use the 'SHOW/<dbname>' style syntax. So you
3317 would need to add a line like:-
3324 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
3336 to work as they may be used to.
3338 See DBIMPORT for the importing of existing AK1A format data to
3339 databases. See DBSHOW for generic database enquiry
3342 1
\b13
\b3.
\b.1
\b19
\b9.
\b. d
\bdb
\bbi
\bim
\bmp
\bpo
\bor
\brt
\bt (
\b(9
\b9)
\b)
3344 d
\bdb
\bbi
\bim
\bmp
\bpo
\bor
\brt
\bt <
\b<d
\bdb
\bbn
\bna
\bam
\bme
\be>
\b> Import AK1A data into a database
3347 If you want to import or update data in bulk to a database you can use
3348 this command. It will either create or update entries into an existing
3349 database. For example:-
3351 DBIMPORT oblast /tmp/OBLAST.FUL
3353 will import the standard OBLAST database that comes with AK1A into the
3354 oblast database held locally.
3357 1
\b13
\b3.
\b.2
\b20
\b0.
\b. d
\bdb
\bbr
\bre
\bem
\bmo
\bov
\bve
\be (
\b(9
\b9)
\b)
3359 d
\bdb
\bbr
\bre
\bem
\bmo
\bov
\bve
\be <
\b<d
\bdb
\bbn
\bna
\bam
\bme
\be>
\b> Delete a database
3362 DBREMOVE will completely remove a database entry and also delete any
3363 data file that is associated with it.
3365 There is no warning, no comeback, no safety net.
3371 will remove the oblast database from the system and it will also
3372 remove the associated datafile.
3376 There is no warning, no comeback, no safety net.
3378 You have been warned.
3381 1
\b13
\b3.
\b.2
\b21
\b1.
\b. d
\bdb
\bbs
\bsh
\bho
\bow
\bw (
\b(0
\b0)
\b)
3383 d
\bdb
\bbs
\bsh
\bho
\bow
\bw <
\b<d
\bdb
\bbn
\bna
\bam
\bme
\be>
\b> <
\b<k
\bke
\bey
\by>
\b> Display an entry, if it exists, in a database
3386 This is the generic user interface to the database to the database
3387 system. It is expected that the sysop will add an entry to the local
3388 Aliases file so that users can use the more familiar AK1A style of
3398 but if he hasn't and the database really does exist (use DBAVAIL or
3399 SHOW/COMMAND to find out) you can do the same thing with:
3410 1
\b13
\b3.
\b.2
\b22
\b2.
\b. d
\bde
\beb
\bbu
\bug
\bg (
\b(9
\b9)
\b)
3412 d
\bde
\beb
\bbu
\bug
\bg Set the cluster program into debug mode
3415 Executing this command will only have an effect if you are running the
3416 cluster in debug mode i.e.
3425 It will interrupt the cluster just after the debug command has
3429 1
\b13
\b3.
\b.2
\b23
\b3.
\b. d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by (
\b(0
\b0)
\b)
3431 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by List messages
3432 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by o
\bow
\bwn
\bn List your own messages
3433 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by n
\bne
\bew
\bw List all new messages
3434 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by t
\bto
\bo <
\b<c
\bca
\bal
\bll
\bl>
\b> List all messages to <call>
3435 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by f
\bfr
\bro
\bom
\bm <
\b<c
\bca
\bal
\bll
\bl>
\b> List all messages from <call>
3436 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by s
\bsu
\bub
\bbj
\bje
\bec
\bct
\bt <
\b<s
\bst
\btr
\bri
\bin
\bng
\bg>
\b> List all messages with <string> in subject
3437 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by <
\b<n
\bnn
\bn>
\b> List last <nn> messages
3438 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by <
\b<f
\bfr
\bro
\bom
\bm>
\b>-
\b-<
\b<t
\bto
\bo>
\b> List messages <from> message <to> message
3441 List the messages in the messages directory.
3443 If there is a 'p' one space after the message number then it is a
3444 personal message. If there is a '-' between the message number and the
3446 You can use shell escape characters such as '*' and '?' in the <call>
3449 You can combine some of the various directory commands together eg:-
3455 DIR SUBJECT IOTA 200-250
3460 You can abbreviate all the commands to one letter and use ak1a
3473 1
\b13
\b3.
\b.2
\b24
\b4.
\b. d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by (
\b(e
\bex
\bxt
\bte
\ben
\bnd
\bde
\bed
\bd f
\bfo
\bor
\br s
\bsy
\bys
\bso
\bop
\bps
\bs)
\b) (
\b(5
\b5)
\b)
3475 Works just like the user command except that sysops can see ALL
3479 1
\b13
\b3.
\b.2
\b25
\b5.
\b. d
\bdi
\bis
\bsc
\bco
\bon
\bnn
\bne
\bec
\bct
\bt (
\b(8
\b8)
\b)
3481 d
\bdi
\bis
\bsc
\bco
\bon
\bnn
\bne
\bec
\bct
\bt <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[<
\b<c
\bca
\bal
\bll
\bl>
\b> .
\b..
\b..
\b.]
\b] Disconnect a user or node
3484 Disconnect any <call> connected locally
3487 1
\b13
\b3.
\b.2
\b26
\b6.
\b. d
\bdx
\bx (
\b(0
\b0)
\b)
3489 d
\bdx
\bx [
\b[b
\bby
\by <
\b<c
\bca
\bal
\bll
\bl>
\b>]
\b] <
\b<f
\bfr
\bre
\beq
\bq>
\b> <
\b<c
\bca
\bal
\bll
\bl>
\b> <
\b<r
\bre
\bem
\bma
\bar
\brk
\bks
\bs>
\b> Send a DX spot
3492 This is how you send a DX Spot to other users. You can, in fact, now
3493 enter the <freq> and the <call> either way round.
3506 will all give the same result. You can add some remarks to the end of
3507 the command and they will be added to the spot.
3511 DX FR0G 144600 this is a test
3516 You can credit someone else by saying:-
3520 DX by G1TLH FR0G 144.600 he isn't on the cluster
3525 The <freq> is compared against the available bands set up in the
3526 cluster. See SHOW/BANDS for more information.
3529 1
\b13
\b3.
\b.2
\b27
\b7.
\b. e
\bex
\bxp
\bpo
\bor
\brt
\bt (
\b(9
\b9)
\b)
3531 e
\bex
\bxp
\bpo
\bor
\brt
\bt <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> <
\b<f
\bfi
\bil
\ble
\ben
\bna
\bam
\bme
\be>
\b> Export a message to a file
3534 Export a message to a file. This command can only be executed on a
3535 local console with a fully privileged user. The file produced will be
3536 in a form ready to be imported back into the cluster by placing it in
3537 the import directory (/spider/msg/import).
3539 This command cannot overwrite an existing file. This is to provide
3540 some measure of security. Any files written will owned by the same
3541 user as the main cluster, otherwise you can put the new files anywhere
3542 the cluster can access. For example:-
3547 1
\b13
\b3.
\b.2
\b28
\b8.
\b. e
\bex
\bxp
\bpo
\bor
\brt
\bt_
\b_u
\bus
\bse
\ber
\brs
\bs (
\b(9
\b9)
\b)
3549 e
\bex
\bxp
\bpo
\bor
\brt
\bt_
\b_u
\bus
\bse
\ber
\brs
\bs [
\b[<
\b<f
\bfi
\bil
\ble
\ben
\bna
\bam
\bme
\be>
\b>]
\b] Export the users database to ascii
3552 Export the users database to a file in ascii format. If no filename is
3553 given then it will export the file to /spider/data/user_asc.
3555 If the file already exists it will be renamed to <filename>.o. In fact
3556 up to 5 generations of the file can be kept each one with an extra 'o'
3559 BE WARNED: this will write to any file you have write access to. No
3560 check is made on the filename (if any) that you specify.
3565 1
\b13
\b3.
\b.2
\b29
\b9.
\b. f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd/
\b/l
\bla
\bat
\btl
\blo
\bon
\bng
\bg (
\b(8
\b8)
\b)
3567 f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd/
\b/l
\bla
\bat
\btl
\blo
\bon
\bng
\bg <
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> Send latitude and longitude information to
3571 This command sends all the latitude and longitude information that
3572 your cluster is holding against callsigns. One advantage of recieving
3573 this information is that more locator information is held by you.
3574 This means that more locators are given on the DX line assuming you
3575 have _
\bs_
\be_
\bt_
\b/_
\bd_
\bx_
\bg_
\br_
\bi_
\bd enabled. This could be a LOT of information though,
3576 so it is not recommended on slow links.
3579 1
\b13
\b3.
\b.3
\b30
\b0.
\b. f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd/
\b/o
\bop
\bpe
\ber
\brn
\bna
\bam
\bme
\be (
\b(1
\b1)
\b)
3581 f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd/
\b/o
\bop
\bpe
\ber
\brn
\bna
\bam
\bme
\be <
\b<c
\bca
\bal
\bll
\bl>
\b> Send out information on this <call> to all
3585 This command sends out any information held in the user file which can
3586 be broadcast in PC41 protocol packets. This information is Name, QTH,
3587 Location and Homenode. PC41s are only sent for the information that is
3591 1
\b13
\b3.
\b.3
\b31
\b1.
\b. h
\bhe
\bel
\blp
\bp (
\b(0
\b0)
\b)
3593 h
\bhe
\bel
\blp
\bp <
\b<c
\bcm
\bmd
\bd>
\b> Get help on a command
3596 All commands can be abbreviated, so SHOW/DX can be abbreviated to
3597 SH/DX, ANNOUNCE can be shortened to AN and so on.
3599 Look at the APROPOS <string> command which will search the help
3600 database for the <string> you specify and give you a list of likely
3601 commands to look at with HELP.
3604 1
\b13
\b3.
\b.3
\b32
\b2.
\b. i
\bin
\bni
\bit
\bt (
\b(5
\b5)
\b)
3606 i
\bin
\bni
\bit
\bt <
\b<n
\bno
\bod
\bde
\be c
\bca
\bal
\bll
\bl>
\b> Re-initialise a link to an AK1A compatible node
3609 This command attempts to re-initialise a link to a (usually) AK1A node
3610 that has got confused, usually by a protocol loop of some kind. It may
3611 work - but you usually will be better off simply disconnecting it (or
3612 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
3615 Best of luck - you will need it.
3618 1
\b13
\b3.
\b.3
\b33
\b3.
\b. k
\bki
\bil
\bll
\bl (
\b(0
\b0)
\b)
3620 k
\bki
\bil
\bll
\bl <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> [
\b[<
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> .
\b..
\b.]
\b] Delete a message from the local system
3623 Delete a message from the local system. You will only be able to
3624 delete messages that you have originated or been sent (unless you are
3631 1
\b13
\b3.
\b.3
\b34
\b4.
\b. k
\bki
\bil
\bll
\bl (
\b(5
\b5)
\b)
3633 k
\bki
\bil
\bll
\bl <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> [
\b[<
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> .
\b..
\b..
\b.]
\b] Remove or erase a message from the system
3634 k
\bki
\bil
\bll
\bl f
\bfr
\bro
\bom
\bm <
\b<c
\bca
\bal
\bll
\bl>
\b> Remove all messages from a callsign
3635 k
\bki
\bil
\bll
\bl t
\bto
\bo <
\b<c
\bca
\bal
\bll
\bl>
\b> Remove all messages to a callsign
3638 You can get rid of any message to or originating from your callsign
3639 using this command. You can remove more than one message at a time.
3641 As a sysop you can kill any message on the system.
3644 1
\b13
\b3.
\b.3
\b35
\b5.
\b. k
\bki
\bil
\bll
\bl f
\bfu
\bul
\bll
\bl (
\b(5
\b5)
\b)
3646 k
\bki
\bil
\bll
\bl f
\bfu
\bul
\bll
\bl <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> [
\b[<
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b>]
\b] Delete a message from the whole cluster
3649 Delete a message (usually a 'bulletin') from the whole cluster system.
3651 This uses the subject field, so any messages that have exactly the
3652 same subject will be deleted. Beware!
3655 1
\b13
\b3.
\b.3
\b36
\b6.
\b. l
\bli
\bin
\bnk
\bks
\bs (
\b(0
\b0)
\b)
3657 l
\bli
\bin
\bnk
\bks
\bs Show which nodes are physically connected
3660 This is a quick listing that shows which links are connected and some
3661 information about them. See WHO for a list of all connections.
3665 1
\b13
\b3.
\b.3
\b37
\b7.
\b. l
\blo
\boa
\bad
\bd/
\b/a
\bal
\bli
\bia
\bas
\bse
\bes
\bs (
\b(9
\b9)
\b)
3667 l
\blo
\boa
\bad
\bd/
\b/a
\bal
\bli
\bia
\bas
\bse
\bes
\bs Reload the command alias table
3670 Reload the /spider/cmd/Aliases file after you have editted it. You
3671 will need to do this if you change this file whilst the cluster is
3672 running in order for the changes to take effect.
3676 1
\b13
\b3.
\b.3
\b38
\b8.
\b. l
\blo
\boa
\bad
\bd/
\b/b
\bba
\bad
\bdd
\bdx
\bx (
\b(9
\b9)
\b)
3678 l
\blo
\boa
\bad
\bd/
\b/b
\bba
\bad
\bdd
\bdx
\bx Reload the bad DX table
3681 Reload the /spider/data/baddx.pl file if you have changed it manually
3682 whilst the cluster is running. This table contains the DX Calls that,
3683 if spotted, will not be passed on. FR0G and TEST are classic examples.
3686 1
\b13
\b3.
\b.3
\b39
\b9.
\b. l
\blo
\boa
\bad
\bd/
\b/b
\bba
\bad
\bdm
\bms
\bsg
\bg (
\b(9
\b9)
\b)
3688 l
\blo
\boa
\bad
\bd/
\b/b
\bba
\bad
\bdm
\bms
\bsg
\bg Reload the bad message table
3691 Reload the /spider/msg/badmsg.pl file if you have changed it manually
3692 whilst the cluster is running. This table contains a number of perl
3693 regular expressions which are searched for in the fields targetted of
3694 each message. If any of them match then that message is immediately
3697 1
\b13
\b3.
\b.4
\b40
\b0.
\b. l
\blo
\boa
\bad
\bd/
\b/b
\bba
\bad
\bdw
\bwo
\bor
\brd
\bds
\bs (
\b(9
\b9)
\b)
3699 l
\blo
\boa
\bad
\bd/
\b/b
\bba
\bad
\bdw
\bwo
\bor
\brd
\bds
\bs Reload the badwords file
3702 Reload the /spider/data/badwords file if you have changed it manually
3703 whilst the cluster is running. This file contains a list of words
3704 which, if found on certain text portions of PC protocol, will cause
3705 those protocol frames to be rejected. It will all put out a message if
3706 any of these words are used on the announce, dx and talk commands. The
3707 words can be one or more on a line, lines starting with '#' are
3711 1
\b13
\b3.
\b.4
\b41
\b1.
\b. l
\blo
\boa
\bad
\bd/
\b/b
\bba
\ban
\bnd
\bds
\bs (
\b(9
\b9)
\b)
3713 l
\blo
\boa
\bad
\bd/
\b/b
\bba
\ban
\bnd
\bds
\bs Reload the band limits table
3716 Reload the /spider/data/bands.pl file if you have changed it manually
3717 whilst the cluster is running.
3720 1
\b13
\b3.
\b.4
\b42
\b2.
\b. l
\blo
\boa
\bad
\bd/
\b/c
\bcm
\bmd
\bd_
\b_c
\bca
\bac
\bch
\bhe
\be (
\b(9
\b9)
\b)
3722 l
\blo
\boa
\bad
\bd/
\b/c
\bcm
\bmd
\bd_
\b_c
\bca
\bac
\bch
\bhe
\be Reload the automatic command cache
3725 Normally, if you change a command file in the cmd or local_cmd tree it
3726 will automatially be picked up by the cluster program. Sometimes it
3727 can get confused if you are doing a lot of moving commands about or
3728 delete a command in the local_cmd tree and want to use the normal one
3729 again. Execute this command to reset everything back to the state it
3730 was just after a cluster restart.
3733 1
\b13
\b3.
\b.4
\b43
\b3.
\b. l
\blo
\boa
\bad
\bd/
\b/f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd (
\b(9
\b9)
\b)
3735 l
\blo
\boa
\bad
\bd/
\b/f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd Reload the msg forwarding routing table
3737 Reload the /spider/msg/forward.pl file if you have changed it manually
3738 whilst the cluster is running.
3741 1
\b13
\b3.
\b.4
\b44
\b4.
\b. l
\blo
\boa
\bad
\bd/
\b/m
\bme
\bes
\bss
\bsa
\bag
\bge
\bes
\bs (
\b(9
\b9)
\b)
3743 l
\blo
\boa
\bad
\bd/
\b/m
\bme
\bes
\bss
\bsa
\bag
\bge
\bes
\bs Reload the system messages file
3746 If you change the /spider/perl/Messages file (usually whilst
3747 fiddling/writing ne commands) you can have them take effect during a
3748 cluster session by executing this command. You need to do this if get
3751 unknown message 'xxxx' in lang 'en'
3754 1
\b13
\b3.
\b.4
\b45
\b5.
\b. l
\blo
\boa
\bad
\bd/
\b/p
\bpr
\bre
\bef
\bfi
\bix
\bxe
\bes
\bs (
\b(9
\b9)
\b)
3756 l
\blo
\boa
\bad
\bd/
\b/p
\bpr
\bre
\bef
\bfi
\bix
\bxe
\bes
\bs Reload the prefix table
3759 Reload the /spider/data/prefix_data.pl file if you have changed it
3760 manually whilst the cluster is running.
3763 1
\b13
\b3.
\b.4
\b46
\b6.
\b. m
\bme
\ber
\brg
\bge
\be (
\b(5
\b5)
\b)
3765 m
\bme
\ber
\brg
\bge
\be <
\b<n
\bno
\bod
\bde
\be>
\b> [
\b[<
\b<n
\bno
\bo s
\bsp
\bpo
\bot
\bts
\bs>
\b>/
\b/<
\b<n
\bno
\bo w
\bww
\bwv
\bv>
\b>]
\b] Ask for the latest spots and WWV
3768 MERGE allows you to bring your spot and wwv database up to date. By
3769 default it will request the last 10 spots and 5 WWVs from the node you
3770 select. The node must be connected locally.
3772 You can request any number of spots or wwv and although they will be
3773 appended to your databases they will not duplicate any that have
3774 recently been added (the last 2 days for spots and last month for WWV
3778 1
\b13
\b3.
\b.4
\b47
\b7.
\b. m
\bms
\bsg
\bg (
\b(9
\b9)
\b)
3780 m
\bms
\bsg
\bg <
\b<c
\bcm
\bmd
\bd>
\b> <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> [
\b[d
\bda
\bat
\bta
\ba .
\b..
\b..
\b.]
\b] Alter various message parameters
3783 Alter message parameters like To, From, Subject, whether private or
3784 bulletin or return receipt (RR) is required or whether to keep this
3785 message from timing out.
3789 MSG TO <msgno> <call> - change TO callsign to <call>
3790 MSG FRom <msgno> <call> - change FROM callsign to <call>
3791 MSG PRrivate <msgno> - set private flag
3792 MSG NOPRrivate <msgno> - unset private flag
3793 MSG RR <msgno> - set RR flag
3794 MSG NORR <msgno> - unset RR flag
3795 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
3796 MSG NOKEep <msgno> - unset the keep flag
3797 MSG SUbject <msgno> <new> - change the subject to <new>
3798 MSG WAittime <msgno> - remove any waitting time for this message
3799 MSG NOREad <msgno> - mark message as unread
3800 MSG REad <msgno> - mark message as read
3801 MSG QUeue - queue any outstanding bulletins
3802 MSG QUeue 1 - queue any outstanding private messages
3807 You can look at the status of a message by using:-
3811 This will display more information on the message than DIR does.
3814 1
\b13
\b3.
\b.4
\b48
\b8.
\b. p
\bpc
\bc (
\b(8
\b8)
\b)
3816 p
\bpc
\bc <
\b<c
\bca
\bal
\bll
\bl>
\b> <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send text (eg PC Protocol) to <call>
3819 Send some arbitrary text to a locally connected callsign. No
3820 processing is done on the text. This command allows you to send PC
3821 Protocol to unstick things if problems arise (messages get stuck etc).
3824 pc gb7djk PC33^GB7TLH^GB7DJK^400^
3826 You can also use in the same way as a talk command to a connected user
3827 but without any processing, added of "from <blah> to <blah>" or
3829 pc G1TLH Try doing that properly!!!
3832 1
\b13
\b3.
\b.4
\b49
\b9.
\b. p
\bpi
\bin
\bng
\bg (
\b(1
\b1)
\b)
3834 p
\bpi
\bin
\bng
\bg <
\b<n
\bno
\bod
\bde
\be>
\b> Check the link quality between nodes
3837 his command allows you to send a frame to another cluster node on the
3838 network and get a return frame. The time it takes to do this is a
3839 good indication of the quality of the link. The actual time it takes
3840 is output to the console in seconds. Any visible cluster node can be
3845 1
\b13
\b3.
\b.5
\b50
\b0.
\b. r
\brc
\bcm
\bmd
\bd (
\b(1
\b1)
\b)
3847 r
\brc
\bcm
\bmd
\bd <
\b<n
\bno
\bod
\bde
\be c
\bca
\bal
\bll
\bl>
\b> <
\b<c
\bcm
\bmd
\bd>
\b> Send a command to another DX cluster
3850 This command allows you to send nearly any command to another DX
3851 Cluster node that is connected to the system.
3853 Whether you get any output is dependant on a) whether the other system
3854 knows that the node callsign of this cluster is in fact a node b)
3855 whether the other system is allowing RCMDs from this node and c)
3856 whether you have permission to send this command at all.
3859 1
\b13
\b3.
\b.5
\b51
\b1.
\b. r
\bre
\bea
\bad
\bd (
\b(0
\b0)
\b)
3861 r
\bre
\bea
\bad
\bd Read the next unread personal message addressed to you
3862 r
\bre
\bea
\bad
\bd <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Read the specified message
3865 You can read any messages that are sent as 'non-personal' and also any
3866 message either sent by or sent to your callsign.
3870 1
\b13
\b3.
\b.5
\b52
\b2.
\b. r
\bre
\bea
\bad
\bd (
\b(e
\bex
\bxt
\bte
\ben
\bnd
\bde
\bed
\bd f
\bfo
\bor
\br s
\bsy
\bys
\bso
\bop
\bps
\bs)
\b) (
\b(5
\b5)
\b)
3872 r
\bre
\bea
\bad
\bd <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Read a message on the system
3875 As a sysop you may read any message on the system
3878 1
\b13
\b3.
\b.5
\b53
\b3.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be
3880 r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set a reject filter for announce
3883 Create an 'reject this announce' line for a filter.
3885 An reject filter line means that if the announce matches this filter
3886 it is passed onto the user. See HELP FILTERS for more info. Please
3887 read this to understand how filters work - it will save a lot of grief
3890 You can use any of the following things in this line:-
3895 info <string> eg: iota or qsl
3896 by <prefixes> eg: G,M,2
3898 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3899 origin_itu <numbers>
3900 origin_zone <numbers>
3905 wx 1 filter WX announces
3906 dest <prefixes> eg: 6MUK,WDX (distros)
3915 rej/ann by_zone 14,15,16 and not by G,M,2
3920 You can use the tag 'all' to reject everything eg:
3929 but this probably for advanced users...
3932 1
\b13
\b3.
\b.5
\b54
\b4.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be (
\b(e
\bex
\bxt
\bte
\ben
\bnd
\bde
\bed
\bd f
\bfo
\bor
\br s
\bsy
\bys
\bso
\bop
\bps
\bs)
\b) (
\b(8
\b8)
\b)
3934 r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[i
\bin
\bnp
\bpu
\but
\bt]
\b] [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Announce filter sysop
3938 This version allows a sysop to set a filter for a callsign as well as
3939 the default for nodes and users eg:-
3944 reject/ann input node_default by G,M,2
3945 reject/ann user_default by G,M,2
3951 1
\b13
\b3.
\b.5
\b55
\b5.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs (
\b(0
\b0)
\b)
3953 r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set a reject filter line for spots
3956 Create a 'reject this spot' line for a filter.
3958 A reject filter line means that if the spot matches this filter it is
3959 dumped (not passed on). See HELP FILTERS for more info. Please read
3960 this to understand how filters work - it will save a lot of grief
3963 You can use any of the following things in this line:-
3967 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
3968 on <range> same as 'freq'
3969 call <prefixes> eg: G,PA,HB9
3970 info <string> eg: iota or qsl
3972 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3984 For frequencies, you can use any of the band names defined in
3985 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
3986 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
3987 this is more efficient than saying simply: on HF (but don't get too
3995 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
4000 You can use the tag 'all' to reject everything eg:
4009 but this probably for advanced users...
4012 1
\b13
\b3.
\b.5
\b56
\b6.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs (
\b(e
\bex
\bxt
\bte
\ben
\bnd
\bde
\bed
\bd f
\bfo
\bor
\br s
\bsy
\bys
\bso
\bop
\bps
\bs)
\b) (
\b(8
\b8)
\b)
4014 r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[i
\bin
\bnp
\bpu
\but
\bt]
\b] [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Reject spot filter sysop
4018 This version allows a sysop to set a filter for a callsign as well as
4019 the default for nodes and users eg:-
4027 reject/spot db0sue-7 1 by_zone 14,15,16
4028 reject/spot node_default all
4029 set/hops node_default 10
4031 reject/spot user_default by G,M,2
4037 1
\b13
\b3.
\b.5
\b57
\b7.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bwc
\bcy
\by (
\b(0
\b0)
\b)
4039 r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bwc
\bcy
\by [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set a reject WCY filter
4042 It is unlikely that you will want to do this, but if you do then you
4043 can filter on the following fields:-
4047 by <prefixes> eg: G,M,2
4049 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
4050 origin_itu <numbers>
4051 origin_zone <numbers>
4060 There are no examples because WCY Broadcasts only come from one place
4061 and you either want them or not (see UNSET/WCY if you don't want
4064 This command is really provided for future use.
4066 See HELP FILTER for information.
4069 1
\b13
\b3.
\b.5
\b58
\b8.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bwc
\bcy
\by (
\b(e
\bex
\bxt
\bte
\ben
\bnd
\bde
\bed
\bd f
\bfo
\bor
\br s
\bsy
\bys
\bso
\bop
\bps
\bs)
\b) (
\b(8
\b8)
\b)
4071 r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bwc
\bcy
\by <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[i
\bin
\bnp
\bpu
\but
\bt]
\b] [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> WCY reject filter sysop
4075 This version allows a sysop to set a filter for a callsign as well as
4076 the default for nodes and users eg:-
4078 reject/wcy gb7djk all
4081 1
\b13
\b3.
\b.5
\b59
\b9.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bww
\bwv
\bv (
\b(0
\b0)
\b)
4083 r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bww
\bwv
\bv [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set a reject WWV filter
4086 It is unlikely that you will want to do this, but if you do then you
4087 can filter on the following fields:-
4093 by <prefixes> eg: G,M,2
4095 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
4096 origin_itu <numbers>
4097 origin_zone <numbers>
4110 reject/wwv by_zone 14,15,16
4115 is probably the only useful thing to do (which will only show WWV
4116 broadcasts by stations in the US).
4118 See HELP FILTER for information.
4121 1
\b13
\b3.
\b.6
\b60
\b0.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bww
\bwv
\bv (
\b(e
\bex
\bxt
\bte
\ben
\bnd
\bde
\bed
\bd f
\bfo
\bor
\br s
\bsy
\bys
\bso
\bop
\bps
\bs)
\b) (
\b(8
\b8)
\b)
4123 r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bww
\bwv
\bv <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[i
\bin
\bnp
\bpu
\but
\bt]
\b] [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> WWV reject filter sysop
4127 This version allows a sysop to set a filter for a callsign as well as
4128 the default for nodes and users eg:-
4132 reject/wwv db0sue-7 1 by_zone 4
4133 reject/wwv node_default all
4135 reject/wwv user_default by W
4141 1
\b13
\b3.
\b.6
\b61
\b1.
\b. r
\bre
\bep
\bpl
\bly
\by (
\b(0
\b0)
\b)
4143 r
\bre
\bep
\bpl
\bly
\by Reply (privately) to the last message that you have read
4144 r
\bre
\bep
\bpl
\bly
\by <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Reply (privately) to the specified message
4145 r
\bre
\bep
\bpl
\bly
\by B
\bB <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Reply as a Bulletin to the specified message
4146 r
\bre
\bep
\bpl
\bly
\by N
\bNO
\bOP
\bPr
\bri
\biv
\bva
\bat
\bte
\be <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Reply as a Bulletin to the specified message
4147 r
\bre
\bep
\bpl
\bly
\by R
\bRR
\bR <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Reply to the specified message with read receipt
4150 You can reply to a message and the subject will automatically have
4151 "Re:" inserted in front of it, if it isn't already present.
4153 You can also use all the extra qualifiers such as RR, PRIVATE,
4154 NOPRIVATE, B that you can use with the SEND command (see SEND for
4159 1
\b13
\b3.
\b.6
\b62
\b2.
\b. s
\bse
\ben
\bnd
\bd (
\b(0
\b0)
\b)
4161 s
\bse
\ben
\bnd
\bd <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[<
\b<c
\bca
\bal
\bll
\bl>
\b> .
\b..
\b..
\b.]
\b] Send a message to one or more callsigns
4162 s
\bse
\ben
\bnd
\bd R
\bRR
\bR <
\b<c
\bca
\bal
\bll
\bl>
\b> Send a message and ask for a read receipt
4163 s
\bse
\ben
\bnd
\bd C
\bCO
\bOP
\bPY
\bY <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> <
\b<c
\bca
\bal
\bll
\bl>
\b> Send a copy of a message to someone
4164 s
\bse
\ben
\bnd
\bd P
\bPR
\bRI
\bIV
\bVA
\bAT
\bTE
\bE <
\b<c
\bca
\bal
\bll
\bl>
\b> Send a personal message
4165 s
\bse
\ben
\bnd
\bd N
\bNO
\bOP
\bPR
\bRI
\bIV
\bVA
\bAT
\bTE
\bE <
\b<c
\bca
\bal
\bll
\bl>
\b> Send a message to all stations
4168 All the SEND commands will create a message which will be sent either
4169 to an individual callsign or to one of the 'bulletin' addresses.
4171 SEND <call> on its own acts as though you had typed SEND PRIVATE, that
4172 is it will mark the message as personal and send it to the cluster
4173 node that that callsign is connected to.
4175 You can have more than one callsign in all of the SEND commands.
4177 You can have multiple qualifiers so that you can have for example:-
4181 SEND RR COPY 123 PRIVATE G1TLH G0RDI
4186 which should send a copy of message 123 to G1TLH and G0RDI and you
4187 will receive a read receipt when they have read the message.
4189 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP
4190 is an alias for SEND PRIVATE
4193 1
\b13
\b3.
\b.6
\b63
\b3.
\b. s
\bse
\bet
\bt/
\b/a
\bad
\bdd
\bdr
\bre
\bes
\bss
\bs (
\b(0
\b0)
\b)
4195 s
\bse
\bet
\bt/
\b/a
\bad
\bdd
\bdr
\bre
\bes
\bss
\bs <
\b<y
\byo
\bou
\bur
\br_
\b_a
\bad
\bdd
\bdr
\bre
\bes
\bss
\bs>
\b> Record your postal address
4198 Literally, record your address details on the cluster.
4201 1
\b13
\b3.
\b.6
\b64
\b4.
\b. s
\bse
\bet
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be (
\b(0
\b0)
\b)
4203 s
\bse
\bet
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be Allow announce messages
4206 Allow announce messages to arrive at your terminal.
4209 1
\b13
\b3.
\b.6
\b65
\b5.
\b. s
\bse
\bet
\bt/
\b/a
\bar
\brc
\bcl
\blu
\bus
\bst
\bte
\ber
\br (
\b(5
\b5)
\b)
4211 s
\bse
\bet
\bt/
\b/a
\bar
\brc
\bcl
\blu
\bus
\bst
\bte
\ber
\br <
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> [
\b[<
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> .
\b..
\b..
\b.]
\b] Make the node_call an AR-
4215 Set the node_call as an AR-Cluster type node
4218 1
\b13
\b3.
\b.6
\b66
\b6.
\b. s
\bse
\bet
\bt/
\b/b
\bba
\bad
\bdd
\bdx
\bx (
\b(8
\b8)
\b)
4220 s
\bse
\bet
\bt/
\b/b
\bba
\bad
\bdd
\bdx
\bx <
\b<c
\bca
\bal
\bll
\bl>
\b> Stop words we do not wish to see in the callsign
4221 field of a dx spot being propagated
4225 Setting a word as 'baddx' will prevent spots with that word in the
4226 callsign field of a DX spot from going any further. They will not be
4227 displayed and they will not be sent onto other nodes.
4229 The word must be wriiten in full, no wild cards are allowed eg:-
4233 set/baddx FORSALE VIDEO FR0G
4238 To allow a word again, use the following command ...
4248 1
\b13
\b3.
\b.6
\b67
\b7.
\b. s
\bse
\bet
\bt/
\b/b
\bba
\bad
\bdn
\bno
\bod
\bde
\be (
\b(6
\b6)
\b)
4250 s
\bse
\bet
\bt/
\b/b
\bba
\bad
\bdn
\bno
\bod
\bde
\be <
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> Stop spots from this node_call being
4254 Setting a callsign as a 'badnode' will prevent spots from that node
4255 going any further. They will not be displayed and they will not be
4256 sent onto other nodes.
4258 The call can be a full or partial call (or a prefix), eg:-
4267 will stop anything from K1TTT (including any SSID's)
4276 will allow spots from him again.
4278 Use with extreme care. This command may well be superceded by
4282 1
\b13
\b3.
\b.6
\b68
\b8.
\b. s
\bse
\bet
\bt/
\b/b
\bba
\bad
\bds
\bsp
\bpo
\bot
\btt
\bte
\ber
\br (
\b(8
\b8)
\b)
4284 s
\bse
\bet
\bt/
\b/b
\bba
\bad
\bds
\bsp
\bpo
\bot
\btt
\bte
\ber
\br <
\b<c
\bca
\bal
\bll
\bl>
\b> Stop spots from this callsign being propagated
4287 Setting a callsign as a 'badspotter' will prevent spots from this
4288 callsign going any further. They will not be displayed and they will
4289 not be sent onto other nodes.
4291 The call must be written in full, no wild cards are allowed eg:-
4295 set/badspotter VE2STN
4300 will stop anything from VE2STN. If you want SSIDs as well then you
4301 must enter them specifically.
4305 unset/badspotter VE2STN
4310 will allow spots from him again.
4312 Use with extreme care. This command may well be superceded by
4316 1
\b13
\b3.
\b.6
\b69
\b9.
\b. s
\bse
\bet
\bt/
\b/b
\bbe
\bee
\bep
\bp (
\b(0
\b0)
\b)
4318 s
\bse
\bet
\bt/
\b/b
\bbe
\bee
\bep
\bp Add beeps to terminal messages
4321 Add a beep to DX and other terminal messages.
4324 1
\b13
\b3.
\b.7
\b70
\b0.
\b. s
\bse
\bet
\bt/
\b/c
\bcl
\blx
\bx (
\b(5
\b5)
\b)
4326 s
\bse
\bet
\bt/
\b/c
\bcl
\blx
\bx <
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> [
\b[<
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> .
\b..
\b..
\b.]
\b] Make the node_call a CLX type
4330 Set the node_call as a CLX type node
4333 1
\b13
\b3.
\b.7
\b71
\b1.
\b. s
\bse
\bet
\bt/
\b/d
\bde
\beb
\bbu
\bug
\bg (
\b(9
\b9)
\b)
4335 s
\bse
\bet
\bt/
\b/d
\bde
\beb
\bbu
\bug
\bg <
\b<n
\bna
\bam
\bme
\be>
\b> Add a debug level to the debug set
4338 You can choose to log several different levels. The levels are
4340 chan state msg cron connect
4342 You can show what levels you are logging with the _
\bs_
\bh_
\bo_
\bw_
\b/_
\bd_
\be_
\bb_
\bu_
\bg command.
4344 You can remove a debug level with unset/debug <name>
4347 1
\b13
\b3.
\b.7
\b72
\b2.
\b. s
\bse
\bet
\bt/
\b/d
\bdx
\bx (
\b(0
\b0)
\b)
4349 s
\bse
\bet
\bt/
\b/d
\bdx
\bxAllow DX messages to arrive at your terminal
4352 You can stop DX messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bd_
\bx command
4357 1
\b13
\b3.
\b.7
\b73
\b3.
\b. s
\bse
\bet
\bt/
\b/d
\bdx
\bxg
\bgr
\bri
\bid
\bd (
\b(0
\b0)
\b)
4359 s
\bse
\bet
\bt/
\b/d
\bdx
\bxg
\bgr
\bri
\bid
\bdAllow grid squares on the end of DX messages
4362 Some logging programs do not like the additional information at the
4363 end of a DX spot. If this is the case, use the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bd_
\bx_
\bg_
\br_
\bi_
\bd command
4364 to remove the grid squares.
4367 1
\b13
\b3.
\b.7
\b74
\b4.
\b. s
\bse
\bet
\bt/
\b/d
\bdx
\bxn
\bne
\bet
\bt (
\b(5
\b5)
\b)
4369 s
\bse
\bet
\bt/
\b/d
\bdx
\bxn
\bne
\bet
\bt <
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> [
\b[<
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> .
\b..
\b..
\b.]
\b] Make the node_call a DXNet
4373 Set the node_call as a DXNet type node
4376 1
\b13
\b3.
\b.7
\b75
\b5.
\b. s
\bse
\bet
\bt/
\b/e
\bec
\bch
\bho
\bo (
\b(0
\b0)
\b)
4378 s
\bse
\bet
\bt/
\b/e
\bec
\bch
\bho
\bo Make the cluster echo your input
4381 If you are connected via a telnet session, different implimentations
4382 of telnet handle echo differently depending on whether you are
4383 connected via port 23 or some other port. You can use this command to
4384 change the setting appropriately.
4386 You can remove the echo with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\be_
\bc_
\bh_
\bo command
4388 The setting is stored in your user profile.
4390 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
4393 1
\b13
\b3.
\b.7
\b76
\b6.
\b. s
\bse
\bet
\bt/
\b/h
\bhe
\ber
\bre
\be (
\b(0
\b0)
\b)
4395 s
\bse
\bet
\bt/
\b/h
\bhe
\ber
\bre
\be Set the here flag
4398 Let others on the cluster know you are here by only displaying your
4399 callsign. If you are away from your terminal you can use the
4400 _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bh_
\be_
\br_
\be command to let people know you are away. This simply puts
4401 brackets around your callsign to indicate you are not available.
4404 1
\b13
\b3.
\b.7
\b77
\b7.
\b. s
\bse
\bet
\bt/
\b/h
\bho
\bom
\bme
\ben
\bno
\bod
\bde
\be (
\b(0
\b0)
\b)
4406 s
\bse
\bet
\bt/
\b/h
\bho
\bom
\bme
\ben
\bno
\bod
\bde
\be <
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> Set your home cluster
4409 Tell the cluster system where you normally connect to. Any Messages
4410 sent to you will normally find their way there should you not be
4423 1
\b13
\b3.
\b.7
\b78
\b8.
\b. s
\bse
\bet
\bt/
\b/h
\bho
\bop
\bps
\bs (
\b(8
\b8)
\b)
4425 s
\bse
\bet
\bt/
\b/h
\bho
\bop
\bps
\bs <
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> a
\ban
\bnn
\bn|
\b|s
\bsp
\bpo
\bot
\bts
\bs|
\b|w
\bww
\bwv
\bv|
\b|w
\bwc
\bcy
\by <
\b<n
\bn>
\b> Set hop count
4428 Set the hop count for a particular type of broadcast for a node.
4430 This command allows you to set up special hop counts for a node for
4431 currently: announce, spots, wwv and wcy broadcasts.
4436 set/hops gb7djk ann 10
4437 set/hops gb7mbc spots 20
4442 Set SHOW/HOPS for information on what is already set. This command
4443 creates a filter and works in conjunction with the filter system.
4446 1
\b13
\b3.
\b.7
\b79
\b9.
\b. s
\bse
\bet
\bt/
\b/i
\bis
\bso
\bol
\bla
\bat
\bte
\be (
\b(9
\b9)
\b)
4448 s
\bse
\bet
\bt/
\b/i
\bis
\bso
\bol
\bla
\bat
\bte
\be <
\b<n
\bno
\bod
\bde
\be c
\bca
\bal
\bll
\bl>
\b> Isolate a node from the rest of the network
4451 Connect a node to your system in such a way that you are a full
4452 protocol member of its network and can see all spots on it, but
4453 nothing either leaks out from it nor goes back into from the rest of
4454 the nodes connected to you.
4456 You can potentially connect several nodes in this way.
4458 You can see which nodes are isolated with the show/isolate (1)
4461 You can remove the isolation with the command unset/isolate.
4464 1
\b13
\b3.
\b.8
\b80
\b0.
\b. s
\bse
\bet
\bt/
\b/l
\bla
\ban
\bng
\bgu
\bua
\bag
\bge
\be (
\b(0
\b0)
\b)
4466 s
\bse
\bet
\bt/
\b/l
\bla
\ban
\bng
\bgu
\bua
\bag
\bge
\be <
\b<l
\bla
\ban
\bng
\bgu
\bua
\bag
\bge
\be>
\b> Set the language you wish to use
4469 You can select the language that you want the cluster to use.
4470 Currently the languages available are _
\be_
\bn (English) and _
\bn_
\bl (Dutch).
4473 1
\b13
\b3.
\b.8
\b81
\b1.
\b. s
\bse
\bet
\bt/
\b/l
\blo
\boc
\bca
\bat
\bti
\bio
\bon
\bn (
\b(0
\b0)
\b)
4475 s
\bse
\bet
\bt/
\b/l
\blo
\boc
\bca
\bat
\bti
\bio
\bon
\bn <
\b<l
\bla
\bat
\bt a
\ban
\bnd
\bd l
\blo
\bon
\bng
\bg>
\b> Set your latitude and longitude
4478 You can set your latitude and longitude manually or alternatively use
4479 the _
\bs_
\be_
\bt_
\b/_
\bq_
\br_
\ba command which will do the conversion for you.
4483 set/location 54 04 N 2 02 E
4489 1
\b13
\b3.
\b.8
\b82
\b2.
\b. s
\bse
\bet
\bt/
\b/s
\bsy
\bys
\bs_
\b_l
\blo
\boc
\bca
\bat
\bti
\bio
\bon
\bn (
\b(9
\b9)
\b)
4491 s
\bse
\bet
\bt/
\b/s
\bsy
\bys
\bs_
\b_l
\blo
\boc
\bca
\bat
\bti
\bio
\bon
\bn <
\b<l
\bla
\bat
\bt &
\b& l
\blo
\bon
\bng
\bg>
\b> Set your cluster latitude and longitude
4494 In order to get accurate headings and such like you must tell the
4495 system what your latitude and longitude is. If you have not yet done a
4496 SET/QRA then this command will set your QRA locator for you. For
4501 SET/LOCATION 52 22 N 0 57 E
4507 1
\b13
\b3.
\b.8
\b83
\b3.
\b. s
\bse
\bet
\bt/
\b/l
\blo
\bog
\bgi
\bin
\bni
\bin
\bnf
\bfo
\bo (
\b(0
\b0)
\b)
4509 s
\bse
\bet
\bt/
\b/l
\blo
\bog
\bgi
\bin
\bni
\bin
\bnf
\bfo
\bo Show logins and logouts of nodes and users
4512 Show users and nodes when they log in and out of the local cluster.
4513 You can stop these messages by using the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bl_
\bo_
\bg_
\bi_
\bn_
\bi_
\bn_
\bf_
\bo command.
4517 1
\b13
\b3.
\b.8
\b84
\b4.
\b. s
\bse
\bet
\bt/
\b/l
\blo
\boc
\bck
\bko
\bou
\but
\bt (
\b(9
\b9)
\b)
4519 s
\bse
\bet
\bt/
\b/l
\blo
\boc
\bck
\bko
\bou
\but
\bt <
\b<c
\bca
\bal
\bll
\bl>
\b> Stop a callsign connecting to the cluster
4522 You can show who is locked out with the _
\bs_
\bh_
\bo_
\bw_
\b/_
\bl_
\bo_
\bc_
\bk_
\bo_
\bu_
\bt command. To
4523 allow the user to connect again, use the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bl_
\bo_
\bc_
\bk_
\bo_
\bu_
\bt command.
4526 1
\b13
\b3.
\b.8
\b85
\b5.
\b. s
\bse
\bet
\bt/
\b/n
\bna
\bam
\bme
\be (
\b(0
\b0)
\b)
4528 s
\bse
\bet
\bt/
\b/n
\bna
\bam
\bme
\be <
\b<y
\byo
\bou
\bur
\br_
\b_n
\bna
\bam
\bme
\be>
\b> Set your name
4531 Tell the cluster what your name is, eg:-
4541 1
\b13
\b3.
\b.8
\b86
\b6.
\b. s
\bse
\bet
\bt/
\b/n
\bno
\bod
\bde
\be (
\b(9
\b9)
\b)
4543 s
\bse
\bet
\bt/
\b/n
\bno
\bod
\bde
\be <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[<
\b<c
\bca
\bal
\bll
\bl>
\b> .
\b..
\b..
\b.]
\b] Make the callsign an AK1A cluster
4546 Tell the system that the call(s) are to be treated as AK1A cluster and
4547 fed PC Protocol rather normal user commands.
4549 From version 1.41 you can also set the following types of cluster
4563 To see what your nodes are set to, use the _
\bs_
\bh_
\bo_
\bw_
\b/_
\bn_
\bo_
\bd_
\be_
\bs command.
4566 1
\b13
\b3.
\b.8
\b87
\b7.
\b. s
\bse
\bet
\bt/
\b/o
\bob
\bbs
\bsc
\bco
\bou
\bun
\bnt
\bt (
\b(9
\b9)
\b)
4568 s
\bse
\bet
\bt/
\b/o
\bob
\bbs
\bsc
\bco
\bou
\bun
\bnt
\bt <
\b<c
\bco
\bou
\bun
\bnt
\bt>
\b> <
\b<n
\bno
\bod
\bde
\be c
\bca
\bal
\bll
\bl>
\b> Set the 'pump-up' obsolescence
4572 From version 1.35 onwards neighbouring nodes are pinged at regular
4573 intervals (see SET/PINGINTERVAL), usually 300 seconds or 5 minutes.
4574 There is a 'pump-up' counter which is decremented on every outgoing
4575 ping and then reset to the 'obscount' value on every incoming ping.
4576 The default value of this parameter is 2.
4578 What this means is that a neighbouring node will be pinged twice at
4579 (default) 300 second intervals and if no reply has been heard just
4580 before what would be the third attempt, that node is disconnected.
4582 If a ping is heard then the obscount is reset to the full value. Using
4583 default values, if a node has not responded to a ping within 15
4584 minutes, it is disconnected.
4587 1
\b13
\b3.
\b.8
\b88
\b8.
\b. s
\bse
\bet
\bt/
\b/p
\bpa
\bag
\bge
\be (
\b(0
\b0)
\b)
4589 s
\bse
\bet
\bt/
\b/p
\bpa
\bag
\bge
\be <
\b<n
\bn>
\b> Set the number of lines per page
4592 Tell the system how many lines you wish on a page when the number of
4593 lines of output from a command is more than this. The default is 20.
4594 Setting it explicitly to 0 will disable paging.
4604 The setting is stored in your user profile.
4608 1
\b13
\b3.
\b.8
\b89
\b9.
\b. s
\bse
\bet
\bt/
\b/p
\bpa
\bas
\bss
\bsw
\bwo
\bor
\brd
\bd (
\b(9
\b9)
\b)
4610 s
\bse
\bet
\bt/
\b/p
\bpa
\bas
\bss
\bsw
\bwo
\bor
\brd
\bd <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> <
\b<s
\bst
\btr
\bri
\bin
\bng
\bg>
\b> Set a users password
4613 The password for a user can only be set by a full sysop. The string
4614 can contain any characters but any spaces are removed (you can type in
4615 spaces - but they won't appear in the password). You can see the
4616 result with STAT/USER. The password is the usual 30 character baycom
4621 1
\b13
\b3.
\b.9
\b90
\b0.
\b. s
\bse
\bet
\bt/
\b/p
\bpi
\bin
\bng
\bgi
\bin
\bnt
\bte
\ber
\brv
\bva
\bal
\bl (
\b(9
\b9)
\b)
4623 s
\bse
\bet
\bt/
\b/p
\bpi
\bin
\bng
\bgi
\bin
\bnt
\bte
\ber
\brv
\bva
\bal
\bl <
\b<t
\bti
\bim
\bme
\be>
\b> <
\b<n
\bno
\bod
\bde
\be c
\bca
\bal
\bll
\bl>
\b> Set the ping time to neighbouring
4627 As from version 1.35 all neighbouring nodes are pinged at regular
4628 intervals in order to determine the rolling quality of the link and,
4629 in future, to affect routing decisions. The default interval is 300
4632 You can use this command to set a different interval. Please don't.
4634 But if you do the value you enter is treated as minutes up 60 and
4635 seconds for numbers greater than that.
4637 This is used also to help determine when a link is down at the far end
4638 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
4639 for more information.
4642 1
\b13
\b3.
\b.9
\b91
\b1.
\b. s
\bse
\bet
\bt/
\b/p
\bpr
\bri
\biv
\bvi
\bil
\ble
\beg
\bge
\be (
\b(9
\b9)
\b)
4644 s
\bse
\bet
\bt/
\b/p
\bpr
\bri
\biv
\bvi
\bil
\ble
\beg
\bge
\be <
\b<n
\bn>
\b> <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[<
\b<c
\bca
\bal
\bll
\bl>
\b> .
\b..
\b..
\b.]
\b] Set the privilege level on a
4648 Set the privilege level on a callsign. The privilege levels that
4649 pertain to commands are as default:-
4654 1 - allow remote nodes normal user RCMDs
4655 5 - various privileged commands (including shutdown, but not disc-
4656 connect), the normal level for another node.
4657 8 - more privileged commands (including disconnect)
4658 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
4664 If you are a sysop and you come in as a normal user on a remote
4665 connection your privilege will automatically be set to 0.
4668 1
\b13
\b3.
\b.9
\b92
\b2.
\b. s
\bse
\bet
\bt/
\b/s
\bsp
\bpi
\bid
\bde
\ber
\br (
\b(5
\b5)
\b)
4670 s
\bse
\bet
\bt/
\b/s
\bsp
\bpi
\bid
\bde
\ber
\br <
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> [
\b[<
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> .
\b..
\b..
\b.]
\b] Make the node_call a DXSpider
4674 Set the node_call as a DXSpider type node
4677 1
\b13
\b3.
\b.9
\b93
\b3.
\b. s
\bse
\bet
\bt/
\b/s
\bsy
\bys
\bs_
\b_q
\bqr
\bra
\ba (
\b(9
\b9)
\b)
4679 s
\bse
\bet
\bt/
\b/s
\bsy
\bys
\bs_
\b_q
\bqr
\bra
\ba <
\b<l
\blo
\boc
\bca
\bat
\bto
\bor
\br>
\b> Set your cluster QRA locator
4682 1
\b13
\b3.
\b.9
\b94
\b4.
\b. s
\bse
\bet
\bt/
\b/q
\bqr
\bra
\ba (
\b(0
\b0)
\b)
4684 s
\bse
\bet
\bt/
\b/q
\bqr
\bra
\ba <
\b<l
\blo
\boc
\bca
\bat
\bto
\bor
\br>
\b> Set your QRA locator
4687 Tell the system what your QRA (or Maidenhead) locator is. If you have
4688 not done a SET/LOCATION then your latitude and longitude will be set
4689 roughly correctly (assuming your locator is correct ;-). For example:-
4699 1
\b13
\b3.
\b.9
\b95
\b5.
\b. s
\bse
\bet
\bt/
\b/q
\bqt
\bth
\bh (
\b(0
\b0)
\b)
4701 s
\bse
\bet
\bt/
\b/q
\bqt
\bth
\bh <
\b<y
\byo
\bou
\bur
\br Q
\bQT
\bTH
\bH>
\b> Set your QTH
4704 Tell the system where your are. For example:-
4708 set/qth East Dereham, Norfolk
4714 1
\b13
\b3.
\b.9
\b96
\b6.
\b. s
\bse
\bet
\bt/
\b/t
\bta
\bal
\blk
\bk (
\b(0
\b0)
\b)
4716 s
\bse
\bet
\bt/
\b/t
\bta
\bal
\blk
\bk Allow talk messages to be seen at your console
4719 Allow talk messages to arrive at your console. You can switch off
4720 talks with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bt_
\ba_
\bl_
\bk command.
4723 1
\b13
\b3.
\b.9
\b97
\b7.
\b. s
\bse
\bet
\bt/
\b/w
\bwc
\bcy
\by (
\b(0
\b0)
\b)
4725 s
\bse
\bet
\bt/
\b/w
\bwc
\bcy
\by Allow WCY messages to be seen at your console
4728 Allow WCY information to be seen at your console. You can switch off
4729 WCY messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bw_
\bc_
\by command.
4732 1
\b13
\b3.
\b.9
\b98
\b8.
\b. s
\bse
\bet
\bt/
\b/w
\bww
\bwv
\bv (
\b(0
\b0)
\b)
4734 s
\bse
\bet
\bt/
\b/w
\bww
\bwv
\bv Allow WWV messages to be seen at your console
4737 Allow WWV information to be seen at your console. You can switch off
4738 WWV messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bw_
\bw_
\bv command.
4741 1
\b13
\b3.
\b.9
\b99
\b9.
\b. s
\bse
\bet
\bt/
\b/w
\bwx
\bx (
\b(0
\b0)
\b)
4743 s
\bse
\bet
\bt/
\b/w
\bwx
\bx Allow WX messages to be seen at your console
4746 Allow WX information to be seen at your console. You can switch off
4747 WX messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bw_
\bx command.
4753 1
\b13
\b3.
\b.1
\b10
\b00
\b0.
\b. s
\bsh
\bho
\bow
\bw/
\b/b
\bba
\bad
\bdd
\bdx
\bx (
\b(1
\b1)
\b)
4755 s
\bsh
\bho
\bow
\bw/
\b/b
\bba
\bad
\bdd
\bdx
\bxShow all the bad dx calls in the system
4758 Display all the bad dx callsigns in the system, see SET/BADDX for more
4762 1
\b13
\b3.
\b.1
\b10
\b01
\b1.
\b. s
\bsh
\bho
\bow
\bw/
\b/b
\bba
\bad
\bdn
\bno
\bod
\bde
\be (
\b(6
\b6)
\b)
4764 s
\bsh
\bho
\bow
\bw/
\b/b
\bba
\bad
\bdn
\bno
\bod
\bde
\be Show all the bad nodes in the system
4767 Display all the bad node callsigns in the system, see SET/BADNODE for
4771 1
\b13
\b3.
\b.1
\b10
\b02
\b2.
\b. s
\bsh
\bho
\bow
\bw/
\b/b
\bba
\bad
\bds
\bsp
\bpo
\bot
\btt
\bte
\ber
\br (
\b(1
\b1)
\b)
4773 s
\bsh
\bho
\bow
\bw/
\b/b
\bba
\bad
\bds
\bsp
\bpo
\bot
\btt
\bte
\ber
\br Show all the bad spotters in the system
4776 Display all the bad spotter's callsigns in the system, see
4777 SET/BADSPOTTER for more information.
4780 1
\b13
\b3.
\b.1
\b10
\b03
\b3.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bda
\bat
\bte
\be (
\b(0
\b0)
\b)
4782 s
\bsh
\bho
\bow
\bw/
\b/d
\bda
\bat
\bte
\be [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show the local time
4785 This is very nearly the same as SHOW/TIME, the only difference the
4786 format of the date string if no arguments are given.
4788 If no prefixes or callsigns are given then this command returns the
4789 local time and UTC as the computer has it right now. If you give some
4790 prefixes then it will show UTC and UTC + the local offset (not
4791 including DST) at the prefixes or callsigns that you specify.
4794 1
\b13
\b3.
\b.1
\b10
\b04
\b4.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bde
\beb
\bbu
\bug
\bg (
\b(9
\b9)
\b)
4796 s
\bsh
\bho
\bow
\bw/
\b/d
\bde
\beb
\bbu
\bug
\bg Show what levels of debug you are logging
4799 The levels can be set with _
\bs_
\be_
\bt_
\b/_
\bd_
\be_
\bb_
\bu_
\bg
4802 1
\b13
\b3.
\b.1
\b10
\b05
\b5.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bx (
\b(0
\b0)
\b)
4804 s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bx [
\b[o
\bop
\bpt
\bti
\bio
\bon
\bns
\bs]
\b] interrogate the spot database
4807 If you just type SHOW/DX you will get the last so many spots (sysop
4808 configurable, but usually 10).
4810 In addition you can add any number of these options in very nearly any
4811 order to the basic SHOW/DX command, they are:-
4819 on <band> - eg 160m 20m 2m 23cm 6mm
4820 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
4822 <number> - the number of spots you want
4823 <from>-<to> - <from> spot no <to> spot no in
4826 <prefix> - for a spotted callsign beginning with <prefix>
4827 *<suffix> - for a spotted callsign ending in <suffix>
4828 *<string>* - for a spotted callsign containing <string>
4830 day <number> - starting <number> days ago
4831 day <from>-<to> - <from> days <to> days ago
4833 info <text> - any spots containing <text> in the info or remarks
4835 by <call> - any spots spotted by <call> (spotter <call>
4838 qsl - this automatically looks for any qsl info on the call
4839 held in the spot database.
4841 iota [<iota>] - If the iota island number is missing it will
4842 look for the string iota and anything which looks like
4843 an iota island number. If you specify then it will look
4846 qra [<locator>] - this will look for the specific locator if
4847 you specify one or else anything that looks like a locator.
4858 SH/DX on 20m info iota
4859 SH/DX 9a on vhf day 30
4869 1
\b13
\b3.
\b.1
\b10
\b06
\b6.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bxc
\bcc
\bc (
\b(0
\b0)
\b)
4871 s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bxc
\bcc
\bc <
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b> Interrogate the spot database by country
4874 This command takes the <prefix> (which can be a full or partial
4875 callsign if desired), looks up which internal country number it is and
4876 then displays all the spots as per SH/DX for that country.
4878 The options for SHOW/DX also apply to this command. e.g.
4886 SH/DXCC W on 20m info iota
4892 1
\b13
\b3.
\b.1
\b10
\b07
\b7.
\b. s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\ble
\bes
\bs (
\b(0
\b0)
\b)
4894 s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\ble
\bes
\bs [
\b[<
\b<f
\bfi
\bil
\ble
\bea
\bar
\bre
\bea
\ba>
\b> [
\b[<
\b<s
\bst
\btr
\bri
\bin
\bng
\bg>
\b>]
\b]]
\b] List the contents of a filearea
4897 SHOW/FILES on its own will show you a list of the various fileareas
4898 available on the system. To see the contents of a particular file area
4908 where <filearea> is the name of the filearea you want to see the
4911 You can also use shell globbing characters like '*' and '?' in a
4912 string to see a selection of files in a filearea eg:-
4916 SH/FILES bulletins arld*
4921 See also TYPE - to see the contents of a file.
4924 1
\b13
\b3.
\b.1
\b10
\b08
\b8.
\b. s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\blt
\bte
\ber
\br (
\b(0
\b0)
\b)
4926 s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\blt
\bte
\ber
\br Show the filters you have set
4929 Show the contents of all the filters that are set by you. This command
4930 displays all the filters set - for all the various categories.
4933 1
\b13
\b3.
\b.1
\b10
\b09
\b9.
\b. s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\blt
\bte
\ber
\br (
\b(e
\bex
\bxt
\bte
\ben
\bnd
\bde
\bed
\bd f
\bfo
\bor
\br s
\bsy
\bys
\bso
\bop
\bps
\bs)
\b) (
\b(5
\b5)
\b)
4935 s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\blt
\bte
\ber
\br <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> Show the filters set by <callsign>
4938 A sysop can look at any filters that have been set.
4941 1
\b13
\b3.
\b.1
\b11
\b10
\b0.
\b. s
\bsh
\bho
\bow
\bw/
\b/h
\bho
\bop
\bps
\bs (
\b(8
\b8)
\b)
4943 s
\bsh
\bho
\bow
\bw/
\b/h
\bho
\bop
\bps
\bs <
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> [
\b[a
\ban
\bnn
\bn|
\b|s
\bsp
\bpo
\bot
\bts
\bs|
\b|w
\bwc
\bcy
\by|
\b|w
\bww
\bwv
\bv|
\b|]
\b] Show the hop counts for a
4947 This command shows the hop counts set up for a node. You can specify
4948 which category you want to see. If you leave the category out then all
4949 the categories will be listed.
4951 1
\b13
\b3.
\b.1
\b11
\b11
\b1.
\b. s
\bsh
\bho
\bow
\bw/
\b/i
\bis
\bso
\bol
\bla
\bat
\bte
\be (
\b(1
\b1)
\b)
4953 s
\bsh
\bho
\bow
\bw/
\b/i
\bis
\bso
\bol
\bla
\bat
\bte
\be Show a list of isolated nodes
4956 Show which nodes are currently set to be isolated.
4959 1
\b13
\b3.
\b.1
\b11
\b12
\b2.
\b. s
\bsh
\bho
\bow
\bw/
\b/l
\blo
\boc
\bck
\bko
\bou
\but
\bt (
\b(9
\b9)
\b)
4961 s
\bsh
\bho
\bow
\bw/
\b/l
\blo
\boc
\bck
\bko
\bou
\but
\bt Show a list of excluded callsigns
4964 Show a list of callsigns that have been excluded (locked out) of the
4965 cluster locally with the _
\bs_
\be_
\bt_
\b/_
\bl_
\bo_
\bc_
\bk_
\bo_
\bu_
\bt command
4968 1
\b13
\b3.
\b.1
\b11
\b13
\b3.
\b. s
\bsh
\bho
\bow
\bw/
\b/l
\blo
\bog
\bg (
\b(8
\b8)
\b)
4970 s
\bsh
\bho
\bow
\bw/
\b/l
\blo
\bog
\bg [
\b[<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show excerpts from the system log
4973 This command outputs a short section of the system log. On its own it
4974 will output a general logfile. With the optional callsign it will
4975 show output from the log associated with that callsign.
4978 1
\b13
\b3.
\b.1
\b11
\b14
\b4.
\b. s
\bsh
\bho
\bow
\bw/
\b/m
\bmo
\boo
\bon
\bn (
\b(0
\b0)
\b)
4980 s
\bsh
\bho
\bow
\bw/
\b/m
\bmo
\boo
\bon
\bn [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show moon rise and set times
4983 Show the Moon rise and set times for a (list of) prefixes or
4984 callsigns, together with the azimuth and elevation of the sun
4985 currently at those locations.
4987 If you don't specify any prefixes or callsigns, it will show the times
4988 for your QTH (assuming you have set it with either SET/LOCATION or
4989 SET/QRA), together with the current azimuth and elevation.
4991 In addition, it will show the gain or loss dB relative to the nominal
4992 distance of 385,000Km due to the ellipsoidal nature of the orbit.
4994 If all else fails it will show the Moonrise and set times for the node
4995 that you are connected to.
5008 1
\b13
\b3.
\b.1
\b11
\b15
\b5.
\b. s
\bsh
\bho
\bow
\bw/
\b/m
\bmu
\buf
\bf (
\b(0
\b0)
\b)
5010 s
\bsh
\bho
\bow
\bw/
\b/m
\bmu
\buf
\bf <
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b> [
\b[<
\b<h
\bho
\bou
\bur
\brs
\bs>
\b>]
\b][
\b[l
\blo
\bon
\bng
\bg]
\b] Show the likely propagation to
5014 This command allow you to estimate the likelihood of you contacting a
5015 station with the prefix you have specified. The output assumes a
5016 modest power of 20dBW and receiver sensitivity of -123dBm (about
5019 The result predicts the most likely operating frequencies and signal
5020 levels for high frequency (shortwave) radio propagation paths on
5021 specified days of the year and hours of the day. It is most useful for
5022 paths between 250 km and 6000 km, but can be used with reduced
5023 accuracy for paths shorter or longer than this.
5025 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
5026 used to predict the MUF given the predicted flux, day of the year,
5027 hour of the day and geographic coordinates of the transmitter and
5028 receiver. This routine is reasonably accurate for the purposes here,
5029 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
5030 than the programs used by major shortwave broadcasting organizations,
5031 such as the Voice of America.
5033 The command will display some header information detailing its
5034 assumptions, together with the locations, latitude and longitudes and
5035 bearings. It will then show UTC (UT), local time at the other end
5036 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
5037 (Zen) and the likely signal strengths. Then for each frequency for
5038 which the system thinks there is a likelihood of a circuit it prints a
5041 The value is currently a likely S meter reading based on the
5042 conventional 6dB / S point scale. If the value has a '+' appended it
5043 means that it is 1/2 an S point stronger. If the value is preceeded by
5044 an 'm' it means that there is likely to be much fading and by an 's'
5045 that the signal is likely to be noisy.
5047 By default SHOW/MUF will show the next two hours worth of data. You
5048 can specify anything up to 24 hours worth of data by appending the no
5049 of hours required after the prefix. For example:-
5062 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
5063 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
5064 Location Lat / Long Azim
5065 East Dereham, Norfolk 52 41 N 0 57 E 47
5066 United-States-W 43 0 N 87 54 W 299
5067 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
5068 18 23 11.5 -35 mS0+ mS2 S3
5069 19 0 11.2 -41 mS0+ mS2 S3
5074 indicating that you will have weak, fading circuits on top band and
5075 80m but usable signals on 40m (about S3).
5083 will get you the above display, but with the next 24 hours worth of
5094 Gives you an estimate of the long path propagation characterics. It
5095 should be noted that the figures will probably not be very useful, nor
5096 terrible accurate, but it is included for completeness.
5099 1
\b13
\b3.
\b.1
\b11
\b16
\b6.
\b. s
\bsh
\bho
\bow
\bw/
\b/n
\bno
\bod
\bde
\be (
\b(1
\b1)
\b)
5101 s
\bsh
\bho
\bow
\bw/
\b/n
\bno
\bod
\bde
\be [
\b[<
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> .
\b..
\b..
\b.]
\b] Show the type and version number of nodes
5104 Show the type and version (if connected) of the nodes specified on the
5105 command line. If no callsigns are specified then a sorted list of all
5106 the non-user callsigns known to the system will be displayed.
5109 1
\b13
\b3.
\b.1
\b11
\b17
\b7.
\b. s
\bsh
\bho
\bow
\bw/
\b/p
\bpr
\bre
\bef
\bfi
\bix
\bx (
\b(0
\b0)
\b)
5111 s
\bsh
\bho
\bow
\bw/
\b/p
\bpr
\bre
\bef
\bfi
\bix
\bx <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> Interrogate the prefix database
5114 This command takes the <callsign> (which can be a full or partial
5115 callsign or a prefix), looks up which internal country number it is
5116 and then displays all the relevant prefixes for that country together
5117 with the internal country no, the CQ and ITU regions.
5123 1
\b13
\b3.
\b.1
\b11
\b18
\b8.
\b. s
\bsh
\bho
\bow
\bw/
\b/p
\bpr
\bro
\bog
\bgr
\bra
\bam
\bm (
\b(5
\b5)
\b)
5125 s
\bsh
\bho
\bow
\bw/
\b/p
\bpr
\bro
\bog
\bgr
\bra
\bam
\bm Show the locations of all the included program modules
5128 Show the name and location where every program module was load from.
5129 This is useful for checking where you think you have loaded a .pm file
5133 1
\b13
\b3.
\b.1
\b11
\b19
\b9.
\b. s
\bsh
\bho
\bow
\bw/
\b/q
\bqr
\bra
\ba (
\b(0
\b0)
\b)
5135 s
\bsh
\bho
\bow
\bw/
\b/q
\bqr
\bra
\ba <
\b<l
\blo
\boc
\bca
\bat
\bto
\bor
\br>
\b> [
\b[<
\b<l
\blo
\boc
\bca
\bat
\bto
\bor
\br>
\b>]
\b] Show the distance between locators
5136 s
\bsh
\bho
\bow
\bw/
\b/q
\bqr
\bra
\ba <
\b<l
\bla
\bat
\bt>
\b> <
\b<l
\blo
\bon
\bng
\bg>
\b> Convert latitude and longitude to a locator
5139 This is a multipurpose command that allows you either to calculate the
5140 distance and bearing between two locators or (if only one locator is
5141 given on the command line) the distance and beraing from your station
5142 to the locator. For example:-
5149 The first example will show the distance and bearing to the locator
5150 from yourself, the second example will calculate the distance and
5151 bearing from the first locator to the second. You can use 4 or 6
5154 It is also possible to convert a latitude and longitude to a locator
5155 by using this command with a latitude and longitude as an argument,
5160 SH/QRA 52 41 N 0 58 E
5166 1
\b13
\b3.
\b.1
\b12
\b20
\b0.
\b. s
\bsh
\bho
\bow
\bw/
\b/q
\bqr
\brz
\bz (
\b(0
\b0)
\b)
5168 s
\bsh
\bho
\bow
\bw/
\b/q
\bqr
\brz
\bz <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> Show any callbook details on a callsign
5171 This command queries the QRZ callbook server on the internet and
5172 returns any information available for that callsign. This service is
5173 provided for users of this software by http://www.qrz.com
5176 1
\b13
\b3.
\b.1
\b12
\b21
\b1.
\b. s
\bsh
\bho
\bow
\bw/
\b/r
\bro
\bou
\but
\bte
\be (
\b(0
\b0)
\b)
5178 s
\bsh
\bho
\bow
\bw/
\b/r
\bro
\bou
\but
\bte
\be <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> Show the route to <callsign>
5181 This command allows you to see to which node the callsigns specified
5182 are connected. It is a sort of inverse sh/config.
5192 1
\b13
\b3.
\b.1
\b12
\b22
\b2.
\b. s
\bsh
\bho
\bow
\bw/
\b/s
\bsa
\bat
\bte
\bel
\bll
\bli
\bit
\bte
\be (
\b(0
\b0)
\b)
5194 s
\bsh
\bho
\bow
\bw/
\b/s
\bsa
\bat
\bte
\bel
\bll
\bli
\bit
\bte
\be <
\b<n
\bna
\bam
\bme
\be>
\b> [
\b[<
\b<h
\bho
\bou
\bur
\brs
\bs>
\b> <
\b<i
\bin
\bnt
\bte
\ber
\brv
\bva
\bal
\bl>
\b>]
\b] Show satellite tracking
5198 Show the tracking data from your location to the satellite of your
5199 choice from now on for the next few hours.
5201 If you use this command without a satellite name it will display a
5202 list of all the satellites known currently to the system.
5204 If you give a name then you can obtain tracking data of all the passes
5205 that start and finish 5 degrees below the horizon. As default it will
5206 give information for the next three hours for every five minute
5209 You can alter the number of hours and the step size, within certain
5212 Each pass in a period is separated with a row of '-----' characters
5220 SH/SAT FENGYUN1 12 2
5226 1
\b13
\b3.
\b.1
\b12
\b23
\b3.
\b. s
\bsh
\bho
\bow
\bw/
\b/s
\bsu
\bun
\bn (
\b(0
\b0)
\b)
5228 s
\bsh
\bho
\bow
\bw/
\b/s
\bsu
\bun
\bn [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show sun rise and set times
5231 Show the sun rise and set times for a (list of) prefixes or callsigns,
5232 together with the azimuth and elevation of the sun currently at those
5235 If you don't specify any prefixes or callsigns, it will show the times
5236 for your QTH (assuming you have set it with either SET/LOCATION or
5237 SET/QRA), together with the current azimuth and elevation.
5239 If all else fails it will show the sunrise and set times for the node
5240 that you are connected to.
5247 SH/SUN G1TLH K9CW ZS
5253 1
\b13
\b3.
\b.1
\b12
\b24
\b4.
\b. s
\bsh
\bho
\bow
\bw/
\b/t
\bti
\bim
\bme
\be (
\b(0
\b0)
\b)
5255 s
\bsh
\bho
\bow
\bw/
\b/t
\bti
\bim
\bme
\be [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show the local time
5258 If no prefixes or callsigns are given then this command returns the
5259 local time and UTC as the computer has it right now. If you give some
5260 prefixes then it will show UTC and UTC + the local offset (not
5261 including DST) at the prefixes or callsigns that you specify.
5264 1
\b13
\b3.
\b.1
\b12
\b25
\b5.
\b. s
\bsh
\bho
\bow
\bw/
\b/w
\bwc
\bcy
\by (
\b(0
\b0)
\b)
5266 s
\bsh
\bho
\bow
\bw/
\b/w
\bwc
\bcy
\by Show the last 10 WCY broadcasts
5267 s
\bsh
\bho
\bow
\bw/
\b/w
\bwc
\bcy
\by <
\b<n
\bn>
\b> Show the last <n> WCY broadcasts
5270 Display the most recent WCY information that has been received by the
5274 1
\b13
\b3.
\b.1
\b12
\b26
\b6.
\b. s
\bsh
\bho
\bow
\bw/
\b/w
\bww
\bwv
\bv (
\b(0
\b0)
\b)
5276 s
\bsh
\bho
\bow
\bw/
\b/w
\bww
\bwv
\bv Show the last 10 WWV broadcasts
5277 s
\bsh
\bho
\bow
\bw/
\b/w
\bww
\bwv
\bv <
\b<n
\bn>
\b> Show the last <n> WWV broadcasts
5281 Display the most recent WWV information that has been received by the
5286 1
\b13
\b3.
\b.1
\b12
\b27
\b7.
\b. s
\bsh
\bhu
\but
\btd
\bdo
\bow
\bwn
\bn (
\b(5
\b5)
\b)
5288 s
\bsh
\bhu
\but
\btd
\bdo
\bow
\bwn
\bn Shutdown the cluster
5291 Shutdown the cluster and disconnect all the users. If you have Spider
5292 set to respawn in /etc/inittab it will of course restart.
5295 1
\b13
\b3.
\b.1
\b12
\b28
\b8.
\b. s
\bsp
\bpo
\boo
\bof
\bf (
\b(9
\b9)
\b)
5297 s
\bsp
\bpo
\boo
\bof
\bf <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> <
\b<c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd>
\b> Run commands as another user
5300 This is a very simple yet powerful command for the sysop. It allows
5301 you to issue commands as if you were a different user. This is very
5302 useful for the kind of things that users seem to always get wrong..
5303 like home_node for example.
5306 1
\b13
\b3.
\b.1
\b12
\b29
\b9.
\b. s
\bst
\bta
\bat
\bt/
\b/d
\bdb
\bb (
\b(5
\b5)
\b)
5308 s
\bst
\bta
\bat
\bt/
\b/d
\bdb
\bb <
\b<d
\bdb
\bbn
\bna
\bam
\bme
\be>
\b> Show the status of a database
5311 Show the internal status of a database descriptor.
5313 Depending on your privilege level you will see more or less
5314 information. This command is unlikely to be of much use to anyone
5318 1
\b13
\b3.
\b.1
\b13
\b30
\b0.
\b. s
\bst
\bta
\bat
\bt/
\b/c
\bch
\bha
\ban
\bnn
\bne
\bel
\bl (
\b(5
\b5)
\b)
5320 s
\bst
\bta
\bat
\bt/
\b/c
\bch
\bha
\ban
\bnn
\bne
\bel
\bl <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> Show the status of a channel on the cluster
5323 Show the internal status of the channel object either for the channel
5324 that you are on or else for the callsign that you asked for.
5326 Only the fields that are defined (in perl term) will be displayed.
5329 1
\b13
\b3.
\b.1
\b13
\b31
\b1.
\b. s
\bst
\bta
\bat
\bt/
\b/m
\bms
\bsg
\bg (
\b(5
\b5)
\b)
5331 s
\bst
\bta
\bat
\bt/
\b/m
\bms
\bsg
\bg <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Show the status of a message
5334 This command shows the internal status of a message and includes
5335 information such as to whom it has been forwarded, its size, origin
5339 1
\b13
\b3.
\b.1
\b13
\b32
\b2.
\b. s
\bst
\bta
\bat
\bt/
\b/u
\bus
\bse
\ber
\br (
\b(5
\b5)
\b)
5341 s
\bst
\bta
\bat
\bt/
\b/u
\bus
\bse
\ber
\br <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> Show the full status of a user
5344 Shows the full contents of a user record including all the secret
5347 Only the fields that are defined (in perl term) will be displayed.
5350 1
\b13
\b3.
\b.1
\b13
\b33
\b3.
\b. s
\bsy
\bys
\bso
\bop
\bp (
\b(0
\b0)
\b)
5352 s
\bsy
\bys
\bso
\bop
\bp Regain your privileges if you login remotely
5355 The system automatically reduces your privilege level to that of a
5356 normal user if you login in remotely. This command allows you to
5357 regain your normal privilege level. It uses the normal system: five
5358 numbers are returned that are indexes into the character array that is
5359 your assigned password (see SET/PASSWORD). The indexes start from
5362 You are expected to return a string which contains the characters
5363 required in the correct order. You may intersperse those characters
5364 with others to obscure your reply for any watchers. For example (and
5365 these values are for explanation :-):
5369 password = 012345678901234567890123456789
5380 aa2bbbb0ccc5ddd7xxx3n
5387 They will all match. If there is no password you will still be offered
5388 numbers but nothing will happen when you input a string. Any match is
5392 1
\b13
\b3.
\b.1
\b13
\b34
\b4.
\b. t
\bta
\bal
\blk
\bk (
\b(0
\b0)
\b)
5394 t
\bta
\bal
\blk
\bk <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> Enter talk mode with <callsign>
5395 t
\bta
\bal
\blk
\bk <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send a text message to <callsign>
5396 t
\bta
\bal
\blk
\bk <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> >
\b> <
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> [
\b[<
\b<t
\bte
\bex
\bxt
\bt>
\b>]
\b] Send a text message to
5397 <callsign> via <node_call>
5400 Send a short message to any other station that is visible on the
5401 cluster system. You can send it to anyone you can see with a
5402 SHOW/CONFIGURATION command, they don't have to be connected locally.
5404 The second form of TALK is used when other cluster nodes are connected
5405 with restricted information. This usually means that they don't send
5406 the user information usually associated with logging on and off the
5409 If you know that G3JNB is likely to be present on GB7TLH, but you can
5410 only see GB7TLH in the SH/C list but with no users, then you would use
5411 the second form of the talk message.
5413 If you want to have a ragchew with someone you can leave the text
5414 message out and the system will go into 'Talk' mode. What this means
5415 is that a short message is sent to the recipient telling them that you
5416 are in a 'Talking' frame of mind and then you just type - everything
5417 you send will go to the station that you asked for.
5419 All the usual announcements, spots and so on will still come out on
5422 If you want to do something (such as send a spot) you precede the
5423 normal command with a '/' character, eg:-
5427 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
5433 To leave talk mode type:
5443 1
\b13
\b3.
\b.1
\b13
\b35
\b5.
\b. t
\bty
\byp
\bpe
\be (
\b(0
\b0)
\b)
5445 t
\bty
\byp
\bpe
\be <
\b<f
\bfi
\bil
\ble
\bea
\bar
\bre
\bea
\ba>
\b>/
\b/<
\b<n
\bna
\bam
\bme
\be>
\b> Look at a file in one of the fileareas
5448 Type out the contents of a file in a filearea. So, for example, in
5449 filearea 'bulletins' you want to look at file 'arld051' you would
5454 TYPE bulletins/arld051
5459 See also SHOW/FILES to see what fileareas are available and a list of
5463 1
\b13
\b3.
\b.1
\b13
\b36
\b6.
\b. w
\bwh
\bho
\bo (
\b(0
\b0)
\b)
5465 w
\bwh
\bho
\bo Show who is physically connected locally
5468 This is a quick listing that shows which callsigns are connected and
5469 what sort of connection they have
5472 1
\b13
\b3.
\b.1
\b13
\b37
\b7.
\b. w
\bwx
\bx (
\b(0
\b0)
\b)
5474 w
\bwx
\bx <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send a weather message to local users
5475 w
\bwx
\bx f
\bfu
\bul
\bll
\bl <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send a weather message to all cluster users
5479 Weather messages can sometimes be useful if you are experiencing an
5480 extreme that may indicate enhanced conditions
5483 1
\b13
\b3.
\b.1
\b13
\b38
\b8.
\b. w
\bwx
\bx (
\b(e
\ben
\bnh
\bha
\ban
\bnc
\bce
\bed
\bd f
\bfo
\bor
\br s
\bsy
\bys
\bso
\bop
\bps
\bs)
\b) (
\b(5
\b5)
\b)
5485 w
\bwx
\bx s
\bsy
\bys
\bso
\bop
\bp <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send a weather message to other clusters only
5488 Send a weather message only to other cluster nodes and not to general