X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=txt%2Fadminmanual.txt;h=16c3e0de813ce54ce03cf22343830b38646e1890;hb=ab0ea211ea17085944f4ce2b0100932fa6af02c8;hp=6c792d9699b910dbd3a5072b8ae3d961a9122ae0;hpb=4f3bdfa16cf0d5adf08ef13fc06384e39db485c6;p=spider.git diff --git a/txt/adminmanual.txt b/txt/adminmanual.txt index 6c792d96..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.33 (Revision 2) February 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 @@ -248,53 +251,59 @@ 13.100 show/baddx (1) 13.101 show/badnode (6) 13.102 show/badspotter (1) - 13.103 show/date (0) - 13.104 show/dx (0) - 13.105 show/dxcc (0) - 13.106 show/files (0) - 13.107 show/filter (0) - 13.108 show/filter (extended for sysops) (5) - 13.109 show/hops (8) - 13.110 show/isolate (1) - 13.111 show/lockout (9) - 13.112 show/log (8) - 13.113 show/moon (0) - 13.114 show/muf (0) - 13.115 show/node (1) - 13.116 show/prefix (0) - 13.117 show/program (5) - 13.118 show/qra (0) - 13.119 show/qrz (0) - 13.120 show/route (0) - 13.121 show/satellite (0) - 13.122 show/sun (0) - 13.123 show/time (0) - 13.124 show/wcy (0) - 13.125 show/wwv (0) - 13.126 shutdown (5) - 13.127 spoof (9) - 13.128 stat/db (5) - 13.129 stat/channel (5) - 13.130 stat/msg (5) - 13.131 stat/user (5) - 13.132 sysop (0) - 13.133 talk (0) - 13.134 type (0) - 13.135 who (0) - 13.136 wx (0) - 13.137 wx (enhanced for sysops) (5) + 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)) + 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 @@ -302,32 +311,25 @@ 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.101.tar.gz - +o Data-Dumper-2.10.tar.gz + +o TimeDate-1.10.tar.gz - +o FreezeThaw-0.3.tar.gz - - +o MLDBM-2.00.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 - +o Curses-1.05.tar.gz +o Time-HiRes-01.20.tar.gz @@ -342,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. @@ -382,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) @@ -392,9 +394,7 @@ 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) + # vi /etc/group (or your favorite editor) @@ -474,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 .... @@ -496,7 +495,7 @@ - $ create_sysop.pl + $ ./create_sysop.pl @@ -509,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 ... @@ -525,8 +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 ... - $ client.pl + to /spider/src. Now issue the following command ... + + $ ./client @@ -560,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 @@ -571,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 @@ -588,12 +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 .... @@ -613,10 +724,7 @@ - - - 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 .... @@ -627,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 @@ -656,9 +764,99 @@ You should now get the login prompt and be able to login as before. + 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 + + - 33..33.. SSeettttiinngg uupp nnooddee ccoonnnneeccttss + + 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 @@ -689,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 ... @@ -707,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) @@ -721,7 +919,7 @@ - client.pl gb7baa + ./client gb7baa PC38^GB7MBC^~ If the callsign you just set up as a cluster node is for an incoming @@ -729,7 +927,19 @@ 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 @@ -743,59 +953,82 @@ - # All lines starting with a # are ignored, as are completely - blank lines. + ## All lines starting with a # are ignored, as are completely blank + lines. + - 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. + 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. - 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! + 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. - ' 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]). + 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. + + + 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 + three examples, one for a NETRom/AX25 connect, one for AGW engines and + one for tcp/ip. + + + + timeout 60 + abort (Busy|Sorry|Fail) + # don't forget to chmod 4775 netrom_call! + connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh + # you can leave this out if you call the script 'gb7dxm' + client gb7dxm ax25 + - 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. - timeout 60 - abort (Busy|Sorry|Fail) - # don't forget to chmod 4775 netrom_call! - connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh - # you can leave this out if you call the script 'gb7dxm' - client gb7dxm ax25 + 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 @@ -819,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 .... @@ -835,53 +1070,37 @@ 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 ... - - - - - - - - - - - - - - - - - - - - - <- D G1TLH connect gb7djk-1 - -> D G1TLH connection to GB7DJK-1 started - -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z > - timeout set to 15 - CONNECT sort: telnet command: dirkl.tobit.co.uk - CHAT "login" -> "gb7djk" - received " - Red Hat Linux release 5.1 (Manhattan) - Kernel 2.0.35 on an i586 - " - received "login: " - sent "gb7djk" - CHAT "word" -> "gb7djk" - received "gb7djk" - received "Password: " - sent "gb7djk" - Connected to GB7DJK-1, starting normal protocol - <- O GB7DJK-1 telnet - -> B GB7DJK-1 0 - GB7DJK-1 channel func state 0 -> init - <- D GB7DJK-1 - <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1 - <- D GB7DJK-1 PC38^GB7DJK-1^~ - <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime - 0 00:00^5447^~ - etc + 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 ... + + + + <- D G1TLH connect gb7djk-1 + -> D G1TLH connection to GB7DJK-1 started + -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z > + timeout set to 15 + CONNECT sort: telnet command: dirkl.tobit.co.uk + CHAT "login" -> "gb7djk" + received " + Red Hat Linux release 5.1 (Manhattan) + Kernel 2.0.35 on an i586 + " + received "login: " + sent "gb7djk" + CHAT "word" -> "gb7djk" + received "gb7djk" + received "Password: " + sent "gb7djk" + Connected to GB7DJK-1, starting normal protocol + <- O GB7DJK-1 telnet + -> B GB7DJK-1 0 + GB7DJK-1 channel func state 0 -> init + <- D GB7DJK-1 + <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1 + <- D GB7DJK-1 PC38^GB7DJK-1^~ + <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime + 0 00:00^5447^~ + etc @@ -901,8 +1120,6 @@ - - In a script, this might look like ... @@ -915,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 @@ -928,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. @@ -988,9 +1205,21 @@ - This line works fine for RedHat and SuSE distributions. The line - required for Slackware distributions is slightly different. My thanks - to Aurelio, PA3EZL for this information. + + 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. @@ -1020,10 +1249,13 @@ - # 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') @@ -1060,55 +1292,81 @@ - # - # hop table construction - # - package DXProt; - # default hopcount to use - $def_hopcount = 5; - # some variable hop counts based on message type - %hopcount = - ( - 11 => 10, - 16 => 10, - 17 => 10, - 19 => 10, - 21 => 10, - ); - # the per node hop control thingy - %nodehops = - GB7ADX => { 11 => 8, - 12 => 8, - 16 => 8, - 17 => 8, - 19 => 8, - 21 => 8, - }, - GB7UDX => { 11 => 8, - 12 => 8, - 16 => 8, - 17 => 8, - 19 => 8, - 21 => 8, - }, - GB7BAA => { - 11 => 5, - 12 => 8, - 16 => 8, - 17 => 8, - 19 => 8, - 21 => 8, - }, - }; + + + + + + + + + + + + + + + + + + # + # hop table construction + # + + package DXProt; + + # default hopcount to use + $def_hopcount = 5; + + # some variable hop counts based on message type + %hopcount = + ( + 11 => 10, + 16 => 10, + 17 => 10, + 19 => 10, + 21 => 10, + ); + + + # the per node hop control thingy + + + %nodehops = + + GB7ADX => { 11 => 8, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + + GB7UDX => { 11 => 8, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + GB7BAA => { + 11 => 5, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + }; @@ -1125,6 +1383,7 @@ will bring your changes into effect. + 55..22.. IIssoollaattiinngg nneettwwoorrkkss It is possible to isolate networks from each other on a "gateway" node @@ -1252,6 +1511,11 @@ + + + + + 0 = frequency 1 = call 2 = date in unix format @@ -2264,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 @@ -2282,13 +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 @@ -2301,14 +2565,14 @@ - 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 + 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 @@ -2332,7 +2596,7 @@ - type bulletins/opdx391 + type bulletin/opdx391 Ohio/Penn DX Bulletin No. 391 The Ohio/Penn Dx PacketCluster DX Bulletin No. 391 @@ -2521,7 +2785,7 @@ 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. + console.pl instead of client. To edit the colours, copy /spider/perl/Console.pl to /spider/local and @@ -4203,7 +4467,13 @@ 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 1133..7722.. sseett//ddxx ((00)) @@ -4214,6 +4484,8 @@ You can stop DX messages with the _u_n_s_e_t_/_d_x command + + 1133..7733.. sseett//ddxxggrriidd ((00)) sseett//ddxxggrriiddAllow grid squares on the end of DX messages @@ -4222,6 +4494,8 @@ Some logging programs do not like the additional information at the end of a DX spot. If this is the case, use the _u_n_s_e_t_/_d_x_g_r_i_d command to remove the grid squares. + + 1133..7744.. sseett//ddxxnneett ((55)) sseett//ddxxnneett <> [[<> ......]] Make the node_call a DXNet @@ -4276,6 +4550,8 @@ + + 1133..7788.. sseett//hhooppss ((88)) sseett//hhooppss <> aannnn||ssppoottss||wwwwvv||wwccyy <> Set hop count @@ -4288,9 +4564,9 @@ - eg: - set/hops gb7djk ann 10 - set/hops gb7mbc spots 20 + eg: + set/hops gb7djk ann 10 + set/hops gb7mbc spots 20 @@ -4342,7 +4618,6 @@ - 1133..8822.. sseett//ssyyss__llooccaattiioonn ((99)) sseett//ssyyss__llooccaattiioonn <> Set your cluster latitude and longitude @@ -4354,6 +4629,7 @@ example:- + SET/LOCATION 52 22 N 0 57 E @@ -4406,18 +4682,17 @@ - set/spider - set/dxnet - set/clx - set/arcluster + set/spider + set/dxnet + set/clx + set/arcluster - To see what your nodes are set to, use the _s_h_o_w_/_n_o_d_e_s command. - + To see what your nodes are set to, use the _s_h_o_w_/_n_o_d_e_s command. 1133..8877.. sseett//oobbssccoouunntt ((99)) @@ -4474,6 +4749,7 @@ type password. + 1133..9900.. sseett//ppiinnggiinntteerrvvaall ((99)) sseett//ppiinnggiinntteerrvvaall <> <> Set the ping time to neighbouring @@ -4485,7 +4761,6 @@ in future, to affect routing decisions. The default interval is 300 secs or 5 minutes. - You can use this command to set a different interval. Please don't. But if you do the value you enter is treated as minutes up 60 and @@ -4552,6 +4827,7 @@ + 1133..9955.. sseett//qqtthh ((00)) sseett//qqtthh <> Set your QTH @@ -4603,6 +4879,9 @@ WX messages with the _u_n_s_e_t_/_w_x command. + + + 1133..110000.. sshhooww//bbaaddddxx ((11)) sshhooww//bbaaddddxxShow all the bad dx calls in the system @@ -4617,102 +4896,115 @@ sshhooww//bbaaddnnooddee Show all the bad nodes in the system - Display all the bad node callsigns in the system, see SET/BADNODE for more information. 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. - 1133..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 - 1133..110044.. 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:- + 1133..110044.. sshhooww//ccoonnffiigguurraattiioonn//nnooddee ((00)) + sshhooww//ccoonnffiigguurraattiioonn//nnooddee Show all the nodes connected + 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. @@ -4722,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 - 1133..110055.. sshhooww//ddxxcccc ((00)) + 1133..110099.. sshhooww//ddxxcccc ((00)) sshhooww//ddxxcccc <> Interrogate the spot database by country @@ -4748,16 +5040,14 @@ + SH/DXCC G + SH/DXCC W on 20m info iota - SH/DXCC G - SH/DXCC W on 20m info iota - - - 1133..110066.. sshhooww//ffiilleess ((00)) + 1133..111100.. sshhooww//ffiilleess ((00)) sshhooww//ffiilleess [[<> [[<>]]]] List the contents of a filearea @@ -4789,7 +5079,8 @@ See also TYPE - to see the contents of a file. - 1133..110077.. sshhooww//ffiilltteerr ((00)) + + 1133..111111.. sshhooww//ffiilltteerr ((00)) sshhooww//ffiilltteerr Show the filters you have set @@ -4798,7 +5089,7 @@ displays all the filters set - for all the various categories. - 1133..110088.. sshhooww//ffiilltteerr ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) + 1133..111122.. sshhooww//ffiilltteerr ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) sshhooww//ffiilltteerr <> Show the filters set by @@ -4806,7 +5097,7 @@ A sysop can look at any filters that have been set. - 1133..110099.. sshhooww//hhooppss ((88)) + 1133..111133.. sshhooww//hhooppss ((88)) sshhooww//hhooppss <> [[aannnn||ssppoottss||wwccyy||wwwwvv||]] Show the hop counts for a node @@ -4816,7 +5107,8 @@ which category you want to see. If you leave the category out then all the categories will be listed. - 1133..111100.. sshhooww//iissoollaattee ((11)) + + 1133..111144.. sshhooww//iissoollaattee ((11)) sshhooww//iissoollaattee Show a list of isolated nodes @@ -4824,7 +5116,7 @@ Show which nodes are currently set to be isolated. - 1133..111111.. sshhooww//lloocckkoouutt ((99)) + 1133..111155.. sshhooww//lloocckkoouutt ((99)) sshhooww//lloocckkoouutt Show a list of excluded callsigns @@ -4833,7 +5125,7 @@ cluster locally with the _s_e_t_/_l_o_c_k_o_u_t command - 1133..111122.. sshhooww//lloogg ((88)) + 1133..111166.. sshhooww//lloogg ((88)) sshhooww//lloogg [[<>]] Show excerpts from the system log @@ -4843,7 +5135,7 @@ show output from the log associated with that callsign. - 1133..111133.. sshhooww//mmoooonn ((00)) + 1133..111177.. sshhooww//mmoooonn ((00)) sshhooww//mmoooonn [[<>||<>]] Show moon rise and set times @@ -4873,7 +5165,7 @@ - 1133..111144.. sshhooww//mmuuff ((00)) + 1133..111188.. sshhooww//mmuuff ((00)) sshhooww//mmuuff <> [[<>]][[lloonngg]] Show the likely propagation to @@ -4920,9 +5212,6 @@ SH/MUF W - - - produces: @@ -4948,6 +5237,9 @@ SH/MUF W 24 + + + will get you the above display, but with the next 24 hours worth of propagation data. @@ -4964,7 +5256,7 @@ terrible accurate, but it is included for completeness. - 1133..111155.. sshhooww//nnooddee ((11)) + 1133..111199.. sshhooww//nnooddee ((11)) sshhooww//nnooddee [[<> ......]] Show the type and version number of nodes @@ -4974,7 +5266,7 @@ the non-user callsigns known to the system will be displayed. - 1133..111166.. sshhooww//pprreeffiixx ((00)) + 1133..112200.. sshhooww//pprreeffiixx ((00)) sshhooww//pprreeffiixx <> Interrogate the prefix database @@ -4986,9 +5278,7 @@ See also SHOW/DXCC - - - 1133..111177.. sshhooww//pprrooggrraamm ((55)) + 1133..112211.. sshhooww//pprrooggrraamm ((55)) sshhooww//pprrooggrraamm Show the locations of all the included program modules @@ -4998,7 +5288,7 @@ from. - 1133..111188.. sshhooww//qqrraa ((00)) + 1133..112222.. sshhooww//qqrraa ((00)) sshhooww//qqrraa <> [[<>]] Show the distance between locators sshhooww//qqrraa <> <> Convert latitude and longitude to a locator @@ -5014,6 +5304,9 @@ SH/QRA IO92QL SH/QRA JN06 IN73 + + + The first example will show the distance and bearing to the locator from yourself, the second example will calculate the distance and bearing from the first locator to the second. You can use 4 or 6 @@ -5031,7 +5324,7 @@ - 1133..111199.. sshhooww//qqrrzz ((00)) + 1133..112233.. sshhooww//qqrrzz ((00)) sshhooww//qqrrzz <> Show any callbook details on a callsign @@ -5041,7 +5334,7 @@ provided for users of this software by http://www.qrz.com - 1133..112200.. sshhooww//rroouuttee ((00)) + 1133..112244.. sshhooww//rroouuttee ((00)) sshhooww//rroouuttee <> Show the route to @@ -5051,13 +5344,13 @@ - sh/route n2tly + sh/route n2tly - 1133..112211.. sshhooww//ssaatteelllliittee ((00)) + 1133..112255.. sshhooww//ssaatteelllliittee ((00)) sshhooww//ssaatteelllliittee <> [[<> <>]] Show satellite tracking data @@ -5079,7 +5372,6 @@ Each pass in a period is separated with a row of '-----' characters - So for example:- @@ -5091,7 +5383,7 @@ - 1133..112222.. sshhooww//ssuunn ((00)) + 1133..112266.. sshhooww//ssuunn ((00)) sshhooww//ssuunn [[<>||<>]] Show sun rise and set times @@ -5118,7 +5410,7 @@ - 1133..112233.. sshhooww//ttiimmee ((00)) + 1133..112277.. sshhooww//ttiimmee ((00)) sshhooww//ttiimmee [[<>||<>]] Show the local time @@ -5129,7 +5421,7 @@ including DST) at the prefixes or callsigns that you specify. - 1133..112244.. sshhooww//wwccyy ((00)) + 1133..112288.. sshhooww//wwccyy ((00)) sshhooww//wwccyy Show the last 10 WCY broadcasts sshhooww//wwccyy <> Show the last WCY broadcasts @@ -5139,19 +5431,18 @@ system - 1133..112255.. sshhooww//wwwwvv ((00)) + 1133..112299.. sshhooww//wwwwvv ((00)) sshhooww//wwwwvv Show the last 10 WWV broadcasts sshhooww//wwwwvv <> Show the last WWV broadcasts - Display the most recent WWV information that has been received by the system - 1133..112266.. sshhuuttddoowwnn ((55)) + 1133..113300.. sshhuuttddoowwnn ((55)) sshhuuttddoowwnn Shutdown the cluster @@ -5160,7 +5451,7 @@ set to respawn in /etc/inittab it will of course restart. - 1133..112277.. ssppooooff ((99)) + 1133..113311.. ssppooooff ((99)) ssppooooff <> <> Run commands as another user @@ -5171,7 +5462,7 @@ like home_node for example. - 1133..112288.. ssttaatt//ddbb ((55)) + 1133..113322.. ssttaatt//ddbb ((55)) ssttaatt//ddbb <> Show the status of a database @@ -5183,7 +5474,9 @@ other than a sysop. - 1133..112299.. ssttaatt//cchhaannnneell ((55)) + + + 1133..113333.. ssttaatt//cchhaannnneell ((55)) ssttaatt//cchhaannnneell <> Show the status of a channel on the cluster @@ -5194,7 +5487,7 @@ Only the fields that are defined (in perl term) will be displayed. - 1133..113300.. ssttaatt//mmssgg ((55)) + 1133..113344.. ssttaatt//mmssgg ((55)) ssttaatt//mmssgg <> Show the status of a message @@ -5204,7 +5497,7 @@ etc etc. - 1133..113311.. ssttaatt//uusseerr ((55)) + 1133..113355.. ssttaatt//uusseerr ((55)) ssttaatt//uusseerr <> Show the full status of a user @@ -5215,7 +5508,7 @@ Only the fields that are defined (in perl term) will be displayed. - 1133..113322.. ssyyssoopp ((00)) + 1133..113366.. ssyyssoopp ((00)) ssyyssoopp Regain your privileges if you login remotely @@ -5249,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. - 1133..113333.. ttaallkk ((00)) + 1133..113377.. ttaallkk ((00)) ttaallkk <> Enter talk mode with ttaallkk <> <> Send a text message to @@ -5308,7 +5598,7 @@ - 1133..113344.. ttyyppee ((00)) + 1133..113388.. ttyyppee ((00)) ttyyppee <>//<> Look at a file in one of the fileareas @@ -5318,7 +5608,6 @@ enter:- - TYPE bulletins/arld051 @@ -5328,7 +5617,7 @@ content. - 1133..113355.. wwhhoo ((00)) + 1133..113399.. wwhhoo ((00)) wwhhoo Show who is physically connected locally @@ -5337,18 +5626,17 @@ what sort of connection they have - 1133..113366.. wwxx ((00)) + 1133..114400.. wwxx ((00)) wwxx <> Send a weather message to local users wwxx ffuullll <> Send a weather message to all cluster users - Weather messages can sometimes be useful if you are experiencing an extreme that may indicate enhanced conditions - 1133..113377.. wwxx ((eennhhaanncceedd ffoorr ssyyssooppss)) ((55)) + 1133..114411.. wwxx ((eennhhaanncceedd ffoorr ssyyssooppss)) ((55)) wwxx ssyyssoopp <> Send a weather message to other clusters only @@ -5375,30 +5663,6 @@ - - - - - - - - - - - - - - - - - - - - - - - -