1 The DXSpider Installation and Administration Manual
2 Ian Maude, G0VGS, (ianmaude@btinternet.com)
3 Version 1.30 January 2001
5 A reference for SysOps of the DXSpider DXCluster program.
6 ______________________________________________________________________
67 1. Installation (Original version by Iain Phillips, G0RDI)
71 1.3 Installing the software
72 1.4 Setting callsigns etc
73 1.5 Starting up for the first time
79 3.1 Allowing ax25 connects from users
80 3.2 Allowing telnet connects from users
81 3.3 Setting up node connects
82 3.4 Connection scripts
83 3.5 Starting the connection
88 4.1 Autostarting the cluster
94 5.2 Isolating networks
96 6. Filtering (Old Style upto v1.44)
102 7. Filtering (New Style v1.45 and later)
104 7.1 General filter rules
108 7.5 Advanced filtering
113 8.2 Filtering DX callouts (Depricated)
114 8.3 Filtering words from text fields in Announce, Talk and DX spots
116 9. Information, files and useful programs
120 9.3 Other text messages
123 9.6 Distribution lists
126 9.9 Updating kepler data
130 11. The DXSpider command set
132 11.1 accept/announce (0)
133 11.2 accept/announce (extended for sysops) (8)
134 11.3 accept/spots (0)
135 11.4 accept/spots (extended for sysops) (8)
137 11.6 accept/wcy (extended for sysops) (8)
139 11.8 accept/wwv (extended for sysops) (8)
141 11.10 announce full (0)
142 11.11 announce sysop (5)
146 11.15 clear/spots (0)
155 11.24 directory (extended for sysops) (5)
159 11.28 export_users (9)
160 11.29 forward/latlong (8)
161 11.30 forward/opername (1)
168 11.37 load/aliases (9)
170 11.39 load/badmsg (9)
171 11.40 load/badwords (9)
173 11.42 load/cmd_cache (9)
174 11.43 load/forward (9)
175 11.44 load/messages (9)
176 11.45 load/prefixes (9)
183 11.52 read (extended for sysops) (5)
184 11.53 reject/announce
185 11.54 reject/announce (extended for sysops) (8)
186 11.55 reject/spots (0)
187 11.56 reject/spots (extended for sysops) (8)
189 11.58 reject/wcy (extended for sysops) (8)
191 11.60 reject/wwv (extended for sysops) (8)
194 11.63 set/address (0)
195 11.64 set/announce (0)
196 11.65 set/arcluster (5)
198 11.67 set/badnode (6)
199 11.68 set/badspotter (8)
208 11.77 set/homenode (0)
210 11.79 set/isolate (9)
211 11.80 set/language (0)
212 11.81 set/location (0)
213 11.82 set/sys_location (9)
214 11.83 set/logininfo (0)
215 11.84 set/lockout (9)
218 11.87 set/obscount (9)
220 11.89 set/password (9)
221 11.90 set/pinginterval (9)
222 11.91 set/privilege (9)
224 11.93 set/sys_qra (9)
231 11.100 show/baddx (1)
232 11.101 show/badnode (6)
233 11.102 show/badspotter (1)
237 11.106 show/files (0)
238 11.107 show/filter (0)
239 11.108 show/filter (extended for sysops) (5)
241 11.110 show/isolate (1)
242 11.111 show/lockout (9)
246 11.115 show/prefix (0)
247 11.116 show/program (5)
250 11.119 show/route (0)
251 11.120 show/satellite (0)
259 11.128 stat/channel (5)
267 11.136 wx (enhanced for sysops) (5)
270 ______________________________________________________________________
272 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
\bll
\bli
\bip
\bps
\bs,
\b, G
\bG0
\b0R
\bRD
\bDI
\bI)
\b)
274 Last modified: 26 January 2001 by Ian Maude, G0VGS
277 1
\b1.
\b.1
\b1.
\b. I
\bIn
\bnt
\btr
\bro
\bod
\bdu
\buc
\bct
\bti
\bio
\bon
\bn
279 This section describes the installation of DX Spider v1.35 on a RedHat
280 Linux Distribution. I do not intend to try and cover the installation
281 of Linux or the setup of the AX25 utilities. If you need help on this
282 then read Iains original HOWTO on the DXSpider website.
285 I am assuming a general knowledge of Linux and its commands. You
286 should know how to use _
\bt_
\ba_
\br and how to edit files using your favourite
290 The crucial ingredient for all of this is Perl 5.004. Now I know Perl
291 5.005 is out and this will almost certainly work with it, but RedHat
292 5.1 comes with 5.004. _
\bB_
\be _
\bW_
\ba_
\br_
\bn_
\be_
\bd, earlier versions of RedHat d
\bdo
\bo n
\bno
\bot
\bt
293 come with 5.004 as standard, you need to upgrade
296 In addition to the standard Red Hat distribution you will require the
297 following CPAN modules: -
303 +
\bo Data-Dumper-2.10.tar.gz
305 +
\bo FreezeThaw-0.3.tar.gz
307 +
\bo MLDBM-2.00.tar.gz
309 +
\bo TimeDate-1.08.tar.gz
313 +
\bo Net-Telnet-3.02.tar.gz
315 +
\bo Curses-1.05.tar.gz
317 +
\bo Time-HiRes-01.20.tar.gz
321 _
\bD_
\bo get the latest versions of these packages and install them but use
322 the above list as the earliest versions usable.
325 1
\b1.
\b.2
\b2.
\b. P
\bPr
\bre
\bep
\bpa
\bar
\bra
\bat
\bti
\bio
\bon
\bn
327 I will assume that you have already downloaded the latest tarball of
328 the DXSpider software and are ready to install it. I am assuming
329 version 1.35 for this section but of course you would use the latest
331 Login as root and create a user to run the cluster under. _
\bU_
\bN_
\bD_
\bE_
\bR _
\bN_
\bO
332 _
\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
333 _
\bs_
\by_
\bs_
\bo_
\bp. You can call it anything you wish. Depending on your security
334 requirements you may wish to use an existing user, however this is
346 Now set a password for the user ...
352 # Retype new UNIX password:
353 passwd: all authentication tokens updated successfully
359 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
361 Now to unpack the DX Spider distribution, set symbolic links and group
362 permissions. Copy the tarball to /home/sysop and do the following.
367 # tar xvfz spider-1.35.tar.gz
368 # ln -s ~sysop/spider /spider
369 # groupadd -g 251 spider (or another number)
374 If you do not have the command _
\bg_
\br_
\bo_
\bu_
\bp_
\ba_
\bd_
\bd available to you simply add a
375 line in /etc/group by hand.
379 # vi /etc/group (or your favorite editor)
384 You also need to add some others to the group, including your own
385 callsign (this will be used as an alias) and root. The finished line
386 in /etc/group should look something like this
388 spider:x:251:sysop,g0vgs,root
391 The next step is to set the permissions on the Spider directory tree
397 # chown -R sysop.spider spider
398 # find . -type d -exec chmod 2775 {} \;
399 # find . -type f -exec chmod 775 {} \;
405 This last step allows various users of the group _
\bs_
\bp_
\bi_
\bd_
\be_
\br to have write
406 access to all the directories. This is not really needed just yet but
407 will be useful when web interfaces start to appear.
410 Finally, you need to fix the permissions on the ax25_call and
411 netrom_call programs. Check where they are with the _
\bl_
\bo_
\bc_
\ba_
\bt_
\be command
412 and alter the permissions with the _
\bc_
\bh_
\bm_
\bo_
\bd command like this ..
416 # chown root ax25_call netrom_call
417 # chmod 4775 ax25_call netrom_call
423 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
425 Now login to your machine as the user you created earlier. In my case
426 that user is called _
\bs_
\by_
\bs_
\bo_
\bp. Once logged in, issue the following
434 $ cp perl/DXVars.pm.issue local/DXVars.pm
436 $ vi DXVars.pm (or your favourite editor)
442 Using the distributed DXVars.pm as a a template, set your cluster
443 callsign, sysop callsign and other user info to suit your own
444 environment. Note that this a perl file which will be parsed and
445 executed as part of the cluster. If you get it wrong then perl will
446 complain when you start the cluster process. It is important only to
447 alter the text of any section. Some of the lines look a little odd.
448 Take this line for example ....
450 $myemail = "ianmaude\@btinternet.com";
453 There appears to be an extra slash in there. However this has to be
454 there for the file to work so leave it in.
457 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
460 DON'T alter the DXVars.pm (or any other file) in /spider/perl, they
461 are overwritten with every release. Any files or commands you place in
462 /spider/local or /spider/local_cmd will automagically be used in
463 preference to the ones in /spider/perl EVEN while the cluster is
467 Save the new file and change directory to ../perl ....
477 Now type the following command which creates the basic user file with
488 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
490 We can now bring spider up for the first time and see if all is well
491 or not! It should look something like this ...
496 DXSpider DX Cluster Version 1.35
497 Copyright (c) 1998 Dirk Koopman G1TLH
499 loading band data ...
500 loading user file system ...
501 starting listener ...
502 reading existing message headers
504 orft we jolly well go ...
510 If all is well then login on another term or console as _
\bs_
\by_
\bs_
\bo_
\bp and cd
511 to /spider/perl. Now issue the following command ...
521 This should log you into the cluster as the sysop under the alias
522 callsign we set earlier. In this case the callsign is G0VGS. The
523 cluster callsign is set in the DXVars.pm file in /spider/local. In
524 this case we will assume that this was set as GB7MBC. You should
525 therefore see this when you login ....
529 G0VGS de GB7MBC 19-Nov-1999 2150Z >
534 If you do, congratulations! If not, look over the instructions again,
535 you have probably missed something out. You can shut spider down
536 again with the command ....
546 and both the cluster and the client should return to Linux prompts.
549 2
\b2.
\b. T
\bTh
\bhe
\be C
\bCl
\bli
\bie
\ben
\bnt
\bt p
\bpr
\bro
\bog
\bgr
\bra
\bam
\bm
551 In earlier versions of Spider, all the processes were Perl scripts.
552 This was fine but with a lot of users your computer memory would soon
553 be used up. To combat this a new client was written in "C". This
554 client only works for _
\bi_
\bn_
\bc_
\bo_
\bm_
\bi_
\bn_
\bg connects at the moment. Before you can
555 use it though it has to be "made". CD to /spider/src and type _
\bm_
\ba_
\bk_
\be.
556 You should see the output on your screen and hopefully now have a
557 small C program called _
\bc_
\bl_
\bi_
\be_
\bn_
\bt. Leave it in this directory.
560 3
\b3.
\b. C
\bCo
\bon
\bnf
\bfi
\big
\bgu
\bur
\bra
\bat
\bti
\bio
\bon
\bn
562 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
564 As stated previously, the aim of this document is not to tell you how
565 to configure Linux or the ax25 utilities. However, you do need to add
566 a line in your ax25d.conf to allow connections to DXSpider for your
567 users. For each interface that you wish to allow connections on, use
568 the following format ...
572 default * * * * * * - sysop /spider/src/client client %u ax25
578 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
580 Allowing telnet connections is quite simple. Firstly you need to add
581 a line in /etc/services to allow connections to a port number, like
586 spdlogin 8000/tcp # spider anonymous login port
591 Then add a line in /etc/inetd.conf like this ....
595 spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
601 This needs to be added above the standard services such as ftp, telnet
602 etc. Once this is done, you need to restart inetd like this ....
613 Now login as _
\bs_
\by_
\bs_
\bo_
\bp and cd spider/perl. You can test that spider is
614 accepting telnet logins by issuing the following command ....
618 client.pl login telnet
623 You should get a login prompt and on issuing a callsign, you will be
624 given access to the cluster. Note, you will not get a password login.
625 There seems no good reason for a password prompt to be given so it is
629 Assuming all is well, then try a telnet from your linux console ....
633 telnet localhost 8000
639 You should now get the login prompt and be able to login as before.
642 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
644 In order to allow cluster node connections, spider needs to know that
645 the connecting callsign is a cluster node. This is the case whether
646 the connect is incoming or outgoing. In spider this is a simple task
647 and can be done in runtime.
650 Later versions of Spider can distinguish different software and treat
651 them differently. For example, the WCY beacon cannot be handles by
652 AK1A type nodes as AK1A does not know what to do with PC73. There are
653 4 different types of node at present and although they may not have
654 any major differences at the moment, it allows for compatibility. The
670 For now, we will assume that the cluster we are going to connect to is
674 Start up the cluster as you did before and login as the sysop with
675 client.pl. The cluster node I am wanting to make a connection to is
676 GB7BAA but you would obviously use whatever callsign you required. At
687 The case does not matter as long as you have a version of DXSpider
688 later than 1.33. Earlier versions required the callsign to be in
692 That is now set, it is as simple as that. To prove it, login on yet
693 another console as sysop and issue the command ...
697 client.pl gb7baa (using the callsign you set as a node)
703 You should get an initialisation string from DXSpider like this ...
713 If the callsign you just set up as a cluster node is for an incoming
714 connect, this is all that needs to be done. If the connection is to
715 be outgoing then a connection script needs to be written.
718 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
720 Because DXSpider operates under Linux, connections can be made using
721 just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all
722 possible examples. Connect scripts live in the /spider/connect
723 directory and are simple ascii files. Writing a script for
724 connections is therefore relatively simple.
727 The connect scripts consist of lines which start with the following
728 keywords or symbols:-
732 # All lines starting with a # are ignored, as are completely
735 timeout timeout followed by a number is the number of seconds to wait for a
736 command to complete. If there is no timeout specified in the script
737 then the default is 60 seconds.
739 abort abort is a regular expression containing one or more strings to look
740 for to abort a connection. This is a perl regular expression and is
741 executed ignoring case.
743 connect connect followed by ax25 or telnet and some type dependent
744 information. In the case of a telnet connection, there can be up to
746 The first is the ip address or hostname of the computer you wish to
747 connect to and the second is the port number you want to use (this
748 can be left out if it is a normal telnet session).
749 In the case of an ax25 session then this would normally be a call to
750 ax25_call or netrom_call as in the example above. It is your
751 responsibility to get your node and other ax25 parameters to work
752 before going down this route!
754 ' line in a chat type script. The words/phrases normally come in pairs,
755 either can be empty. Each line reads input from the connection until
756 it sees the string (or perl regular expression) contained in the
757 left hand string. If the left hand string is empty then it doesn't
758 read or wait for anything. The comparison is done ignoring case.
759 When the left hand string has found what it is looking for (if it is)
760 then the right hand string is sent to the connection.
761 This process is repeated for every line of chat script.
763 client client starts the connection, put the arguments you would want here
764 if you were starting the client program manually. You only need this
765 if the script has a different name to the callsign you are trying to
766 connect to (i.e. you have a script called other which actually
767 connects to GB7DJK-1 [instead of a script called gb7djk-1]).
772 There are many possible ways to configure the script but here are two
773 examples, one for a NETRom/AX25 connect and one for tcp/ip.
778 abort (Busy|Sorry|Fail)
779 # don't forget to chmod 4775 netrom_call!
780 connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
781 # you can leave this out if you call the script 'gb7dxm'
794 connect telnet dirkl.tobit.co.uk
795 # tell GB7DJK-1 that it is connected to GB7DJK
796 # you can leave this out if you call this script 'gb7djk'
803 Both these examples assume that everything is set up properly at the
804 other end. You will find other examples in the /spider/examples
808 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
810 You start the connection, from within a sysop enabled cluster login,
811 by typing in the word _
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt followed by a script name like this ....
815 G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1
816 connection to GB7DJK-1 started
817 G0VGS de GB7MBC 13-Dec-1998 2043Z >
822 This will start a connection using the script called _
\bg_
\bb_
\b7_
\bd_
\bj_
\bk_
\b-_
\b1. You
823 can follow the connection by watching the term or console from where
824 you started _
\bc_
\bl_
\bu_
\bs_
\bt_
\be_
\br_
\b._
\bp_
\bl. You should see something like this ...
828 <- D G1TLH connect gb7djk-1
829 -> D G1TLH connection to GB7DJK-1 started
830 -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
832 CONNECT sort: telnet command: dirkl.tobit.co.uk
833 CHAT "login" -> "gb7djk"
835 Red Hat Linux release 5.1 (Manhattan)
836 Kernel 2.0.35 on an i586
840 CHAT "word" -> "gb7djk"
842 received "Password: "
844 Connected to GB7DJK-1, starting normal protocol
847 GB7DJK-1 channel func state 0 -> init
849 <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1
850 <- D GB7DJK-1 PC38^GB7DJK-1^~
851 <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime
859 With later versions of Spider there is a set/login command for users.
860 This tells them when a user or node logs in or out. If you do not add
861 a line to your scripts after the final line (or before the client line
862 which should always be last if needed) then the login/logout
863 information will be sent to users _
\bb_
\be_
\bf_
\bo_
\br_
\be the login actually completes.
864 This means if a node is unreachable, it will continue sending logins
865 and logouts to users even though it is not actually connecting. To
866 avoid this use the following line ...
875 In a script, this might look like ...
880 abort (Busy|Sorry|Fail)
881 connect telnet mary 3000
887 3
\b3.
\b.6
\b6.
\b. T
\bTe
\bel
\bln
\bne
\bet
\bt e
\bec
\bch
\bho
\bo
889 Cluster links in particular suffer greatly from the presence of telnet
890 echo. This is caused by the telnet negotiation itself and can create
891 at worst severe loops. At best it creates unnecessary bandwidth and
892 large logfiles! There are things that can be done to limit this
893 problem but will not always work dependent on the route taken to
897 Telnet echo itself should only be a problem if the connection is being
898 made to the telnet port (23). This port uses special rules that
899 include echo negotiation. If the connection is to a different port,
900 such as 8000, this negotiation does not happen and therefore no echo
904 Sometimes it is not possible to make a direct connection to another
905 node and this can cause problems. There is a way of trying to
906 suppress the telnet echo but this will not always work, unfortunately
907 it is difficult to be more specific. Here is an example of what I
913 abort (Busy|Sorry|Fail)
914 connect telnet mary.lancs.ac.uk
919 So, the first connection is made by Spider. This is fine as Spider
920 uses the Net_Telnet script from within perl. This actually uses TCP
921 rather than TELNET so no negotiation will be done on the first
922 connection. Once connected to mary.lancs.ac.uk, the command is sent
923 to suppress echo. Now a telnet is made to a cluster node that is
924 accepting connections on port 23. The problem with this link is that
925 the negotiation is made by the remote machine, therefore you have no
926 control over it. The chances are that this link will create echo and
927 there will be no way you can stop it.
931 4
\b4.
\b. A
\bAu
\but
\bto
\bom
\bma
\bat
\bti
\bin
\bng
\bg t
\bth
\bhi
\bin
\bng
\bgs
\bs
933 Ok, you should now have DXSpider running nicely and allowing connects
934 by cluster nodes or users. However, it has to be shutdown and
935 restarted manually and if connection scripts fail they have to be
936 started again manually too, not much use if you are not at the
937 console! So, in this section we will automate both. Firstly starting
941 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
943 This is not only a way to start the cluster automatically, it also
944 works as a watchdog, checking the sanity of DXSpider and respawning it
945 should it crash for any reason. Before doing the following, shutdown
946 the cluster as you did earlier.
949 Login as root and bring up the /etc/inittab file in your favourite
950 editor. Add the following lines to the file near the end ...
954 ##Start DXSpider on bootup and respawn it should it crash
955 DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
961 This will automatically start DXSpider on tty7 (ALT-F7) on bootup and
962 restart it should it crash for any reason.
965 As root type the command _
\bt_
\be_
\bl_
\bi_
\bn_
\bi_
\bt _
\bq. DXSpider should start up
966 immediately. You will see the output on tty7 and if you login as
967 _
\bs_
\by_
\bs_
\bo_
\bp you should find everything running nicely.
970 So far so good, now to automate script connections...
973 4
\b4.
\b.2
\b2.
\b. T
\bTh
\bhe
\be c
\bcr
\bro
\bon
\bnt
\bta
\bab
\bb f
\bfi
\bil
\ble
\be
975 Login as _
\bs_
\by_
\bs_
\bo_
\bp and create a file in /spider/local_cmd called crontab.
976 Edit it with your favourite editor and add a line like this (I have
981 # check every 10 minutes to see if gb7xxx is connected and if not
982 # start a connect job going
984 0,10,20,30,40,50 * * * * start_connect('gb7xxx') if !connected('gb7xxx')
991 The callsign involved will be the callsign of the cluster node you are
992 going to connect to. This will now check every 10 minutes to see if
993 gb7xxx is connected, if it is then nothing will be done. If it is
994 not, then a connect attempt will be started.
997 There are probably lots of other things you could use this crontab
998 file for. If you want to know more about it, look at the DXSpider
999 website at the cron page where it is explained more fully.
1002 5
\b5.
\b. H
\bHo
\bop
\bp c
\bco
\bon
\bnt
\btr
\bro
\bol
\bl
1004 Starting with version 1.13 there is simple hop control available on a
1005 per node basis. Also it is possible to isolate a network completely so
1006 that you get all the benefits of being on that network, but can't pass
1007 on information from it to any other networks you may be connected to
1011 5
\b5.
\b.1
\b1.
\b. B
\bBa
\bas
\bsi
\bic
\bc h
\bho
\bop
\bp c
\bco
\bon
\bnt
\btr
\bro
\bol
\bl
1013 In /spider/data you will find a file called hop_table.pl. This is the
1014 file that controls your hop count settings. It has a set of default
1015 hops on the various PC frames and also a set for each node you want to
1016 alter the hops for. You may be happy with the default settings of
1017 course, but this powerful tool can help to protect and improve the
1018 network. The file will look something like this ...
1058 # hop table construction
1063 # default hopcount to use
1066 # some variable hop counts based on message type
1077 # the per node hop control thingy
1082 GB7ADX => { 11 => 8,
1090 GB7UDX => { 11 => 8,
1111 Each set of hops is contained within a pair of curly braces and
1112 contains a series of PC frame types. PC11 for example is a DX spot.
1113 The figures here are not exhaustive but should give you a good idea of
1117 You can alter this file at any time, including whilst the cluster is
1118 running. If you alter the file during runtime, the command _
\bl_
\bo_
\ba_
\bd_
\b/_
\bh_
\bo_
\bp_
\bs
1119 will bring your changes into effect.
1123 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
1125 It is possible to isolate networks from each other on a "gateway" node
1126 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.
1129 The effect of this is to partition an isolated network completely from
1130 another nodes connected to your node. Your node will appear on and
1131 otherwise behave normally on every network to which you are connected,
1132 but data from an isolated network will not cross onto any other
1133 network or vice versa. However all the spot, announce and WWV traffic
1134 and personal messages will still be handled locally (because you are a
1135 real node on all connected networks), that is locally connected users
1136 will appear on all networks and will be able to access and receive
1137 information from all networks transparently. All routed messages will
1138 be sent as normal, so if a user on one network knows that you are a
1139 gateway for another network, he can still still send a talk/announce
1140 etc message via your node and it will be routed across.
1143 The only limitation currently is that non-private messages cannot be
1144 passed down isolated links regardless of whether they are generated
1145 locally. This will change when the bulletin routing facility is added.
1148 If you use isolate on a node connection you will continue to receive
1149 all information from the isolated partner, however you will not pass
1150 any information back to the isolated node. There are times when you
1151 would like to forward only spots across a link (maybe during a contest
1152 for example). To do this, isolate the node in the normal way and put
1153 in a filter in the /spider/filter/spots directory to override the
1154 isolate. This filter can be very simple and consists of just one line
1160 [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count
1167 There is a lot more on filtering in the next section.
1170 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)
1172 Filters can be set for spots, announcements and WWV. You will find
1173 the directories for these under /spider/filter. You will find some
1174 examples in the directories with the suffix _
\b._
\bi_
\bs_
\bs_
\bu_
\be. There are two
1175 types of filter, one for incoming information and one for outgoing
1176 information. Outgoing filters are in the form _
\bC_
\bA_
\bL_
\bL_
\bS_
\bI_
\bG_
\bN_
\b._
\bp_
\bl and
1177 incoming filters are in the form _
\bi_
\bn_
\b__
\bC_
\bA_
\bL_
\bL_
\bS_
\bI_
\bG_
\bN_
\b._
\bp_
\bl. Filters can be set
1178 for both nodes and users.
1181 All filters work in basically the same way. There are several
1182 elements delimited by commas. There can be many lines in the filter
1183 and they are read from the top by the program. When writing a filter
1184 you need to think carefully about just what you want to achieve. You
1185 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
1186 filter as having 2 main elements. For a reject filter, you would have
1187 a line or multiple lines rejecting the things you do not wish to
1188 receive and then a default line accepting everything else that is not
1189 included in the filter. Likewise, for an accept filter, you would
1190 have a line or multiple lines accepting the things you wish to receive
1191 and a default line rejecting everthing else.
1194 In the example below, a user requires a filter that would only return
1195 SSB spots posted in Europe on the HF bands. This is achieved by first
1196 rejecting the CW section of each HF band and rejecting all of VHF, UHF
1197 etc based on frequency. Secondly, a filter rule is set based on CQ
1198 zones to only accept spots posted in Europe. Lastly, a default filter
1199 rule is set to reject anything outside the filter.
1204 [ 0, 0, 'r', # reject all CW spots
1214 30000.0, 49000000000.0,
1216 [ 1, 11, 'n', [ 14, 15, 16, 20, 33, ], 15 ], #accept EU
1217 [ 0, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
1224 The actual elements of each filter are described more fully in the
1228 6
\b6.
\b.1
\b1.
\b. S
\bSp
\bpo
\bot
\bts
\bs
1230 The elements of the Spot filter are ....
1234 [action, field_no, sort, possible_values, hops]
1240 There are 3 elements here to look at. Firstly, the action element.
1241 This is very simple and only 2 possible states exist, accept (1) or
1245 The second element is the field_no. There are 13 possiblities to
1246 choose from here ....
1257 2 = date in unix format
1260 5 = spotted dxcc country
1261 6 = spotter's dxcc country
1267 12 = callsign of the channel on which the spot has appeared
1273 The third element tells us what to expect in the fourth element.
1274 There are 4 possibilities ....
1278 n - numeric list of numbers e.g. [ 1,2,3 ]
1279 r - ranges of pairs of numbers e.g. between 2 and 4 or 10 to 17 - [ 2,4, 10,17 ]
1280 a - an alphanumeric regex
1281 d - the default rule
1287 The fifth element is simply the hops to set in this filter. This
1288 would only be used if the filter was for a node of course and
1289 overrides the hop count in hop_table.pl.
1292 So, let's look at an example spot filter. It does not matter in the
1293 example who the filter is to be used for. So, what do we need in the
1294 filter? We need to filter the spots the user/node requires and also
1295 set a default rule for anything else outside the filter. Below is a
1296 simple filter that stops spots arriving from outside Europe.
1301 [ 0, 4, 'a', '^(K|N|A|W|VE|VA|J)'], # 0 = drop, 'a' = alphanumeric
1302 [ 1, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
1309 So the filter is wrapped in between a pair of square brackets. This
1310 tells Spider to look in between these limits. Then each line is
1311 contained within its own square brackets and ends with a comma. Lets
1312 look carefully at the first line. The first element is 0 (drop).
1313 Therefore anything we put on this line will not be accepted. The next
1314 element is 4. This means we are filtering by the spotter. The third
1315 element is the letter "a" which tells the program to expect an
1316 alphanumeric expression in the fourth element. The fourth element is
1317 a list of letters separated by the pipe symbol.
1321 What this line does is tell the program to drop any spots posted by
1322 anyone in the USA, Canada or Japan.
1325 The second line is the default rule for anything else. The "d" tells
1326 us this and the line simply reads... accept anything else.
1329 You can add as many lines as you need to complete the filter but if
1330 there are several lines of the same type it is neater to enclose them
1331 all as one line. An example of this is where specific bands are set.
1332 We could write this like this ....
1336 [ 0,0,'r',[1800.0, 2000.0], 1],
1337 [ 0,0,'r',[10100.0, 10150.0], 1],
1338 [ 0,0,'r',[14000.0, 14350.0], 1],
1339 [ 0,0,'r',[18000.0, 18200.0], 1],
1345 But the line below achieves the same thing and is more efficient ....
1351 1800.0, 2000.0, # top band
1352 10100.0, 10150.0, # WARC
1353 14000.0, 14350.0, # 20m
1354 18000.0, 18200.0, # WARC
1362 6
\b6.
\b.2
\b2.
\b. A
\bAn
\bnn
\bno
\bou
\bun
\bnc
\bce
\bem
\bme
\ben
\bnt
\bts
\bs
1367 # This is an example announce or filter allowing only West EU announces
1369 # The element list is:-
1370 # 0 - callsign of announcer
1371 # 1 - destination * = all, <callsign> = routed to the node
1373 # 3 - * - sysop, <some text> - special list eg 6MUK, ' ', normal announce
1375 # 5 - 0 - announce, 1 - wx
1376 # 6 - channel callsign (the interface from which this spot came)
1379 [ 1, 0, 'a', '^(P[ABCDE]|DK0WCY|G|M|2|EI|F|ON)' ],
1387 In this example, only the prefixes listed will be allowed. It is
1388 possible to be quite specific. The Dutch prefix "P" is followed by
1389 several secondary identifiers which are allowed. So, in the example,
1390 "PA" or "PE" would be ok but not "PG". It is even possible to allow
1391 information from a single callsign. In the example this is DK0WCY, to
1392 allow the posting of his Aurora Beacon.
1395 6
\b6.
\b.3
\b3.
\b. W
\bWW
\bWV
\bV
1400 # This is an example WWV filter
1402 # The element list is:-
1403 # 0 - nominal unix date of spot (ie the day + hour:13)
1411 # 8 - incoming interface callsign
1413 # this one doesn't filter, it just sets the hop count to 6 and is
1414 # used mainly just to override any isolation from WWV coming from
1425 It should be noted that the filter will start to be used only once a
1426 user/node has logged out and back in again.
1428 I am not going to spend any more time on these filters now as they
1429 will become more "comprehensive" in the near future.
1432 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)
1434 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
1436 Upto v1.44 it was not possible for the user to set their own filters.
1437 From v1.45 though that has all changed. It is now possible to set
1438 filters for just about anything you wish. If you have just updated
1439 from an older version of DXSpider you will need to update your new
1440 filters. You do not need to do anything with your old filters, they
1441 will be renamed as you update.
1444 There are 3 basic commands involved in setting and manipulating
1445 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
1446 generally at filtering. There are a number of things you can filter in
1447 the DXSpider system. They all use the same general mechanism.
1450 In general terms you can create a 'reject' or an 'accept' filter which
1451 can have up to 10 lines in it. You do this using, for example ...
1459 where ..... are the specific commands for that type of filter. There
1460 are filters for spots, wwv, announce, wcy and (for sysops) connects.
1461 See each different accept or reject command reference for more
1464 There is also a command to clear out one or more lines in a filter.
1475 There is clear/xxxx command for each type of filter.
1478 and you can check that your filters have worked by the command ...
1489 For now we are going to use spots for the examples, but you can apply
1490 the same principles to all types of filter.
1493 7
\b7.
\b.2
\b2.
\b. T
\bTy
\byp
\bpe
\bes
\bs o
\bof
\bf f
\bfi
\bil
\blt
\bte
\ber
\br
1495 There are two main types of filter, _
\ba_
\bc_
\bc_
\be_
\bp_
\bt or _
\br_
\be_
\bj_
\be_
\bc_
\bt. You can use
1496 either to achieve the result you want dependent on your own preference
1497 and which is more simple to do. It is pointless writing 8 lines of
1498 reject filters when 1 accept filter would do the same thing! Each
1499 filter has 10 lines (of any length) which are tried in order. If a
1500 line matches then the action you have specified is taken (ie reject
1501 means ignore it and accept means take it)
1504 If you specify reject filters, then any lines that arrive that match
1505 the filter will be dumped but all else will be accepted. If you use
1506 an accept filter, then ONLY the lines in the filter will be accepted
1507 and all else will be dumped. For example if you have a single line
1508 _
\ba_
\bc_
\bc_
\be_
\bp_
\bt filter ...
1512 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1517 then you will _
\bO_
\bN_
\bL_
\bY get VHF spots _
\bf_
\br_
\bo_
\bm or _
\bt_
\bo CQ zones 14, 15 and 16.
1519 If you set a reject filter like this ...
1523 reject/spots on hf/cw
1528 Then you will get everything _
\bE_
\bX_
\bC_
\bE_
\bP_
\bT HF CW spots. You could make this
1529 single filter even more flexible. For example, if you are interested
1530 in IOTA and will work it even on CW even though normally you are not
1531 interested in CW, then you could say ...
1535 reject/spots on hf/cw and not info iota
1540 But in that case you might only be interested in iota and say:-
1544 accept/spots not on hf/cw or info iota
1549 which achieves exactly the same thing. You should choose one or the
1550 other until you are comfortable with the way it works. You can mix
1551 them if you wish (actually you can have an accept AND a reject on the
1552 same line) but don't attempt this until you are sure you know what you
1556 You can arrange your filter lines into logical units, either for your
1557 own understanding or simply convenience. Here is an example ...
1561 reject/spots 1 on hf/cw
1562 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
1567 What this does is to ignore all HF CW spots and also rejects any spots
1568 on VHF which don't either originate or spot someone in Europe.
1571 This is an example where you would use a line number (1 and 2 in this
1572 case), if you leave the digit out, the system assumes '1'. Digits
1573 '0'-'9' are available. This make it easier to see just what filters
1574 you have set. It also makes it more simple to remove individual
1575 filters, during a contest for example.
1578 You will notice in the above example that the second line has
1579 brackets. Look at the line logically. You can see there are 2
1580 separate sections to it. We are saying reject spots that are VHF or
1581 above _
\bA_
\bP_
\bA_
\bR_
\bT from those in zones 14, 15 and 16 (either spotted there or
1582 originated there). If you did not have the brackets to separate the 2
1583 sections, then Spider would read it logically from the front and see a
1584 different expression entirely ...
1585 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
1590 The simple way to remember this is, if you use OR - use brackets.
1591 Whilst we are here CASE is not important. 'And BY_Zone' is just the
1592 same as 'and by_zone'.
1594 As mentioned earlier, setting several filters can be more flexible
1595 than simply setting one complex one. Doing it in this way means that
1596 if you want to alter your filter you can just redefine or remove one
1597 or more lines of it or one line. For example ...
1601 reject/spots 1 on hf/ssb
1606 would redefine our earlier example, or
1615 To remove all the filter lines in the spot filter ...
1625 7
\b7.
\b.3
\b3.
\b. F
\bFi
\bil
\blt
\bte
\ber
\br o
\bop
\bpt
\bti
\bio
\bon
\bns
\bs
1627 You can filter in several different ways. The options are listed in
1628 the various helpfiles for accept, reject and filter.
1631 7
\b7.
\b.4
\b4.
\b. D
\bDe
\bef
\bfa
\bau
\bul
\blt
\bt f
\bfi
\bil
\blt
\bte
\ber
\brs
\bs
1633 Sometimes all that is needed is a general rule for node connects.
1634 This can be done with a node_default filter. This rule will always be
1635 followed, even if the link is isolated, unless another filter is set
1636 specifically. Default rules can be set for nodes and users. They can
1637 be set for spots, announces, WWV and WCY. They can also be used for
1638 hops. An example might look like this ...
1642 accept/spot node_default by_zone 14,15,16,20,33
1643 set/hops node_default spot 50
1648 This filter is for spots only, you could set others for announce, WWV
1649 and WCY. This filter would work for ALL nodes unless a specific
1650 filter is written to override it for a particular node. You can also
1651 set a user_default should you require. It is important to note that
1652 default filters should be considered to be "connected". By this I
1653 mean that should you override the default filter for spots, you need
1654 to add a rule for the hops for spots also.
1657 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
1659 Once you are happy with the results you get, you may like to
1663 The previous example that filters hf/cw spots and accepts vhf/uhf
1664 spots from EU can be written with a mixed filter, for example ...
1670 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
1675 Note that the first filter has not been specified with a number. This
1676 will automatically be assumed to be number 1. In this case, we have
1677 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
1678 _
\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
1679 _
\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
1680 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
1684 It was mentioned earlier that after a reject test that doesn't match,
1685 the default for following tests is 'accept', the reverse is true for
1686 'accept'. In the example what happens is that the reject is executed
1687 first, any non hf/cw spot is passed to the accept line, which lets
1688 through everything else on HF. The next filter line lets through just
1689 VHF/UHF spots from EU.
1693 8
\b8.
\b. O
\bOt
\bth
\bhe
\ber
\br f
\bfi
\bil
\blt
\bte
\ber
\brs
\bs
1695 8
\b8.
\b.1
\b1.
\b. F
\bFi
\bil
\blt
\bte
\ber
\bri
\bin
\bng
\bg M
\bMa
\bai
\bil
\bl
1697 In the /spider/msg directory you will find a file called
1698 badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
1699 original looks something like this ....
1717 # the list of regexes for messages that we won't store having
1718 # received them (bear in mind that we must receive them fully before
1722 # The format of each line is as follows
1724 # type source pattern
1725 # P/B/F T/F/O/S regex
1727 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1728 # source: T - to field, F - from field, O - origin, S - subject
1729 # pattern: a perl regex on the field requested
1731 # Currently only type B and P msgs are affected by this code.
1733 # The list is read from the top down, the first pattern that matches
1734 # causes the action to be taken.
1736 # The pattern can be undef or 0 in which case it will always be selected
1737 # for the action specified
1750 I think this is fairly self explanatory. It is simply a list of
1751 subject headers that we do not want to pass on to either the users of
1752 the cluster or the other cluster nodes that we are linked to. This is
1753 usually because of rules and regulations pertaining to items for sale
1754 etc in a particular country.
1757 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)
1759 _
\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
1762 In the same way as mail, there are some types of spot we do not wish
1763 to pass on to users or linked cluster nodes. In the /spider/data
1764 directory you will find a file called baddx.pl.issue. Rename this to
1765 baddx.pl and edit the file. The original looks like this ....
1783 # the list of dx spot addresses that we don't store and don't pass on
1806 Again, this is simply a list of names we do not want to see in the
1807 spotted field of a DX callout.
1811 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
1813 Create a file in /spider/data called _
\bb_
\ba_
\bd_
\bw_
\bo_
\br_
\bd_
\bs. The format is quite
1814 simple. Lines beginning with # are ignored so comments can be added.
1815 An example file is below ...
1819 # Below is a list of words we do not wish to see on the cluster
1820 grunge grunged grunging
1821 splodge splodger splodging
1828 Multiple words can be used on the same line as shown. Obviously these
1829 are just examples :-)
1832 You can reload the file from the cluster prompt as sysop with
1836 9
\b9.
\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
1838 9
\b9.
\b.1
\b1.
\b. M
\bMO
\bOT
\bTD
\bD
1840 One of the more important things a cluster sysop needs to do is to get
1841 information to his users. The simplest way to do this is to have a
1842 banner that is sent to the user on login. This is know as a "message
1843 of the day" or "motd". To set this up, simply create a file in
1844 /spider/data called motd and edit it to say whatever you want. It is
1845 purely a text file and will be sent automatically to anyone logging in
1849 9
\b9.
\b.2
\b2.
\b. D
\bDo
\bow
\bwn
\bnt
\bti
\bim
\bme
\be m
\bme
\bes
\bss
\bsa
\bag
\bge
\be
1851 If for any reason the cluster is down, maybe for upgrade or
1852 maintenance but the machine is still running, a message can be sent to
1853 the user advising them of the fact. This message lives in the
1854 /spider/data directory and is called "offline". Simply create the
1855 file and edit it to say whatever you wish. This file will be sent to
1856 a user attempting to log into the cluster when DXSpider is not
1860 9
\b9.
\b.3
\b3.
\b. O
\bOt
\bth
\bhe
\ber
\br t
\bte
\bex
\bxt
\bt m
\bme
\bes
\bss
\bsa
\bag
\bge
\bes
\bs
1862 You can set other text messages to be read by the user if they input
1863 the file name. This could be for news items or maybe information for
1864 new users. To set this up, make a directory under /spider called
1865 _
\bp_
\ba_
\bc_
\bk_
\bc_
\bl_
\bu_
\bs. Under this directory you can create files called _
\bn_
\be_
\bw_
\bs or
1866 _
\bn_
\be_
\bw_
\bu_
\bs_
\be_
\br for example. In fact you can create files with any names you
1867 like. These can be listed by the user with the command ....
1876 They can be read by the user by typing the command ....
1885 If the file they want to read is called _
\bn_
\be_
\bw_
\bs. You could also set an
1886 alias for this in the Alias file to allow them just to type _
\bn_
\be_
\bw_
\bs
1889 You can also store other information in this directory, either
1890 directly or nested under directories. One use for this would be to
1891 store DX bulletins such as the OPDX bulletins. These can be listed
1892 and read by the user. To keep things tidy, make a directory under
1893 /spider/packclus called _
\bb_
\bu_
\bl_
\bl_
\be_
\bt_
\bi_
\bn_
\bs. Now copy any OPDX or similar
1894 bulletins into it. These can be listed by the user in the same way as
1895 above using the _
\bs_
\bh_
\bo_
\bw_
\b/_
\bf_
\bi_
\bl_
\be_
\bs command with an extension for the bulletins
1896 directory you have just created, like this ....
1900 show/files bulletins
1906 An example would look like this ....
1911 bulletins DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
1915 You can see that in the files area (basically the packclus directory)
1916 there is a file called _
\bn_
\be_
\bw_
\bs and a directory called _
\bb_
\bu_
\bl_
\bl_
\be_
\bt_
\bi_
\bn_
\bs. You can
1917 also see that dates they were created. In the case of the file _
\bn_
\be_
\bw_
\bs,
1918 you can also see the time it was last modified, a good clue as to
1919 whether the file has been updated since you last read it. To read the
1920 file called _
\bn_
\be_
\bw_
\bs you would simply issue the command ....
1929 To look what is in the bulletins directory you issue the command ....
1933 show/files bulletins
1934 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
1935 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
1936 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
1937 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
1938 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
1939 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
1940 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
1941 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
1942 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
1943 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
1944 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
1945 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
1946 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
1947 Press Enter to continue, A to abort (16 lines) >
1952 You can now read any file in this directory using the type command,
1957 type bulletins/opdx391
1958 Ohio/Penn DX Bulletin No. 391
1959 The Ohio/Penn Dx PacketCluster
1963 Editor Tedd Mirgliotta, KB8NW
1964 Provided by BARF-80 BBS Cleveland, Ohio
1965 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
1966 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
1967 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
1968 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
1969 Press Enter to continue, A to abort (508 lines) >
1974 The page length will of course depend on what you have it set to!
1977 9
\b9.
\b.4
\b4.
\b. T
\bTh
\bhe
\be A
\bAl
\bli
\bia
\bas
\bse
\bes
\bs f
\bfi
\bil
\ble
\be
1979 You will find a file in /spider/cmd/ called Aliases. First, copy this
1980 file to /spider/local_cmd/Aliases and edit this file. You will see
1981 something like this ...
2049 # provide some standard aliases for commands for terminally
2050 # helpless ak1a user (helpless in the sense that they never
2051 # read nor understand help files)
2053 # This file is automagically reloaded if its modification time is
2054 # later than the one stored in CmdAlias.pm
2056 # PLEASE make this file consistant with reality! (the patterns MUST
2057 # match the filenames!)
2059 # Don't alter this file, copy it into the local_cmd tree and modify it.
2060 # This file will be replaced everytime I issue a new release.
2062 # You only need to put aliases in here for commands that don't work as
2063 # you desire naturally, e.g sh/dx on its own just works as you expect
2064 # so you need not add it as an alias.
2072 '^\?', 'apropos', 'apropos',
2075 '^ann.*/full', 'announce full', 'announce',
2076 '^ann.*/sysop', 'announce sysop', 'announce',
2077 '^ann.*/(.*)$', 'announce $1', 'announce',
2084 '^del', 'kill', 'kill',
2085 '^del\w*/fu', 'kill full', 'kill',
2086 '^di\w*/a\w*', 'directory all', 'directory',
2087 '^di\w*/b\w*', 'directory bulletins', 'directory',
2088 '^di\w*/n\w*', 'directory new', 'directory',
2089 '^di\w*/o\w*', 'directory own', 'directory',
2090 '^di\w*/s\w*', 'directory subject', 'directory',
2091 '^di\w*/t\w*', 'directory to', 'directory',
2092 '^di\w*/f\w*', 'directory from', 'directory',
2093 '^di\w*/(\d+)', 'directory $1', 'directory',
2110 '^l$', 'directory', 'directory',
2111 '^ll$', 'directory', 'directory',
2112 '^ll/(\d+)', 'directory $1', 'directory',
2117 '^news', 'type news', 'type',
2127 '^r$', 'read', 'read',
2128 '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
2131 '^s/p$', 'send', 'send',
2132 '^sb$', 'send noprivate', 'send',
2133 '^set/home$', 'set/homenode', 'set/homenode',
2134 '^set/nobe', 'unset/beep', 'unset/beep',
2135 '^set/nohe', 'unset/here', 'unset/here',
2136 '^set/noan', 'unset/announce', 'unset/announce',
2137 '^set/nodx', 'unset/dx', 'unset/dx',
2138 '^set/nota', 'unset/talk', 'unset/talk',
2139 '^set/noww', 'unset/wwv', 'unset/wwv',
2140 '^set/nowx', 'unset/wx', 'unset/wx',
2141 '^sh$', 'show', 'show',
2142 '^sh\w*/buck', 'dbshow buck', 'dbshow',
2143 '^sh\w*/bu', 'show/files bulletins', 'show/files',
2144 '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
2145 '^sh\w*/c$', 'show/configuration', 'show/configuration',
2146 '^sh\w*/com', 'dbavail', 'dbavail',
2147 '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
2148 '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
2149 '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
2150 '^sh\w*/email', 'dbshow email', 'dbshow',
2151 '^sh\w*/hftest', 'dbshow hftest', 'dbshow',
2152 '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
2153 '^sh\w*/qsl', 'dbshow qsl', 'dbshow',
2154 '^sh\w*/tnc', 'who', 'who',
2155 '^sh\w*/up', 'show/cluster', 'show/cluster',
2156 '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
2157 '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
2158 '^sp$', 'send', 'send',
2162 '^ta$', 'talk', 'talk',
2163 '^t$', 'talk', 'talk',
2170 '^wx/full', 'wx full', 'wx',
2171 '^wx/sysop', 'wx sysop', 'wx',
2184 You can create aliases for commands at will. Beware though, these may
2185 not always turn out as you think. Care is needed and you need to test
2186 the results once you have set an alias.
2189 9
\b9.
\b.5
\b5.
\b. F
\bFo
\bor
\brw
\bwa
\bar
\brd
\bd.
\b.p
\bpl
\bl
2191 DXSpider receives all and any mail sent to it without any alterations
2192 needed in files. Because personal and bulletin mail are treated
2193 differently, there is no need for a list of accepted bulletin
2194 addresses. It is necessary, however, to tell the program which links
2195 accept which bulletins. For example, it is pointless sending
2196 bulletins addresses to "UK" to any links other than UK ones. The file
2197 that does this is called forward.pl and lives in /spider/msg. At
2198 default, like other spider files it is named forward.pl.issue. Rename
2199 it to forward.pl and edit the file to match your requirements. The
2205 # this is an example message forwarding file for the system
2207 # The format of each line is as follows
2209 # type to/from/at pattern action destinations
2210 # P/B/F T/F/A regex I/F [ call [, call ...] ]
2212 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
2213 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
2214 # pattern: a perl regex on the field requested
2215 # action: I - ignore, F - forward
2216 # destinations: a reference to an array containing node callsigns
2218 # if it is non-private and isn't in here then it won't get forwarded
2220 # Currently only type B msgs are affected by this code.
2222 # The list is read from the top down, the first pattern that matches
2223 # causes the action to be taken.
2225 # The pattern can be undef or 0 in which case it will always be selected
2226 # for the action specified
2228 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
2229 # pattern) then it will always be forwarded to every node that doesn't have
2230 # it (I strongly recommend you don't use this unless you REALLY mean it, if
2231 # you allow a new link with this on EVERY bull will be forwarded immediately
2232 # on first connection)
2243 Simply insert a bulletin address and state in the brackets where you
2244 wish that mail to go. For example, you can see here that mail sent to
2245 "UK" will only be sent to the UK links and not to PA4AB-14.
2248 To force the cluster to reread the file use load/forward
2251 9
\b9.
\b.6
\b6.
\b. D
\bDi
\bis
\bst
\btr
\bri
\bib
\bbu
\but
\bti
\bio
\bon
\bn l
\bli
\bis
\bst
\bts
\bs
2253 Distribution lists are simply a list of users to send certain types of
2254 mail to. An example of this is mail you only wish to send to other
2255 sysops. In /spider/msg there is a directory called _
\bd_
\bi_
\bs_
\bt_
\br_
\bo. You put
2256 any distibution lists in here. For example, here is a file called
2257 SYSOP.pl that caters for the UK sysops.
2261 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
2262 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
2263 GB7DXK GB7DXI GB7DXS)
2268 Any mail sent to "sysop" would only be sent to the callsigns in this
2272 9
\b9.
\b.7
\b7.
\b. C
\bCo
\bon
\bns
\bso
\bol
\ble
\be.
\b.p
\bpl
\bl
2274 In later versions of Spider a simple console program is provided for
2275 the sysop. This has a type ahead buffer with line editing facilities
2276 and colour for spots, announces etc. To use this program, simply use
2277 console.pl instead of client.pl.
2280 To edit the colours, copy /spider/perl/Console.pl to /spider/local and
2281 edit the file with your favourite editor.
2284 9
\b9.
\b.8
\b8.
\b. B
\bBB
\bBS
\bS i
\bin
\bnt
\bte
\ber
\brf
\bfa
\bac
\bce
\be
2286 Spider provides a simple BBS interface. No input is required from the
2287 sysop of the cluster at all. The BBS simply sets the cluster as a BBS
2288 and pushes any required mail to the cluster. No mail can flow from
2289 Spider to the BBS, the interface is one-way.
2292 Please be careful not to flood the cluster network with unnecessary
2293 mail. Make sure you only send mail to the clusters that want it by
2294 using the Forward.pl file very carefully.
2297 9
\b9.
\b.9
\b9.
\b. U
\bUp
\bpd
\bda
\bat
\bti
\bin
\bng
\bg k
\bke
\bep
\bpl
\ble
\ber
\br d
\bda
\bat
\bta
\ba
2299 Spider has a powerful and flexible show/satellite command. In order
2300 for this to be accurate, the kepler data has to be updated regularly.
2301 In general, this data is available as an email or via cluster mail.
2302 Updating it is simple. First you need to export the mail message as a
2303 file. You do this with the _
\be_
\bx_
\bp_
\bo_
\br_
\bt command from the cluster prompt as
2304 the sysop. For example ...
2308 export 5467 /spider/perl/keps.in
2311 would export message number 5467 as a file called keps.in in the
2312 /spider/perl directory.
2314 Now login to a VT as sysop and cd /spider/perl. There is a command in
2315 the perl directory called _
\bc_
\bo_
\bn_
\bv_
\bk_
\be_
\bp_
\bs_
\b._
\bp_
\bl. All we need to do now is
2316 convert the file like so ...
2320 ./convkeps.pl keps.in
2325 Now go back to the cluster and issue the command ...
2334 That is it! the kepler data has been updated.
2338 1
\b10
\b0.
\b. C
\bCV
\bVS
\bS
2340 CVS stands for "Concurrent Versions System" and the CVS for DXSpider
2341 is held at Sourceforge. This means that it is possible to update your
2342 DXSpider installation to the latest sources by using a few simple
2346 THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST
2347 INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!! THIS
2348 MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!! YOU
2352 DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE
2356 I am of course assuming that you have a machine with both DXSpider and
2357 Internet access running.
2360 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
2361 ENTIRE SPIDER TREE!!
2364 Assuming you are connected to the Internet, you need to login to the
2365 CVS repository and then update your Spider source. There are several
2366 steps which are listed below ...
2369 First login as the user _
\bs_
\by_
\bs_
\bo_
\bp. Next you need to connect to the CVS
2370 repository. You do this with the command below ...
2373 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2377 You will get a password prompt. Simply hit return here and your
2378 machine should return to a normal linux prompt.
2381 What happens next depends on whether you have an existing installation
2382 that you want to update with the latest and greatest or whether you
2383 just want to see what is there and/or run it on a new machine for
2384 testing. Either way you will want to change directory to a new place,
2385 if you want to update an existing installation then I suggest /tmp,
2386 otherwise choose a suitable place according to the normal installation
2390 The next step will create a brand new 'spider' directory in your
2394 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
2398 This command is all on one line.
2401 Hopefully your screen should show you downloading files. The -z3
2402 simply compresses the download to improve speed. When this has
2403 finished, you will have exactly the same as if you had untarred a full
2404 tarball PLUS some extra directories and files that CVS needs to do the
2408 Now if you are doing a new installation, that's it. Carry on as if
2409 you have just downloaded and untarred the lastest tarball.
2412 If you want to upgrade your current installation then do this ...
2416 tar cvfz /tmp/s.tgz spider
2418 tar xvfzp /tmp/s.tgz
2423 This is assuming you downloaded to the /tmp directory of course.
2426 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
2427 permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
2430 Remember to recompile the C client (cd /spider/src; make)
2433 At this point the files have been upgraded. You can (usually) restrt
2434 the cluster in your own time. However, if you attempt to use any new
2435 commands or features expect it to be fatal! At least your cluster
2436 will have been restarted then so it will be too late to worry about
2440 Now the magic part! From now on when you want to update, simply
2441 connect to the Internet and then, as the user _
\bs_
\by_
\bs_
\bo_
\bp ...
2449 and your files will be updated. As above, remember to recompile the
2450 "C" client if it has been updated (CVS will tell you) and restart if
2451 any of the perl scripts have been altered or added, again, CVS will
2455 You will find any changes documented in the /spider/Changes file.
2458 1
\b11
\b1.
\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
2460 Below is a complete list of commands available from the cluster
2461 prompt. Most maintenance tasks are automatic but there are some
2462 commands that are useful for a sysop. These are listed below in
2463 alphabetical order. The number in brackets following the command name
2464 is the permissions level needed to use the command.
2467 1
\b11
\b1.
\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)
2469 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
2472 Create an 'accept this announce' line for a filter.
2474 An accept filter line means that if the announce matches this filter
2475 it is passed onto the user. See HELP FILTERS for more info. Please
2476 read this to understand how filters work - it will save a lot of grief
2479 You can use any of the following things in this line:-
2483 info <string> eg: iota or qsl
2484 by <prefixes> eg: G,M,2
2486 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2487 origin_itu <numbers>
2488 origin_zone <numbers>
2493 wx 1 filter WX announces
2494 dest <prefixes> eg: 6MUK,WDX (distros)
2504 acc/ann 2 by_zone 14,15,16
2505 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
2518 This filter would only allow announces that were posted buy UK
2519 stations. You can use the tag 'all' to accept everything eg:
2528 but this probably for advanced users...
2531 1
\b11
\b1.
\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)
2533 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
2537 This version allows a sysop to set a filter for a callsign as well as
2538 the default for nodes and users eg:-
2543 accept/ann input node_default by G,M,2
2544 accept/ann user_default by G,M,2
2550 1
\b11
\b1.
\b.3
\b3.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs (
\b(0
\b0)
\b)
2552 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
2555 Create an 'accept this spot' line for a filter.
2558 An accept filter line means that if the spot matches this filter it is
2559 passed onto the user. See HELP FILTERS for more info. Please read this
2560 to understand how filters work - it will save a lot of grief later on.
2562 You can use any of the following things in this line:-
2575 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
2576 on <range> same as 'freq'
2577 call <prefixes> eg: G,PA,HB9
2578 info <string> eg: iota or qsl
2580 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2593 For frequencies, you can use any of the band names defined in
2594 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
2595 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
2596 this is more efficient than saying simply: freq HF (but don't get too
2604 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2609 You can use the tag 'all' to accept everything, eg:
2618 but this probably for advanced users...
2621 1
\b11
\b1.
\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)
2623 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
2626 This version allows a sysop to set a filter for a callsign as well as
2627 the default for nodes and users eg:-
2631 accept/spot db0sue-7 1 by_zone 14,15,16
2632 accept/spot node_default all
2633 set/hops node_default 10
2635 accept/spot user_default by G,M,2
2641 1
\b11
\b1.
\b.5
\b5.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bwc
\bcy
\by (
\b(0
\b0)
\b)
2643 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
2646 It is unlikely that you will want to do this, but if you do then you
2647 can filter on the following fields:-
2651 by <prefixes> eg: G,M,2
2653 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2654 origin_itu <numbers>
2655 origin_zone <numbers>
2665 There are no examples because WCY Broadcasts only come from one place
2666 and you either want them or not (see UNSET/WCY if you don't want
2669 This command is really provided for future use.
2671 See HELP FILTER for information.
2674 1
\b11
\b1.
\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)
2676 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
2679 This version allows a sysop to set a filter for a callsign as well as
2680 the default for nodes and users eg:-
2684 accept/wcy node_default all
2685 set/hops node_default 10
2691 1
\b11
\b1.
\b.7
\b7.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bww
\bwv
\bv (
\b(0
\b0)
\b)
2693 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
2696 It is unlikely that you will want to do this, but if you do then you
2697 can filter on the following fields:-
2707 by <prefixes> eg: G,M,2
2709 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2710 origin_itu <numbers>
2711 origin_zone <numbers>
2724 accept/wwv by_zone 4
2729 is probably the only useful thing to do (which will only show WWV
2730 broadcasts by stations in the US).
2732 See HELP FILTER for information.
2735 1
\b11
\b1.
\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)
2737 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
2740 This version allows a sysop to set a filter for a callsign as well as
2741 the default for nodes and users eg:-
2745 accept/wwv db0sue-7 1 by_zone 4
2746 accept/wwv node_default all
2747 set/hops node_default 10
2749 accept/wwv user_default by W,K
2755 1
\b11
\b1.
\b.9
\b9.
\b. a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be (
\b(0
\b0)
\b)
2757 a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send an announcement to local users
2760 Send an announcement to LOCAL users only, where <text> is the text of
2761 the announcement you wish to broadcast
2764 1
\b11
\b1.
\b.1
\b10
\b0.
\b. a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be f
\bfu
\bul
\bll
\bl (
\b(0
\b0)
\b)
2766 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
2769 This command will send your announcement across the whole cluster
2773 1
\b11
\b1.
\b.1
\b11
\b1.
\b. a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be s
\bsy
\bys
\bso
\bop
\bp (
\b(5
\b5)
\b)
2775 a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be s
\bsy
\bys
\bso
\bop
\bp <
\b<t
\bte
\bex
\bxt
\bt>
\b>
2778 Send an announcement to Sysops only
2781 1
\b11
\b1.
\b.1
\b12
\b2.
\b. a
\bap
\bpr
\bro
\bop
\bpo
\bos
\bs (
\b(0
\b0)
\b)
2783 a
\bap
\bpr
\bro
\bop
\bpo
\bos
\bs <
\b<s
\bst
\btr
\bri
\bin
\bng
\bg>
\b> Search the help database
2786 Search the help database for <string> (it isn't case sensitive), and
2787 print the names of all the commands that may be relevant.
2790 1
\b11
\b1.
\b.1
\b13
\b3.
\b. b
\bby
\bye
\be (
\b(0
\b0)
\b)
2792 b
\bby
\bye
\be Exit from the cluster
2795 This will disconnect you from the cluster
2798 1
\b11
\b1.
\b.1
\b14
\b4.
\b. c
\bca
\bat
\btc
\bch
\bhu
\bup
\bp (
\b(5
\b5)
\b)
2800 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
2803 When you send messages the fact that you have forwarded it to another
2804 node is remembered so that it isn't sent again. When you have a new
2805 partner node and you add their callsign to your /spider/msg/forward.pl
2806 file, all outstanding non-private messages will be forwarded to them.
2807 This may well be ALL the non-private messages. You can prevent this by
2808 using these commmands:-
2813 catchup GB7DJK 300 301 302 303 500-510
2818 and to undo what you have just done:-
2822 uncatchup GB7DJK all
2823 uncatchup GB7DJK 300 301 302 303 500-510
2828 which will arrange for them to be forward candidates again.
2830 Order is not important.
2833 1
\b11
\b1.
\b.1
\b15
\b5.
\b. c
\bcl
\ble
\bea
\bar
\br/
\b/s
\bsp
\bpo
\bot
\bts
\bs (
\b(0
\b0)
\b)
2835 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
2839 This command allows you to clear (remove) a line in a spot filter or
2840 to remove the whole filter.
2842 If you have a filter:-
2847 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2861 you will be left with:-
2865 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2879 the filter will be completely removed.
2883 1
\b11
\b1.
\b.1
\b16
\b6.
\b. c
\bco
\bon
\bnn
\bne
\bec
\bct
\bt (
\b(5
\b5)
\b)
2885 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
2888 Start a connection process that will culminate in a new connection to
2889 the DX cluster <callsign>. This process creates a new 'client' process
2890 which will use the script in /spider/connect/<callsign> to effect the
2891 'chat' exchange necessary to traverse the network(s) to logon to the
2895 1
\b11
\b1.
\b.1
\b17
\b7.
\b. d
\bdb
\bba
\bav
\bva
\bai
\bil
\bl (
\b(0
\b0)
\b)
2897 d
\bdb
\bba
\bav
\bva
\bai
\bil
\bl Show a list of all the databases in the system
2900 The title says it all really, this command lists all the databases
2901 defined in the system. It is also aliased to SHOW/COMMAND.
2905 1
\b11
\b1.
\b.1
\b18
\b8.
\b. d
\bdb
\bbc
\bcr
\bre
\bea
\bat
\bte
\be (
\b(9
\b9)
\b)
2907 d
\bdb
\bbc
\bcr
\bre
\bea
\bat
\bte
\be <
\b<n
\bna
\bam
\bme
\be>
\b> Create a database entry
2908 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
2910 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
2913 DBCREATE allows you to define a database in the system. It doesn't
2914 actually create anything, just defines it.
2916 The databases that are created are simple DB_File hash databases, they
2917 are therefore already 'indexed'.
2919 You can define a local database with the first form of the command eg:
2923 You can also chain databases with the addition of the 'chain' keyword.
2924 This will search each database one after the other. A typical example
2927 DBCREATE sdx_qsl chain sql_ad
2929 No checking is done to see if the any of the chained databases exist,
2930 in fact it is usually better to do the above statement first then do
2931 each of the chained databases.
2933 Databases can exist offsite. To define a database that lives on
2936 DBCREATE buckmaster remote gb7dxc
2938 Remote databases cannot be chained; however, the last database in a a
2939 chain can be a remote database eg:
2941 DBCREATE qsl chain gb7dxc
2943 To see what databases have been defined do:
2945 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
2947 It would be normal for you to add an entry into your local Aliases
2948 file to allow people to use the 'SHOW/<dbname>' style syntax. So you
2949 would need to add a line like:-
2956 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
2968 to work as they may be used to.
2971 See DBIMPORT for the importing of existing AK1A format data to
2972 databases. See DBSHOW for generic database enquiry
2975 1
\b11
\b1.
\b.1
\b19
\b9.
\b. d
\bdb
\bbi
\bim
\bmp
\bpo
\bor
\brt
\bt (
\b(9
\b9)
\b)
2977 d
\bdb
\bbi
\bim
\bmp
\bpo
\bor
\brt
\bt <
\b<d
\bdb
\bbn
\bna
\bam
\bme
\be>
\b> Import AK1A data into a database
2980 If you want to import or update data in bulk to a database you can use
2981 this command. It will either create or update entries into an existing
2982 database. For example:-
2984 DBIMPORT oblast /tmp/OBLAST.FUL
2986 will import the standard OBLAST database that comes with AK1A into the
2987 oblast database held locally.
2990 1
\b11
\b1.
\b.2
\b20
\b0.
\b. d
\bdb
\bbr
\bre
\bem
\bmo
\bov
\bve
\be (
\b(9
\b9)
\b)
2992 d
\bdb
\bbr
\bre
\bem
\bmo
\bov
\bve
\be <
\b<d
\bdb
\bbn
\bna
\bam
\bme
\be>
\b> Delete a database
2995 DBREMOVE will completely remove a database entry and also delete any
2996 data file that is associated with it.
2998 There is no warning, no comeback, no safety net.
3004 will remove the oblast database from the system and it will also
3005 remove the associated datafile.
3009 There is no warning, no comeback, no safety net.
3011 You have been warned.
3014 1
\b11
\b1.
\b.2
\b21
\b1.
\b. d
\bdb
\bbs
\bsh
\bho
\bow
\bw (
\b(0
\b0)
\b)
3016 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
3019 This is the generic user interface to the database to the database
3020 system. It is expected that the sysop will add an entry to the local
3021 Aliases file so that users can use the more familiar AK1A style of
3031 but if he hasn't and the database really does exist (use DBAVAIL or
3032 SHOW/COMMAND to find out) you can do the same thing with:
3044 1
\b11
\b1.
\b.2
\b22
\b2.
\b. d
\bde
\beb
\bbu
\bug
\bg (
\b(9
\b9)
\b)
3046 d
\bde
\beb
\bbu
\bug
\bg Set the cluster program into debug mode
3049 Executing this command will only have an effect if you are running the
3050 cluster in debug mode i.e.
3059 It will interrupt the cluster just after the debug command has
3063 1
\b11
\b1.
\b.2
\b23
\b3.
\b. d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by (
\b(0
\b0)
\b)
3065 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by List messages
3066 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by o
\bow
\bwn
\bn List your own messages
3067 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by n
\bne
\bew
\bw List all new messages
3068 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>
3069 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>
3070 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
3071 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by <
\b<n
\bnn
\bn>
\b> List last <nn> messages
3072 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
3075 List the messages in the messages directory.
3077 If there is a 'p' one space after the message number then it is a
3078 personal message. If there is a '-' between the message number and the
3080 You can use shell escape characters such as '*' and '?' in the <call>
3083 You can combine some of the various directory commands together eg:-
3089 DIR SUBJECT IOTA 200-250
3094 You can abbreviate all the commands to one letter and use ak1a
3103 1
\b11
\b1.
\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)
3105 Works just like the user command except that sysops can see ALL
3109 1
\b11
\b1.
\b.2
\b25
\b5.
\b. d
\bdi
\bis
\bsc
\bco
\bon
\bnn
\bne
\bec
\bct
\bt (
\b(8
\b8)
\b)
3111 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
3114 Disconnect any <call> connected locally
3117 1
\b11
\b1.
\b.2
\b26
\b6.
\b. d
\bdx
\bx (
\b(0
\b0)
\b)
3119 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
3122 This is how you send a DX Spot to other users. You can, in fact, now
3123 enter the <freq> and the <call> either way round.
3134 will all give the same result. You can add some remarks to the end of
3135 the command and they will be added to the spot.
3139 DX FR0G 144600 this is a test
3144 You can credit someone else by saying:-
3148 DX by G1TLH FR0G 144.600 he isn't on the cluster
3153 The <freq> is compared against the available bands set up in the
3154 cluster. See SHOW/BANDS for more information.
3157 1
\b11
\b1.
\b.2
\b27
\b7.
\b. e
\bex
\bxp
\bpo
\bor
\brt
\bt (
\b(9
\b9)
\b)
3159 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
3162 Export a message to a file. This command can only be executed on a
3163 local console with a fully privileged user. The file produced will be
3164 in a form ready to be imported back into the cluster by placing it in
3165 the import directory (/spider/msg/import).
3167 This command cannot overwrite an existing file. This is to provide
3168 some measure of security. Any files written will owned by the same
3169 user as the main cluster, otherwise you can put the new files anywhere
3170 the cluster can access. For example:-
3175 1
\b11
\b1.
\b.2
\b28
\b8.
\b. e
\bex
\bxp
\bpo
\bor
\brt
\bt_
\b_u
\bus
\bse
\ber
\brs
\bs (
\b(9
\b9)
\b)
3177 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
3180 Export the users database to a file in ascii format. If no filename is
3181 given then it will export the file to /spider/data/user_asc.
3183 If the file already exists it will be renamed to <filename>.o. In fact
3184 up to 5 generations of the file can be kept each one with an extra 'o'
3187 BE WARNED: this will write to any file you have write access to. No
3188 check is made on the filename (if any) that you specify.
3191 1
\b11
\b1.
\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)
3193 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
3197 This command sends all the latitude and longitude information that
3198 your cluster is holding against callsigns. One advantage of recieving
3199 this information is that more locator information is held by you.
3200 This means that more locators are given on the DX line assuming you
3201 have _
\bs_
\be_
\bt_
\b/_
\bd_
\bx_
\bg_
\br_
\bi_
\bd enabled. This could be a LOT of information though,
3202 so it is not recommended on slow links.
3205 1
\b11
\b1.
\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)
3207 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
3211 This command sends out any information held in the user file which can
3212 be broadcast in PC41 protocol packets. This information is Name, QTH,
3213 Location and Homenode. PC41s are only sent for the information that is
3217 1
\b11
\b1.
\b.3
\b31
\b1.
\b. h
\bhe
\bel
\blp
\bp (
\b(0
\b0)
\b)
3219 h
\bhe
\bel
\blp
\bp <
\b<c
\bcm
\bmd
\bd>
\b> Get help on a command
3222 All commands can be abbreviated, so SHOW/DX can be abbreviated to
3223 SH/DX, ANNOUNCE can be shortened to AN and so on.
3225 Look at the APROPOS <string> command which will search the help
3226 database for the <string> you specify and give you a list of likely
3227 commands to look at with HELP.
3230 1
\b11
\b1.
\b.3
\b32
\b2.
\b. i
\bin
\bni
\bit
\bt (
\b(5
\b5)
\b)
3232 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
3235 This command attempts to re-initialise a link to a (usually) AK1A node
3236 that has got confused, usually by a protocol loop of some kind. It may
3237 work - but you usually will be better off simply disconnecting it (or
3238 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
3241 Best of luck - you will need it.
3244 1
\b11
\b1.
\b.3
\b33
\b3.
\b. k
\bki
\bil
\bll
\bl (
\b(0
\b0)
\b)
3246 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
3249 Delete a message from the local system. You will only be able to
3250 delete messages that you have originated or been sent (unless you are
3254 1
\b11
\b1.
\b.3
\b34
\b4.
\b. k
\bki
\bil
\bll
\bl (
\b(5
\b5)
\b)
3256 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
3257 k
\bki
\bil
\bll
\bl f
\bfr
\bro
\bom
\bm <
\b<c
\bca
\bal
\bll
\bl>
\b> Remove all messages from a callsign
3258 k
\bki
\bil
\bll
\bl t
\bto
\bo <
\b<c
\bca
\bal
\bll
\bl>
\b> Remove all messages to a callsign
3261 You can get rid of any message to or originating from your callsign
3262 using this command. You can remove more than one message at a time.
3264 As a sysop you can kill any message on the system.
3267 1
\b11
\b1.
\b.3
\b35
\b5.
\b. k
\bki
\bil
\bll
\bl f
\bfu
\bul
\bll
\bl (
\b(5
\b5)
\b)
3269 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
3272 Delete a message (usually a 'bulletin') from the whole cluster system.
3274 This uses the subject field, so any messages that have exactly the
3275 same subject will be deleted. Beware!
3278 1
\b11
\b1.
\b.3
\b36
\b6.
\b. l
\bli
\bin
\bnk
\bks
\bs (
\b(0
\b0)
\b)
3280 l
\bli
\bin
\bnk
\bks
\bs Show which nodes are physically connected
3283 This is a quick listing that shows which links are connected and some
3284 information about them. See WHO for a list of all connections.
3288 1
\b11
\b1.
\b.3
\b37
\b7.
\b. l
\blo
\boa
\bad
\bd/
\b/a
\bal
\bli
\bia
\bas
\bse
\bes
\bs (
\b(9
\b9)
\b)
3290 l
\blo
\boa
\bad
\bd/
\b/a
\bal
\bli
\bia
\bas
\bse
\bes
\bs Reload the command alias table
3293 Reload the /spider/cmd/Aliases file after you have editted it. You
3294 will need to do this if you change this file whilst the cluster is
3295 running in order for the changes to take effect.
3301 1
\b11
\b1.
\b.3
\b38
\b8.
\b. l
\blo
\boa
\bad
\bd/
\b/b
\bba
\bad
\bdd
\bdx
\bx (
\b(9
\b9)
\b)
3303 l
\blo
\boa
\bad
\bd/
\b/b
\bba
\bad
\bdd
\bdx
\bx Reload the bad DX table
3306 Reload the /spider/data/baddx.pl file if you have changed it manually
3307 whilst the cluster is running. This table contains the DX Calls that,
3308 if spotted, will not be passed on. FR0G and TEST are classic examples.
3311 1
\b11
\b1.
\b.3
\b39
\b9.
\b. l
\blo
\boa
\bad
\bd/
\b/b
\bba
\bad
\bdm
\bms
\bsg
\bg (
\b(9
\b9)
\b)
3313 l
\blo
\boa
\bad
\bd/
\b/b
\bba
\bad
\bdm
\bms
\bsg
\bg Reload the bad message table
3316 Reload the /spider/msg/badmsg.pl file if you have changed it manually
3317 whilst the cluster is running. This table contains a number of perl
3318 regular expressions which are searched for in the fields targetted of
3319 each message. If any of them match then that message is immediately
3323 1
\b11
\b1.
\b.4
\b40
\b0.
\b. l
\blo
\boa
\bad
\bd/
\b/b
\bba
\bad
\bdw
\bwo
\bor
\brd
\bds
\bs (
\b(9
\b9)
\b)
3325 l
\blo
\boa
\bad
\bd/
\b/b
\bba
\bad
\bdw
\bwo
\bor
\brd
\bds
\bs Reload the badwords file
3328 Reload the /spider/data/badwords file if you have changed it manually
3329 whilst the cluster is running. This file contains a list of words
3330 which, if found on certain text portions of PC protocol, will cause
3331 those protocol frames to be rejected. It will all put out a message if
3332 any of these words are used on the announce, dx and talk commands. The
3333 words can be one or more on a line, lines starting with '#' are
3337 1
\b11
\b1.
\b.4
\b41
\b1.
\b. l
\blo
\boa
\bad
\bd/
\b/b
\bba
\ban
\bnd
\bds
\bs (
\b(9
\b9)
\b)
3339 l
\blo
\boa
\bad
\bd/
\b/b
\bba
\ban
\bnd
\bds
\bs Reload the band limits table
3342 Reload the /spider/data/bands.pl file if you have changed it manually
3343 whilst the cluster is running.
3346 1
\b11
\b1.
\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)
3348 l
\blo
\boa
\bad
\bd/
\b/c
\bcm
\bmd
\bd_
\b_c
\bca
\bac
\bch
\bhe
\be Reload the automatic command cache
3351 Normally, if you change a command file in the cmd or local_cmd tree it
3352 will automatially be picked up by the cluster program. Sometimes it
3353 can get confused if you are doing a lot of moving commands about or
3354 delete a command in the local_cmd tree and want to use the normal one
3355 again. Execute this command to reset everything back to the state it
3356 was just after a cluster restart.
3359 1
\b11
\b1.
\b.4
\b43
\b3.
\b. l
\blo
\boa
\bad
\bd/
\b/f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd (
\b(9
\b9)
\b)
3361 l
\blo
\boa
\bad
\bd/
\b/f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd Reload the msg forwarding routing table
3363 Reload the /spider/msg/forward.pl file if you have changed it manually
3364 whilst the cluster is running.
3367 1
\b11
\b1.
\b.4
\b44
\b4.
\b. l
\blo
\boa
\bad
\bd/
\b/m
\bme
\bes
\bss
\bsa
\bag
\bge
\bes
\bs (
\b(9
\b9)
\b)
3369 l
\blo
\boa
\bad
\bd/
\b/m
\bme
\bes
\bss
\bsa
\bag
\bge
\bes
\bs Reload the system messages file
3372 If you change the /spider/perl/Messages file (usually whilst
3373 fiddling/writing ne commands) you can have them take effect during a
3374 cluster session by executing this command. You need to do this if get
3377 unknown message 'xxxx' in lang 'en'
3380 1
\b11
\b1.
\b.4
\b45
\b5.
\b. l
\blo
\boa
\bad
\bd/
\b/p
\bpr
\bre
\bef
\bfi
\bix
\bxe
\bes
\bs (
\b(9
\b9)
\b)
3382 l
\blo
\boa
\bad
\bd/
\b/p
\bpr
\bre
\bef
\bfi
\bix
\bxe
\bes
\bs Reload the prefix table
3385 Reload the /spider/data/prefix_data.pl file if you have changed it
3386 manually whilst the cluster is running.
3389 1
\b11
\b1.
\b.4
\b46
\b6.
\b. m
\bme
\ber
\brg
\bge
\be (
\b(5
\b5)
\b)
3391 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
3394 MERGE allows you to bring your spot and wwv database up to date. By
3395 default it will request the last 10 spots and 5 WWVs from the node you
3396 select. The node must be connected locally.
3398 You can request any number of spots or wwv and although they will be
3399 appended to your databases they will not duplicate any that have
3400 recently been added (the last 2 days for spots and last month for WWV
3404 1
\b11
\b1.
\b.4
\b47
\b7.
\b. m
\bms
\bsg
\bg (
\b(9
\b9)
\b)
3406 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
3409 Alter message parameters like To, From, Subject, whether private or
3410 bulletin or return receipt (RR) is required or whether to keep this
3411 message from timing out.
3415 MSG TO <msgno> <call> - change TO callsign to <call>
3416 MSG FRom <msgno> <call> - change FROM callsign to <call>
3417 MSG PRrivate <msgno> - set private flag
3418 MSG NOPRrivate <msgno> - unset private flag
3419 MSG RR <msgno> - set RR flag
3420 MSG NORR <msgno> - unset RR flag
3421 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
3422 MSG NOKEep <msgno> - unset the keep flag
3423 MSG SUbject <msgno> <new> - change the subject to <new>
3424 MSG WAittime <msgno> - remove any waitting time for this message
3425 MSG NOREad <msgno> - mark message as unread
3426 MSG REad <msgno> - mark message as read
3427 MSG QUeue - queue any outstanding bulletins
3428 MSG QUeue 1 - queue any outstanding private messages
3433 You can look at the status of a message by using:-
3437 This will display more information on the message than DIR does.
3440 1
\b11
\b1.
\b.4
\b48
\b8.
\b. p
\bpc
\bc (
\b(8
\b8)
\b)
3442 p
\bpc
\bc <
\b<c
\bca
\bal
\bll
\bl>
\b> <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send text (eg PC Protocol) to <call>
3445 Send some arbitrary text to a locally connected callsign. No
3446 processing is done on the text. This command allows you to send PC
3447 Protocol to unstick things if problems arise (messages get stuck etc).
3450 pc gb7djk PC33^GB7TLH^GB7DJK^400^
3452 You can also use in the same way as a talk command to a connected user
3453 but without any processing, added of "from <blah> to <blah>" or
3456 pc G1TLH Try doing that properly!!!
3459 1
\b11
\b1.
\b.4
\b49
\b9.
\b. p
\bpi
\bin
\bng
\bg (
\b(1
\b1)
\b)
3461 p
\bpi
\bin
\bng
\bg <
\b<n
\bno
\bod
\bde
\be>
\b> Check the link quality between nodes
3464 his command allows you to send a frame to another cluster node on the
3465 network and get a return frame. The time it takes to do this is a
3466 good indication of the quality of the link. The actual time it takes
3467 is output to the console in seconds. Any visible cluster node can be
3472 1
\b11
\b1.
\b.5
\b50
\b0.
\b. r
\brc
\bcm
\bmd
\bd (
\b(1
\b1)
\b)
3474 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
3477 This command allows you to send nearly any command to another DX
3478 Cluster node that is connected to the system.
3480 Whether you get any output is dependant on a) whether the other system
3481 knows that the node callsign of this cluster is in fact a node b)
3482 whether the other system is allowing RCMDs from this node and c)
3483 whether you have permission to send this command at all.
3486 1
\b11
\b1.
\b.5
\b51
\b1.
\b. r
\bre
\bea
\bad
\bd (
\b(0
\b0)
\b)
3488 r
\bre
\bea
\bad
\bd Read the next unread personal message addressed to you
3489 r
\bre
\bea
\bad
\bd <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Read the specified message
3492 You can read any messages that are sent as 'non-personal' and also any
3493 message either sent by or sent to your callsign.
3499 1
\b11
\b1.
\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)
3501 r
\bre
\bea
\bad
\bd <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Read a message on the system
3504 As a sysop you may read any message on the system
3507 1
\b11
\b1.
\b.5
\b53
\b3.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be
3509 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
3512 Create an 'reject this announce' line for a filter.
3514 An reject filter line means that if the announce matches this filter
3515 it is passed onto the user. See HELP FILTERS for more info. Please
3516 read this to understand how filters work - it will save a lot of grief
3519 You can use any of the following things in this line:-
3523 info <string> eg: iota or qsl
3524 by <prefixes> eg: G,M,2
3526 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3527 origin_itu <numbers>
3528 origin_zone <numbers>
3533 wx 1 filter WX announces
3534 dest <prefixes> eg: 6MUK,WDX (distros)
3543 rej/ann by_zone 14,15,16 and not by G,M,2
3548 You can use the tag 'all' to reject everything eg:
3557 but this probably for advanced users...
3560 1
\b11
\b1.
\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)
3562 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
3565 This version allows a sysop to set a filter for a callsign as well as
3566 the default for nodes and users eg:-
3571 reject/ann input node_default by G,M,2
3572 reject/ann user_default by G,M,2
3578 1
\b11
\b1.
\b.5
\b55
\b5.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs (
\b(0
\b0)
\b)
3580 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
3583 Create a 'reject this spot' line for a filter.
3585 A reject filter line means that if the spot matches this filter it is
3586 dumped (not passed on). See HELP FILTERS for more info. Please read
3587 this to understand how filters work - it will save a lot of grief
3590 You can use any of the following things in this line:-
3594 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
3595 on <range> same as 'freq'
3596 call <prefixes> eg: G,PA,HB9
3597 info <string> eg: iota or qsl
3599 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3611 For frequencies, you can use any of the band names defined in
3612 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
3613 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
3614 this is more efficient than saying simply: on HF (but don't get too
3622 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3627 You can use the tag 'all' to reject everything eg:
3636 but this probably for advanced users...
3639 1
\b11
\b1.
\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)
3641 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
3645 This version allows a sysop to set a filter for a callsign as well as
3646 the default for nodes and users eg:-
3650 reject/spot db0sue-7 1 by_zone 14,15,16
3651 reject/spot node_default all
3652 set/hops node_default 10
3654 reject/spot user_default by G,M,2
3660 1
\b11
\b1.
\b.5
\b57
\b7.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bwc
\bcy
\by (
\b(0
\b0)
\b)
3662 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
3665 It is unlikely that you will want to do this, but if you do then you
3666 can filter on the following fields:-
3670 by <prefixes> eg: G,M,2
3672 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3673 origin_itu <numbers>
3674 origin_zone <numbers>
3683 There are no examples because WCY Broadcasts only come from one place
3684 and you either want them or not (see UNSET/WCY if you don't want
3687 This command is really provided for future use.
3689 See HELP FILTER for information.
3692 1
\b11
\b1.
\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)
3694 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
3697 This version allows a sysop to set a filter for a callsign as well as
3698 the default for nodes and users eg:-
3700 reject/wcy gb7djk all
3703 1
\b11
\b1.
\b.5
\b59
\b9.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bww
\bwv
\bv (
\b(0
\b0)
\b)
3705 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
3708 It is unlikely that you will want to do this, but if you do then you
3709 can filter on the following fields:-
3713 by <prefixes> eg: G,M,2
3715 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3716 origin_itu <numbers>
3717 origin_zone <numbers>
3730 reject/wwv by_zone 14,15,16
3735 is probably the only useful thing to do (which will only show WWV
3736 broadcasts by stations in the US).
3738 See HELP FILTER for information.
3741 1
\b11
\b1.
\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)
3743 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
3747 This version allows a sysop to set a filter for a callsign as well as
3748 the default for nodes and users eg:-
3752 reject/wwv db0sue-7 1 by_zone 4
3753 reject/wwv node_default all
3755 reject/wwv user_default by W
3763 1
\b11
\b1.
\b.6
\b61
\b1.
\b. r
\bre
\bep
\bpl
\bly
\by (
\b(0
\b0)
\b)
3765 r
\bre
\bep
\bpl
\bly
\by Reply (privately) to the last message that you have read
3766 r
\bre
\bep
\bpl
\bly
\by <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Reply (privately) to the specified message
3767 r
\bre
\bep
\bpl
\bly
\by B
\bB <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Reply as a Bulletin to the specified message
3768 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
3769 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
3772 You can reply to a message and the subject will automatically have
3773 "Re:" inserted in front of it, if it isn't already present.
3775 You can also use all the extra qualifiers such as RR, PRIVATE,
3776 NOPRIVATE, B that you can use with the SEND command (see SEND for
3780 1
\b11
\b1.
\b.6
\b62
\b2.
\b. s
\bse
\ben
\bnd
\bd (
\b(0
\b0)
\b)
3782 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
3783 s
\bse
\ben
\bnd
\bd R
\bRR
\bR <
\b<c
\bca
\bal
\bll
\bl>
\b> Send a message and ask for a read receipt
3784 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
3785 s
\bse
\ben
\bnd
\bd P
\bPR
\bRI
\bIV
\bVA
\bAT
\bTE
\bE <
\b<c
\bca
\bal
\bll
\bl>
\b> Send a personal message
3786 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
3789 All the SEND commands will create a message which will be sent either
3790 to an individual callsign or to one of the 'bulletin' addresses.
3792 SEND <call> on its own acts as though you had typed SEND PRIVATE, that
3793 is it will mark the message as personal and send it to the cluster
3794 node that that callsign is connected to.
3796 You can have more than one callsign in all of the SEND commands.
3798 You can have multiple qualifiers so that you can have for example:-
3802 SEND RR COPY 123 PRIVATE G1TLH G0RDI
3807 which should send a copy of message 123 to G1TLH and G0RDI and you
3808 will receive a read receipt when they have read the message.
3810 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP
3811 is an alias for SEND PRIVATE
3814 1
\b11
\b1.
\b.6
\b63
\b3.
\b. s
\bse
\bet
\bt/
\b/a
\bad
\bdd
\bdr
\bre
\bes
\bss
\bs (
\b(0
\b0)
\b)
3816 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
3819 Literally, record your address details on the cluster.
3822 1
\b11
\b1.
\b.6
\b64
\b4.
\b. s
\bse
\bet
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be (
\b(0
\b0)
\b)
3824 s
\bse
\bet
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be Allow announce messages
3827 Allow announce messages to arrive at your terminal.
3829 1
\b11
\b1.
\b.6
\b65
\b5.
\b. s
\bse
\bet
\bt/
\b/a
\bar
\brc
\bcl
\blu
\bus
\bst
\bte
\ber
\br (
\b(5
\b5)
\b)
3831 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-
3835 Set the node_call as an AR-Cluster type node
3838 1
\b11
\b1.
\b.6
\b66
\b6.
\b. s
\bse
\bet
\bt/
\b/b
\bba
\bad
\bdd
\bdx
\bx (
\b(8
\b8)
\b)
3840 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
3841 field of a dx spot being propagated
3844 Setting a word as 'baddx' will prevent spots with that word in the
3845 callsign field of a DX spot from going any further. They will not be
3846 displayed and they will not be sent onto other nodes.
3848 The word must be wriiten in full, no wild cards are allowed eg:-
3852 set/baddx FORSALE VIDEO FR0G
3857 To allow a word again, use the following command ...
3867 1
\b11
\b1.
\b.6
\b67
\b7.
\b. s
\bse
\bet
\bt/
\b/b
\bba
\bad
\bdn
\bno
\bod
\bde
\be (
\b(6
\b6)
\b)
3869 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
3873 Setting a callsign as a 'badnode' will prevent spots from that node
3874 going any further. They will not be displayed and they will not be
3875 sent onto other nodes.
3877 The call can be a full or partial call (or a prefix), eg:-
3886 will stop anything from K1TTT (including any SSID's)
3895 will allow spots from him again.
3897 Use with extreme care. This command may well be superceded by
3901 1
\b11
\b1.
\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)
3903 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
3906 Setting a callsign as a 'badspotter' will prevent spots from this
3907 callsign going any further. They will not be displayed and they will
3908 not be sent onto other nodes.
3910 The call must be written in full, no wild cards are allowed eg:-
3914 set/badspotter VE2STN
3919 will stop anything from VE2STN. If you want SSIDs as well then you
3920 must enter them specifically.
3924 unset/badspotter VE2STN
3929 will allow spots from him again.
3931 Use with extreme care. This command may well be superceded by
3935 1
\b11
\b1.
\b.6
\b69
\b9.
\b. s
\bse
\bet
\bt/
\b/b
\bbe
\bee
\bep
\bp (
\b(0
\b0)
\b)
3937 s
\bse
\bet
\bt/
\b/b
\bbe
\bee
\bep
\bp Add beeps to terminal messages
3940 Add a beep to DX and other terminal messages.
3943 1
\b11
\b1.
\b.7
\b70
\b0.
\b. s
\bse
\bet
\bt/
\b/c
\bcl
\blx
\bx (
\b(5
\b5)
\b)
3945 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
3949 Set the node_call as a CLX type node
3952 1
\b11
\b1.
\b.7
\b71
\b1.
\b. s
\bse
\bet
\bt/
\b/d
\bde
\beb
\bbu
\bug
\bg (
\b(9
\b9)
\b)
3954 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
3957 You can remove this level with unset/debug <name>
3961 1
\b11
\b1.
\b.7
\b72
\b2.
\b. s
\bse
\bet
\bt/
\b/d
\bdx
\bx (
\b(0
\b0)
\b)
3963 s
\bse
\bet
\bt/
\b/d
\bdx
\bxAllow DX messages to arrive at your terminal
3966 You can stop DX messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bd_
\bx command
3969 1
\b11
\b1.
\b.7
\b73
\b3.
\b. s
\bse
\bet
\bt/
\b/d
\bdx
\bxg
\bgr
\bri
\bid
\bd (
\b(0
\b0)
\b)
3971 s
\bse
\bet
\bt/
\b/d
\bdx
\bxg
\bgr
\bri
\bid
\bdAllow grid squares on the end of DX messages
3974 Some logging programs do not like the additional information at the
3975 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
3976 to remove the grid squares.
3979 1
\b11
\b1.
\b.7
\b74
\b4.
\b. s
\bse
\bet
\bt/
\b/d
\bdx
\bxn
\bne
\bet
\bt (
\b(5
\b5)
\b)
3981 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
3985 Set the node_call as a DXNet type node
3988 1
\b11
\b1.
\b.7
\b75
\b5.
\b. s
\bse
\bet
\bt/
\b/e
\bec
\bch
\bho
\bo (
\b(0
\b0)
\b)
3990 s
\bse
\bet
\bt/
\b/e
\bec
\bch
\bho
\bo Make the cluster echo your input
3993 If you are connected via a telnet session, different implimentations
3994 of telnet handle echo differently depending on whether you are
3995 connected via port 23 or some other port. You can use this command to
3996 change the setting appropriately.
3998 You can remove the echo with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\be_
\bc_
\bh_
\bo command
4000 The setting is stored in your user profile.
4002 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
4005 1
\b11
\b1.
\b.7
\b76
\b6.
\b. s
\bse
\bet
\bt/
\b/h
\bhe
\ber
\bre
\be (
\b(0
\b0)
\b)
4007 s
\bse
\bet
\bt/
\b/h
\bhe
\ber
\bre
\be Set the here flag
4010 Let others on the cluster know you are here by only displaying your
4011 callsign. If you are away from your terminal you can use the
4012 _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bh_
\be_
\br_
\be command to let people know you are away. This simply puts
4013 brackets around your callsign to indicate you are not available.
4016 1
\b11
\b1.
\b.7
\b77
\b7.
\b. s
\bse
\bet
\bt/
\b/h
\bho
\bom
\bme
\ben
\bno
\bod
\bde
\be (
\b(0
\b0)
\b)
4018 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
4021 Tell the cluster system where you normally connect to. Any Messages
4022 sent to you will normally find their way there should you not be
4033 1
\b11
\b1.
\b.7
\b78
\b8.
\b. s
\bse
\bet
\bt/
\b/h
\bho
\bop
\bps
\bs (
\b(8
\b8)
\b)
4035 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
4038 Set the hop count for a particular type of broadcast for a node.
4040 This command allows you to set up special hop counts for a node for
4041 currently: announce, spots, wwv and wcy broadcasts.
4046 set/hops gb7djk ann 10
4047 set/hops gb7mbc spots 20
4052 Set SHOW/HOPS for information on what is already set. This command
4053 creates a filter and works in conjunction with the filter system.
4056 1
\b11
\b1.
\b.7
\b79
\b9.
\b. s
\bse
\bet
\bt/
\b/i
\bis
\bso
\bol
\bla
\bat
\bte
\be (
\b(9
\b9)
\b)
4058 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
4061 Connect a node to your system in such a way that you are a full
4062 protocol member of its network and can see all spots on it, but
4063 nothing either leaks out from it nor goes back into from the rest of
4064 the nodes connected to you.
4066 You can potentially connect several nodes in this way.
4068 You can see which nodes are isolated with the show/isolate (1)
4071 You can remove the isolation with the command unset/isolate.
4074 1
\b11
\b1.
\b.8
\b80
\b0.
\b. s
\bse
\bet
\bt/
\b/l
\bla
\ban
\bng
\bgu
\bua
\bag
\bge
\be (
\b(0
\b0)
\b)
4076 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
4079 You can select the language that you want the cluster to use.
4080 Currently the languages available are _
\be_
\bn (English) and _
\bn_
\bl (Dutch).
4083 1
\b11
\b1.
\b.8
\b81
\b1.
\b. s
\bse
\bet
\bt/
\b/l
\blo
\boc
\bca
\bat
\bti
\bio
\bon
\bn (
\b(0
\b0)
\b)
4085 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
4088 You can set your latitude and longitude manually or alternatively use
4089 the _
\bs_
\be_
\bt_
\b/_
\bq_
\br_
\ba command which will do the conversion for you.
4093 set/location 54 04 N 2 02 E
4100 1
\b11
\b1.
\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)
4102 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
4105 In order to get accurate headings and such like you must tell the
4106 system what your latitude and longitude is. If you have not yet done a
4107 SET/QRA then this command will set your QRA locator for you. For
4112 SET/LOCATION 52 22 N 0 57 E
4118 1
\b11
\b1.
\b.8
\b83
\b3.
\b. s
\bse
\bet
\bt/
\b/l
\blo
\bog
\bgi
\bin
\bni
\bin
\bnf
\bfo
\bo (
\b(0
\b0)
\b)
4120 s
\bse
\bet
\bt/
\b/l
\blo
\bog
\bgi
\bin
\bni
\bin
\bnf
\bfo
\bo Show logins and logouts of nodes and users
4123 Show users and nodes when they log in and out of the local cluster.
4124 You can stop these messages by using the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bl_
\bo_
\bg_
\bi_
\bn_
\bi_
\bn_
\bf_
\bo command.
4128 1
\b11
\b1.
\b.8
\b84
\b4.
\b. s
\bse
\bet
\bt/
\b/l
\blo
\boc
\bck
\bko
\bou
\but
\bt (
\b(9
\b9)
\b)
4130 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
4133 You can show who is locked out with the _
\bs_
\bh_
\bo_
\bw_
\b/_
\bl_
\bo_
\bc_
\bk_
\bo_
\bu_
\bt command. To
4134 allow the user to connect again, use the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bl_
\bo_
\bc_
\bk_
\bo_
\bu_
\bt command.
4137 1
\b11
\b1.
\b.8
\b85
\b5.
\b. s
\bse
\bet
\bt/
\b/n
\bna
\bam
\bme
\be (
\b(0
\b0)
\b)
4139 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
4142 Tell the cluster what your name is, eg:-
4152 1
\b11
\b1.
\b.8
\b86
\b6.
\b. s
\bse
\bet
\bt/
\b/n
\bno
\bod
\bde
\be (
\b(9
\b9)
\b)
4154 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
4157 Tell the system that the call(s) are to be treated as AK1A cluster and
4158 fed PC Protocol rather normal user commands.
4159 From version 1.41 you can also set the following types of cluster
4171 To see what your nodes are set to, use the _
\bs_
\bh_
\bo_
\bw_
\b/_
\bn_
\bo_
\bd_
\be_
\bs command.
4174 1
\b11
\b1.
\b.8
\b87
\b7.
\b. s
\bse
\bet
\bt/
\b/o
\bob
\bbs
\bsc
\bco
\bou
\bun
\bnt
\bt (
\b(9
\b9)
\b)
4176 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
4180 From version 1.35 onwards neighbouring nodes are pinged at regular
4181 intervals (see SET/PINGINTERVAL), usually 300 seconds or 5 minutes.
4182 There is a 'pump-up' counter which is decremented on every outgoing
4183 ping and then reset to the 'obscount' value on every incoming ping.
4184 The default value of this parameter is 2.
4186 What this means is that a neighbouring node will be pinged twice at
4187 (default) 300 second intervals and if no reply has been heard just
4188 before what would be the third attempt, that node is disconnected.
4190 If a ping is heard then the obscount is reset to the full value. Using
4191 default values, if a node has not responded to a ping within 15
4192 minutes, it is disconnected.
4195 1
\b11
\b1.
\b.8
\b88
\b8.
\b. s
\bse
\bet
\bt/
\b/p
\bpa
\bag
\bge
\be (
\b(0
\b0)
\b)
4197 s
\bse
\bet
\bt/
\b/p
\bpa
\bag
\bge
\be <
\b<n
\bn>
\b> Set the number of lines per page
4200 Tell the system how many lines you wish on a page when the number of
4201 lines of output from a command is more than this. The default is 20.
4202 Setting it explicitly to 0 will disable paging.
4212 The setting is stored in your user profile.
4216 1
\b11
\b1.
\b.8
\b89
\b9.
\b. s
\bse
\bet
\bt/
\b/p
\bpa
\bas
\bss
\bsw
\bwo
\bor
\brd
\bd (
\b(9
\b9)
\b)
4218 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
4221 The password for a user can only be set by a full sysop. The string
4222 can contain any characters but any spaces are removed (you can type in
4223 spaces - but they won't appear in the password). You can see the
4224 result with STAT/USER. The password is the usual 30 character baycom
4228 1
\b11
\b1.
\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)
4230 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
4234 As from version 1.35 all neighbouring nodes are pinged at regular
4235 intervals in order to determine the rolling quality of the link and,
4236 in future, to affect routing decisions. The default interval is 300
4239 You can use this command to set a different interval. Please don't.
4241 But if you do the value you enter is treated as minutes up 60 and
4242 seconds for numbers greater than that.
4244 This is used also to help determine when a link is down at the far end
4245 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
4246 for more information.
4249 1
\b11
\b1.
\b.9
\b91
\b1.
\b. s
\bse
\bet
\bt/
\b/p
\bpr
\bri
\biv
\bvi
\bil
\ble
\beg
\bge
\be (
\b(9
\b9)
\b)
4251 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
4255 Set the privilege level on a callsign. The privilege levels that
4256 pertain to commands are as default:-
4261 1 - allow remote nodes normal user RCMDs
4262 5 - various privileged commands (including shutdown, but not disc-
4263 connect), the normal level for another node.
4264 8 - more privileged commands (including disconnect)
4265 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
4271 If you are a sysop and you come in as a normal user on a remote
4272 connection your privilege will automatically be set to 0.
4275 1
\b11
\b1.
\b.9
\b92
\b2.
\b. s
\bse
\bet
\bt/
\b/s
\bsp
\bpi
\bid
\bde
\ber
\br (
\b(5
\b5)
\b)
4277 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
4281 Set the node_call as a DXSpider type node
4284 1
\b11
\b1.
\b.9
\b93
\b3.
\b. s
\bse
\bet
\bt/
\b/s
\bsy
\bys
\bs_
\b_q
\bqr
\bra
\ba (
\b(9
\b9)
\b)
4286 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
4291 1
\b11
\b1.
\b.9
\b94
\b4.
\b. s
\bse
\bet
\bt/
\b/q
\bqr
\bra
\ba (
\b(0
\b0)
\b)
4293 s
\bse
\bet
\bt/
\b/q
\bqr
\bra
\ba <
\b<l
\blo
\boc
\bca
\bat
\bto
\bor
\br>
\b> Set your QRA locator
4296 Tell the system what your QRA (or Maidenhead) locator is. If you have
4297 not done a SET/LOCATION then your latitude and longitude will be set
4298 roughly correctly (assuming your locator is correct ;-). For example:-
4308 1
\b11
\b1.
\b.9
\b95
\b5.
\b. s
\bse
\bet
\bt/
\b/q
\bqt
\bth
\bh (
\b(0
\b0)
\b)
4310 s
\bse
\bet
\bt/
\b/q
\bqt
\bth
\bh <
\b<y
\byo
\bou
\bur
\br Q
\bQT
\bTH
\bH>
\b> Set your QTH
4313 Tell the system where your are. For example:-
4317 set/qth East Dereham, Norfolk
4323 1
\b11
\b1.
\b.9
\b96
\b6.
\b. s
\bse
\bet
\bt/
\b/t
\bta
\bal
\blk
\bk (
\b(0
\b0)
\b)
4325 s
\bse
\bet
\bt/
\b/t
\bta
\bal
\blk
\bk Allow talk messages to be seen at your console
4328 Allow talk messages to arrive at your console. You can switch off
4329 talks with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bt_
\ba_
\bl_
\bk command.
4332 1
\b11
\b1.
\b.9
\b97
\b7.
\b. s
\bse
\bet
\bt/
\b/w
\bwc
\bcy
\by (
\b(0
\b0)
\b)
4334 s
\bse
\bet
\bt/
\b/w
\bwc
\bcy
\by Allow WCY messages to be seen at your console
4337 Allow WCY information to be seen at your console. You can switch off
4338 WCY messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bw_
\bc_
\by command.
4341 1
\b11
\b1.
\b.9
\b98
\b8.
\b. s
\bse
\bet
\bt/
\b/w
\bww
\bwv
\bv (
\b(0
\b0)
\b)
4343 s
\bse
\bet
\bt/
\b/w
\bww
\bwv
\bv Allow WWV messages to be seen at your console
4346 Allow WWV information to be seen at your console. You can switch off
4347 WWV messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bw_
\bw_
\bv command.
4350 1
\b11
\b1.
\b.9
\b99
\b9.
\b. s
\bse
\bet
\bt/
\b/w
\bwx
\bx (
\b(0
\b0)
\b)
4352 s
\bse
\bet
\bt/
\b/w
\bwx
\bx Allow WX messages to be seen at your console
4355 Allow WX information to be seen at your console. You can switch off
4356 WX messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bw_
\bx command.
4357 1
\b11
\b1.
\b.1
\b10
\b00
\b0.
\b. s
\bsh
\bho
\bow
\bw/
\b/b
\bba
\bad
\bdd
\bdx
\bx (
\b(1
\b1)
\b)
4359 s
\bsh
\bho
\bow
\bw/
\b/b
\bba
\bad
\bdd
\bdx
\bxShow all the bad dx calls in the system
4362 Display all the bad dx callsigns in the system, see SET/BADDX for more
4366 1
\b11
\b1.
\b.1
\b10
\b01
\b1.
\b. s
\bsh
\bho
\bow
\bw/
\b/b
\bba
\bad
\bdn
\bno
\bod
\bde
\be (
\b(6
\b6)
\b)
4368 s
\bsh
\bho
\bow
\bw/
\b/b
\bba
\bad
\bdn
\bno
\bod
\bde
\be Show all the bad nodes in the system
4371 Display all the bad node callsigns in the system, see SET/BADNODE for
4375 1
\b11
\b1.
\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)
4377 s
\bsh
\bho
\bow
\bw/
\b/b
\bba
\bad
\bds
\bsp
\bpo
\bot
\btt
\bte
\ber
\brShow all the bad spotters in the system
4380 Display all the bad spotter's callsigns in the system, see
4381 SET/BADSPOTTER for more information.
4384 1
\b11
\b1.
\b.1
\b10
\b03
\b3.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bda
\bat
\bte
\be (
\b(0
\b0)
\b)
4386 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
4389 This is very nearly the same as SHOW/TIME, the only difference the
4390 format of the date string if no arguments are given.
4392 If no prefixes or callsigns are given then this command returns the
4393 local time and UTC as the computer has it right now. If you give some
4394 prefixes then it will show UTC and UTC + the local offset (not
4395 including DST) at the prefixes or callsigns that you specify.
4398 1
\b11
\b1.
\b.1
\b10
\b04
\b4.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bx (
\b(0
\b0)
\b)
4400 s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bx [
\b[o
\bop
\bpt
\bti
\bio
\bon
\bns
\bs]
\b] interrogate the spot database
4403 If you just type SHOW/DX you will get the last so many spots (sysop
4404 configurable, but usually 10).
4406 In addition you can add any number of these options in very nearly any
4407 order to the basic SHOW/DX command, they are:-
4423 on <band> - eg 160m 20m 2m 23cm 6mm
4424 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
4426 <number> - the number of spots you want
4427 <from>-<to> - <from> spot no <to> spot no in
4430 <prefix> - for a spotted callsign beginning with <prefix>
4431 *<suffix> - for a spotted callsign ending in <suffix>
4432 *<string>* - for a spotted callsign containing <string>
4434 day <number> - starting <number> days ago
4435 day <from>-<to> - <from> days <to> days ago
4437 info <text> - any spots containing <text> in the info or remarks
4439 by <call> - any spots spotted by <call> (spotter <call>
4442 qsl - this automatically looks for any qsl info on the call
4443 held in the spot database.
4445 iota [<iota>] - If the iota island number is missing it will
4446 look for the string iota and anything which looks like
4447 an iota island number. If you specify then it will look
4450 qra [<locator>] - this will look for the specific locator if
4451 you specify one or else anything that looks like a locator.
4462 SH/DX on 20m info iota
4463 SH/DX 9a on vhf day 30
4473 1
\b11
\b1.
\b.1
\b10
\b05
\b5.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bxc
\bcc
\bc (
\b(0
\b0)
\b)
4475 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
4478 This command takes the <prefix> (which can be a full or partial
4479 callsign if desired), looks up which internal country number it is and
4480 then displays all the spots as per SH/DX for that country.
4482 The options for SHOW/DX also apply to this command. e.g.
4490 SH/DXCC W on 20m info iota
4496 1
\b11
\b1.
\b.1
\b10
\b06
\b6.
\b. s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\ble
\bes
\bs (
\b(0
\b0)
\b)
4498 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
4501 SHOW/FILES on its own will show you a list of the various fileareas
4502 available on the system. To see the contents of a particular file area
4512 where <filearea> is the name of the filearea you want to see the
4515 You can also use shell globbing characters like '*' and '?' in a
4516 string to see a selection of files in a filearea eg:-
4520 SH/FILES bulletins arld*
4525 See also TYPE - to see the contents of a file.
4528 1
\b11
\b1.
\b.1
\b10
\b07
\b7.
\b. s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\blt
\bte
\ber
\br (
\b(0
\b0)
\b)
4530 s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\blt
\bte
\ber
\br Show the filters you have set
4533 Show the contents of all the filters that are set by you. This command
4534 displays all the filters set - for all the various categories.
4537 1
\b11
\b1.
\b.1
\b10
\b08
\b8.
\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)
4539 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>
4542 A sysop can look at any filters that have been set.
4545 1
\b11
\b1.
\b.1
\b10
\b09
\b9.
\b. s
\bsh
\bho
\bow
\bw/
\b/h
\bho
\bop
\bps
\bs (
\b(8
\b8)
\b)
4547 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
4551 This command shows the hop counts set up for a node. You can specify
4552 which category you want to see. If you leave the category out then all
4553 the categories will be listed.
4555 1
\b11
\b1.
\b.1
\b11
\b10
\b0.
\b. s
\bsh
\bho
\bow
\bw/
\b/i
\bis
\bso
\bol
\bla
\bat
\bte
\be (
\b(1
\b1)
\b)
4557 s
\bsh
\bho
\bow
\bw/
\b/i
\bis
\bso
\bol
\bla
\bat
\bte
\be Show a list of isolated nodes
4560 Show which nodes are currently set to be isolated.
4563 1
\b11
\b1.
\b.1
\b11
\b11
\b1.
\b. s
\bsh
\bho
\bow
\bw/
\b/l
\blo
\boc
\bck
\bko
\bou
\but
\bt (
\b(9
\b9)
\b)
4565 s
\bsh
\bho
\bow
\bw/
\b/l
\blo
\boc
\bck
\bko
\bou
\but
\bt Show a list of excluded callsigns
4568 Show a list of callsigns that have been excluded (locked out) of the
4569 cluster locally with the _
\bs_
\be_
\bt_
\b/_
\bl_
\bo_
\bc_
\bk_
\bo_
\bu_
\bt command
4572 1
\b11
\b1.
\b.1
\b11
\b12
\b2.
\b. s
\bsh
\bho
\bow
\bw/
\b/m
\bmo
\boo
\bon
\bn (
\b(0
\b0)
\b)
4574 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
4577 Show the Moon rise and set times for a (list of) prefixes or
4578 callsigns, together with the azimuth and elevation of the sun
4579 currently at those locations.
4581 If you don't specify any prefixes or callsigns, it will show the times
4582 for your QTH (assuming you have set it with either SET/LOCATION or
4583 SET/QRA), together with the current azimuth and elevation.
4585 In addition, it will show the gain or loss dB relative to the nominal
4586 distance of 385,000Km due to the ellipsoidal nature of the orbit.
4588 If all else fails it will show the Moonrise and set times for the node
4589 that you are connected to.
4602 1
\b11
\b1.
\b.1
\b11
\b13
\b3.
\b. s
\bsh
\bho
\bow
\bw/
\b/m
\bmu
\buf
\bf (
\b(0
\b0)
\b)
4604 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
4608 This command allow you to estimate the likelihood of you contacting a
4609 station with the prefix you have specified. The output assumes a
4610 modest power of 20dBW and receiver sensitivity of -123dBm (about
4613 The result predicts the most likely operating frequencies and signal
4614 levels for high frequency (shortwave) radio propagation paths on
4615 specified days of the year and hours of the day. It is most useful for
4616 paths between 250 km and 6000 km, but can be used with reduced
4617 accuracy for paths shorter or longer than this.
4619 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
4620 used to predict the MUF given the predicted flux, day of the year,
4621 hour of the day and geographic coordinates of the transmitter and
4622 receiver. This routine is reasonably accurate for the purposes here,
4623 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
4624 than the programs used by major shortwave broadcasting organizations,
4625 such as the Voice of America.
4627 The command will display some header information detailing its
4628 assumptions, together with the locations, latitude and longitudes and
4629 bearings. It will then show UTC (UT), local time at the other end
4630 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
4631 (Zen) and the likely signal strengths. Then for each frequency for
4632 which the system thinks there is a likelihood of a circuit it prints a
4635 The value is currently a likely S meter reading based on the
4636 conventional 6dB / S point scale. If the value has a '+' appended it
4637 means that it is 1/2 an S point stronger. If the value is preceeded by
4638 an 'm' it means that there is likely to be much fading and by an 's'
4639 that the signal is likely to be noisy.
4641 By default SHOW/MUF will show the next two hours worth of data. You
4642 can specify anything up to 24 hours worth of data by appending the no
4643 of hours required after the prefix. For example:-
4656 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
4657 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
4658 Location Lat / Long Azim
4659 East Dereham, Norfolk 52 41 N 0 57 E 47
4660 United-States-W 43 0 N 87 54 W 299
4661 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
4662 18 23 11.5 -35 mS0+ mS2 S3
4663 19 0 11.2 -41 mS0+ mS2 S3
4668 indicating that you will have weak, fading circuits on top band and
4669 80m but usable signals on 40m (about S3).
4680 will get you the above display, but with the next 24 hours worth of
4693 Gives you an estimate of the long path propagation characterics. It
4694 should be noted that the figures will probably not be very useful, nor
4695 terrible accurate, but it is included for completeness.
4698 1
\b11
\b1.
\b.1
\b11
\b14
\b4.
\b. s
\bsh
\bho
\bow
\bw/
\b/n
\bno
\bod
\bde
\be (
\b(1
\b1)
\b)
4700 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
4703 Show the type and version (if connected) of the nodes specified on the
4704 command line. If no callsigns are specified then a sorted list of all
4705 the non-user callsigns known to the system will be displayed.
4708 1
\b11
\b1.
\b.1
\b11
\b15
\b5.
\b. s
\bsh
\bho
\bow
\bw/
\b/p
\bpr
\bre
\bef
\bfi
\bix
\bx (
\b(0
\b0)
\b)
4710 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
4713 This command takes the <callsign> (which can be a full or partial
4714 callsign or a prefix), looks up which internal country number it is
4715 and then displays all the relevant prefixes for that country together
4716 with the internal country no, the CQ and ITU regions.
4722 1
\b11
\b1.
\b.1
\b11
\b16
\b6.
\b. s
\bsh
\bho
\bow
\bw/
\b/p
\bpr
\bro
\bog
\bgr
\bra
\bam
\bm (
\b(5
\b5)
\b)
4724 s
\bsh
\bho
\bow
\bw/
\b/p
\bpr
\bro
\bog
\bgr
\bra
\bam
\bm Show the locations of all the included program modules
4727 Show the name and location where every program module was load from.
4728 This is useful for checking where you think you have loaded a .pm file
4732 1
\b11
\b1.
\b.1
\b11
\b17
\b7.
\b. s
\bsh
\bho
\bow
\bw/
\b/q
\bqr
\bra
\ba (
\b(0
\b0)
\b)
4734 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
4735 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
4738 This is a multipurpose command that allows you either to calculate the
4739 distance and bearing between two locators or (if only one locator is
4740 given on the command line) the distance and beraing from your station
4741 to the locator. For example:-
4751 The first example will show the distance and bearing to the locator
4752 from yourself, the second example will calculate the distance and
4753 bearing from the first locator to the second. You can use 4 or 6
4756 It is also possible to convert a latitude and longitude to a locator
4757 by using this command with a latitude and longitude as an argument,
4762 SH/QRA 52 41 N 0 58 E
4768 1
\b11
\b1.
\b.1
\b11
\b18
\b8.
\b. s
\bsh
\bho
\bow
\bw/
\b/q
\bqr
\brz
\bz (
\b(0
\b0)
\b)
4770 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
4773 This command queries the QRZ callbook server on the internet and
4774 returns any information available for that callsign. This service is
4775 provided for users of this software by http://www.qrz.com
4778 1
\b11
\b1.
\b.1
\b11
\b19
\b9.
\b. s
\bsh
\bho
\bow
\bw/
\b/r
\bro
\bou
\but
\bte
\be (
\b(0
\b0)
\b)
4780 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>
4783 This command allows you to see to which node the callsigns specified
4784 are connected. It is a sort of inverse sh/config.
4794 1
\b11
\b1.
\b.1
\b12
\b20
\b0.
\b. s
\bsh
\bho
\bow
\bw/
\b/s
\bsa
\bat
\bte
\bel
\bll
\bli
\bit
\bte
\be (
\b(0
\b0)
\b)
4796 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
4800 Show the tracking data from your location to the satellite of your
4801 choice from now on for the next few hours.
4803 If you use this command without a satellite name it will display a
4804 list of all the satellites known currently to the system.
4806 If you give a name then you can obtain tracking data of all the passes
4807 that start and finish 5 degrees below the horizon. As default it will
4808 give information for the next three hours for every five minute
4811 You can alter the number of hours and the step size, within certain
4814 Each pass in a period is separated with a row of '-----' characters
4820 SH/SAT FENGYUN1 12 2
4826 1
\b11
\b1.
\b.1
\b12
\b21
\b1.
\b. s
\bsh
\bho
\bow
\bw/
\b/s
\bsu
\bun
\bn (
\b(0
\b0)
\b)
4828 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
4831 Show the sun rise and set times for a (list of) prefixes or callsigns,
4832 together with the azimuth and elevation of the sun currently at those
4835 If you don't specify any prefixes or callsigns, it will show the times
4836 for your QTH (assuming you have set it with either SET/LOCATION or
4837 SET/QRA), together with the current azimuth and elevation.
4839 If all else fails it will show the sunrise and set times for the node
4840 that you are connected to.
4847 SH/SUN G1TLH K9CW ZS
4853 1
\b11
\b1.
\b.1
\b12
\b22
\b2.
\b. s
\bsh
\bho
\bow
\bw/
\b/t
\bti
\bim
\bme
\be (
\b(0
\b0)
\b)
4855 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
4858 If no prefixes or callsigns are given then this command returns the
4859 local time and UTC as the computer has it right now. If you give some
4860 prefixes then it will show UTC and UTC + the local offset (not
4861 including DST) at the prefixes or callsigns that you specify.
4864 1
\b11
\b1.
\b.1
\b12
\b23
\b3.
\b. s
\bsh
\bho
\bow
\bw/
\b/w
\bwc
\bcy
\by (
\b(0
\b0)
\b)
4866 s
\bsh
\bho
\bow
\bw/
\b/w
\bwc
\bcy
\by Show the last 10 WCY broadcasts
4867 s
\bsh
\bho
\bow
\bw/
\b/w
\bwc
\bcy
\by <
\b<n
\bn>
\b> Show the last <n> WCY broadcasts
4870 Display the most recent WCY information that has been received by the
4874 1
\b11
\b1.
\b.1
\b12
\b24
\b4.
\b. s
\bsh
\bho
\bow
\bw/
\b/w
\bww
\bwv
\bv (
\b(0
\b0)
\b)
4876 s
\bsh
\bho
\bow
\bw/
\b/w
\bww
\bwv
\bv Show the last 10 WWV broadcasts
4877 s
\bsh
\bho
\bow
\bw/
\b/w
\bww
\bwv
\bv <
\b<n
\bn>
\b> Show the last <n> WWV broadcasts
4880 Display the most recent WWV information that has been received by the
4885 1
\b11
\b1.
\b.1
\b12
\b25
\b5.
\b. s
\bsh
\bhu
\but
\btd
\bdo
\bow
\bwn
\bn (
\b(5
\b5)
\b)
4887 s
\bsh
\bhu
\but
\btd
\bdo
\bow
\bwn
\bn Shutdown the cluster
4890 Shutdown the cluster and disconnect all the users. If you have Spider
4891 set to respawn in /etc/inittab it will of course restart.
4894 1
\b11
\b1.
\b.1
\b12
\b26
\b6.
\b. s
\bsp
\bpo
\boo
\bof
\bf (
\b(9
\b9)
\b)
4896 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
4899 This is a very simple yet powerful command for the sysop. It allows
4900 you to issue commands as if you were a different user. This is very
4901 useful for the kind of things that users seem to always get wrong..
4902 like home_node for example.
4905 1
\b11
\b1.
\b.1
\b12
\b27
\b7.
\b. s
\bst
\bta
\bat
\bt/
\b/d
\bdb
\bb (
\b(5
\b5)
\b)
4907 s
\bst
\bta
\bat
\bt/
\b/d
\bdb
\bb <
\b<d
\bdb
\bbn
\bna
\bam
\bme
\be>
\b> Show the status of a database
4910 Show the internal status of a database descriptor.
4912 Depending on your privilege level you will see more or less
4913 information. This command is unlikely to be of much use to anyone
4917 1
\b11
\b1.
\b.1
\b12
\b28
\b8.
\b. s
\bst
\bta
\bat
\bt/
\b/c
\bch
\bha
\ban
\bnn
\bne
\bel
\bl (
\b(5
\b5)
\b)
4919 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
4922 Show the internal status of the channel object either for the channel
4923 that you are on or else for the callsign that you asked for.
4925 Only the fields that are defined (in perl term) will be displayed.
4928 1
\b11
\b1.
\b.1
\b12
\b29
\b9.
\b. s
\bst
\bta
\bat
\bt/
\b/m
\bms
\bsg
\bg (
\b(5
\b5)
\b)
4930 s
\bst
\bta
\bat
\bt/
\b/m
\bms
\bsg
\bg <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Show the status of a message
4933 This command shows the internal status of a message and includes
4934 information such as to whom it has been forwarded, its size, origin
4938 1
\b11
\b1.
\b.1
\b13
\b30
\b0.
\b. s
\bst
\bta
\bat
\bt/
\b/u
\bus
\bse
\ber
\br (
\b(5
\b5)
\b)
4940 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
4943 Shows the full contents of a user record including all the secret
4946 Only the fields that are defined (in perl term) will be displayed.
4951 1
\b11
\b1.
\b.1
\b13
\b31
\b1.
\b. s
\bsy
\bys
\bso
\bop
\bp (
\b(0
\b0)
\b)
4953 s
\bsy
\bys
\bso
\bop
\bp Regain your privileges if you login remotely
4956 The system automatically reduces your privilege level to that of a
4957 normal user if you login in remotely. This command allows you to
4958 regain your normal privilege level. It uses the normal system: five
4959 numbers are returned that are indexes into the character array that is
4960 your assigned password (see SET/PASSWORD). The indexes start from
4963 You are expected to return a string which contains the characters
4964 required in the correct order. You may intersperse those characters
4965 with others to obscure your reply for any watchers. For example (and
4966 these values are for explanation :-):
4970 password = 012345678901234567890123456789
4981 aa2bbbb0ccc5ddd7xxx3n
4988 They will all match. If there is no password you will still be offered
4989 numbers but nothing will happen when you input a string. Any match is
4993 1
\b11
\b1.
\b.1
\b13
\b32
\b2.
\b. t
\bta
\bal
\blk
\bk (
\b(0
\b0)
\b)
4995 t
\bta
\bal
\blk
\bk <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> Enter talk mode with <callsign>
4996 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>
4997 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
4998 <callsign> via <node_call>
5001 Send a short message to any other station that is visible on the
5002 cluster system. You can send it to anyone you can see with a
5003 SHOW/CONFIGURATION command, they don't have to be connected locally.
5005 The second form of TALK is used when other cluster nodes are connected
5006 with restricted information. This usually means that they don't send
5007 the user information usually associated with logging on and off the
5010 If you know that G3JNB is likely to be present on GB7TLH, but you can
5011 only see GB7TLH in the SH/C list but with no users, then you would use
5012 the second form of the talk message.
5014 If you want to have a ragchew with someone you can leave the text
5015 message out and the system will go into 'Talk' mode. What this means
5016 is that a short message is sent to the recipient telling them that you
5017 are in a 'Talking' frame of mind and then you just type - everything
5018 you send will go to the station that you asked for.
5020 All the usual announcements, spots and so on will still come out on
5023 If you want to do something (such as send a spot) you precede the
5024 normal command with a '/' character, eg:-
5028 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
5034 To leave talk mode type:
5044 1
\b11
\b1.
\b.1
\b13
\b33
\b3.
\b. t
\bty
\byp
\bpe
\be (
\b(0
\b0)
\b)
5046 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
5049 Type out the contents of a file in a filearea. So, for example, in
5050 filearea 'bulletins' you want to look at file 'arld051' you would
5055 TYPE bulletins/arld051
5060 See also SHOW/FILES to see what fileareas are available and a list of
5064 1
\b11
\b1.
\b.1
\b13
\b34
\b4.
\b. w
\bwh
\bho
\bo (
\b(0
\b0)
\b)
5066 w
\bwh
\bho
\bo Show who is physically connected locally
5069 This is a quick listing that shows which callsigns are connected and
5070 what sort of connection they have
5073 1
\b11
\b1.
\b.1
\b13
\b35
\b5.
\b. w
\bwx
\bx (
\b(0
\b0)
\b)
5075 w
\bwx
\bx <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send a weather message to local users
5076 w
\bwx
\bx f
\bfu
\bul
\bll
\bl <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send a weather message to all cluster users
5079 Weather messages can sometimes be useful if you are experiencing an
5080 extreme that may indicate enhanced conditions
5083 1
\b11
\b1.
\b.1
\b13
\b36
\b6.
\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)
5085 w
\bwx
\bx s
\bsy
\bys
\bso
\bop
\bp <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send a weather message to other clusters only
5088 Send a weather message only to other cluster nodes and not to general