- 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.1
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.
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
# 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
projects / spider.git / blobdiff