The DXSpider Installation and Administration Manual
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.33 (Revision 1.21) February 2001
+ Version 1.33 (Revision 1.22) March 2001
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
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
+ $ ./cluster.pl
DXSpider DX Cluster Version 1.46
Copyright (c) 1998 Dirk Koopman G1TLH
loading prefixes ...
-
- $ 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
..
- default * * * * * * - sysop /spider/src/client client %s ax25
+ default * * * * * * - sysop /spider/src/client client %s ax25
- client.pl login telnet
+ ./client.pl login telnet
+
You should now get the login prompt and be able to login as before.
+
+
3\b3.\b.3\b3.\b. S\bSe\bet\btt\bti\bin\bng\bg u\bup\bp n\bno\bod\bde\be c\bco\bon\bnn\bne\bec\bct\bts\bs
In order to allow cluster node connections, spider needs to know that
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
- PC38^GB7MBC^~
-
-
-
+ ./client.pl gb7baa
+ PC38^GB7MBC^~
If the callsign you just set up as a cluster node is for an incoming
connect, this is all that needs to be done. If the connection is to
-
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.
- timeout 60
- abort (Busy|Sorry|Fail)
- # don't forget to chmod 4775 netrom_call!
- connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
- # you can leave this out if you call the script 'gb7dxm'
- client gb7dxm ax25
+
+
+ timeout 60
+ abort (Busy|Sorry|Fail)
+ # don't forget to chmod 4775 netrom_call!
+ connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
+ # you can leave this out if you call the script 'gb7dxm'
+ client gb7dxm ax25
+
+
+
+
+
<- D G1TLH connect gb7djk-1
-> D G1TLH connection to GB7DJK-1 started
-> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
- 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