The DXSpider Installation and Administration Manual
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.33 (Revision 1.20) February 2001
+ Version 1.33 (Revision 1.22) March 2001
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
1\b1.\b.1\b1.\b. I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
- This section describes the installation of DX Spider v1.35 on a RedHat
- Linux Distribution. I do not intend to try and cover the installation
- of Linux or the setup of the AX25 utilities. If you need help on this
- then read Iains original HOWTO on the DXSpider website.
+ This section describes the installation of DX Spider v1.46 on a RedHat
+ Linux Distribution. Wherever possible I will try to include
+ differences for other distributions. I do not intend to try and cover
+ the installation of Linux or the setup of the AX25 utilities. If you
+ need help on this then read Iains original installation guide that
+ comes with the Spider distribution.
I am assuming a general knowledge of Linux and its commands. You
editor.
- The crucial ingredient for all of this is Perl 5.004. Now I know Perl
- 5.005 is out and this will almost certainly work with it, but RedHat
- 5.1 comes with 5.004. _\bB_\be _\bW_\ba_\br_\bn_\be_\bd, earlier versions of RedHat d\bdo\bo n\bno\bot\bt
- come with 5.004 as standard, you need to upgrade
+ The crucial ingredient for all of this is Perl. Earlier versions of
+ Spider required perl 5.004, however it is now _\bS_\bT_\bR_\bO_\bN_\bG_\bL_\bY recommended
+ that you use at least version 5.005_03 as this is the version being
+ used in the development of Spider.
In addition to the standard Red Hat distribution you will require the
- following CPAN modules: -
+ following modules from http://www.cpan.org/CPAN.html ...
+\bo Data-Dumper-2.10.tar.gz
- +\bo FreezeThaw-0.3.tar.gz
-
- +\bo MLDBM-2.00.tar.gz
-
+\bo TimeDate-1.08.tar.gz
+\bo IO-1.20.tar.gz
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.
# 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)
- # vi /etc/group (or your favorite editor)
-
-
-
+ # vi /etc/group (or your favorite editor)
You also need to add some others to the group, including your own
callsign (this will be used as an alias) and root. The finished line
alter the text of any section. Some of the lines look a little odd.
Take this line for example ....
+
$myemail = "ianmaude\@btinternet.com";
P\bPL\bLE\bEA\bAS\bSE\bE U\bUS\bSE\bE C\bCA\bAP\bPI\bIT\bTA\bAL\bL L\bLE\bET\bTT\bTE\bER\bRS\bS F\bFO\bOR\bR C\bCA\bAL\bLL\bLS\bSI\bIG\bGN\bNS\bS
- DON'T alter the DXVars.pm (or any other file) in /spider/perl, they
- are overwritten with every release. Any files or commands you place in
- /spider/local or /spider/local_cmd will automagically be used in
- preference to the ones in /spider/perl EVEN while the cluster is
- running!
+ DON'T alter any file in /spider/perl, they are overwritten with every
+ release. Any files or commands you place in /spider/local or
+ /spider/local_cmd will automagically be used in preference to the ones
+ in /spider/perl EVEN while the cluster is running!
Save the new file and change directory to ../perl ....
- $ create_sysop.pl
+ $ ./create_sysop.pl
- $ 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 ...
If all is well then login on another term or console as _\bs_\by_\bs_\bo_\bp and cd
to /spider/perl. Now issue the following command ...
- $ client.pl
-
+ $ ./client.pl
This should log you into the cluster as the sysop under the alias
callsign we set earlier. In this case the callsign is G0VGS. The
+ or, if you wish your users to be able to use SSID's on their callsigns
+ ..
+
+
+
+ default * * * * * * - sysop /spider/src/client client %s ax25
- client.pl login telnet
+ ./client.pl login telnet
That is now set, it is as simple as that. To prove it, login on yet
- another console as sysop and issue the command ...
+ another console as sysop, cd to spider/perl and issue the command ...
- client.pl gb7baa (using the callsign you set as a node)
+ ./client.pl gb7baa (using the callsign you set as a node)
- client.pl gb7baa
+ ./client.pl gb7baa
PC38^GB7MBC^~
If the callsign you just set up as a cluster node is for an incoming
- This line works fine for RedHat and SuSE distributions. The line
- required for Slackware distributions is slightly different. My thanks
- to Aurelio, PA3EZL for this information.
+ This line works fine for RedHat distributions. It is also fine for
+ SuSE up to 7.0. From Suse 7.1 you need to add runlevels 2 and 5 like
+ this ...
+
+
+
+ DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
+
+
+
+
+
+ The line required for Slackware distributions is slightly different.
+ My thanks to Aurelio, PA3EZL for this information.
website at the cron page where it is explained more fully.
+
+
+
5\b5.\b. H\bHo\bop\bp c\bco\bon\bnt\btr\bro\bol\bl
Starting with version 1.13 there is simple hop control available on a
- #
- # hop table construction
- #
- package DXProt;
- # default hopcount to use
- $def_hopcount = 5;
- # some variable hop counts based on message type
- %hopcount =
- (
- 11 => 10,
- 16 => 10,
- 17 => 10,
- 19 => 10,
- 21 => 10,
- );
- # the per node hop control thingy
- %nodehops =
- GB7ADX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- GB7UDX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- GB7BAA => {
- 11 => 5,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- };
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ #
+ # hop table construction
+ #
+
+ package DXProt;
+
+ # default hopcount to use
+ $def_hopcount = 5;
+
+ # some variable hop counts based on message type
+ %hopcount =
+ (
+ 11 => 10,
+ 16 => 10,
+ 17 => 10,
+ 19 => 10,
+ 21 => 10,
+ );
+
+
+ # the per node hop control thingy
+
+
+ %nodehops =
+
+ GB7ADX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+
+ GB7UDX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ GB7BAA => {
+ 11 => 5,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ };
will bring your changes into effect.
+
5\b5.\b.2\b2.\b. I\bIs\bso\bol\bla\bat\bti\bin\bng\bg n\bne\bet\btw\bwo\bor\brk\bks\bs
It is possible to isolate networks from each other on a "gateway" node
+
+
+
+
+
0 = frequency
1 = call
2 = date in unix format
projects / spider.git / blobdiff