X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=txt%2Fadminmanual.txt;h=16c3e0de813ce54ce03cf22343830b38646e1890;hb=ab0ea211ea17085944f4ce2b0100932fa6af02c8;hp=48afba2772a3458e1b98aff1d59d29d06efbc6e7;hpb=1a739957114ea367098a5731c86edb6d9bb808e2;p=spider.git diff --git a/txt/adminmanual.txt b/txt/adminmanual.txt index 48afba27..16c3e0de 100644 --- a/txt/adminmanual.txt +++ b/txt/adminmanual.txt @@ -1,6 +1,6 @@ The DXSpider Installation and Administration Manual Ian Maude, G0VGS, (ianmaude@btinternet.com) - Version 1.29 January 2001 + Version 1.47 (Revision 1.30), April 2001 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -64,24 +64,27 @@ - 1. Installation (Original version by Iain Phillips, G0RDI) + 1. Installation (Original version by Iain Philipps, G0RDI) 1.1 Introduction 1.2 Preparation 1.3 Installing the software 1.4 Setting callsigns etc 1.5 Starting up for the first time + 1.6 The Client program - 2. The Client program + 2. Quick installation guide (Linux version) 3. Configuration 3.1 Allowing ax25 connects from users 3.2 Allowing telnet connects from users - 3.3 Setting up node connects - 3.4 Connection scripts - 3.5 Starting the connection - 3.6 Telnet echo + 3.3 Setting up telnet connects (from 1.47 onwards) + 3.4 Setting up for AGW Engine (1.47 onwards) + 3.5 Setting up node connects + 3.6 Connection scripts + 3.7 Starting the connection + 3.8 Telnet echo 4. Automating things @@ -113,171 +116,194 @@ 8.2 Filtering DX callouts (Depricated) 8.3 Filtering words from text fields in Announce, Talk and DX spots - 9. Information, files and useful programs - - 9.1 MOTD - 9.2 Downtime message - 9.3 Other text messages - 9.4 The Aliases file - 9.5 Forward.pl - 9.6 Distribution lists - 9.7 Console.pl - - 10. CVS - - 11. The DXSpider command set - - 11.1 accept/announce (0) - 11.2 accept/announce (extended for sysops) (8) - 11.3 accept/spots (0) - 11.4 accept/spots (extended for sysops) (8) - 11.5 accept/wcy (0) - 11.6 accept/wcy (extended for sysops) (8) - 11.7 accept/wwv (0) - 11.8 accept/wwv (extended for sysops) (8) - 11.9 announce (0) - 11.10 announce full (0) - 11.11 announce sysop (5) - 11.12 apropos (0) - 11.13 bye (0) - 11.14 catchup (5) - 11.15 clear/spots (0) - 11.16 connect (5) - 11.17 dbavail (0) - 11.18 dbcreate (9) - 11.19 dbimport (9) - 11.20 dbremove (9) - 11.21 dbshow (0) - 11.22 debug (9) - 11.23 directory (0) - 11.24 directory (extended for sysops) (5) - 11.25 disconnect (8) - 11.26 dx (0) - 11.27 export (9) - 11.28 export_users (9) - 11.29 forward/latlong (8) - 11.30 forward/opername (1) - 11.31 help (0) - 11.32 init (5) - 11.33 kill (0) - 11.34 kill (5) - 11.35 kill full (5) - 11.36 links (0) - 11.37 load/aliases (9) - 11.38 load/baddx (9) - 11.39 load/badmsg (9) - 11.40 load/badwords (9) - 11.41 load/bands (9) - 11.42 load/cmd_cache (9) - 11.43 load/forward (9) - 11.44 load/messages (9) - 11.45 load/prefixes (9) - 11.46 merge (5) - 11.47 msg (9) - 11.48 pc (8) - 11.49 ping (1) - 11.50 rcmd (1) - 11.51 read (0) - 11.52 read (extended for sysops) (5) - 11.53 reject/announce - 11.54 reject/announce (extended for sysops) (8) - 11.55 reject/spots (0) - 11.56 reject/spots (extended for sysops) (8) - 11.57 reject/wcy (0) - 11.58 reject/wcy (extended for sysops) (8) - 11.59 reject/wwv (0) - 11.60 reject/wwv (extended for sysops) (8) - 11.61 reply (0) - 11.62 send (0) - 11.63 set/address (0) - 11.64 set/announce (0) - 11.65 set/arcluster (5) - 11.66 set/baddx (8) - 11.67 set/badnode (6) - 11.68 set/badspotter (8) - 11.69 set/beep (0) - 11.70 set/clx (5) - 11.71 set/debug (9) - 11.72 set/dx (0) - 11.73 set/dxgrid (0) - 11.74 set/dxnet (5) - 11.75 set/echo (0) - 11.76 set/here (0) - 11.77 set/homenode (0) - 11.78 set/hops (8) - 11.79 set/isolate (9) - 11.80 set/language (0) - 11.81 set/location (0) - 11.82 set/sys_location (9) - 11.83 set/logininfo (0) - 11.84 set/lockout (9) - 11.85 set/name (0) - 11.86 set/node (9) - 11.87 set/obscount (9) - 11.88 set/page (0) - 11.89 set/password (9) - 11.90 set/pinginterval (9) - 11.91 set/privilege (9) - 11.92 set/spider (5) - 11.93 set/sys_qra (9) - 11.94 set/qra (0) - 11.95 set/qth (0) - 11.96 set/talk (0) - 11.97 set/wcy (0) - 11.98 set/wwv (0) - 11.99 set/wx (0) - 11.100 show/baddx (1) - 11.101 show/badnode (6) - 11.102 show/badspotter (1) - 11.103 show/date (0) - 11.104 show/dx (0) - 11.105 show/dxcc (0) - 11.106 show/files (0) - 11.107 show/filter (0) - 11.108 show/filter (extended for sysops) (5) - 11.109 show/hops (8) - 11.110 show/isolate (1) - 11.111 show/lockout (9) - 11.112 show/moon (0) - 11.113 show/muf (0) - 11.114 show/node (1) - 11.115 show/prefix (0) - 11.116 show/program (5) - 11.117 show/qra (0) - 11.118 show/qrz (0) - 11.119 show/route (0) - 11.120 show/satellite (0) - 11.121 show/sun (0) - 11.122 show/time (0) - 11.123 show/wcy (0) - 11.124 show/wwv (0) - 11.125 shutdown (5) - 11.126 spoof (9) - 11.127 stat/db (5) - 11.128 stat/channel (5) - 11.129 stat/msg (5) - 11.130 stat/user (5) - 11.131 sysop (0) - 11.132 talk (0) - 11.133 type (0) - 11.134 who (0) - 11.135 wx (0) - 11.136 wx (enhanced for sysops) (5) + 9. Mail + + 9.1 Personal mail + 9.2 Bulletin mail + 9.3 Forward.pl + 9.4 The msg command + 9.5 Message status + 9.6 Filtering mail + 9.7 Distribution lists + 9.8 BBS interface + + 10. Databases + + 10.1 Creating databases + 10.2 Importing databases + 10.3 Checking available databases + 10.4 Looking up databases + 10.5 Removing databases + + 11. Information, files and useful programs + + 11.1 MOTD + 11.2 Downtime message + 11.3 Other text messages + 11.4 The Aliases file + 11.5 Console.pl + 11.6 Updating kepler data + 11.7 The QRZ callbook + + 12. CVS + + 13. The DXSpider command set + + 13.1 accept/announce (0) + 13.2 accept/announce (extended for sysops) (8) + 13.3 accept/spots (0) + 13.4 accept/spots (extended for sysops) (8) + 13.5 accept/wcy (0) + 13.6 accept/wcy (extended for sysops) (8) + 13.7 accept/wwv (0) + 13.8 accept/wwv (extended for sysops) (8) + 13.9 announce (0) + 13.10 announce full (0) + 13.11 announce sysop (5) + 13.12 apropos (0) + 13.13 bye (0) + 13.14 catchup (5) + 13.15 clear/spots (0) + 13.16 connect (5) + 13.17 dbavail (0) + 13.18 dbcreate (9) + 13.19 dbimport (9) + 13.20 dbremove (9) + 13.21 dbshow (0) + 13.22 debug (9) + 13.23 directory (0) + 13.24 directory (extended for sysops) (5) + 13.25 disconnect (8) + 13.26 dx (0) + 13.27 export (9) + 13.28 export_users (9) + 13.29 forward/latlong (8) + 13.30 forward/opername (1) + 13.31 help (0) + 13.32 init (5) + 13.33 kill (0) + 13.34 kill (5) + 13.35 kill full (5) + 13.36 links (0) + 13.37 load/aliases (9) + 13.38 load/baddx (9) + 13.39 load/badmsg (9) + 13.40 load/badwords (9) + 13.41 load/bands (9) + 13.42 load/cmd_cache (9) + 13.43 load/forward (9) + 13.44 load/messages (9) + 13.45 load/prefixes (9) + 13.46 merge (5) + 13.47 msg (9) + 13.48 pc (8) + 13.49 ping (1) + 13.50 rcmd (1) + 13.51 read (0) + 13.52 read (extended for sysops) (5) + 13.53 reject/announce + 13.54 reject/announce (extended for sysops) (8) + 13.55 reject/spots (0) + 13.56 reject/spots (extended for sysops) (8) + 13.57 reject/wcy (0) + 13.58 reject/wcy (extended for sysops) (8) + 13.59 reject/wwv (0) + 13.60 reject/wwv (extended for sysops) (8) + 13.61 reply (0) + 13.62 send (0) + 13.63 set/address (0) + 13.64 set/announce (0) + 13.65 set/arcluster (5) + 13.66 set/baddx (8) + 13.67 set/badnode (6) + 13.68 set/badspotter (8) + 13.69 set/beep (0) + 13.70 set/clx (5) + 13.71 set/debug (9) + 13.72 set/dx (0) + 13.73 set/dxgrid (0) + 13.74 set/dxnet (5) + 13.75 set/echo (0) + 13.76 set/here (0) + 13.77 set/homenode (0) + 13.78 set/hops (8) + 13.79 set/isolate (9) + 13.80 set/language (0) + 13.81 set/location (0) + 13.82 set/sys_location (9) + 13.83 set/logininfo (0) + 13.84 set/lockout (9) + 13.85 set/name (0) + 13.86 set/node (9) + 13.87 set/obscount (9) + 13.88 set/page (0) + 13.89 set/password (9) + 13.90 set/pinginterval (9) + 13.91 set/privilege (9) + 13.92 set/spider (5) + 13.93 set/sys_qra (9) + 13.94 set/qra (0) + 13.95 set/qth (0) + 13.96 set/talk (0) + 13.97 set/wcy (0) + 13.98 set/wwv (0) + 13.99 set/wx (0) + 13.100 show/baddx (1) + 13.101 show/badnode (6) + 13.102 show/badspotter (1) + 13.103 show/configuration (0) + 13.104 show/configuration/node (0) + 13.105 show/connect (1) + 13.106 show/date (0) + 13.107 show/debug (9) + 13.108 show/dx (0) + 13.109 show/dxcc (0) + 13.110 show/files (0) + 13.111 show/filter (0) + 13.112 show/filter (extended for sysops) (5) + 13.113 show/hops (8) + 13.114 show/isolate (1) + 13.115 show/lockout (9) + 13.116 show/log (8) + 13.117 show/moon (0) + 13.118 show/muf (0) + 13.119 show/node (1) + 13.120 show/prefix (0) + 13.121 show/program (5) + 13.122 show/qra (0) + 13.123 show/qrz (0) + 13.124 show/route (0) + 13.125 show/satellite (0) + 13.126 show/sun (0) + 13.127 show/time (0) + 13.128 show/wcy (0) + 13.129 show/wwv (0) + 13.130 shutdown (5) + 13.131 spoof (9) + 13.132 stat/db (5) + 13.133 stat/channel (5) + 13.134 stat/msg (5) + 13.135 stat/user (5) + 13.136 sysop (0) + 13.137 talk (0) + 13.138 type (0) + 13.139 who (0) + 13.140 wx (0) + 13.141 wx (enhanced for sysops) (5) ______________________________________________________________________ - 11.. IInnssttaallllaattiioonn ((OOrriiggiinnaall vveerrssiioonn bbyy IIaaiinn PPhhiilllliippss,, GG00RRDDII)) - - Last modified: 13 January 2001 by Ian Maude, G0VGS - + 11.. IInnssttaallllaattiioonn ((OOrriiggiinnaall vveerrssiioonn bbyy IIaaiinn PPhhiilliippppss,, GG00RRDDII)) 11..11.. IInnttrroodduuccttiioonn - This section describes the installation of DX Spider v1.35 on a RedHat - Linux Distribution. I do not intend to try and cover the installation - of Linux or the setup of the AX25 utilities. If you need help on this - then read Iains original HOWTO on the DXSpider website. + This section describes the installation of DX Spider v1.46 on a RedHat + Linux Distribution. Wherever possible I will try to include + differences for other distributions. I do not intend to try and cover + the installation of Linux or the setup of the AX25 utilities. If you + need help on this then read Iains original installation guide that + comes with the Spider distribution. I am assuming a general knowledge of Linux and its commands. You @@ -285,28 +311,22 @@ editor. - The crucial ingredient for all of this is Perl 5.004. Now I know Perl - 5.005 is out and this will almost certainly work with it, but RedHat - 5.1 comes with 5.004. _B_e _W_a_r_n_e_d, earlier versions of RedHat ddoo nnoott - come with 5.004 as standard, you need to upgrade + The crucial ingredient for all of this is Perl. Earlier versions of + Spider required perl 5.004, however it is now _S_T_R_O_N_G_L_Y recommended + that you use at least version 5.005_03 as this is the version being + used in the development of Spider. In addition to the standard Red Hat distribution you will require the - following CPAN modules: - - - + following modules from http://www.cpan.org/CPAN.html ... - +o MD5-1.7.tar.gz - +o Data-Dumper-2.10.tar.gz - +o FreezeThaw-0.3.tar.gz + +o Data-Dumper-2.101.tar.gz - +o MLDBM-2.00.tar.gz + +o TimeDate-1.10.tar.gz - +o TimeDate-1.08.tar.gz - - +o IO-1.20.tar.gz + +o IO-1.20.tar.gz (for perl 5.00403 and lower) +o Net-Telnet-3.02.tar.gz @@ -324,7 +344,7 @@ I will assume that you have already downloaded the latest tarball of the DXSpider software and are ready to install it. I am assuming - version 1.35 for this section but of course you would use the latest + version 1.46 for this section but of course you would use the latest version. @@ -364,7 +384,7 @@ # cd ~sysop - # tar xvfz spider-1.35.tar.gz + # tar xvfz spider-1.46.tar.gz # ln -s ~sysop/spider /spider # groupadd -g 251 spider (or another number) @@ -374,8 +394,6 @@ If you do not have the command _g_r_o_u_p_a_d_d available to you simply add a line in /etc/group by hand. - - # vi /etc/group (or your favorite editor) @@ -393,10 +411,9 @@ - - # chown -R sysop.spider spider - # find . -type d -exec chmod 2775 {} \; - # find . -type f -exec chmod 775 {} \; + # chown -R sysop.spider spider + # find . -type d -exec chmod 2775 {} \; + # find . -type f -exec chmod 775 {} \; @@ -457,11 +474,10 @@ PPLLEEAASSEE UUSSEE CCAAPPIITTAALL LLEETTTTEERRSS FFOORR CCAALLLLSSIIGGNNSS - DON'T alter the DXVars.pm (or any other file) in /spider/perl, they - are overwritten with every release. Any files or commands you place in - /spider/local or /spider/local_cmd will automagically be used in - preference to the ones in /spider/perl EVEN while the cluster is - running! + DON'T alter any file in /spider/perl, they are overwritten with every + release. Any files or commands you place in /spider/local or + /spider/local_cmd will automagically be used in preference to the ones + in /spider/perl EVEN while the cluster is running! Save the new file and change directory to ../perl .... @@ -479,7 +495,7 @@ - $ create_sysop.pl + $ ./create_sysop.pl @@ -492,8 +508,8 @@ - $ cluster.pl - DXSpider DX Cluster Version 1.35 + $ ./cluster.pl + DXSpider DX Cluster Version 1.46 Copyright (c) 1998 Dirk Koopman G1TLH loading prefixes ... loading band data ... @@ -508,11 +524,9 @@ If all is well then login on another term or console as _s_y_s_o_p and cd - to /spider/perl. Now issue the following command ... + to /spider/src. Now issue the following command ... - - - $ client.pl + $ ./client @@ -526,7 +540,7 @@ - G0VGS de GB7MBC 19-Nov-1999 2150Z > + G0VGS de GB7MBC 19-Nov-1999 2150Z > @@ -546,7 +560,7 @@ and both the cluster and the client should return to Linux prompts. - 22.. TThhee CClliieenntt pprrooggrraamm + 11..66.. TThhee CClliieenntt pprrooggrraamm In earlier versions of Spider, all the processes were Perl scripts. This was fine but with a lot of users your computer memory would soon @@ -557,8 +571,93 @@ small C program called _c_l_i_e_n_t. Leave it in this directory. + + 22.. QQuuiicckk iinnssttaallllaattiioonn gguuiiddee ((LLiinnuuxx vveerrssiioonn)) + + This section is designed for experienced Spider sysops who want to + install Spider from scratch. It is simply a check list of things that + need to be done without any explanations. The name in brackets at the + end of each line is the user that should be doing that process. + + + +o Login as root + + +o Get the additional CPAN modules and install them (root) + + +o Create the "sysop" user and set a password (root) + + +o Put the Spider tarball in sysop and untar it (root) + + +o ln -s sysop/spider /spider (root) + + +o groupadd -g 251 spider (root) + + +o Add any more users you need to the group entry in /etc/group (root) + + +o Set the permissions on the spider tree (root) + + +o Fix permissions on ax25_call and netrom_call (root) + + +o Login as the sysop user + + +o cd to /spider (sysop) + + +o mkdir local (sysop) + + +o mkdir local_cmd (sysop) + + +o cp perl/DXVars.pm.issue local/DXVars.pm (sysop) + + +o cd to /spider/local and edit DXVars to set your details (sysop) + + +o cd ../perl (sysop) + + +o ./create_sysop.pl (sysop) + + +o ./cluster.pl (sysop) + + Spider should now be running and you should be able to login using the + client program. + + + +o Login as root + + +o Enter the correct line in ax25d.conf (root) + + +o Enter the correct line in /etc/services (root) + + +o Enter the correct line in /etc/inetd.conf (root) + + +o killall -HUP inetd (root) + + Spider should now be able to accept logins via telnet, netrom and + ax25. + + + +o Login as sysop + + +o Start the cluster (sysop) + + +o set/node and type for links (sysop) + + +o Write any connect scripts (sysop) + + +o Edit /spider/crontab as required (sysop) + + +o Edit any other files as necessary (sysop) + + +o Set filters, hops and forwarding files (sysop) + + +o Login as root + + +o Enter the correct line in /etc/inittab (root) + + 33.. CCoonnffiigguurraattiioonn + + + 33..11.. AAlllloowwiinngg aaxx2255 ccoonnnneeccttss ffrroomm uusseerrss As stated previously, the aim of this document is not to tell you how @@ -574,9 +673,38 @@ + or, if you wish your users to be able to use SSID's on their callsigns + .. + + + + default * * * * * * - sysop /spider/src/client client %s ax25 + + + + + For most purposes this is not desirable. The only time you probably + will need this is when you need to allow other cluster nodes that are + using SSID's in. In this case it would probably be better to use the + first example and then add a specific line for that node like this: + + + + GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25 + default * * * * * * - sysop /spider/src/client client %u ax25 + + + + 33..22.. AAlllloowwiinngg tteellnneett ccoonnnneeccttss ffrroomm uusseerrss + + From version 1.47 there is a new (more efficient) way of doing this + (see next section) but, if you prefer, the method of doing it + described here will continue to work just fine. + + Allowing telnet connections is quite simple. Firstly you need to add a line in /etc/services to allow connections to a port number, like this .... @@ -592,14 +720,11 @@ - spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet - + spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet - - This needs to be added above the standard services such as ftp, telnet - etc. Once this is done, you need to restart inetd like this .... + Once this is done, you need to restart inetd like this .... @@ -610,12 +735,12 @@ - Now login as _s_y_s_o_p and cd spider/perl. You can test that spider is + Now login as _s_y_s_o_p and cd spider/src. You can test that spider is accepting telnet logins by issuing the following command .... - client.pl login telnet + ./client login telnet @@ -639,7 +764,99 @@ You should now get the login prompt and be able to login as before. - 33..33.. SSeettttiinngg uupp nnooddee ccoonnnneeccttss + 33..33.. SSeettttiinngg uupp tteellnneett ccoonnnneeccttss ((ffrroomm 11..4477 oonnwwaarrddss)) + + From version 1.47 you can choose to allow the perl cluster.pl program + to allow connections directly (i.e. not via the /spider/src/client + interface program). If you are using Windows then this is the only + method available of allowing incoming telnet connections. + + + To do this you need first to remove any line that you may previously + have set up in /etc/inetd.conf. Remember to:- + + + + killall -HUP inetd + + + + + + to make the change happen... + + + Having done that, you need to copy the file _/_s_p_i_d_e_r_/_p_e_r_l_/_L_i_s_t_e_n_e_r_s_._p_m + to _/_s_p_i_d_e_r_/_l_o_c_a_l and then edit it. You will need to uncomment the line + containing "0.0.0.0" and select the correct port to listen on. So that + it looks like this:- + @listen = ( + ["0.0.0.0", 8000], + ); + + + + + + As standard, the listener will listen on all interfaces + simultaneously. If you require more control than this, you can + specify each interface individually:- + + + + @listen = ( + ["gb7baa.dxcluster.net", 8000], + ["44.131.16.2", 6300], + ); + + + + + + This will only be successful if the IP addresses on each interface are + static. If you are using some kind of dynamic IP addressing then the + 'default' method is the only one that will work. + + + Restart the cluster.pl program to enable the listener. + + + One important difference with the internal listener is that no echoing + is done by the cluster program. Users will need to set 'local-echo' on + in their telnet clients if it isn't set automatically (as per the + standards). Needless to say this will probably only apply to Windows + users. + + + 33..44.. SSeettttiinngg uupp ffoorr AAGGWW EEnnggiinnee ((11..4477 oonnwwaarrddss)) + + AGW Engine is a Windows based ax25 stack. You can connect to an AGW + engine from Linux as well as Windows based machines. + + + In order to enable access to an AGW Engine you need to copy + _/_s_p_i_d_e_r_/_p_e_r_l_/_A_G_W_C_o_n_n_e_c_t_._p_m to _/_s_p_i_d_e_r_/_l_o_c_a_l and edit it. Specifically + you must:- + + + +o set $enable to 1. + + +o set $login and $passwd to the values set up in your AGW + installation. If you haven't set any there, then you should not + touch these values. + + +o You can connect to a remote AGW engine (ie on some other machine) + by changing $addr and $port appropriately. + + +o Restart the cluster.pl program + + + + + + + + 33..55.. SSeettttiinngg uupp nnooddee ccoonnnneeccttss In order to allow cluster node connections, spider needs to know that the connecting callsign is a cluster node. This is the case whether @@ -656,12 +873,10 @@ - - - set/node (AK1A type) - set/spider - set/dxnet - set/clx + set/node (AK1A type) + set/spider + set/dxnet + set/clx @@ -672,7 +887,7 @@ Start up the cluster as you did before and login as the sysop with - client.pl. The cluster node I am wanting to make a connection to is + client. The cluster node I am wanting to make a connection to is GB7BAA but you would obviously use whatever callsign you required. At the prompt type ... @@ -690,11 +905,11 @@ That is now set, it is as simple as that. To prove it, login on yet - another console as sysop and issue the command ... + another console as sysop, cd to spider/src and issue the command ... - client.pl gb7baa (using the callsign you set as a node) + ./client gb7baa (using the callsign you set as a node) @@ -704,18 +919,27 @@ - client.pl gb7baa + ./client gb7baa PC38^GB7MBC^~ - - - If the callsign you just set up as a cluster node is for an incoming connect, this is all that needs to be done. If the connection is to be outgoing then a connection script needs to be written. - 33..44.. CCoonnnneeccttiioonn ssccrriippttss + Sometimes you make a mistake... Honest, it does happen. If you want + to make a node back to being a normal user, regardless of what type it + is, do: + + + + unset/node gb7baa + + + + + + 33..66.. CCoonnnneeccttiioonn ssccrriippttss Because DXSpider operates under Linux, connections can be made using just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all @@ -729,48 +953,58 @@ - # All lines starting with a # are ignored, as are completely - blank lines. + ## All lines starting with a # are ignored, as are completely blank + lines. + + + ttiimmeeoouutt + timeout followed by a number is the number of seconds to wait + for a command to complete. If there is no timeout specified in + the script then the default is 60 seconds. + - timeout timeout followed by a number is the number of seconds to wait for a - command to complete. If there is no timeout specified in the script - then the default is 60 seconds. + aabboorrtt + abort is a regular expression containing one or more strings to + look for to abort a connection. This is a perl regular + expression and is executed ignoring case. - abort abort is a regular expression containing one or more strings to look - for to abort a connection. This is a perl regular expression and is - executed ignoring case. - connect connect followed by ax25 or telnet and some type dependent - information. In the case of a telnet connection, there can be up to - two parameters. - The first is the ip address or hostname of the computer you wish to - connect to and the second is the port number you want to use (this - can be left out if it is a normal telnet session). - In the case of an ax25 session then this would normally be a call to - ax25_call or netrom_call as in the example above. It is your - responsibility to get your node and other ax25 parameters to work - before going down this route! + ccoonnnneecctt + connect followed by ax25, agw (for Windows users) or telnet and + some type dependent information. In the case of a telnet + connection, there can be up to two parameters. The first is the + ip address or hostname of the computer you wish to connect to + and the second is the port number you want to use (this can be + left out if it is a normal telnet session). In the case of an + ax25 session then this would normally be a call to ax25_call or + netrom_call as in the example above. It is your responsibility + to get your node and other ax25 parameters to work before going + down this route! - ' line in a chat type script. The words/phrases normally come in pairs, - either can be empty. Each line reads input from the connection until - it sees the string (or perl regular expression) contained in the - left hand string. If the left hand string is empty then it doesn't - read or wait for anything. The comparison is done ignoring case. - When the left hand string has found what it is looking for (if it is) - then the right hand string is sent to the connection. - This process is repeated for every line of chat script. - client client starts the connection, put the arguments you would want here - if you were starting the client program manually. You only need this - if the script has a different name to the callsign you are trying to - connect to (i.e. you have a script called other which actually - connects to GB7DJK-1 [instead of a script called gb7djk-1]). + '' line in a chat type script. The words/phrases normally come in + pairs, either can be empty. Each line reads input from the + connection until it sees the string (or perl regular expression) + contained in the left hand string. If the left hand string is + empty then it doesn't read or wait for anything. The comparison + is done ignoring case. When the left hand string has found what + it is looking for (if it is) then the right hand string is sent + to the connection. This process is repeated for every line of + chat script. + cclliieenntt + client starts the connection, put the arguments you would want + here if you were starting the client program manually. You only + need this if the script has a different name to the callsign you + are trying to connect to (i.e. you have a script called other + which actually connects to GB7DJK-1 [instead of a script called + gb7djk-1]). - There are many possible ways to configure the script but here are two - examples, one for a NETRom/AX25 connect and one for tcp/ip. + There are many possible ways to configure the script but here are + three examples, one for a NETRom/AX25 connect, one for AGW engines and + one for tcp/ip. @@ -788,13 +1022,26 @@ + timeout 60 + abort (Busy|Sorry|Fail) + # this does exactly the same as the previous example + # the '1' is the AGW port number to connect thru for g1tlh + connect agw 1 g1tlh + # you can leave this out if you call the script 'gb7dxm' + client gb7dxm ax25 + + + + - timeout 15 - connect telnet dirkl.tobit.co.uk - # tell GB7DJK-1 that it is connected to GB7DJK - # you can leave this out if you call this script 'gb7djk' - client gb7djk telnet + + + timeout 15 + connect telnet dirkl.tobit.co.uk + # tell GB7DJK-1 that it is connected to GB7DJK + # you can leave this out if you call this script 'gb7djk' + client gb7djk telnet @@ -805,7 +1052,9 @@ directory. - 33..55.. SSttaarrttiinngg tthhee ccoonnnneeccttiioonn + + + 33..77.. SSttaarrttiinngg tthhee ccoonnnneeccttiioonn You start the connection, from within a sysop enabled cluster login, by typing in the word _c_o_n_n_e_c_t followed by a script name like this .... @@ -821,7 +1070,8 @@ This will start a connection using the script called _g_b_7_d_j_k_-_1. You can follow the connection by watching the term or console from where - you started _c_l_u_s_t_e_r_._p_l. You should see something like this ... + you started _c_l_u_s_t_e_r_._p_l. From version 1.47 onwards, you will need to + set/debug connect first. You should see something like this ... @@ -870,8 +1120,6 @@ - - In a script, this might look like ... @@ -884,7 +1132,7 @@ - 33..66.. TTeellnneett eecchhoo + 33..88.. TTeellnneett eecchhoo Cluster links in particular suffer greatly from the presence of telnet echo. This is caused by the telnet negotiation itself and can create @@ -897,7 +1145,7 @@ Telnet echo itself should only be a problem if the connection is being made to the telnet port (23). This port uses special rules that include echo negotiation. If the connection is to a different port, - such as 8000, this negotiation does not happen and therefore no echo + such as 7300, this negotiation does not happen and therefore no echo should be present. @@ -958,6 +1206,29 @@ + This line works fine for RedHat distributions. It is also fine for + SuSE up to 7.0. From Suse 7.1 you need to add runlevels 2 and 5 like + this ... + + + + DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 + + + + + + The line required for Slackware distributions is slightly different. + My thanks to Aurelio, PA3EZL for this information. + + + + DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7 + + + + + This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart it should it crash for any reason. @@ -978,12 +1249,14 @@ - # check every 10 minutes to see if gb7xxx is connected and if not - # start a connect job going - 0,10,20,30,40,50 * * * * start_connect('gb7xxx') if !connected('gb7xxx') + # check every 10 minutes to see if gb7xxx is connected and if not + # start a connect job going + + 0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx') + @@ -1035,15 +1308,6 @@ - - - - - - - - - @@ -1833,9 +2097,384 @@ load/badwords. - 99.. IInnffoorrmmaattiioonn,, ffiilleess aanndd uusseeffuull pprrooggrraammss + 99.. MMaaiill + + DXSpider deals seamlessly with standard AK1A type mail. It supports + both personal and bulletin mail and the sysop has additional commands + to ensure that mail gets to where it is meant. DXSpider will send + mail almost immediately, assuming that the target is on line. + However, only one mail message is dealt with at any one time. If a + mail message is already being sent or recieved, then the new message + will be queued until it has finished. + + The cluster mail is automatically deleted after 30 days unless the + sysop sets the "keep" flag using the _m_s_g command. + + 99..11.. PPeerrssoonnaall mmaaiill + + Personal mail is sent using the _s_p command. This is actually the + default method of sending mail and so a simple _s for send will do. A + full list of the send commands and options is in the _c_o_m_m_a_n_d _s_e_t + section, so I will not duplicate them here. + - 99..11.. MMOOTTDD + 99..22.. BBuulllleettiinn mmaaiill + + Bulletin mail is sent by using the _s_b command. This is one of the + most common mistakes users make when sending mail. They send a + bulletin mail with _s or _s_p instead of _s_b and of course the message + never leaves the cluster. This can be rectified by the sysop by using + the _m_s_g command. + + + Bulletin addresses can be set using the Forward.pl file. + + + 99..33.. FFoorrwwaarrdd..ppll + + DXSpider receives all and any mail sent to it without any alterations + needed in files. Because personal and bulletin mail are treated + differently, there is no need for a list of accepted bulletin + addresses. It is necessary, however, to tell the program which links + accept which bulletins. For example, it is pointless sending + bulletins addresses to "UK" to any links other than UK ones. The file + that does this is called forward.pl and lives in /spider/msg. At + default, like other spider files it is named forward.pl.issue. Rename + it to forward.pl and edit the file to match your requirements. The + format is below ... + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + # + # this is an example message forwarding file for the system + # + # The format of each line is as follows + # + # type to/from/at pattern action destinations + # P/B/F T/F/A regex I/F [ call [, call ...] ] + # + # type: P - private, B - bulletin (msg), F - file (ak1a bull) + # to/from/at: T - to field, F - from field, A - home bbs, O - origin + # pattern: a perl regex on the field requested + # action: I - ignore, F - forward + # destinations: a reference to an array containing node callsigns + # + # if it is non-private and isn't in here then it won't get forwarded + # + # Currently only type B msgs are affected by this code. + # + # The list is read from the top down, the first pattern that matches + # causes the action to be taken. + # + # The pattern can be undef or 0 in which case it will always be selected + # for the action specified + # + # If the BBS list is undef or 0 and the action is 'F' (and it matches the + # pattern) then it will always be forwarded to every node that doesn't have + # it (I strongly recommend you don't use this unless you REALLY mean it, if + # you allow a new link with this on EVERY bull will be forwarded immediately + # on first connection) + # + + package DXMsg; + + @forward = ( + ); + + + + + Simply insert a bulletin address and state in the brackets where you + wish that mail to go. For example, you can see here that mail sent to + "UK" will only be sent to the UK links and not to PA4AB-14. + + + To force the cluster to reread the file use load/forward + + + + 99..44.. TThhee mmssgg ccoommmmaanndd + + The _m_s_g command is a very powerful and flexible tool for the sysop. + It allows the sysop to alter to and from fields and make other changes + to manage the cluster mail. + + Here is a full list of the various options ... + + + + + + + + + + + + MSG TO - change TO callsign to + MSG FRom - change FROM callsign to + MSG PRrivate - set private flag + MSG NOPRrivate - unset private flag + MSG RR - set RR flag + MSG NORR - unset RR flag + MSG KEep - set the keep flag (message won't be deleted ever) + MSG NOKEep - unset the keep flag + MSG SUbject - change the subject to + MSG WAittime - remove any waiting time for this message + MSG NOREad - mark message as unread + MSG REad - mark message as read + MSG QUeue - queue any outstanding bulletins + MSG QUeue 1 - queue any outstanding private messages + + + + + These commands are simply typed from within the cluster as the sysop + user. + + + 99..55.. MMeessssaaggee ssttaattuuss + + You can check on a message from within the cluster by using the + command _s_t_a_t_/_m_s_g. This will give you additional information on the + message number including which nodes have received it, which node it + was received from and when etc. Here is an example of the output of + the command ... + + + + G0VGS de GB7MBC 28-Jan-2001 1308Z > + stat/msg 6869 + From: GB7DJK + Msg Time: 26-Jan-2001 1302Z + Msgno: 6869 + Origin: GB7DJK + Size: 8012 + Subject: AMSAT 2line KEPS 01025.AMSAT + To: UK + Got it Nodes: GB7BAA, GB7ADX + Private: 0 + Read Confirm: 0 + Times read: 0 + G0VGS de GB7MBC 28-Jan-2001 1308Z > + + + + + + 99..66.. FFiilltteerriinngg mmaaiill + + This is described in the section on _O_t_h_e_r _f_i_l_t_e_r_s so I will not + duplicate it here. + + + 99..77.. DDiissttrriibbuuttiioonn lliissttss + + Distribution lists are simply a list of users to send certain types of + mail to. An example of this is mail you only wish to send to other + sysops. In /spider/msg there is a directory called _d_i_s_t_r_o. You put + any distibution lists in here. For example, here is a file called + SYSOP.pl that caters for the UK sysops. + + + qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX + GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH + GB7DXK GB7DXI GB7DXS) + + + + + Any mail sent to "sysop" would only be sent to the callsigns in this + list. + + + 99..88.. BBBBSS iinntteerrffaaccee + + Spider provides a simple BBS interface. No input is required from the + sysop of the cluster at all. The BBS simply sets the cluster as a BBS + and pushes any required mail to the cluster. No mail can flow from + Spider to the BBS, the interface is one-way. + + + Please be careful not to flood the cluster network with unnecessary + mail. Make sure you only send mail to the clusters that want it by + using the Forward.pl file very carefully. + + + 1100.. DDaattaabbaasseess + + Spider allows the creation of local or remote databases. It supports + chained databases, allowing several different databases to be scanned + with one simple command. Importing of databases is limited at present + to the standard AK1A databases such as OBLAST and the DB0SDX QSL + database but will expand with time. + + + 1100..11.. CCrreeaattiinngg ddaattaabbaasseess + + Creating a database could not be more simple. All the commands are + sent from the cluster prompt as the _s_y_s_o_p user. + + To create a database you use the command _d_b_c_r_e_a_t_e. It can be used in + 3 different ways like so .. + + + + dbcreate + + + + + To simply create a database locally, you just tell the command the + name of the database. This does not create the actual database, it + simply defines it to say that it exists. + + + + dbcreate chain [...] + + + + + This creates a chained database entry. The first database will be + scanned, then the second, the third etc... + + + + dbcreate remote + + This creates a remote entry. the first name field is the database + name at the remote node, then the remote switch, then the actual + node_call of the remote node, for example... + + + + dbcreate buckmaster remote gb7dxc + + + + + Remote databases cannot be chained, however, the last database in a + chain can be a remote database. + + + 1100..22.. IImmppoorrttiinngg ddaattaabbaasseess + + The only databases that Spider can currently import are the standard + AK1A databases such as OBLAST or the DB0SDX qsl and address database. + This will be added to with time. + + To import such a database, first put the file somewhere useful like + /tmp and then issue the following command ... + + + + dbimport oblast /tmp/OBLAST.FUL + + + + + This will update the existing local oblast database or create it if it + does not exist. + + + 1100..33.. CChheecckkiinngg aavvaaiillaabbllee ddaattaabbaasseess + + Once a database is created, you will want to check that it has been + added. To do this use the _d_b_a_v_a_i_l command. This will output the + available databases. For example ... + + + + dbavail + DB Name Location Chain + qsl Local + buck GB7ADX + hftest GB7DXM + G0VGS de GB7MBC 3-Feb-2001 1925Z > + + + + + + 1100..44.. LLooookkiinngg uupp ddaattaabbaasseess + + To look for information in a defined database, simply use the _d_b_s_h_o_w + command, for example ... + + + + dbshow buckmaster G0YLM + + + + + will show the information for the callsign G0YLM from the buckmaster + database if it exists. To make things more standard for the users you + can add an entry in the Aliases file so that it looks like a standard + _s_h_o_w command like this ... + + + + + + + + Now you can simply use show/buckmaster or an abreviation. + + + 1100..55.. RReemmoovviinngg ddaattaabbaasseess + + To delete an existing database you use the _d_b_r_e_m_o_v_e command. For + example ... + + + + dbremove oblast + + + + + would remove the oblast database and its associated datafile from the + system. There are no warnings or recovery possible from this command. + If you remove a database it ceases to exist and would have to be + created from scratch if you still required it. + + + 1111.. IInnffoorrmmaattiioonn,, ffiilleess aanndd uusseeffuull pprrooggrraammss + + 1111..11.. MMOOTTDD One of the more important things a cluster sysop needs to do is to get information to his users. The simplest way to do this is to have a @@ -1846,7 +2485,7 @@ to the cluster. - 99..22.. DDoowwnnttiimmee mmeessssaaggee + 1111..22.. DDoowwnnttiimmee mmeessssaaggee If for any reason the cluster is down, maybe for upgrade or maintenance but the machine is still running, a message can be sent to @@ -1857,7 +2496,7 @@ actually running. - 99..33.. OOtthheerr tteexxtt mmeessssaaggeess + 1111..33.. OOtthheerr tteexxtt mmeessssaaggeess You can set other text messages to be read by the user if they input the file name. This could be for news items or maybe information for @@ -1867,7 +2506,6 @@ like. These can be listed by the user with the command .... - show/files @@ -1890,14 +2528,14 @@ directly or nested under directories. One use for this would be to store DX bulletins such as the OPDX bulletins. These can be listed and read by the user. To keep things tidy, make a directory under - /spider/packclus called _b_u_l_l_e_t_i_n_s. Now copy any OPDX or similar + /spider/packclus called _b_u_l_l_e_t_i_n. Now copy any OPDX or similar bulletins into it. These can be listed by the user in the same way as - above using the _s_h_o_w_/_f_i_l_e_s command with an extension for the bulletins + above using the _s_h_o_w_/_f_i_l_e_s command with an extension for the bulletin directory you have just created, like this .... - show/files bulletins + show/files bulletin @@ -1908,12 +2546,13 @@ sh/files - bulletins DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z + bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z + You can see that in the files area (basically the packclus directory) - there is a file called _n_e_w_s and a directory called _b_u_l_l_e_t_i_n_s. You can + there is a file called _n_e_w_s and a directory called _b_u_l_l_e_t_i_n. You can also see that dates they were created. In the case of the file _n_e_w_s, you can also see the time it was last modified, a good clue as to whether the file has been updated since you last read it. To read the @@ -1926,25 +2565,28 @@ - To look what is in the bulletins directory you issue the command .... + To look what is in the bulletin directory you issue the command .... - show/files bulletins - opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z - opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z - opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z - opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z - opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z - opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z - opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z - opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z - opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z - opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z - opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z - opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z - opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z - Press Enter to continue, A to abort (16 lines) > + + + + show/files bulletin + opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z + opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z + opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z + opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z + opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z + opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z + opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z + opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z + opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z + opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z + opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z + opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z + opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z + Press Enter to continue, A to abort (16 lines) > @@ -1954,7 +2596,7 @@ - type bulletins/opdx391 + type bulletin/opdx391 Ohio/Penn DX Bulletin No. 391 The Ohio/Penn Dx PacketCluster DX Bulletin No. 391 @@ -1974,7 +2616,7 @@ The page length will of course depend on what you have it set to! - 99..44.. TThhee AAlliiaasseess ffiillee + 1111..44.. TThhee AAlliiaasseess ffiillee You will find a file in /spider/cmd/ called Aliases. First, copy this file to /spider/local_cmd/Aliases and edit this file. You will see @@ -1996,54 +2638,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - #!/usr/bin/perl # provide some standard aliases for commands for terminally @@ -2186,102 +2780,74 @@ the results once you have set an alias. - 99..55.. FFoorrwwaarrdd..ppll + 1111..55.. CCoonnssoollee..ppll - DXSpider receives all and any mail sent to it without any alterations - needed in files. Because personal and bulletin mail are treated - differently, there is no need for a list of accepted bulletin - addresses. It is necessary, however, to tell the program which links - accept which bulletins. For example, it is pointless sending - bulletins addresses to "UK" to any links other than UK ones. The file - that does this is called forward.pl and lives in /spider/msg. At - default, like other spider files it is named forward.pl.issue. Rename - it to forward.pl and edit the file to match your requirements. The - format is below ... + In later versions of Spider a simple console program is provided for + the sysop. This has a type ahead buffer with line editing facilities + and colour for spots, announces etc. To use this program, simply use + console.pl instead of client. + To edit the colours, copy /spider/perl/Console.pl to /spider/local and + edit the file with your favourite editor. - # - # this is an example message forwarding file for the system - # - # The format of each line is as follows - # - # type to/from/at pattern action destinations - # P/B/F T/F/A regex I/F [ call [, call ...] ] - # - # type: P - private, B - bulletin (msg), F - file (ak1a bull) - # to/from/at: T - to field, F - from field, A - home bbs, O - origin - # pattern: a perl regex on the field requested - # action: I - ignore, F - forward - # destinations: a reference to an array containing node callsigns - # - # if it is non-private and isn't in here then it won't get forwarded - # - # Currently only type B msgs are affected by this code. - # - # The list is read from the top down, the first pattern that matches - # causes the action to be taken. - # - # The pattern can be undef or 0 in which case it will always be selected - # for the action specified - # - # If the BBS list is undef or 0 and the action is 'F' (and it matches the - # pattern) then it will always be forwarded to every node that doesn't have - # it (I strongly recommend you don't use this unless you REALLY mean it, if - # you allow a new link with this on EVERY bull will be forwarded immediately - # on first connection) - # - package DXMsg; + 1111..66.. UUppddaattiinngg kkeepplleerr ddaattaa - @forward = ( - ); + Spider has a powerful and flexible show/satellite command. In order + for this to be accurate, the kepler data has to be updated regularly. + In general, this data is available as an email or via cluster mail. + Updating it is simple. First you need to export the mail message as a + file. You do this with the _e_x_p_o_r_t command from the cluster prompt as + the sysop. For example ... + export 5467 /spider/perl/keps.in - Simply insert a bulletin address and state in the brackets where you - wish that mail to go. For example, you can see here that mail sent to - "UK" will only be sent to the UK links and not to PA4AB-14. - To force the cluster to reread the file use load/forward + would export message number 5467 as a file called keps.in in the + /spider/perl directory. - 99..66.. DDiissttrriibbuuttiioonn lliissttss + Now login to a VT as sysop and cd /spider/perl. There is a command in + the perl directory called _c_o_n_v_k_e_p_s_._p_l. All we need to do now is + convert the file like so ... + + + + ./convkeps.pl keps.in - Distribution lists are simply a list of users to send certain types of - mail to. An example of this is mail you only wish to send to other - sysops. In /spider/msg there is a directory called _d_i_s_t_r_o. You put - any distibution lists in here. For example, here is a file called - SYSOP.pl that caters for the UK sysops. - qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX - GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH - GB7DXK GB7DXI GB7DXS) + Now go back to the cluster and issue the command ... + load/keps - Any mail sent to "sysop" would only be sent to the callsigns in this - list. - 99..77.. CCoonnssoollee..ppll - In later versions of Spider a simple console program is provided for - the sysop. This has a type ahead buffer with line editing facilities - and colour for spots, announces etc. To use this program, simply use - console.pl instead of client.pl. + That is it! the kepler data has been updated. - To edit the colours, copy /spider/perl/Console.pl to /spider/local and - edit the file with your favourite editor. - 1100.. CCVVSS + 1111..77.. TThhee QQRRZZ ccaallllbbooookk + + The command _s_h_/_q_r_z will only work once you have followed a few simple + steps. First you need to get a user ID and password from qrz.com. + Simply go to the site and create one. Secondly you need to copy the + file /spider/perl/Internet.pm to /spider/local and alter it to match + your user ID and password. You also at this point need to set + $allow=1 to complete the setup. Many thanks to Fred Lloyd, the + proprieter of qrz.com for allowing this access. + + + 1122.. CCVVSS CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held at Sourceforge. This means that it is possible to update your @@ -2307,7 +2873,6 @@ ENTIRE SPIDER TREE!! - Assuming you are connected to the Internet, you need to login to the CVS repository and then update your Spider source. There are several steps which are listed below ... @@ -2328,10 +2893,13 @@ What happens next depends on whether you have an existing installation that you want to update with the latest and greatest or whether you just want to see what is there and/or run it on a new machine for - testing. Either way you will want to change directory to a new place, - if you want to update an existing installation then I suggest /tmp, - otherwise choose a suitable place according to the normal installation - instructions. + testing. + + If you are installing Spider from CVS then change directory to + /home/sysop + + If you are wanting to update Spider then cd to /tmp + The next step will create a brand new 'spider' directory in your @@ -2377,7 +2945,7 @@ Remember to recompile the C client (cd /spider/src; make) - At this point the files have been upgraded. You can (usually) restrt + At this point the files have been upgraded. You can (usually) restart the cluster in your own time. However, if you attempt to use any new commands or features expect it to be fatal! At least your cluster will have been restarted then so it will be too late to worry about @@ -2400,11 +2968,10 @@ any of the perl scripts have been altered or added, again, CVS will tell you. - You will find any changes documented in the /spider/Changes file. - 1111.. TThhee DDXXSSppiiddeerr ccoommmmaanndd sseett + 1133.. TThhee DDXXSSppiiddeerr ccoommmmaanndd sseett Below is a complete list of commands available from the cluster prompt. Most maintenance tasks are automatic but there are some @@ -2413,7 +2980,7 @@ is the permissions level needed to use the command. - 1111..11.. aacccceepptt//aannnnoouunnccee ((00)) + 1133..11.. aacccceepptt//aannnnoouunnccee ((00)) aacccceepptt//aannnnoouunnccee [[00--99]] <> Set an accept filter line for announce @@ -2429,29 +2996,18 @@ - - - - - - - - - - - - info eg: iota or qsl - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - wx 1 filter WX announces - dest eg: 6MUK,WDX (distros) + info eg: iota or qsl + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu + origin_zone + by_dxcc + by_itu + by_zone + channel + wx 1 filter WX announces + dest eg: 6MUK,WDX (distros) @@ -2478,9 +3034,6 @@ This filter would only allow announces that were posted buy UK stations. You can use the tag 'all' to accept everything eg: - - - acc/ann all @@ -2489,7 +3042,7 @@ but this probably for advanced users... - 1111..22.. aacccceepptt//aannnnoouunnccee ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 1133..22.. aacccceepptt//aannnnoouunnccee ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) aacccceepptt//aannnnoouunnccee <> [[iinnppuutt]] [[00--99]]<> Announce filter sysop version @@ -2506,7 +3059,9 @@ - 1111..33.. aacccceepptt//ssppoottss ((00)) + + + 1133..33.. aacccceepptt//ssppoottss ((00)) aacccceepptt//aannnnoouunnccee [[00--99]] <> Set an accept filter line for spots @@ -2545,7 +3100,6 @@ thus: hf/ssb. You can also just have a simple range like: 0/30000 - this is more efficient than saying simply: freq HF (but don't get too hung up about that) - some examples:- @@ -2568,10 +3122,11 @@ but this probably for advanced users... - 1111..44.. aacccceepptt//ssppoottss ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 1133..44.. aacccceepptt//ssppoottss ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) aacccceepptt//ssppoottss <> [[iinnppuutt]] [[00--99]] <> Spot filter sysop version + This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:- @@ -2587,7 +3142,7 @@ - 1111..55.. aacccceepptt//wwccyy ((00)) + 1133..55.. aacccceepptt//wwccyy ((00)) aacccceepptt//wwccyy [[00--99]] <> set an accept WCY filter @@ -2620,7 +3175,7 @@ See HELP FILTER for information. - 1111..66.. aacccceepptt//wwccyy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 1133..66.. aacccceepptt//wwccyy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) aacccceepptt//wwccyy <> [[iinnppuutt]] [[00--99]] <> WCY filter sysop version @@ -2637,8 +3192,7 @@ - - 1111..77.. aacccceepptt//wwwwvv ((00)) + 1133..77.. aacccceepptt//wwwwvv ((00)) aacccceepptt//wwwwvv [[00--99]] <> Set an accept WWV filter @@ -2676,7 +3230,9 @@ See HELP FILTER for information. - 1111..88.. aacccceepptt//wwwwvv ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + + + 1133..88.. aacccceepptt//wwwwvv ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) aacccceepptt//wwwwvv <> [[iinnppuutt]] [[00--99]] <> WWV filter sysop version @@ -2696,7 +3252,7 @@ - 1111..99.. aannnnoouunnccee ((00)) + 1133..99.. aannnnoouunnccee ((00)) aannnnoouunnccee <> Send an announcement to local users @@ -2704,7 +3260,8 @@ Send an announcement to LOCAL users only, where is the text of the announcement you wish to broadcast - 1111..1100.. aannnnoouunnccee ffuullll ((00)) + + 1133..1100.. aannnnoouunnccee ffuullll ((00)) aannnnoouunnccee ffuullll <> Send an announcement cluster wide @@ -2714,7 +3271,7 @@ - 1111..1111.. aannnnoouunnccee ssyyssoopp ((55)) + 1133..1111.. aannnnoouunnccee ssyyssoopp ((55)) aannnnoouunnccee ssyyssoopp <> @@ -2722,7 +3279,7 @@ Send an announcement to Sysops only - 1111..1122.. aapprrooppooss ((00)) + 1133..1122.. aapprrooppooss ((00)) aapprrooppooss <> Search the help database @@ -2731,7 +3288,7 @@ print the names of all the commands that may be relevant. - 1111..1133.. bbyyee ((00)) + 1133..1133.. bbyyee ((00)) bbyyee Exit from the cluster @@ -2739,7 +3296,9 @@ This will disconnect you from the cluster - 1111..1144.. ccaattcchhuupp ((55)) + + + 1133..1144.. ccaattcchhuupp ((55)) ccaattcchhuupp <> AAllll||[[<> ......]] Mark a message as sent @@ -2769,13 +3328,12 @@ - which will arrange for them to be forward candidates again. Order is not important. - 1111..1155.. cclleeaarr//ssppoottss ((00)) + 1133..1155.. cclleeaarr//ssppoottss ((00)) cclleeaarr//ssppoottss [[11||aallll]] Clear a spot filter line @@ -2806,7 +3364,7 @@ - acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) + acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) @@ -2824,7 +3382,7 @@ - 1111..1166.. ccoonnnneecctt ((55)) + 1133..1166.. ccoonnnneecctt ((55)) ccoonnnneecctt <> Start a connection to another DX Cluster @@ -2836,7 +3394,7 @@ cluster . - 1111..1177.. ddbbaavvaaiill ((00)) + 1133..1177.. ddbbaavvaaiill ((00)) ddbbaavvaaiill Show a list of all the databases in the system @@ -2845,7 +3403,7 @@ defined in the system. It is also aliased to SHOW/COMMAND. - 1111..1188.. ddbbccrreeaattee ((99)) + 1133..1188.. ddbbccrreeaattee ((99)) ddbbccrreeaattee <> Create a database entry ddbbccrreeaattee <> cchhaaiinn <> [[<>....]] Create a chained database @@ -2872,7 +3430,6 @@ No checking is done to see if the any of the chained databases exist, in fact it is usually better to do the above statement first then do each of the chained databases. - Databases can exist offsite. To define a database that lives on another node do: @@ -2902,6 +3459,8 @@ ], + + to allow SH/BUCK g1tlh @@ -2912,7 +3471,7 @@ databases. See DBSHOW for generic database enquiry - 1111..1199.. ddbbiimmppoorrtt ((99)) + 1133..1199.. ddbbiimmppoorrtt ((99)) ddbbiimmppoorrtt <> Import AK1A data into a database @@ -2927,7 +3486,7 @@ oblast database held locally. - 1111..2200.. ddbbrreemmoovvee ((99)) + 1133..2200.. ddbbrreemmoovvee ((99)) ddbbrreemmoovvee <> Delete a database @@ -2951,7 +3510,7 @@ You have been warned. - 1111..2211.. ddbbsshhooww ((00)) + 1133..2211.. ddbbsshhooww ((00)) ddbbsshhooww <> <> Display an entry, if it exists, in a database @@ -2980,7 +3539,7 @@ - 1111..2222.. ddeebbuugg ((99)) + 1133..2222.. ddeebbuugg ((99)) ddeebbuugg Set the cluster program into debug mode @@ -2999,7 +3558,7 @@ finished. - 1111..2233.. ddiirreeccttoorryy ((00)) + 1133..2233.. ddiirreeccttoorryy ((00)) ddiirreeccttoorryy List messages ddiirreeccttoorryy oowwnn List your own messages @@ -3034,6 +3593,7 @@ syntax:- + DIR/T G1* 10 DIR/S QSL 10-100 5 @@ -3042,13 +3602,13 @@ - 1111..2244.. ddiirreeccttoorryy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) + 1133..2244.. ddiirreeccttoorryy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) Works just like the user command except that sysops can see ALL messages. - 1111..2255.. ddiissccoonnnneecctt ((88)) + 1133..2255.. ddiissccoonnnneecctt ((88)) ddiissccoonnnneecctt <> [[<> ......]] Disconnect a user or node @@ -3056,7 +3616,7 @@ Disconnect any connected locally - 1111..2266.. ddxx ((00)) + 1133..2266.. ddxx ((00)) ddxx [[bbyy <>]] <> <> <> Send a DX spot @@ -3066,9 +3626,11 @@ - DX FR0G 144.600 - DX 144.600 FR0G - DX 144600 FR0G + + + DX FR0G 144.600 + DX 144.600 FR0G + DX 144600 FR0G @@ -3096,10 +3658,11 @@ cluster. See SHOW/BANDS for more information. - 1111..2277.. eexxppoorrtt ((99)) + 1133..2277.. eexxppoorrtt ((99)) eexxppoorrtt <> <> Export a message to a file + Export a message to a file. This command can only be executed on a local console with a fully privileged user. The file produced will be in a form ready to be imported back into the cluster by placing it in @@ -3113,7 +3676,7 @@ EXPORT 2345 /tmp/a - 1111..2288.. eexxppoorrtt__uusseerrss ((99)) + 1133..2288.. eexxppoorrtt__uusseerrss ((99)) eexxppoorrtt__uusseerrss [[<>]] Export the users database to ascii @@ -3129,7 +3692,9 @@ check is made on the filename (if any) that you specify. - 1111..2299.. ffoorrwwaarrdd//llaattlloonngg ((88)) + + + 1133..2299.. ffoorrwwaarrdd//llaattlloonngg ((88)) ffoorrwwaarrdd//llaattlloonngg <> Send latitude and longitude information to another cluster @@ -3143,7 +3708,7 @@ so it is not recommended on slow links. - 1111..3300.. ffoorrwwaarrdd//ooppeerrnnaammee ((11)) + 1133..3300.. ffoorrwwaarrdd//ooppeerrnnaammee ((11)) ffoorrwwaarrdd//ooppeerrnnaammee <> Send out information on this to all clusters @@ -3155,7 +3720,7 @@ available. - 1111..3311.. hheellpp ((00)) + 1133..3311.. hheellpp ((00)) hheellpp <> Get help on a command @@ -3166,7 +3731,9 @@ Look at the APROPOS command which will search the help database for the you specify and give you a list of likely commands to look at with HELP. - 1111..3322.. iinniitt ((55)) + + + 1133..3322.. iinniitt ((55)) iinniitt <> Re-initialise a link to an AK1A compatible node @@ -3180,7 +3747,7 @@ Best of luck - you will need it. - 1111..3333.. kkiillll ((00)) + 1133..3333.. kkiillll ((00)) kkiillll <> [[<> ....]] Delete a message from the local system @@ -3190,7 +3757,10 @@ the sysop). - 1111..3344.. kkiillll ((55)) + + + + 1133..3344.. kkiillll ((55)) kkiillll <> [[<> ......]] Remove or erase a message from the system kkiillll ffrroomm <> Remove all messages from a callsign @@ -3203,8 +3773,10 @@ As a sysop you can kill any message on the system. - 1111..3355.. kkiillll ffuullll <> [[<>]] DDeelleettee aa mmeessssaaggee ffrroomm tthhee wwhhoollee - cclluusstteerr kkiillll ffuullll ((55)) + 1133..3355.. kkiillll ffuullll ((55)) + + kkiillll ffuullll <> [[<>]] Delete a message from the whole cluster + Delete a message (usually a 'bulletin') from the whole cluster system. @@ -3212,7 +3784,7 @@ same subject will be deleted. Beware! - 1111..3366.. lliinnkkss ((00)) + 1133..3366.. lliinnkkss ((00)) lliinnkkss Show which nodes are physically connected @@ -3222,7 +3794,7 @@ - 1111..3377.. llooaadd//aalliiaasseess ((99)) + 1133..3377.. llooaadd//aalliiaasseess ((99)) llooaadd//aalliiaasseess Reload the command alias table @@ -3232,14 +3804,18 @@ running in order for the changes to take effect. - 1111..3388.. llooaadd//bbaaddddxx RReellooaadd tthhee bbaadd DDXX ttaabbllee llooaadd//bbaaddddxx ((99)) + + 1133..3388.. llooaadd//bbaaddddxx ((99)) + + llooaadd//bbaaddddxx Reload the bad DX table + Reload the /spider/data/baddx.pl file if you have changed it manually whilst the cluster is running. This table contains the DX Calls that, if spotted, will not be passed on. FR0G and TEST are classic examples. - 1111..3399.. llooaadd//bbaaddmmssgg ((99)) + 1133..3399.. llooaadd//bbaaddmmssgg ((99)) llooaadd//bbaaddmmssgg Reload the bad message table @@ -3250,8 +3826,7 @@ each message. If any of them match then that message is immediately deleted on receipt. - - 1111..4400.. llooaadd//bbaaddwwoorrddss ((99)) + 1133..4400.. llooaadd//bbaaddwwoorrddss ((99)) llooaadd//bbaaddwwoorrddss Reload the badwords file @@ -3265,7 +3840,7 @@ ignored. - 1111..4411.. llooaadd//bbaannddss ((99)) + 1133..4411.. llooaadd//bbaannddss ((99)) llooaadd//bbaannddss Reload the band limits table @@ -3274,7 +3849,7 @@ whilst the cluster is running. - 1111..4422.. llooaadd//ccmmdd__ccaacchhee ((99)) + 1133..4422.. llooaadd//ccmmdd__ccaacchhee ((99)) llooaadd//ccmmdd__ccaacchhee Reload the automatic command cache @@ -3287,7 +3862,7 @@ was just after a cluster restart. - 1111..4433.. llooaadd//ffoorrwwaarrdd ((99)) + 1133..4433.. llooaadd//ffoorrwwaarrdd ((99)) llooaadd//ffoorrwwaarrdd Reload the msg forwarding routing table @@ -3295,10 +3870,7 @@ whilst the cluster is running. - - - - 1111..4444.. llooaadd//mmeessssaaggeess ((99)) + 1133..4444.. llooaadd//mmeessssaaggeess ((99)) llooaadd//mmeessssaaggeess Reload the system messages file @@ -3311,7 +3883,7 @@ unknown message 'xxxx' in lang 'en' - 1111..4455.. llooaadd//pprreeffiixxeess ((99)) + 1133..4455.. llooaadd//pprreeffiixxeess ((99)) llooaadd//pprreeffiixxeess Reload the prefix table @@ -3320,7 +3892,7 @@ manually whilst the cluster is running. - 1111..4466.. mmeerrggee ((55)) + 1133..4466.. mmeerrggee ((55)) mmeerrggee <> [[<>//<>]] Ask for the latest spots and WWV @@ -3335,7 +3907,7 @@ data). - 1111..4477.. mmssgg ((99)) + 1133..4477.. mmssgg ((99)) mmssgg <> <> [[ddaattaa ......]] Alter various message parameters @@ -3371,7 +3943,7 @@ This will display more information on the message than DIR does. - 1111..4488.. ppcc ((88)) + 1133..4488.. ppcc ((88)) ppcc <> <> Send text (eg PC Protocol) to @@ -3386,11 +3958,10 @@ You can also use in the same way as a talk command to a connected user but without any processing, added of "from to " or whatever. - pc G1TLH Try doing that properly!!! - 1111..4499.. ppiinngg ((11)) + 1133..4499.. ppiinngg ((11)) ppiinngg <> Check the link quality between nodes @@ -3403,7 +3974,7 @@ - 1111..5500.. rrccmmdd ((11)) + 1133..5500.. rrccmmdd ((11)) rrccmmdd <> <> Send a command to another DX cluster @@ -3417,7 +3988,7 @@ whether you have permission to send this command at all. - 1111..5511.. rreeaadd ((00)) + 1133..5511.. rreeaadd ((00)) rreeaadd Read the next unread personal message addressed to you rreeaadd <> Read the specified message @@ -3428,9 +3999,7 @@ - - - 1111..5522.. rreeaadd ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) + 1133..5522.. rreeaadd ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) rreeaadd <> Read a message on the system @@ -3438,7 +4007,7 @@ As a sysop you may read any message on the system - 1111..5533.. rreejjeecctt//aannnnoouunnccee + 1133..5533.. rreejjeecctt//aannnnoouunnccee rreejjeecctt//aannnnoouunnccee [[00--99]] <> Set a reject filter for announce @@ -3454,18 +4023,19 @@ - info eg: iota or qsl - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - wx 1 filter WX announces - dest eg: 6MUK,WDX (distros) + + info eg: iota or qsl + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu + origin_zone + by_dxcc + by_itu + by_zone + channel + wx 1 filter WX announces + dest eg: 6MUK,WDX (distros) @@ -3491,11 +4061,12 @@ but this probably for advanced users... - 1111..5544.. rreejjeecctt//aannnnoouunnccee ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 1133..5544.. rreejjeecctt//aannnnoouunnccee ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) rreejjeecctt//aannnnoouunnccee <> [[iinnppuutt]] [[00--99]] <> Announce filter sysop version + This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:- @@ -3509,7 +4080,7 @@ - 1111..5555.. rreejjeecctt//ssppoottss ((00)) + 1133..5555.. rreejjeecctt//ssppoottss ((00)) rreejjeecctt//ssppoottss [[00--99]] <> Set a reject filter line for spots @@ -3562,7 +4133,7 @@ - rej/spot 3 all + rej/spot 3 all @@ -3570,7 +4141,7 @@ but this probably for advanced users... - 1111..5566.. rreejjeecctt//ssppoottss ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 1133..5566.. rreejjeecctt//ssppoottss ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) rreejjeecctt//ssppoottss <> [[iinnppuutt]] [[00--99]] <> Reject spot filter sysop version @@ -3581,17 +4152,21 @@ - reject/spot db0sue-7 1 by_zone 14,15,16 - reject/spot node_default all - set/hops node_default 10 - reject/spot user_default by G,M,2 + reject/spot db0sue-7 1 by_zone 14,15,16 + reject/spot node_default all + set/hops node_default 10 + + reject/spot user_default by G,M,2 + + - 1111..5577.. rreejjeecctt//wwccyy ((00)) + + 1133..5577.. rreejjeecctt//wwccyy ((00)) rreejjeecctt//wwccyy [[00--99]] <> Set a reject WCY filter @@ -3623,18 +4198,19 @@ See HELP FILTER for information. - 1111..5588.. rreejjeecctt//wwccyy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 1133..5588.. rreejjeecctt//wwccyy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) rreejjeecctt//wwccyy <> [[iinnppuutt]] [[00--99]] <> WCY reject filter sysop version + This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:- reject/wcy gb7djk all - 1111..5599.. rreejjeecctt//wwwwvv ((00)) + 1133..5599.. rreejjeecctt//wwwwvv ((00)) rreejjeecctt//wwwwvv [[00--99]] <> Set a reject WWV filter @@ -3644,15 +4220,17 @@ - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel + + + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu + origin_zone + by_dxcc + by_itu + by_zone + channel @@ -3672,7 +4250,7 @@ See HELP FILTER for information. - 1111..6600.. rreejjeecctt//wwwwvv ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 1133..6600.. rreejjeecctt//wwwwvv ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) rreejjeecctt//wwwwvv <> [[iinnppuutt]] [[00--99]] <> WWV reject filter sysop version @@ -3692,9 +4270,7 @@ - - - 1111..6611.. rreeppllyy ((00)) + 1133..6611.. rreeppllyy ((00)) rreeppllyy Reply (privately) to the last message that you have read rreeppllyy <> Reply (privately) to the specified message @@ -3711,7 +4287,8 @@ further details) - 1111..6622.. sseenndd ((00)) + + 1133..6622.. sseenndd ((00)) sseenndd <> [[<> ......]] Send a message to one or more callsigns sseenndd RRRR <> Send a message and ask for a read receipt @@ -3745,7 +4322,7 @@ is an alias for SEND PRIVATE - 1111..6633.. sseett//aaddddrreessss ((00)) + 1133..6633.. sseett//aaddddrreessss ((00)) sseett//aaddddrreessss <> Record your postal address @@ -3753,14 +4330,15 @@ Literally, record your address details on the cluster. - 1111..6644.. sseett//aannnnoouunnccee ((00)) + 1133..6644.. sseett//aannnnoouunnccee ((00)) sseett//aannnnoouunnccee Allow announce messages Allow announce messages to arrive at your terminal. - 1111..6655.. sseett//aarrcclluusstteerr ((55)) + + 1133..6655.. sseett//aarrcclluusstteerr ((55)) sseett//aarrcclluusstteerr <> [[<> ......]] Make the node_call an AR- Cluster type node @@ -3769,12 +4347,13 @@ Set the node_call as an AR-Cluster type node - 1111..6666.. sseett//bbaaddddxx ((88)) + 1133..6666.. sseett//bbaaddddxx ((88)) sseett//bbaaddddxx <> Stop words we do not wish to see in the callsign field of a dx spot being propagated + Setting a word as 'baddx' will prevent spots with that word in the callsign field of a DX spot from going any further. They will not be displayed and they will not be sent onto other nodes. @@ -3798,7 +4377,7 @@ - 1111..6677.. sseett//bbaaddnnooddee ((66)) + 1133..6677.. sseett//bbaaddnnooddee ((66)) sseett//bbaaddnnooddee <> Stop spots from this node_call being propagated @@ -3832,7 +4411,7 @@ FILTERing. - 1111..6688.. sseett//bbaaddssppootttteerr ((88)) + 1133..6688.. sseett//bbaaddssppootttteerr ((88)) sseett//bbaaddssppootttteerr <> Stop spots from this callsign being propagated @@ -3866,7 +4445,7 @@ FILTERing. - 1111..6699.. sseett//bbeeeepp ((00)) + 1133..6699.. sseett//bbeeeepp ((00)) sseett//bbeeeepp Add beeps to terminal messages @@ -3874,7 +4453,7 @@ Add a beep to DX and other terminal messages. - 1111..7700.. sseett//ccllxx ((55)) + 1133..7700.. sseett//ccllxx ((55)) sseett//ccllxx <> [[<> ......]] Make the node_call a CLX type node @@ -3883,16 +4462,21 @@ Set the node_call as a CLX type node - 1111..7711.. sseett//ddeebbuugg ((99)) + 1133..7711.. sseett//ddeebbuugg ((99)) sseett//ddeebbuugg <> Add a debug level to the debug set - You can remove this level with unset/debug + You can choose to log several different levels. The levels are + + chan state msg cron connect + You can show what levels you are logging with the _s_h_o_w_/_d_e_b_u_g command. + You can remove a debug level with unset/debug - 1111..7722.. sseett//ddxx ((00)) + + 1133..7722.. sseett//ddxx ((00)) sseett//ddxxAllow DX messages to arrive at your terminal @@ -3900,7 +4484,9 @@ You can stop DX messages with the _u_n_s_e_t_/_d_x command - 1111..7733.. sseett//ddxxggrriidd ((00)) + + + 1133..7733.. sseett//ddxxggrriidd ((00)) sseett//ddxxggrriiddAllow grid squares on the end of DX messages @@ -3910,7 +4496,7 @@ to remove the grid squares. - 1111..7744.. sseett//ddxxnneett ((55)) + 1133..7744.. sseett//ddxxnneett ((55)) sseett//ddxxnneett <> [[<> ......]] Make the node_call a DXNet type node @@ -3919,7 +4505,7 @@ Set the node_call as a DXNet type node - 1111..7755.. sseett//eecchhoo ((00)) + 1133..7755.. sseett//eecchhoo ((00)) sseett//eecchhoo Make the cluster echo your input @@ -3936,7 +4522,7 @@ YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25. - 1111..7766.. sseett//hheerree ((00)) + 1133..7766.. sseett//hheerree ((00)) sseett//hheerree Set the here flag @@ -3947,7 +4533,7 @@ brackets around your callsign to indicate you are not available. - 1111..7777.. sseett//hhoommeennooddee ((00)) + 1133..7777.. sseett//hhoommeennooddee ((00)) sseett//hhoommeennooddee <> Set your home cluster @@ -3958,13 +4544,15 @@ - SET/HOMENODE gb7djk + SET/HOMENODE gb7djk + - 1111..7788.. sseett//hhooppss ((88)) + + 1133..7788.. sseett//hhooppss ((88)) sseett//hhooppss <> aannnn||ssppoottss||wwwwvv||wwccyy <> Set hop count @@ -3987,7 +4575,7 @@ creates a filter and works in conjunction with the filter system. - 1111..7799.. sseett//iissoollaattee ((99)) + 1133..7799.. sseett//iissoollaattee ((99)) sseett//iissoollaattee <> Isolate a node from the rest of the network @@ -4005,7 +4593,7 @@ You can remove the isolation with the command unset/isolate. - 1111..8800.. sseett//llaanngguuaaggee ((00)) + 1133..8800.. sseett//llaanngguuaaggee ((00)) sseett//llaanngguuaaggee <> Set the language you wish to use @@ -4014,7 +4602,7 @@ Currently the languages available are _e_n (English) and _n_l (Dutch). - 1111..8811.. sseett//llooccaattiioonn ((00)) + 1133..8811.. sseett//llooccaattiioonn ((00)) sseett//llooccaattiioonn <> Set your latitude and longitude @@ -4024,14 +4612,13 @@ - set/location 54 04 N 2 02 E - + set/location 54 04 N 2 02 E - 1111..8822.. sseett//ssyyss__llooccaattiioonn ((99)) + 1133..8822.. sseett//ssyyss__llooccaattiioonn ((99)) sseett//ssyyss__llooccaattiioonn <> Set your cluster latitude and longitude @@ -4049,7 +4636,7 @@ - 1111..8833.. sseett//llooggiinniinnffoo ((00)) + 1133..8833.. sseett//llooggiinniinnffoo ((00)) sseett//llooggiinniinnffoo Show logins and logouts of nodes and users @@ -4059,7 +4646,7 @@ - 1111..8844.. sseett//lloocckkoouutt ((99)) + 1133..8844.. sseett//lloocckkoouutt ((99)) sseett//lloocckkoouutt <> Stop a callsign connecting to the cluster @@ -4068,7 +4655,7 @@ allow the user to connect again, use the _u_n_s_e_t_/_l_o_c_k_o_u_t command. - 1111..8855.. sseett//nnaammee ((00)) + 1133..8855.. sseett//nnaammee ((00)) sseett//nnaammee <> Set your name @@ -4083,21 +4670,24 @@ - 1111..8866.. sseett//nnooddee ((99)) + 1133..8866.. sseett//nnooddee ((99)) sseett//nnooddee <> [[<> ......]] Make the callsign an AK1A cluster Tell the system that the call(s) are to be treated as AK1A cluster and fed PC Protocol rather normal user commands. + From version 1.41 you can also set the following types of cluster - set/spider - set/dxnet - set/clx - set/arcluster + + + set/spider + set/dxnet + set/clx + set/arcluster @@ -4105,7 +4695,7 @@ To see what your nodes are set to, use the _s_h_o_w_/_n_o_d_e_s command. - 1111..8877.. sseett//oobbssccoouunntt ((99)) + 1133..8877.. sseett//oobbssccoouunntt ((99)) sseett//oobbssccoouunntt <> <> Set the 'pump-up' obsolescence counter @@ -4126,7 +4716,7 @@ minutes, it is disconnected. - 1111..8888.. sseett//ppaaggee ((00)) + 1133..8888.. sseett//ppaaggee ((00)) sseett//ppaaggee <> Set the number of lines per page @@ -4147,7 +4737,7 @@ - 1111..8899.. sseett//ppaasssswwoorrdd ((99)) + 1133..8899.. sseett//ppaasssswwoorrdd ((99)) sseett//ppaasssswwoorrdd <> <> Set a users password @@ -4159,7 +4749,8 @@ type password. - 1111..9900.. sseett//ppiinnggiinntteerrvvaall ((99)) + + 1133..9900.. sseett//ppiinnggiinntteerrvvaall ((99)) sseett//ppiinnggiinntteerrvvaall <> <> Set the ping time to neighbouring nodes @@ -4180,7 +4771,7 @@ for more information. - 1111..9911.. sseett//pprriivviilleeggee ((99)) + 1133..9911.. sseett//pprriivviilleeggee ((99)) sseett//pprriivviilleeggee <> <> [[<> ......]] Set the privilege level on a call @@ -4206,7 +4797,7 @@ connection your privilege will automatically be set to 0. - 1111..9922.. sseett//ssppiiddeerr ((55)) + 1133..9922.. sseett//ssppiiddeerr ((55)) sseett//ssppiiddeerr <> [[<> ......]] Make the node_call a DXSpider type node @@ -4215,14 +4806,12 @@ Set the node_call as a DXSpider type node - 1111..9933.. sseett//ssyyss__qqrraa ((99)) + 1133..9933.. sseett//ssyyss__qqrraa ((99)) sseett//ssyyss__qqrraa <> Set your cluster QRA locator - - - 1111..9944.. sseett//qqrraa ((00)) + 1133..9944.. sseett//qqrraa ((00)) sseett//qqrraa <> Set your QRA locator @@ -4239,7 +4828,7 @@ - 1111..9955.. sseett//qqtthh ((00)) + 1133..9955.. sseett//qqtthh ((00)) sseett//qqtthh <> Set your QTH @@ -4254,7 +4843,7 @@ - 1111..9966.. sseett//ttaallkk ((00)) + 1133..9966.. sseett//ttaallkk ((00)) sseett//ttaallkk Allow talk messages to be seen at your console @@ -4263,7 +4852,7 @@ talks with the _u_n_s_e_t_/_t_a_l_k command. - 1111..9977.. sseett//wwccyy ((00)) + 1133..9977.. sseett//wwccyy ((00)) sseett//wwccyy Allow WCY messages to be seen at your console @@ -4272,7 +4861,7 @@ WCY messages with the _u_n_s_e_t_/_w_c_y command. - 1111..9988.. sseett//wwwwvv ((00)) + 1133..9988.. sseett//wwwwvv ((00)) sseett//wwwwvv Allow WWV messages to be seen at your console @@ -4281,14 +4870,19 @@ WWV messages with the _u_n_s_e_t_/_w_w_v command. - 1111..9999.. sseett//wwxx ((00)) + 1133..9999.. sseett//wwxx ((00)) sseett//wwxx Allow WX messages to be seen at your console Allow WX information to be seen at your console. You can switch off WX messages with the _u_n_s_e_t_/_w_x command. - 1111..110000.. sshhooww//bbaaddddxx ((11)) + + + + + + 1133..110000.. sshhooww//bbaaddddxx ((11)) sshhooww//bbaaddddxxShow all the bad dx calls in the system @@ -4297,7 +4891,7 @@ information. - 1111..110011.. sshhooww//bbaaddnnooddee ((66)) + 1133..110011.. sshhooww//bbaaddnnooddee ((66)) sshhooww//bbaaddnnooddee Show all the bad nodes in the system @@ -4306,83 +4900,111 @@ more information. - 1111..110022.. sshhooww//bbaaddssppootttteerr ((11)) + 1133..110022.. sshhooww//bbaaddssppootttteerr ((11)) - sshhooww//bbaaddssppootttteerrShow all the bad spotters in the system + sshhooww//bbaaddssppootttteerr Show all the bad spotters in the system Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER for more information. - 1111..110033.. sshhooww//ddaattee ((00)) + 1133..110033.. sshhooww//ccoonnffiigguurraattiioonn ((00)) - sshhooww//ddaattee [[<>||<>]] Show the local time + sshhooww//ccoonnffiigguurraattiioonn [[<>]] Show all visible nodes and their users - This is very nearly the same as SHOW/TIME, the only difference the - format of the date string if no arguments are given. + This command allows you to see all the users that can be seen and the + nodes to which they are connected. With the optional _n_o_d_e, you can + specify a particular node to look at. - If no prefixes or callsigns are given then this command returns the - local time and UTC as the computer has it right now. If you give some - prefixes then it will show UTC and UTC + the local offset (not - including DST) at the prefixes or callsigns that you specify. + This command is normally abbreviated to: sh/c + BE WARNED: the list that is returned can be VERY long - 1111..110044.. sshhooww//ddxx ((00)) - sshhooww//ddxx [[ooppttiioonnss]] interrogate the spot database + 1133..110044.. sshhooww//ccoonnffiigguurraattiioonn//nnooddee ((00)) + sshhooww//ccoonnffiigguurraattiioonn//nnooddee Show all the nodes connected - If you just type SHOW/DX you will get the last so many spots (sysop - configurable, but usually 10). - In addition you can add any number of these options in very nearly any - order to the basic SHOW/DX command, they are:- + Show all the nodes connected locally and the nodes they have + connected. + + + 1133..110055.. sshhooww//ccoonnnneecctt ((11)) + + sshhooww//ccoonnnneecctt Show all the active connections + + + This command shows information on all the active connections known to + the node. This command gives slightly more information than WHO. + + + 1133..110066.. sshhooww//ddaattee ((00)) + + sshhooww//ddaattee [[<>||<>]] Show the local time + + + This is very nearly the same as SHOW/TIME, the only difference the + format of the date string if no arguments are given. + If no prefixes or callsigns are given then this command returns the + local time and UTC as the computer has it right now. If you give some + prefixes then it will show UTC and UTC + the local offset (not + including DST) at the prefixes or callsigns that you specify. + 1133..110077.. sshhooww//ddeebbuugg ((99)) + sshhooww//ddeebbuugg Show what levels of debug you are logging + The levels can be set with _s_e_t_/_d_e_b_u_g + 1133..110088.. sshhooww//ddxx ((00)) + sshhooww//ddxx [[ooppttiioonnss]] interrogate the spot database + If you just type SHOW/DX you will get the last so many spots (sysop + configurable, but usually 10). + In addition you can add any number of these options in very nearly any + order to the basic SHOW/DX command, they are:- - on - eg 160m 20m 2m 23cm 6mm - on - eg hf vhf uhf shf (see SHOW/BANDS) + on - eg 160m 20m 2m 23cm 6mm + on - eg hf vhf uhf shf (see SHOW/BANDS) - - the number of spots you want - - - spot no spot no in - the selected list + - the number of spots you want + - - spot no spot no in + the selected list - - for a spotted callsign beginning with - * - for a spotted callsign ending in - ** - for a spotted callsign containing + - for a spotted callsign beginning with + * - for a spotted callsign ending in + ** - for a spotted callsign containing - day - starting days ago - day - - days days ago + day - starting days ago + day - - days days ago - info - any spots containing in the info or remarks + info - any spots containing in the info or remarks - by - any spots spotted by (spotter - is the same). + by - any spots spotted by (spotter + is the same). - qsl - this automatically looks for any qsl info on the call - held in the spot database. + qsl - this automatically looks for any qsl info on the call + held in the spot database. - iota [] - If the iota island number is missing it will - look for the string iota and anything which looks like - an iota island number. If you specify then it will look - for that island. + iota [] - If the iota island number is missing it will + look for the string iota and anything which looks like + an iota island number. If you specify then it will look + for that island. - qra [] - this will look for the specific locator if - you specify one or else anything that looks like a locator. + qra [] - this will look for the specific locator if + you specify one or else anything that looks like a locator. @@ -4392,19 +5014,19 @@ - SH/DX 9m0 - SH/DX on 20m info iota - SH/DX 9a on vhf day 30 - SH/DX rf1p qsl - SH/DX iota - SH/DX iota eu-064 - SH/DX qra jn86 + SH/DX 9m0 + SH/DX on 20m info iota + SH/DX 9a on vhf day 30 + SH/DX rf1p qsl + SH/DX iota + SH/DX iota eu-064 + SH/DX qra jn86 - 1111..110055.. sshhooww//ddxxcccc ((00)) + 1133..110099.. sshhooww//ddxxcccc ((00)) sshhooww//ddxxcccc <> Interrogate the spot database by country @@ -4418,16 +5040,14 @@ + SH/DXCC G + SH/DXCC W on 20m info iota - SH/DXCC G - SH/DXCC W on 20m info iota - - - 1111..110066.. sshhooww//ffiilleess ((00)) + 1133..111100.. sshhooww//ffiilleess ((00)) sshhooww//ffiilleess [[<> [[<>]]]] List the contents of a filearea @@ -4459,7 +5079,8 @@ See also TYPE - to see the contents of a file. - 1111..110077.. sshhooww//ffiilltteerr ((00)) + + 1133..111111.. sshhooww//ffiilltteerr ((00)) sshhooww//ffiilltteerr Show the filters you have set @@ -4468,7 +5089,7 @@ displays all the filters set - for all the various categories. - 1111..110088.. sshhooww//ffiilltteerr ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) + 1133..111122.. sshhooww//ffiilltteerr ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) sshhooww//ffiilltteerr <> Show the filters set by @@ -4476,7 +5097,7 @@ A sysop can look at any filters that have been set. - 1111..110099.. sshhooww//hhooppss ((88)) + 1133..111133.. sshhooww//hhooppss ((88)) sshhooww//hhooppss <> [[aannnn||ssppoottss||wwccyy||wwwwvv||]] Show the hop counts for a node @@ -4486,7 +5107,8 @@ which category you want to see. If you leave the category out then all the categories will be listed. - 1111..111100.. sshhooww//iissoollaattee ((11)) + + 1133..111144.. sshhooww//iissoollaattee ((11)) sshhooww//iissoollaattee Show a list of isolated nodes @@ -4494,7 +5116,7 @@ Show which nodes are currently set to be isolated. - 1111..111111.. sshhooww//lloocckkoouutt ((99)) + 1133..111155.. sshhooww//lloocckkoouutt ((99)) sshhooww//lloocckkoouutt Show a list of excluded callsigns @@ -4503,7 +5125,17 @@ cluster locally with the _s_e_t_/_l_o_c_k_o_u_t command - 1111..111122.. sshhooww//mmoooonn ((00)) + 1133..111166.. sshhooww//lloogg ((88)) + + sshhooww//lloogg [[<>]] Show excerpts from the system log + + + This command outputs a short section of the system log. On its own it + will output a general logfile. With the optional callsign it will + show output from the log associated with that callsign. + + + 1133..111177.. sshhooww//mmoooonn ((00)) sshhooww//mmoooonn [[<>||<>]] Show moon rise and set times @@ -4533,7 +5165,7 @@ - 1111..111133.. sshhooww//mmuuff ((00)) + 1133..111188.. sshhooww//mmuuff ((00)) sshhooww//mmuuff <> [[<>]][[lloonngg]] Show the likely propagation to @@ -4580,9 +5212,6 @@ SH/MUF W - - - produces: @@ -4616,10 +5245,8 @@ - - - SH/MUF W L 24 - SH/MUF W 24 Long + SH/MUF W L 24 + SH/MUF W 24 Long @@ -4629,7 +5256,7 @@ terrible accurate, but it is included for completeness. - 1111..111144.. sshhooww//nnooddee ((11)) + 1133..111199.. sshhooww//nnooddee ((11)) sshhooww//nnooddee [[<> ......]] Show the type and version number of nodes @@ -4639,7 +5266,7 @@ the non-user callsigns known to the system will be displayed. - 1111..111155.. sshhooww//pprreeffiixx ((00)) + 1133..112200.. sshhooww//pprreeffiixx ((00)) sshhooww//pprreeffiixx <> Interrogate the prefix database @@ -4651,9 +5278,7 @@ See also SHOW/DXCC - - - 1111..111166.. sshhooww//pprrooggrraamm ((55)) + 1133..112211.. sshhooww//pprrooggrraamm ((55)) sshhooww//pprrooggrraamm Show the locations of all the included program modules @@ -4663,7 +5288,7 @@ from. - 1111..111177.. sshhooww//qqrraa ((00)) + 1133..112222.. sshhooww//qqrraa ((00)) sshhooww//qqrraa <> [[<>]] Show the distance between locators sshhooww//qqrraa <> <> Convert latitude and longitude to a locator @@ -4699,7 +5324,7 @@ - 1111..111188.. sshhooww//qqrrzz ((00)) + 1133..112233.. sshhooww//qqrrzz ((00)) sshhooww//qqrrzz <> Show any callbook details on a callsign @@ -4709,7 +5334,7 @@ provided for users of this software by http://www.qrz.com - 1111..111199.. sshhooww//rroouuttee ((00)) + 1133..112244.. sshhooww//rroouuttee ((00)) sshhooww//rroouuttee <> Show the route to @@ -4719,13 +5344,13 @@ - sh/route n2tly + sh/route n2tly - 1111..112200.. sshhooww//ssaatteelllliittee ((00)) + 1133..112255.. sshhooww//ssaatteelllliittee ((00)) sshhooww//ssaatteelllliittee <> [[<> <>]] Show satellite tracking data @@ -4750,6 +5375,7 @@ So for example:- + SH/SAT AO-10 SH/SAT FENGYUN1 12 2 @@ -4757,7 +5383,7 @@ - 1111..112211.. sshhooww//ssuunn ((00)) + 1133..112266.. sshhooww//ssuunn ((00)) sshhooww//ssuunn [[<>||<>]] Show sun rise and set times @@ -4784,7 +5410,7 @@ - 1111..112222.. sshhooww//ttiimmee ((00)) + 1133..112277.. sshhooww//ttiimmee ((00)) sshhooww//ttiimmee [[<>||<>]] Show the local time @@ -4795,7 +5421,7 @@ including DST) at the prefixes or callsigns that you specify. - 1111..112233.. sshhooww//wwccyy ((00)) + 1133..112288.. sshhooww//wwccyy ((00)) sshhooww//wwccyy Show the last 10 WCY broadcasts sshhooww//wwccyy <> Show the last WCY broadcasts @@ -4805,7 +5431,7 @@ system - 1111..112244.. sshhooww//wwwwvv ((00)) + 1133..112299.. sshhooww//wwwwvv ((00)) sshhooww//wwwwvv Show the last 10 WWV broadcasts sshhooww//wwwwvv <> Show the last WWV broadcasts @@ -4816,7 +5442,7 @@ - 1111..112255.. sshhuuttddoowwnn ((55)) + 1133..113300.. sshhuuttddoowwnn ((55)) sshhuuttddoowwnn Shutdown the cluster @@ -4825,7 +5451,7 @@ set to respawn in /etc/inittab it will of course restart. - 1111..112266.. ssppooooff ((99)) + 1133..113311.. ssppooooff ((99)) ssppooooff <> <> Run commands as another user @@ -4836,7 +5462,7 @@ like home_node for example. - 1111..112277.. ssttaatt//ddbb ((55)) + 1133..113322.. ssttaatt//ddbb ((55)) ssttaatt//ddbb <> Show the status of a database @@ -4848,7 +5474,9 @@ other than a sysop. - 1111..112288.. ssttaatt//cchhaannnneell ((55)) + + + 1133..113333.. ssttaatt//cchhaannnneell ((55)) ssttaatt//cchhaannnneell <> Show the status of a channel on the cluster @@ -4859,7 +5487,7 @@ Only the fields that are defined (in perl term) will be displayed. - 1111..112299.. ssttaatt//mmssgg ((55)) + 1133..113344.. ssttaatt//mmssgg ((55)) ssttaatt//mmssgg <> Show the status of a message @@ -4869,7 +5497,7 @@ etc etc. - 1111..113300.. ssttaatt//uusseerr ((55)) + 1133..113355.. ssttaatt//uusseerr ((55)) ssttaatt//uusseerr <> Show the full status of a user @@ -4880,9 +5508,7 @@ Only the fields that are defined (in perl term) will be displayed. - - - 1111..113311.. ssyyssoopp ((00)) + 1133..113366.. ssyyssoopp ((00)) ssyyssoopp Regain your privileges if you login remotely @@ -4916,15 +5542,12 @@ or 2 0 5 7 3 or 20573 - - - They will all match. If there is no password you will still be offered numbers but nothing will happen when you input a string. Any match is case sensitive. - 1111..113322.. ttaallkk ((00)) + 1133..113377.. ttaallkk ((00)) ttaallkk <> Enter talk mode with ttaallkk <> <> Send a text message to @@ -4975,7 +5598,7 @@ - 1111..113333.. ttyyppee ((00)) + 1133..113388.. ttyyppee ((00)) ttyyppee <>//<> Look at a file in one of the fileareas @@ -4985,7 +5608,6 @@ enter:- - TYPE bulletins/arld051 @@ -4995,7 +5617,7 @@ content. - 1111..113344.. wwhhoo ((00)) + 1133..113399.. wwhhoo ((00)) wwhhoo Show who is physically connected locally @@ -5004,7 +5626,7 @@ what sort of connection they have - 1111..113355.. wwxx ((00)) + 1133..114400.. wwxx ((00)) wwxx <> Send a weather message to local users wwxx ffuullll <> Send a weather message to all cluster users @@ -5014,7 +5636,7 @@ extreme that may indicate enhanced conditions - 1111..113366.. wwxx ((eennhhaanncceedd ffoorr ssyyssooppss)) ((55)) + 1133..114411.. wwxx ((eennhhaanncceedd ffoorr ssyyssooppss)) ((55)) wwxx ssyyssoopp <> Send a weather message to other clusters only @@ -5041,34 +5663,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - -