- The DXSpider Installation Manual v1.49
+ The DXSpider Installation Manual v1.50
Iain Philipps, G0RDI (g0rdi@77hz.com) and Ian Maude, G0VGS,
(g0vgs@gb7mbc.net)
- February 2002 revision 1.2
+ July 2002 revision 0.3
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
1.1. Introduction
- This section describes the installation of DX Spider v1.47 on a RedHat
+ This section describes the installation of DX Spider v1.50 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.
-
-
+ differences for other distributions.
I am assuming a general knowledge of Linux and its commands. You
should know how to use tar and how to edit files using your favourite
editor.
In addition to the standard Red Hat distribution you will require the
- following modules from http://www.cpan.org/CPAN.html , please note
- however that with later versions of perl, some of these modules may be
- included with the distribution. Get the modules anyway and try to
- install as below. If they complain, they are probably already a part
- of your perl distribution.
+ following modules from http://www.cpan.org/modules/by-module/ , please
+ note however that with later versions of perl, some of these modules
+ may be included with the distribution. Get the modules anyway and try
+ to install as below. If they complain, they are probably already a
+ part of your perl distribution.
o Time-HiRes-01.20.tar.gz
+ o Digest-SHA1-2.01.tar.gz
+
Copy the CPAN modules listed above to a convenient place on your
computer. One good place would be /usr/local/packages, and the
+
+
+
# make test
# make install
# cd ..
+ #
+ # tar xvfz /usr/local/packages/Digest-SHA1-2.01.tar.gz
+ # cd Digest-SHA1-2.01
+ # perl Makefile.PL
+ # make test
+ # make install
+ # cd ..
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.47 for this section but of course you would use the latest
+ version 1.50 for this section but of course you would use the latest
version.
your own choice.
+
# adduser -m sysop
- For SUSE distributions, the command would be ..
+ For SuSE distributions, the command would be ..
# cd ~sysop
- # tar xvfz spider-1.47.tar.gz
+ # tar xvfz spider-1.50.tar.gz
# ln -s ~sysop/spider /spider
# groupadd -g 251 spider (or another number)
The next step is to set the permissions on the Spider directory tree
and files ....
+
+
# chown -R sysop.spider spider
# find . -type d -exec chmod 2775 {} \;
# find . -type f -exec chmod 775 {} \;
-
This is the call sign of your cluster. If you use an SSID then
include it here also.
+
+
This is the sysop user callsign, normally your own.
use it though it has to be "made". CD to /spider/src and type make.
You should see the output on your screen and hopefully now have a
small C program called client. Leave it in this directory.
-
-
-
1.6. Starting up for the first time
We can now bring spider up for the first time and see if all is well
-
- $ ./cluster.pl
- DXSpider DX Cluster Version 1.47
- Copyright (c) 1998 Dirk Koopman G1TLH
- loading prefixes ...
- loading band data ...
- loading user file system ...
- starting listener ...
- reading existing message headers
- reading cron jobs
- orft we jolly well go ...
+ $ ./cluster.pl
+ DXSpider DX Cluster Version 1.50
+ Copyright (c) 1998 Dirk Koopman G1TLH
+ loading prefixes ...
+ loading band data ...
+ loading user file system ...
+ starting listener ...
+ reading existing message headers
+ reading cron jobs
+ orft we jolly well go ...
+
+
+
2. Linux quick installation guide
This section is designed for experienced Spider sysops who want to
as standard. The other is AWZNode by IZ5AWZ.
+ NB: The AX25 stuff in 2.4 kernels appears to have been broken until
+ 2.4.18. I strongly suggest you get at least this kernel.
+
+
For 2.4 kernels you need these files...
+
o libax25-0.0.7-7.i386.rpm
o ax25-tools-0.0.6-13.i386.rpm
NOTE:- before we start it is important to realise that every interface
requires a different SSID. You should be able to follow this in the
following examples.
-
-
3.5. axports
This file sets up the ax25 ports you want to use. An example is below
+
+
Note that the portnames have to be unique.
+
+
+
3.7. nrbroadcast
This file sets up the netrom broadcast qualities. An example is below
The file headings are as follows ...
-
axport - The port name in axports that you wish to broadcast
NET/ROM on.
min_obs - The minimum obsolescence value for the port
- [gb7mbc-0 via 2m]
- parameters 2 1 6 900 * 15 0
- NOCALL * * * * * * L
- default * * * * * * - sysop /spider/src/client client %u ax25
- [gb7mbc-1 via 2m]
- parameters 2 1 6 900 * 15 0
- NOCALL * * * * * * L
- default * * * * * * 0 root /usr/sbin/node node
- [gb7mbc-0 via 4m]
- parameters 2 1 6 900 * 15 0
- NOCALL * * * * * * L
- default * * * * * * - sysop /spider/src/client client %u ax25
- [gb7mbc-1 via 4m]
- parameters 2 1 6 900 * 15 0
- NOCALL * * * * * * L
- default * * * * * * 0 root /usr/sbin/node node
- <netrom2>
- parameters 1 10 * * * 3 *
- NOCALL * * * * * * L
- default * * * * * * - sysop /spider/src/client client %u ax25
- <netrom>
- parameters 1 10 * * * 3 *
- NOCALL * * * * * * L
- default * * * * * * 0 root /usr/sbin/node node
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ [gb7mbc-0 via 2m]
+ parameters 2 1 6 900 * 15 0
+ NOCALL * * * * * * L
+ default * * * * * * - sysop /spider/src/client client %u ax25
+
+ [gb7mbc-1 via 2m]
+ parameters 2 1 6 900 * 15 0
+ NOCALL * * * * * * L
+ default * * * * * * 0 root /usr/sbin/node node
+
+ [gb7mbc-0 via 4m]
+ parameters 2 1 6 900 * 15 0
+ NOCALL * * * * * * L
+ default * * * * * * - sysop /spider/src/client client %u ax25
+
+ [gb7mbc-1 via 4m]
+ parameters 2 1 6 900 * 15 0
+ NOCALL * * * * * * L
+ default * * * * * * 0 root /usr/sbin/node node
+
+ <netrom2>
+ parameters 1 10 * * * 3 *
+ NOCALL * * * * * * L
+ default * * * * * * - sysop /spider/src/client client %u ax25
+
+ <netrom>
+ parameters 1 10 * * * 3 *
+ NOCALL * * * * * * L
+ default * * * * * * 0 root /usr/sbin/node node
in interface order.
-
You should be able to see that the normal line for access to the
cluster is like this ..
+
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
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
# /etc/ax25/node.conf - LinuxNode configuration file
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
+ SuSE up to 7.0. From SuSE 7.1 you need to add runlevels 2 and 5 like
this ...
restart it should it crash for any reason.
+ NB: It should be noted that /dev/tty7 is only an example. Some SuSE
+ systems will only accept upto tty6. It really does not matter which
+ tty you run it on.
+
+
As root type the command telinit q. DXSpider should start up
immediately. You will see the output on tty7 and if you login as
sysop you should find everything running nicely.
- D:\ppm>ppm install Data-Dumper.ppd
- Installing package 'Data-Dumper.ppd'
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib
- Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html
- Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm
- Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist
- D:\ppm>
+
+
+
+
+
+ D:\ppm>ppm install Data-Dumper.ppd
+ Installing package 'Data-Dumper.ppd'
+ Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs
+ Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll
+ Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp
+ Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib
+ Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html
+ Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm
+ Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist
+ D:\ppm>
+
+
+
+
I'm not going to bother you with exhaustive details of the rest of
them, but suffice it to say you need to:
local disk. If you got the TGZ file, unpack it to somewhere
convenient. The following examples assume that you put it on drive
"C:\", for convenience.
-
-
You will need winzip to manipulate the TGZ files (they are bit like
ZIP files) if you are not using CVS.
go to "C:\spider\" and create them. If "C:\spider" is missing, go back
and figure out why, because it shouldn't be.
-
Now create your own local copy of the DXVars.pm file by:-
you must write them as "\@" or "\$".
-
6.1. Incoming telnets
If you want to enable inbound "TELNET" connections (or you are running
-
-
- copy \spider\perl\Listeners.pm \spider\local
- cd \spider\local
- notepad listeners.pm
+ copy \spider\perl\Listeners.pm \spider\local
+ cd \spider\local
+ notepad listeners.pm
- notepad AGWConnect.pm
+
+ notepad AGWConnect.pm
- DXSpider DX Cluster Version 1.47
- Copyright (c) 1998-2001 Dirk Koopman G1TLH
- loading prefixes ...
- loading band data ...
- loading user file system ...
- starting listeners ...
- Internal port: localhost 27754
- load badwords: Ok
- reading in duplicate spot and WWV info ...
- reading existing message headers ...
- load badmsg: Ok
- load forward: Ok
- load swop: Ok
- @msg = 0 before delete
- @msg = 0 after delete
- reading cron jobs ...v cron: reading /spider/cmd/crontab
- cron: adding 1 0 * * 0
- DXUser::export("$main::data/user_asc")
- reading database descriptors ...
- doing local initialisation ...
- orft we jolly well go ...
- queue msg (0)
+
+
+
+
+
+
+
+
+
+
+
+
+
+ DXSpider DX Cluster Version 1.47
+ Copyright (c) 1998-2001 Dirk Koopman G1TLH
+ loading prefixes ...
+ loading band data ...
+ loading user file system ...
+ starting listeners ...
+ Internal port: localhost 27754
+ load badwords: Ok
+ reading in duplicate spot and WWV info ...
+ reading existing message headers ...
+ load badmsg: Ok
+ load forward: Ok
+ load swop: Ok
+ @msg = 0 before delete
+ @msg = 0 after delete
+ reading cron jobs ...v cron: reading /spider/cmd/crontab
+ cron: adding 1 0 * * 0
+ DXUser::export("$main::data/user_asc")
+ reading database descriptors ...
+ doing local initialisation ...
+ orft we jolly well go ...
+ queue msg (0)
+
+
+
+
Now, if that's what you've got, you are very nearly home and dry (in
as far as these particular experiments are concerned, anyhow)
like:-
-
Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.47
Cluster: 1 nodes, 1 local / 1 total users Max users 2 Uptime 0 00:00
M0ADI de GB7SJP 4-Mar-2001 1511Z >
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
projects / spider.git / blobdiff