- The DXSpider Installation Manual v1.49
- Iain Philipps, G0RDI (g0rdi@77hz.com) and Ian Maude, G0VGS,
- (g0vgs@gb7mbc.net)
- February 2002 revision 1.2
+ The DXSpider Installation Manual v1.50
+ Iain Philipps, G0RDI (g0rdi@77hz.com), Ian Maude, G0VGS,
+ (g0vgs@gb7mbc.net) and Charlie Carroll, K1XX,
+ (k1xx@ptcnh.net)
+ September 2002 revision 0.4
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
-
1. Linux Installation
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
4.2. Allowing telnet connects from users
- From version 1.47 there is a new (more efficient) way of doing this
+ >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.
4.3. Setting up telnet connects (from 1.47 onwards)
- From version 1.47 you can choose to allow the perl cluster.pl program
+ >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.
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.
IMPORTANT:
What you'll be left with once you've followed these instructions is
- (hopefully) a working DX Spider v1.47 system that is capable of
- accepting or originating "internet" connections, plus inbound AX.25
- and TCP/IP radio connections. If the absence of outbound radio
- connections is a serious limitation for you, it would be better for
- you to wait a couple more weeks until this support has been added.
+ (hopefully) a working DX Spider v1.50 system that is capable of
+ accepting or originating "internet" connections, plus inbound and
+ outbound AX.25 and TCP/IP radio connections.
On the other hand, you may have an enquiring mind, or better yet, may
be looking for a useful way of connecting your current (perhaps) AK1A
Install your chosen Perl environment. Unless you have a very good
reason for not doing so, I strongly suggest that you use ActivePerl
- v5.6. For my testing & development, I used build 623. You can get
- this from:-
+ v5.6. For my testing & development, I used build 623. (A recent
+ installation used the newer ActivePerl v5.6.1, build 633 without any
+ noticable difficulty.) You can get this from:
http://www.activestate.com/Products/ActivePerl/Download.html
- You will need to choose either the MSI or the AS package. My
- recommendation is that you choose the MSI package and deal with the
- consequences if your system isn't equipped with support for the latest
- MS Installer; you'll be better off in the long run. The build 623
- download is 7,460 KB, so now is a really good time to have some tea if
- you're on a slow dial-up connection.
+
+ The link takes you to an initial page of System Requirements and
+ Software Prerequisites. If you do not have it already installed, you
+ can download and install the Windows Installer 2.0 for a Win98
+ installation. Be forewarned, you will have to reboot your PC at the
+ completion of the installer's installation.
+
+ If you already have the installer on your PC, simply click on the Next
+ arrow at the bottom of the page. Two clicks will finally get you to
+ the actual download page. The MSI version of Build 633 is now 8.6MB
+ in size, so make that a big cup of tea or coffee if you're on a slow
+ dial-up connection.
During installation, please ensure that you do choose the options to
"Add Perl to the PATH environment variable" and "Create Perl file
- Make yourself a convenient directory to unpack all of these zip files
- into (I put mine in "D:\ppm>") and do the following (the bits you type
- in are blue ). Note that where these files land will be directly
+ If this is a new installation, now would also be a good time to
+ install a copy of WinZip on your PC. Make yourself a convenient
+ directory to unpack all of these zip files into (I put mine in
+ "D:\ppm>" but "C:\ppm" works just as well.) and do the following (the
+ bits you type in are blue ). You can upzip all of the files into the
+ same directory. When prompted, simply overwrite the Readme file from
+ each zip package. Note that where these files land will be directly
related to where you chose to install your ActivePerl (mine, as you
can probably guess from what follows, went into "D:\Perl"):-
- 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>
5.6. Getting Spider
Get the current version of the DX Spider distribution. This needs to
- be v1.47 or later. You've got two ways (currently) of getting this;
+ be v1.50 or later. You've got two ways (currently) of getting this;
either get a CVS update from sourceforge (if you don't know what this
- is, then it isn't for you) or get the latest "official" release from:-
+ is, then it isn't for you) or get the latest "official" release from:
http://www.dxcluster.org/download/index.html
The only difference between "CVSlatest.tgz" and the latest "official"
- release version is that it is more up to date. Don't confuse this TGZ
- file with "Downloading from Sourceforge with CVS" - they are two quite
- different things.
-
-
- If you went down the CVS route (ie installed wincvs and downloaded
- from sourceforge), then everything will be nicely set out on your
- local disk. If you got the TGZ file, unpack it to somewhere
- convenient. The following examples assume that you put it on drive
+ release version is that it is more up to date. Do not confuse the
+ "CVSlatest.tgz" file with "Downloading from Sourceforge with CVS" -
+ they are two quite different things. "Downloading from Sourceforge
+ with CVS" is explained in a section within the Admin manual.
+
+
+ If you go down the CVS route (ie installing WinCVS as explained in the
+ Admin manual and downloaded from sourceforge), then everything will be
+ nicely installed on your local disk. If you got the CVSlatest.tgz
+ file, unzip (winzip) it to "C:\". This is an important point since
+ paths are included within the .tgz file. Make sure you unzip to the
+ root directory of whichever drive you use... "C:\" or "D:\" or ..,
+ not "C:\spider." If you double click on CVSlatest.tgz, WinZip should
+ open with a dialogue box that says the Archive contains a single file
+ (CVSlatest.tar) and asks whether WinZip should decompress it to a
+ temporary fold and then open it. Say "Yes" and then you will get the
+ typical Classical WinZip listing of files ready for extraction.
+ Remember, extract them to your desired root directory ("C:\" or "D:\"
+ or ...). 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.
-
-
6. Installing the software
- Ensure that your CVS session or your WINunZIPped file have left you
- with a directory "C:\spider\local" and C:\spider\local_cmd"; if not,
- go to "C:\spider\" and create them. If "C:\spider" is missing, go back
- and figure out why, because it shouldn't be.
-
+ At this point you will need to create 2 additional directories under
+ "C:\Spider." Make directories "C:\spider\local" and
+ "C:\spider\local_cmd". 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:-
- Now you'll need to edit this file using a text editor. If nothing
- else, you can simply
+ Now you'll need to edit this file using a text editor like Notepad. If
+ nothing else, you can simply
o $mylongitude - The station longitude in degrees and decimal
fractions
+
o $mylocator - The Maidenhead (or QRA) locator of the station
You really also ought to update the $myqth and $myemail variables. And
you must write them as "\@" or "\$".
-
6.1. Incoming telnets
If you want to enable inbound "TELNET" connections (or you are running
- Windows NT, 2000 or XP), you've got a little more work to do. From a
- handy "DOS box" that's not doing anything else, do the following:-
-
-
+ Windows 98, NT, 2000 or XP), you've got a little more work to do. From
+ a handy "DOS box" that's not doing anything else, do the following:-
- 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
- The following lines need attention:-
+ The following line need attention:-
- ["0.0.0.0", 7300],
+ # ["0.0.0.0", 7300],
On my machine, I've simply uncommented the "0.0.0.0" entry by removing
the '#' from the front of the line.
- You MUST carry out this step if you are running on a Windows NT, 2000
- or XP based system
+ You MUST carry out this step if you are running on a Windows 98, NT,
+ 2000 or XP based system
If you don't have a static hostname for your machine, and you intend
to allow folk to connect to your machine across the internet, then I'd
suggest you pay a visit to www.dyndns.org and create one for yourself.
- While it's free, it will take a modest an amount of effort on your
- part to read, understand and implement what needs to be done to set
- this up.
+ While it's free, it will take a modest amount of effort on your part
+ to read, understand and implement what needs to be done to set this
+ up.
If your machine is connected to the internet and you don't want to
6.2. The AGW packet engine
On the assumption that you'll be using the SV2AGW Packet Engine to
- interface your radios to the cluster, you should now create your own
- local copy of AGWConnect.pm by:-
+ interface your radios to the cluster, it would be a good idea to
+ download the Packet Engine software! You can get this software from:
+
+ http://www.raag.org/sv2agw/agwpe.zip
+
+ Depending upon your TNCs, you may also need to get:
+
+ http://www.raag.org/sv2agw/drivers.zip
+
+ A couple of the tools:
+
+ http://www.raag.org/sv2agw/agwterm.zip
+
+ http://www.raag.org/sv2agw/agwmonitor.zip
+
+ will also help with troubleshooting of the RF links themselves.
+
+ Install and configure AGWPE. You should now create your own local
+ copy of AGWConnect.pm by:-
o $passwd - password that matches $login
+ The login ID and passwd only need to be set if you are accessing AGW
+ separately via its web interface. This interface is normally not
+ needed for use with DXSpider.
+
6.3. Setting up the initial user files
following:-
-
perl cluster.pl
- DXSpider DX Cluster Version 1.47
- Copyright (c) 1998-2001 Dirk Koopman G1TLH
+ DXSpider DX Cluster Version 1.50
+ Copyright (c) 1998-2002 Dirk Koopman G1TLH
loading prefixes ...
loading band data ...
loading user file system ...
-
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)
On getting the login: prompt, enter your sysop callsign (the one you
put in DXVars.pm as $myalias).
-
-
I would recommend strongly that you obtain a better telnet client than
that which comes with windows (I use PuTTY).
- Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.47
+ Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.50
Cluster: 1 nodes, 1 local / 1 total users Max users 2 Uptime 0 00:00
M0ADI de GB7SJP 4-Mar-2001 1511Z >
going to connect to. This will now check every 10 minutes to see if
gb7xxx is connected, if it is then nothing will be done. If it is
not, then a connect attempt will be started.
-
-
There are probably lots of other things you could use this crontab
file for. If you want to know more about it, look at the DXSpider
website at the cron page where it is explained more fully.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
projects / spider.git / blobdiff