<!-- Title information -->
-<title>The DXSpider Installation and Administration Manual
-<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
-<date>Version 1.28 January 2001
+<title>The DXSpider Installation and Administration Manual</title>
+<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)</author>
+<date>Version 1.47 (Revision 1.30), April 2001</date>
+
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
</abstract>
<!-- Begin the document -->
-<sect>Installation (Original version by Iain Phillips, G0RDI)
-
-<P>
-Last modified: 02 January 2001 by Ian Maude, G0VGS
+<sect>Installation (Original version by Iain Philipps, G0RDI)
<sect1>Introduction
<P>
-This section describes the installation of DX Spider v1.35 on a
-<htmlurl url="http://www.redhat.com" name="RedHat"> Linux Distribution.
+This section describes the installation of DX Spider v1.46 on a
+<htmlurl url="http://www.redhat.com" name="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
-HOWTO on the <htmlurl url="http://www.dxcluster.org" name="DXSpider">
-website.
+installation guide that comes with the Spider distribution.
<P>
I am assuming a general knowledge of Linux and its commands. You should
<P>
The crucial ingredient for all of this is
-<htmlurl url="http://www.perl.org" name="Perl 5.004">. Now I know Perl 5.005
-is out and this will almost certainly work with it, but
-<htmlurl url="http://www.redhat.com" name="RedHat 5.1"> comes with 5.004.
-<em>Be Warned</em>, earlier versions of
-<htmlurl url="http://www.redhat.com" name="RedHat"> <bf>do not</bf> come
-with 5.004 as standard, you need to
-<htmlurl url="ftp://upgrade.redhat.com" name="upgrade">
+<htmlurl url="http://www.perl.org" name="Perl">. Earlier versions of
+Spider required perl 5.004, however it is now <it>STRONGLY</it> recommended
+that you use at least version 5.005_03 as this is the version being used
+in the development of Spider.
<P>In addition to the standard Red Hat distribution you will require the
-following <htmlurl url="http://www.cpan.org/CPAN.html" name="CPAN"> modules: -
+following modules from <htmlurl url="http://www.cpan.org/CPAN.html" name="http://www.cpan.org/CPAN.html"> ...
<P>
<itemize>
-<item> MD5-1.7.tar.gz
-<item> Data-Dumper-2.10.tar.gz
-<item> FreezeThaw-0.3.tar.gz
-<item> MLDBM-2.00.tar.gz
-<item> TimeDate-1.08.tar.gz
-<item> IO-1.20.tar.gz
+<item> Data-Dumper-2.101.tar.gz
+<item> TimeDate-1.10.tar.gz
+<item> IO-1.20.tar.gz (for perl 5.00403 and lower)
<item> Net-Telnet-3.02.tar.gz
<item> Curses-1.05.tar.gz
<item> Time-HiRes-01.20.tar.gz
<P>
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.
<P>
Login as root and create a user to run the cluster under. <bf><it>UNDER
<tscreen><verb>
# 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)
</verb></tscreen>
<P><bf>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</bf>
<P>
-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!
<P>
Save the new file and change directory to ../perl ....
the sysop.
<tscreen><verb>
-$ create_sysop.pl
+$ ./create_sysop.pl
</verb></tscreen>
<sect1>Starting up for the first time
It should look something like this ...
<tscreen><verb>
-$ 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 ...
<P>
If all is well then login on another term or console as <em>sysop</em> and
-cd to /spider/perl. Now issue the following command ...
+cd to /spider/src. Now issue the following command ...
<tscreen><verb>
-$ client.pl
+$ ./client
</verb></tscreen>
<P>
<P>
and both the cluster and the client should return to Linux prompts.
-<sect>The Client program
+<sect1>The Client program
<P>
In earlier versions of Spider, all the processes were Perl scripts. This
should see the output on your screen and hopefully now have a small C program
called <em>client</em>. Leave it in this directory.
+
+<sect>Quick installation guide (Linux version)
+
+<P>
+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.
+
+<itemize>
+<item>Login as root
+<item>Get the additional CPAN modules and install them (root)
+<item>Create the "sysop" user and set a password (root)
+<item>Put the Spider tarball in ~sysop and untar it (root)
+<item>ln -s ~sysop/spider /spider (root)
+<item>groupadd -g 251 spider (root)
+<item>Add any more users you need to the group entry in /etc/group (root)
+<item>Set the permissions on the spider tree (root)
+<item>Fix permissions on ax25_call and netrom_call (root)
+<item>Login as the sysop user
+<item>cd to /spider (sysop)
+<item>mkdir local (sysop)
+<item>mkdir local_cmd (sysop)
+<item>cp perl/DXVars.pm.issue local/DXVars.pm (sysop)
+<item>cd to /spider/local and edit DXVars to set your details (sysop)
+<item>cd ../perl (sysop)
+<item>./create_sysop.pl (sysop)
+<item>./cluster.pl (sysop)
+</itemize>
+
+Spider should now be running and you should be able to login using the
+client program.
+
+<itemize>
+<item>Login as root
+<item>Enter the correct line in ax25d.conf (root)
+<item>Enter the correct line in /etc/services (root)
+<item>Enter the correct line in /etc/inetd.conf (root)
+<item>killall -HUP inetd (root)
+</itemize>
+
+Spider should now be able to accept logins via telnet, netrom and ax25.
+
+<itemize>
+<item>Login as sysop
+<item>Start the cluster (sysop)
+<item>set/node and type for links (sysop)
+<item>Write any connect scripts (sysop)
+<item>Edit /spider/crontab as required (sysop)
+<item>Edit any other files as necessary (sysop)
+<item>Set filters, hops and forwarding files (sysop)
+<item>Login as root
+<item>Enter the correct line in /etc/inittab (root)
+</itemize>
+
<sect>Configuration
<sect1>Allowing ax25 connects from users
default * * * * * * - sysop /spider/src/client client %u ax25
</verb></tscreen>
-<sect1>Allowing telnet connects from users
+or, if you wish your users to be able to use SSID's on their callsigns ..
+
+<tscreen><verb>
+default * * * * * * - sysop /spider/src/client client %s ax25
+</verb></tscreen>
+
+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:
+
+<tscreen><verb>
+GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25
+default * * * * * * - sysop /spider/src/client client %u ax25
+</verb></tscreen>
+
+<sect1>Allowing telnet connects from users
+<P>
+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.
+
<P>
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 ....
</verb></tscreen>
<P>
-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 ....
<tscreen><verb>
</verb></tscreen>
-<P>Now login as <em>sysop</em> and cd spider/perl. You can test that spider
+<P>Now login as <em>sysop</em> and cd spider/src. You can test that spider
is accepting telnet logins by issuing the following command ....
<tscreen><verb>
-client.pl login telnet
+./client login telnet
</verb></tscreen>
You should get a login prompt and on issuing a callsign, you will be given
<P>
You should now get the login prompt and be able to login as before.
+<sect1>Setting up telnet connects (from 1.47 onwards)
+
+<P>
+From version 1.47 you can choose to allow the perl cluster.pl program to
+allow connections directly (i.e. not via the <tt>/spider/src/client</tt>
+interface program). If you are using Windows then this is the only method
+available of allowing incoming telnet connections.
+
+<P>
+To do this you need first to remove any line that you may previously have set
+up in /etc/inetd.conf. Remember to:-
+
+<tscreen><verb>
+killall -HUP inetd
+</verb></tscreen>
+
+<P>
+to make the change happen...
+
+<P>
+Having done that, you need to copy the file
+<em>/spider/perl/Listeners.pm</em> to <em>/spider/local</em> and
+then edit it. You will need to uncomment the line containing &dquot;0.0.0.0&dquot;
+and select the correct port to listen on. So that it looks like this:-
+
+<tscreen><verb>
+@listen = (
+ ["0.0.0.0", 8000],
+);
+</verb></tscreen>
+
+<P>
+As standard, the listener will listen on all interfaces simultaneously.
+If you require more control than this, you can specify each interface
+individually:-
+
+<tscreen><verb>
+@listen = (
+ ["gb7baa.dxcluster.net", 8000],
+ ["44.131.16.2", 6300],
+);
+</verb></tscreen>
+
+<P>
+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.
+
+<P>
+Restart the cluster.pl program to enable the listener.
+
+<P>
+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.
+
+<sect1>Setting up for AGW Engine (1.47 onwards)
+
+<P>
+AGW Engine is a Windows based ax25 stack. You can connect to an AGW engine
+from Linux as well as Windows based machines.
+
+<P>
+In order to enable access to an AGW Engine you need to copy
+<em>/spider/perl/AGWConnect.pm</em> to <em>/spider/local</em> and edit it.
+Specifically you must:-
+
+<itemize>
+<item> set <tt>$enable</tt> to 1.
+<item> set <tt>$login</tt> and <tt>$passwd</tt> to the values set up in your AGW installation.
+If you haven't set any there, then you should not touch these values.
+<item> You can connect to a remote AGW engine (ie on some other machine) by changing <tt>$addr</tt>
+and <tt>$port</tt> appropriately.
+<item> Restart the cluster.pl program
+</itemize>
+
+
<sect1>Setting up node connects
<P>
AK1A type node.
<P>
-Start up the cluster as you did before and login as the sysop with client.pl.
+Start up the cluster as you did before and login as the sysop with 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 ...
<P>
That is now set, it is as simple as that. To prove it, login on yet another
-console as sysop and issue the command ...
+console as sysop, cd to spider/src and issue the command ...
<tscreen><verb>
-client.pl gb7baa (using the callsign you set as a node)
+./client gb7baa (using the callsign you set as a node)
</verb></tscreen>
<P>
You should get an initialisation string from DXSpider like this ...
<tscreen><verb>
-client.pl gb7baa
+./client gb7baa
PC38^GB7MBC^~
</verb></tscreen>
this is all that needs to be done. If the connection is to be outgoing then
a connection script needs to be written.
+<P>
+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:
+
+<tscreen><verb>
+unset/node gb7baa
+</verb></tscreen>
+
<sect1>Connection scripts
<P>
The connect scripts consist of lines which start with the following keywords
or symbols:-
-<verb>
+<descrip>
-# All lines starting with a # are ignored, as are completely
+<tag/#/All lines starting with a <tt>#</tt> are ignored, as are completely
blank lines.
-timeout timeout followed by a number is the number of seconds to wait for a
+<tag/timeout/<tt>timeout</tt> 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
+<tag/abort/ <tt>abort</tt> 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
+<tag/connect/<tt>connect</tt> 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
responsibility to get your node and other ax25 parameters to work
before going down this route!
-' ' is the delimiting character for a word or phrase of an expect/send
+<tag/'/<tt>'</tt> is the delimiting character for a word or phrase of an expect/send
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
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
+<tag/client/<tt>client</tt> 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]).
-</verb>
+</descrip>
-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.
<tscreen><verb>
timeout 60
<P>
+<tscreen><verb>
+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
+'Connect' ''
+'Connect' 'c np7'
+'Connect' 'c gb7dxm'
+# you can leave this out if you call the script 'gb7dxm'
+client gb7dxm ax25
+</verb></tscreen>
+
+<P>
+
<tscreen><verb>
timeout 15
connect telnet dirkl.tobit.co.uk
This will start a connection using the script called <em>gb7djk-1</em>. You can
follow the connection by watching the term or console from where you started
-<em>cluster.pl</em>. You should see something like this ...
+<em>cluster.pl</em>. From version 1.47 onwards, you will need to <tt>set/debug connect</tt> first.
+You should see something like this ...
<tscreen><verb>
<- D G1TLH connect gb7djk-1
<P>
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
+If the connection is to a different port, such as 7300, this negotiation does
not happen and therefore no echo should be present.
<P>
DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
</verb></tscreen>
+<P>
+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 ...
+
+<tscreen><verb>
+DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
+</verb></tscreen>
+
+
+The line required for Slackware distributions is slightly different. My thanks to
+Aurelio, PA3EZL for this information.
+
+<tscreen><verb>
+DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7
+</verb></tscreen>
+
<P>
This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart
it should it crash for any reason.
# 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')
+0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx')
</verb></tscreen>
<P>
the other cluster nodes that we are linked to. This is usually because of
rules and regulations pertaining to items for sale etc in a particular country.
-<sect1>Filtering DX callouts
+<sect1>Filtering DX callouts (Depricated)
+
+<P>
+<bf><it>From version 1.47, this method is replaced by the command set/baddx</it></bf>
<P>
In the same way as mail, there are some types of spot we do not wish to pass on
<P>
You can reload the file from the cluster prompt as sysop with load/badwords.
+<sect>Mail
+
+<P>
+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 <em>msg</em> command.
+
+<sect1>Personal mail
+
+<P>
+Personal mail is sent using the <em>sp</em> command. This is actually the
+default method of sending mail and so a simple <em>s</em> for send will do.
+A full list of the send commands and options is in the <em>command set</em>
+section, so I will not duplicate them here.
+
+<sect1>Bulletin mail
+
+<P>
+Bulletin mail is sent by using the <em>sb</em> command. This is one of the
+most common mistakes users make when sending mail. They send a bulletin
+mail with <em>s</em> or <em>sp</em> instead of <em>sb</em> and of course
+the message never leaves the cluster. This can be rectified by the sysop
+by using the <em>msg</em> command.
+
+<P>Bulletin addresses can be set using the Forward.pl file.
+
+<sect1>Forward.pl
+
+<P>
+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 ...
+
+<tscreen><verb>
+#
+# 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 = (
+'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ],
+'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ],
+'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ],
+'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+);
+</verb></tscreen>
+
+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.
+
+<P>
+To force the cluster to reread the file use load/forward
+
+
+<sect1>The msg command
+
+<P>
+The <em>msg</em> 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 ...
+
+<tscreen><verb>
+ MSG TO <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - remove any waiting time for this message
+ MSG NOREad <msgno> - mark message as unread
+ MSG REad <msgno> - mark message as read
+ MSG QUeue - queue any outstanding bulletins
+ MSG QUeue 1 - queue any outstanding private messages
+</verb></tscreen>
+
+These commands are simply typed from within the cluster as the sysop user.
+
+<sect1>Message status
+
+<P>
+You can check on a message from within the cluster by using the command
+<em>stat/msg</em>. 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 ...
+
+<tscreen><verb>
+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 >
+</verb></tscreen>
+
+<sect1>Filtering mail
+
+<P>
+This is described in the section on <em>Other filters</em> so I will not
+duplicate it here.
+
+<sect1>Distribution lists
+
+<P>
+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 <em>distro</em>. You
+put any distibution lists in here. For example, here is a file called
+SYSOP.pl that caters for the UK sysops.
+
+<tscreen><verb>
+qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
+ GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
+ GB7DXK GB7DXI GB7DXS)
+</verb></tscreen>
+
+Any mail sent to "sysop" would only be sent to the callsigns in this list.
+
+<sect1>BBS interface
+
+<P>
+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.
+
+<P>
+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.
+
+<sect>Databases
+
+<P>
+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.
+
+<sect1>Creating databases
+
+<P>
+Creating a database could not be more simple. All the commands are
+sent from the cluster prompt as the <em>sysop</em> user.
+
+To create a database you use the command <em>dbcreate</em>. It can
+be used in 3 different ways like so ..
+
+<tscreen><verb>
+dbcreate <name>
+</verb></tscreen>
+
+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.
+
+<tscreen><verb>
+dbcreate <name> chain <name> [<name>...]
+</verb></tscreen>
+
+This creates a chained database entry. The first database will be
+scanned, then the second, the third etc...
+
+<tscreen><verb>
+dbcreate <name> remote <name>
+</verb></tscreen>
+
+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...
+
+<tscreen><verb>
+dbcreate buckmaster remote gb7dxc
+</verb></tscreen>
+
+Remote databases cannot be chained, however, the last database in a
+chain can be a remote database.
+
+<sect1>Importing databases
+
+<P>
+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 ...
+
+<tscreen><verb>
+dbimport oblast /tmp/OBLAST.FUL
+</verb></tscreen>
+
+This will update the existing local oblast database or create it if
+it does not exist.
+
+<sect1>Checking available databases
+
+<P>
+Once a database is created, you will want to check that it has been
+added. To do this use the <em>dbavail</em> command. This will
+output the available databases. For example ...
+
+<tscreen><verb>
+dbavail
+DB Name Location Chain
+qsl Local
+buck GB7ADX
+hftest GB7DXM
+G0VGS de GB7MBC 3-Feb-2001 1925Z >
+</verb></tscreen>
+
+<sect1>Looking up databases
+
+<P>
+To look for information in a defined database, simply use the <em>dbshow</em>
+command, for example ...
+
+<tscreen><verb>
+dbshow buckmaster G0YLM
+</verb></tscreen>
+
+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
+<em>show</em> command like this ...
+
+<tscreen><verb>
+'^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
+</verb></tscreen>
+
+Now you can simply use show/buckmaster or an abreviation.
+
+<sect1>Removing databases
+
+<P>
+To delete an existing database you use the <em>dbremove</em> command.
+For example ...
+
+<tscreen><verb>
+dbremove oblast
+</verb></tscreen>
+
+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.
+
<sect>Information, files and useful programs
<sect1>MOTD
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
-<em>bulletins</em>. Now copy any OPDX or similar bulletins into it. These
+<em>bulletin</em>. Now copy any OPDX or similar bulletins into it. These
can be listed by the user in the same way as above using the <em>show/files</em>
-command with an extension for the bulletins directory you have just created,
+command with an extension for the bulletin directory you have just created,
like this ....
<tscreen><verb>
-show/files bulletins
+show/files bulletin
</verb></tscreen>
<P>
<tscreen><verb>
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
</verb></tscreen>
You can see that in the files area (basically the packclus directory) there is a
-file called <em>news</em> and a directory called <em>bulletins</em>. You can
+file called <em>news</em> and a directory called <em>bulletin</em>. You can
also see that dates they were created. In the case of the file <em>news</em>,
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 file called
type news
</verb></tscreen>
-To look what is in the bulletins directory you issue the command ....
+To look what is in the bulletin directory you issue the command ....
<tscreen><verb>
-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
You can now read any file in this directory using the type command, like this ....
<tscreen><verb>
-type bulletins/opdx391
+type bulletin/opdx391
Ohio/Penn DX Bulletin No. 391
The Ohio/Penn Dx PacketCluster
DX Bulletin No. 391
always turn out as you think. Care is needed and you need to test the
results once you have set an alias.
-<sect1>Forward.pl
+<sect1>Console.pl
<P>
-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.
-<tscreen><verb>
-#
-# 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)
-#
+<P>
+To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
+file with your favourite editor.
-package DXMsg;
+<sect1>Updating kepler data
-@forward = (
-'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ],
-'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ],
-'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ],
-'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-);
+<P>
+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 <em>export</em> command from the cluster prompt
+as the sysop. For example ...
+
+<tscreen><verb>
+export 5467 /spider/perl/keps.in
</verb></tscreen>
-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.
+would export message number 5467 as a file called keps.in in the
+/spider/perl directory.
-<P>
-To force the cluster to reread the file use load/forward
+Now login to a VT as sysop and cd /spider/perl. There is a command in
+the perl directory called <em>convkeps.pl</em>. All we need to do now is
+convert the file like so ...
-<sect1>Distribution lists
+<tscreen><verb>
+./convkeps.pl keps.in
+</verb></tscreen>
-<P>
-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 <em>distro</em>. You
-put any distibution lists in here. For example, here is a file called
-SYSOP.pl that caters for the UK sysops.
+Now go back to the cluster and issue the command ...
<tscreen><verb>
-qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
- GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
- GB7DXK GB7DXI GB7DXS)
+load/keps
</verb></tscreen>
-Any mail sent to "sysop" would only be sent to the callsigns in this list.
-
-<sect1>Console.pl
+That is it! the kepler data has been updated.
-<P>
-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.
+<sect1>The QRZ callbook
<P>
-To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
-file with your favourite editor.
+The command <em>sh/qrz</em> 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
+<htmlurl url="http://www.qrz.com" name="qrz.com"> for allowing this access.
<sect>CVS
repository. You do this with the command below ...
<verb>
-cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/DXSpider login
+cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
</verb>
You will get a password prompt. Simply hit return here and your machine should
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.
+
+If you are installing Spider from CVS then change directory to /home/sysop
+
+If you are wanting to update Spider then cd to /tmp
<P>
The next step will create a brand new 'spider' directory in your current
directory.
<verb>
-cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/DXSpider co spider
+cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
</verb>
This command is all on one line.
Remember to recompile the C client (cd /spider/src; make)
<P>
-At this point the files have been upgraded. You can (usually) restrt the cluster
+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 it!
You can use any of the following things in this line:-
-<verb>
+<tscreen><verb>
info <string> eg: iota or qsl
by <prefixes> eg: G,M,2
origin <prefixes>
channel <prefixes>
wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX (distros)
-</verb>
+</verb></tscreen>
some examples:-
-<verb>
+<tscreen><verb>
acc/ann dest 6MUK
acc/ann 2 by_zone 14,15,16
(this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
-</verb>
+</verb></tscreen>
or
-<verb>
+<tscreen><verb>
acc/ann by G,M,2
-</verb>
+</verb></tscreen>
This filter would only allow announces that were posted buy UK stations.
You can use the tag 'all' to accept everything eg:
-<verb>
+<tscreen><verb>
acc/ann all
-</verb>
+</verb></tscreen>
but this probably for advanced users...
This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
accept/ann by G,M,2
accept/ann input node_default by G,M,2
accept/ann user_default by G,M,2
-</verb>
+</verb></tscreen>
<sect1>accept/spots (0)
You can use any of the following things in this line:-
-<verb>
+<tscreen><verb>
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on <range> same as 'freq'
call <prefixes> eg: G,PA,HB9
by_zone <numbers>
origin <prefixes>
channel <prefixes>
-</verb>
+</verb></tscreen>
<P>
For frequencies, you can use any of the band names defined in
some examples:-
-<verb>
+<tscreen><verb>
acc/spot 1 on hf/cw
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</verb>
+</verb></tscreen>
You can use the tag 'all' to accept everything, eg:
-<verb>
+<tscreen><verb>
acc/spot 3 all
-</verb>
+</verb></tscreen>
but this probably for advanced users...
This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
accept/spot db0sue-7 1 by_zone 14,15,16
accept/spot node_default all
set/hops node_default 10
accept/spot user_default by G,M,2
-</verb>
+</verb></tscreen>
<sect1>accept/wcy (0)
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
-<verb>
+<tscreen><verb>
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
by_itu <numbers>
by_zone <numbers>
channel <prefixes>
-</verb>
+</verb></tscreen>
<P>
There are no examples because WCY Broadcasts only come from one place and
This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
accept/wcy node_default all
set/hops node_default 10
-</verb>
+</verb></tscreen>
<sect1>accept/wwv (0)
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
-<verb>
+<tscreen><verb>
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
by_itu <numbers>
by_zone <numbers>
channel <prefixes>
-</verb>
+</verb></tscreen>
for example
-<verb>
+<tscreen><verb>
accept/wwv by_zone 4
-</verb>
+</verb></tscreen>
is probably the only useful thing to do (which will only show WWV broadcasts
by stations in the US).
This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
accept/wwv db0sue-7 1 by_zone 4
accept/wwv node_default all
set/hops node_default 10
accept/wwv user_default by W,K
-</verb>
+</verb></tscreen>
<sect1>announce (0)
be ALL the non-private messages. You can prevent this by using these
commmands:-
-<verb>
+<tscreen><verb>
catchup GB7DJK all
catchup GB7DJK 300 301 302 303 500-510
-</verb>
+</verb></tscreen>
and to undo what you have just done:-
-<verb>
+<tscreen><verb>
uncatchup GB7DJK all
uncatchup GB7DJK 300 301 302 303 500-510
-</verb>
+</verb></tscreen>
which will arrange for them to be forward candidates again.
If you have a filter:-
-<verb>
+<tscreen><verb>
acc/spot 1 on hf/cw
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</verb>
+</verb></tscreen>
and you say:-
-<verb>
+<tscreen><verb>
clear/spot 1
-</verb>
+</verb></tscreen>
you will be left with:-
-<verb>
+<tscreen><verb>
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</verb>
+</verb></tscreen>
If you do:
-<verb>
+<tscreen><verb>
clear/spot all
-</verb>
+</verb></tscreen>
the filter will be completely removed.
It is expected that the sysop will add an entry to the local Aliases file
so that users can use the more familiar AK1A style of enquiry such as:
-<verb>
+<tscreen><verb>
SH/BUCK G1TLH
-</verb>
+</verb></tscreen>
but if he hasn't and the database really does exist (use DBAVAIL or
SHOW/COMMAND to find out) you can do the same thing with:
-<verb>
+<tscreen><verb>
DBSHOW buck G1TLH
-</verb>
+</verb></tscreen>
<sect1>debug (9)
You can combine some of the various directory commands together eg:-
-<verb>
+<tscreen><verb>
DIR TO G1TLH 5
or
DIR SUBJECT IOTA 200-250
-</verb>
+</verb></tscreen>
You can abbreviate all the commands to one letter and use ak1a syntax:-
-<verb>
+<tscreen><verb>
DIR/T G1* 10
DIR/S QSL 10-100 5
-</verb>
+</verb></tscreen>
<sect1>directory (extended for sysops) (5)
This is how you send a DX Spot to other users. You can, in fact, now
enter the <freq> and the <call> either way round.
-<verb>
+<tscreen><verb>
DX FR0G 144.600
DX 144.600 FR0G
DX 144600 FR0G
-</verb>
+</verb></tscreen>
will all give the same result. You can add some remarks to the end
of the command and they will be added to the spot.
-<verb>
+<tscreen><verb>
DX FR0G 144600 this is a test
-</verb>
+</verb></tscreen>
You can credit someone else by saying:-
-<verb>
+<tscreen><verb>
DX by G1TLH FR0G 144.600 he isn't on the cluster
-</verb>
+</verb></tscreen>
The <freq> is compared against the available bands set up in the
cluster. See SHOW/BANDS for more information.
<sect1>kill full (5)
+<P>
<tt>
<bf>kill full <msgno> [<msgno>]</bf> Delete a message from the
whole cluster
<sect1>load/baddx (9)
+
+<P>
<tt>
<bf>load/baddx</bf> Reload the bad DX table
</tt>
<P>
<tt>
-<bf>ping <node></bf> Send a ping command to another cluster node
+<bf>ping <node></bf> Check the link quality between nodes
</tt>
<P>
-This command is used to estimate the quality of the link to another cluster.
-The time returned is the length of time taken for a PC51 to go to another
-cluster and be returned.
-
+his command allows you to send a frame to another cluster node on
+the network and get a return frame. The time it takes to do this
+is a good indication of the quality of the link. The actual time
+it takes is output to the console in seconds.
Any visible cluster node can be PINGed.
+
<sect1>rcmd (1)
<P>
You can use any of the following things in this line:-
-<verb>
+<tscreen><verb>
info <string> eg: iota or qsl
by <prefixes> eg: G,M,2
origin <prefixes>
channel <prefixes>
wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX (distros)
-</verb>
+</verb></tscreen>
some examples:-
-<verb>
+<tscreen><verb>
rej/ann by_zone 14,15,16 and not by G,M,2
-</verb>
+</verb></tscreen>
You can use the tag 'all' to reject everything eg:
-<verb>
+<tscreen><verb>
rej/ann all
-</verb>
+</verb></tscreen>
but this probably for advanced users...
This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
reject/ann by G,M,2
reject/ann input node_default by G,M,2
reject/ann user_default by G,M,2
-</verb>
+</verb></tscreen>
<sect1>reject/spots (0)
</tt>
<P>
-Create an 'reject this spot' line for a filter.
+Create a 'reject this spot' line for a filter.
-An reject filter line means that if the spot matches this filter it is
+A reject filter line means that if the spot matches this filter it is
dumped (not passed on). See HELP FILTERS for more info. Please read this
to understand how filters work - it will save a lot of grief later on.
You can use any of the following things in this line:-
-<verb>
+<tscreen><verb>
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on <range> same as 'freq'
call <prefixes> eg: G,PA,HB9
by_zone <numbers>
origin <prefixes>
channel <prefixes>
-</verb>
+</verb></tscreen>
For frequencies, you can use any of the band names defined in
SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
some examples:-
-<verb>
+<tscreen><verb>
rej/spot 1 on hf
rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
-</verb>
+</verb></tscreen>
You can use the tag 'all' to reject everything eg:
-<verb>
+<tscreen><verb>
rej/spot 3 all
-</verb>
+</verb></tscreen>
but this probably for advanced users...
This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
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
-</verb>
+</verb></tscreen>
<sect1>reject/wcy (0)
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
-<verb>
+<tscreen><verb>
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
by_itu <numbers>
by_zone <numbers>
channel <prefixes>
-</verb>
+</verb></tscreen>
There are no examples because WCY Broadcasts only come from one place and
you either want them or not (see UNSET/WCY if you don't want them).
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
-<verb>
+<tscreen><verb>
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
by_itu <numbers>
by_zone <numbers>
channel <prefixes>
-</verb>
+</verb></tscreen>
for example
-<verb>
+<tscreen><verb>
reject/wwv by_zone 14,15,16
-</verb>
+</verb></tscreen>
is probably the only useful thing to do (which will only show WWV broadcasts
by stations in the US).
<P>This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
reject/wwv db0sue-7 1 by_zone 4
reject/wwv node_default all
reject/wwv user_default by W
-</verb>
+</verb></tscreen>
<sect1>reply (0)
You can have multiple qualifiers so that you can have for example:-
-<verb>
+<tscreen><verb>
SEND RR COPY 123 PRIVATE G1TLH G0RDI
-</verb>
+</verb></tscreen>
which should send a copy of message 123 to G1TLH and G0RDI and you will
receive a read receipt when they have read the message.
<P>
Set the node_call as an AR-Cluster type node
+<sect1>set/baddx (8)
+
+<P>
+<tt>
+<bf>set/baddx <call></bf> Stop words we do not wish to see in the callsign field
+of a dx spot being propagated
+</tt>
+
+<P>
+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.
+
+The word must be wriiten in full, no wild cards are allowed eg:-
+
+<tscreen><verb>
+ set/baddx FORSALE VIDEO FR0G
+</verb></tscreen>
+
+To allow a word again, use the following command ...
+
+<tscreen><verb>
+ unset/baddx VIDEO
+</verb></tscreen>
+
<sect1>set/badnode (6)
<P>
The call can be a full or partial call (or a prefix), eg:-
-<verb>
+<tscreen><verb>
set/badnode K1TTT
-</verb>
+</verb></tscreen>
will stop anything from K1TTT (including any SSID's)
-<verb>
+<tscreen><verb>
unset/badnode K1TTT
-</verb>
+</verb></tscreen>
+
+will allow spots from him again.
+
+Use with extreme care. This command may well be superceded by FILTERing.
+
+<sect1>set/badspotter (8)
+
+<P>
+<tt>
+<bf>set/badspotter <call></bf> Stop spots from this callsign being propagated
+</tt>
+
+<P>
+Setting a callsign as a 'badspotter' will prevent spots from this callsign
+going any further. They will not be displayed and they will not be
+sent onto other nodes.
+
+The call must be written in full, no wild cards are allowed eg:-
+
+<tscreen><verb>
+ set/badspotter VE2STN
+</verb></tscreen>
+
+will stop anything from VE2STN. If you want SSIDs as well then you must
+enter them specifically.
+
+<tscreen><verb>
+ unset/badspotter VE2STN
+</verb></tscreen>
will allow spots from him again.
</tt>
<P>
-You can remove this level with unset/debug <name>
+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 <em>show/debug</em>
+command.
+
+You can remove a debug level with unset/debug <name>
<sect1>set/dx (0)
to you will normally find their way there should you not be connected.
eg:-
-<verb>
+<tscreen><verb>
SET/HOMENODE gb7djk
-</verb>
+</verb></tscreen>
<sect1>set/hops (8)
This command allows you to set up special hop counts for a node
for currently: announce, spots, wwv and wcy broadcasts.
-<verb>
+<tscreen><verb>
eg:
set/hops gb7djk ann 10
set/hops gb7mbc spots 20
-</verb>
+</verb></tscreen>
Set SHOW/HOPS for information on what is already set. This command
creates a filter and works in conjunction with the filter system.
You can set your latitude and longitude manually or alternatively use the
<em>set/qra</em> command which will do the conversion for you.
-<verb>
+<tscreen><verb>
set/location 54 04 N 2 02 E
-</verb>
+</verb></tscreen>
<sect1>set/sys_location (9)
what your latitude and longitude is. If you have not yet done a SET/QRA
then this command will set your QRA locator for you. For example:-
-<verb>
+<tscreen><verb>
SET/LOCATION 52 22 N 0 57 E
-</verb>
+</verb></tscreen>
<sect1>set/logininfo (0)
<P>
Tell the cluster what your name is, eg:-
-<verb>
+<tscreen><verb>
set/name Dirk
-</verb>
+</verb></tscreen>
<sect1>set/node (9)
From version 1.41 you can also set the following types of cluster
-<verb>
+<tscreen><verb>
set/spider
set/dxnet
set/clx
set/arcluster
-</verb>
+</verb></tscreen>
To see what your nodes are set to, use the <em>show/nodes</em> command.
of output from a command is more than this. The default is 20. Setting it
explicitly to 0 will disable paging.
-<verb>
+<tscreen><verb>
SET/PAGE 30
SET/PAGE 0
-</verb>
+</verb></tscreen>
The setting is stored in your user profile.
done a SET/LOCATION then your latitude and longitude will be set roughly
correctly (assuming your locator is correct ;-). For example:-
-<verb>
+<tscreen><verb>
SET/QRA JO02LQ
-</verb>
+</verb></tscreen>
<sect1>set/qth (0)
<P>
Tell the system where your are. For example:-
-<verb>
+<tscreen><verb>
set/qth East Dereham, Norfolk
-</verb>
+</verb></tscreen>
<sect1>set/talk (0)
Allow WX information to be seen at your console. You can switch off
WX messages with the <em>unset/wx</em> command.
+<sect1>show/baddx (1)
+
+<P>
+<tt>
+<bf>show/baddx</bf>Show all the bad dx calls in the system
+</tt>
+
+<P>
+Display all the bad dx callsigns in the system, see SET/BADDX
+for more information.
+
<sect1>show/badnode (6)
<P>
Display all the bad node callsigns in the system, see SET/BADNODE
for more information.
+<sect1>show/badspotter (1)
+
+<P>
+<tt>
+<bf>show/badspotter</bf> Show all the bad spotters in the system
+</tt>
+
+<P>
+Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
+for more information.
+
+<sect1>show/configuration (0)
+
+<P>
+<tt>
+<bf>show/configuration [<node>]</bf> Show all visible nodes and their users
+</tt>
+
+<P>
+This command allows you to see all the users that can be seen
+and the nodes to which they are connected. With the optional <em>node</em>,
+you can specify a particular node to look at.
+
+This command is normally abbreviated to: sh/c
+
+BE WARNED: the list that is returned can be VERY long
+
+<sect1>show/configuration/node (0)
+
+<P>
+<tt>
+<bf>show/configuration/node</bf> Show all the nodes connected
+</tt>
+
+<P>
+Show all the nodes connected locally and the nodes they have connected.
+
+<sect1>show/connect (1)
+
+<P>
+<tt>
+<bf>show/connect</bf> Show all the active connections
+</tt>
+
+<P>
+This command shows information on all the active connections known to
+the node. This command gives slightly more information than WHO.
+
<sect1>show/date (0)
<P>
then it will show UTC and UTC + the local offset (not including DST) at
the prefixes or callsigns that you specify.
+<sect1>show/debug (9)
+
+<P>
+<tt>
+<bf>show/debug</bf> Show what levels of debug you are logging
+</tt>
+
+<P>
+The levels can be set with <em>set/debug</em>
+
<sect1>show/dx (0)
<P>
In addition you can add any number of these options in very nearly
any order to the basic SHOW/DX command, they are:-
-<verb>
+<tscreen><verb>
on <band> - eg 160m 20m 2m 23cm 6mm
on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
qra [<locator>] - this will look for the specific locator if
you specify one or else anything that looks like a locator.
-</verb>
+</verb></tscreen>
e.g.
-<verb>
+<tscreen><verb>
SH/DX 9m0
SH/DX on 20m info iota
SH/DX 9a on vhf day 30
SH/DX iota
SH/DX iota eu-064
SH/DX qra jn86
-</verb>
+</verb></tscreen>
<sect1>show/dxcc (0)
The options for SHOW/DX also apply to this command.
e.g.
-<verb>
+<tscreen><verb>
SH/DXCC G
SH/DXCC W on 20m info iota
-</verb>
+</verb></tscreen>
<sect1>show/files (0)
available on the system. To see the contents of a particular file
area type:-
-<verb>
+<tscreen><verb>
SH/FILES <filearea>
-</verb>
+</verb></tscreen>
where <filearea> is the name of the filearea you want to see the
contents of.
You can also use shell globbing characters like '*' and '?' in a
string to see a selection of files in a filearea eg:-
-<verb>
+<tscreen><verb>
SH/FILES bulletins arld*
-</verb>
+</verb></tscreen>
See also TYPE - to see the contents of a file.
Show a list of callsigns that have been excluded (locked out) of the
cluster locally with the <em>set/lockout</em> command
+<sect1>show/log (8)
+
+<P>
+<tt>
+<bf>show/log [<callsign>]</bf> Show excerpts from the system log
+</tt>
+
+<P>
+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.
+
<sect1>show/moon (0)
<P>
For example:-
-<verb>
+<tscreen><verb>
SH/MOON
SH/MOON G1TLH W5UN
-</verb>
+</verb></tscreen>
<sect1>show/muf (0)
can specify anything up to 24 hours worth of data by appending the no of
hours required after the prefix. For example:-
-<verb>
+<tscreen><verb>
SH/MUF W
-</verb>
+</verb></tscreen>
produces:
-<verb>
+<tscreen><verb>
RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
Location Lat / Long Azim
UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
18 23 11.5 -35 mS0+ mS2 S3
19 0 11.2 -41 mS0+ mS2 S3
-</verb>
+</verb></tscreen>
indicating that you will have weak, fading circuits on top band and
80m but usable signals on 40m (about S3).
inputing:-
-<verb>
+<tscreen><verb>
SH/MUF W 24
-</verb>
+</verb></tscreen>
will get you the above display, but with the next 24 hours worth of
propagation data.
-<verb>
+<tscreen><verb>
SH/MUF W L 24
SH/MUF W 24 Long
-</verb>
+</verb></tscreen>
Gives you an estimate of the long path propagation characterics. It
should be noted that the figures will probably not be very useful, nor
given on the command line) the distance and beraing from your station
to the locator. For example:-
-<verb>
+<tscreen><verb>
SH/QRA IO92QL
SH/QRA JN06 IN73
-</verb>
+</verb></tscreen>
The first example will show the distance and bearing to the locator from
yourself, the second example will calculate the distance and bearing from
using this command with a latitude and longitude as an argument, for
example:-
-<verb>
+<tscreen><verb>
SH/QRA 52 41 N 0 58 E
-</verb>
+</verb></tscreen>
<sect1>show/qrz (0)
and returns any information available for that callsign. This service
is provided for users of this software by http://www.qrz.com
+<sect1>show/route (0)
+
+<P>
+<tt>
+<bf>show/route <callsign></bf> Show the route to <callsign>
+</tt>
+
+<P>
+This command allows you to see to which node the callsigns specified are
+connected. It is a sort of inverse sh/config.
+
+<tscreen><verb>
+ sh/route n2tly
+</verb></tscreen>
+
<sect1>show/satellite (0)
<P>
So for example:-
-<verb>
+<tscreen><verb>
SH/SAT AO-10
SH/SAT FENGYUN1 12 2
-</verb>
+</verb></tscreen>
<sect1>show/sun (0)
For example:-
-<verb>
+<tscreen><verb>
SH/SUN
SH/SUN G1TLH K9CW ZS
-</verb>
+</verb></tscreen>
<sect1>show/time (0)
with others to obscure your reply for any watchers. For example (and
these values are for explanation :-):
-<verb>
+<tscreen><verb>
password = 012345678901234567890123456789
> sysop
22 10 15 17 3
-</verb>
+</verb></tscreen>
you type:-
-<verb>
+<tscreen><verb>
aa2bbbb0ccc5ddd7xxx3n
or 2 0 5 7 3
or 20573
-</verb>
+</verb></tscreen>
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
If you want to do something (such as send a spot) you precede the normal
command with a '/' character, eg:-
-<verb>
+<tscreen><verb>
/DX 14001 G1TLH What's a B class licensee doing on 20m CW?
/HELP talk
-</verb>
+</verb></tscreen>
To leave talk mode type:
-<verb>
+<tscreen><verb>
/EX
-</verb>
+</verb></tscreen>
<sect1>type (0)
filearea 'bulletins' you want to look at file 'arld051' you would
enter:-
-<verb>
+<tscreen><verb>
TYPE bulletins/arld051
-</verb>
+</verb></tscreen>
See also SHOW/FILES to see what fileareas are available and a
list of content.
projects / spider.git / blobdiff