Table of Contents
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1. Linux Installation
-
1.1 Introduction
1.2 Preparation
1.3 Installing the software
1.6 Starting up for the first time
2. Linux quick installation guide
-
3. Setting up the AX25 Utilities
-
3.1 Getting Started
3.2 The kernel
3.3 Installing the RPM's
3.10 Getting it all running
4. Configuration
-
4.1 Allowing ax25 connects from users
4.2 Allowing telnet connects from users
4.3 Setting up telnet connects (from 1.47 onwards)
4.9 Autostarting the cluster
5. Microsoft Windows Installation
-
5.1 Introduction
5.2 The requirements
5.3 The system
5.6 Getting Spider
6. Installing the software
-
6.1 Incoming telnets
6.2 The AGW packet engine
6.3 Setting up the initial user files
6.4 Connecting to other clusters
7. General Information
-
7.1 The crontab file
______________________________________________________________________
+
+
1. Linux Installation
1.1. Introduction
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 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.
Here are exactly the commands you must issue next: -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
# tar xvfz /usr/local/packages/Data-Dumper-2.10.tar.gz
# cd Data-Dumper-2.10
-
Do not fall into the trap of thinking they're all the same, just
because they nearly are! Pay particular attention to the instructions
of IO, above.
-
-
For SuSE distributions, the command would be ..
-
-
Now set a password for the user ...
-
-
1.3. Installing the software
Now to unpack the DX Spider distribution, set symbolic links and group
-
-
If you do not have the command groupadd available to you simply add a
line in /etc/group by hand.
-
-
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
in /etc/group should look something like this
-
-
This last step allows various users of the group spider to have write
access to all the directories. This is not really needed just yet but
will be useful when web interfaces start to appear.
-
-
1.4. Setting callsigns etc
Now login to your machine as the user you created earlier. In my case
-
-
Using the distributed DXVars.pm as a a template, set your cluster
callsign, sysop callsign and other user info to suit your own
environment.
-
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.
-
-
Now type the following command which creates the basic user file with
you as the sysop.
-
-
1.5. The client program
In earlier versions of Spider, all the processes were Perl scripts.
-
-
If all is well then login on another term or console as sysop and cd
to /spider/src. Now issue the following command ...
-
-
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
cluster callsign is set in the DXVars.pm file in /spider/local. In
-
-
If you do, congratulations! If not, look over the instructions again,
you have probably missed something out. You can shut spider down
again with the command ....
-
-
and both the cluster and the client should return to Linux prompts.
-
-
-
2. Linux quick installation guide
This section is designed for experienced Spider sysops who want to
-
o libax25-0.0.7-7.i386.rpm
o ax25-tools-0.0.6-13.i386.rpm
-
-
3.4. Configuration
You will find the configuration files in /etc/ax25. These consist of
-
-
Note that the portnames have to be unique.
-
3.6. nrports
This file sets up the netrom ports you want to use. An example is
-
-
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 ...
-
3.8. ax25d.conf
This file controls any incoming ax25 and NET/ROM connections and
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[gb7mbc-0 via 2m]
parameters 2 1 6 900 * 15 0
NOCALL * * * * * * L
-
-
There are a few things to take note of here. Firstly, all ax25
sections are wrapped in [ ] and all NET/ROM sections are wrapped in <
>. Secondly you should be able to see that anyone who forgets to set
-
-
however, if you wish your users to be able to use SSID's on their
callsigns ..
-
-
-
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
-
-
3.9. node.conf
For those of you that wish to run the node, you need to set up the
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
# /etc/ax25/node.conf - LinuxNode configuration file
#
# see node.conf(5)
-
-
This should be fairly obvious I hope.
-
-
Assuming that 44.131.96.199 is your IP address. The devices ttyS0 and
ttyS1 are com1 and com2 respectively. Now we can set some parameters
...
-
-
The command 'man kissparms' will give you the explanation of the
switches.
-
-
All should now be running. All that remains is to get the node
working for telnet connections. If nothing else, this will allow you
to connect to the node yourself to check on connection status etc.
-
-
Assuming you want it to run on port 3000
-
-
You now need to restart the xinetd daemon. First find out what the
PID is like so ..
-
You will get a reply something like this ...
-
-
The PID or Process ID is 592 in this case so now we can issue the
command ...
-
-
All should now be operational and you should be able to log into the
node by using a telnet session to the relevant port, like so ...
-
-
If that works, you are just about there. you should (assuming you
have radios connected to the TNC's) be able to connect out to other
stations and receive incoming ax25 and netrom connections.
-
-
Then add a line in /etc/inetd.conf like this ....
spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
-
-
Once this is done, you need to restart inetd like this ....
-
-
Now login as sysop and cd spider/src. You can test that spider is
accepting telnet logins by issuing the following command ....
-
-
You should get a login prompt and on issuing a callsign, you will be
given access to the cluster. Note, you will not get a password login.
There seems no good reason for a password prompt to be given so it is
-
-
You should now get the login prompt and be able to login as before.
-
-
-
to make the change happen...
-
-
As standard, the listener will listen on all interfaces
simultaneously. If you require more control than this, you can
specify each interface individually:-
-
-
This will only be successful if the IP addresses on each interface are
static. If you are using some kind of dynamic IP addressing then the
'default' method is the only one that will work.
-
4.5. Setting up node connects
In order to allow cluster node connections, spider needs to know that
-
-
For now, we will assume that the cluster we are going to connect to is
an AK1A type node.
-
-
The case does not matter as long as you have a version of DXSpider
later than 1.33. Earlier versions required the callsign to be in
upper case.
-
You should get an initialisation string from DXSpider like this ...
-
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
be outgoing then a connection script needs to be written.
-
-
4.6. Connection scripts
Because DXSpider operates under Linux, connections can be made using
-
-
-
-
-
timeout 60
abort (Busy|Sorry|Fail)
# this does exactly the same as the previous example
-
-
-
-
-
timeout 15
connect telnet dirkl.tobit.co.uk
# tell GB7DJK-1 that it is connected to GB7DJK
-
-
This will start a connection using the script called gb7djk-1. You
can follow the connection by watching the term or console from where
you started cluster.pl. From version 1.47 onwards, you will need to
-
-
With later versions of Spider there is a set/login command for users.
This tells them when a user or node logs in or out. If you do not add
a line to your scripts after the final line (or before the client line
-
-
4.8. Telnet echo
Cluster links in particular suffer greatly from the presence of telnet
-
-
So, the first connection is made by Spider. This is fine as Spider
uses the Net_Telnet script from within perl. This actually uses TCP
rather than TELNET so no negotiation will be done on the first
-
-
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 ...
-
-
The line required for Slackware distributions is slightly different.
My thanks to Aurelio, PA3EZL for this information.
-
-
This will automatically start DXSpider on tty7 (ALT-F7) on bootup and
restart it should it crash for any reason.
-
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>ppm install Data-Dumper.ppd
Installing package 'Data-Dumper.ppd'
Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs
-
I'm not going to bother you with exhaustive details of the rest of
them, but suffice it to say you need to:
-
If all that seemed to work OK, time to move along. Before anyone who
is familiar with PPM tells me that we didn't need to download and keep
those files locally, I knew that. I also knew that PPM is sometimes
-
Now you'll need to edit this file using a text editor like Notepad. If
nothing else, you can simply
-
and then
-
to bring up an editor window containing the file. As an absolute
minimum you must adjust the following items in DXVars.pm:-
-
The following line need attention:-
-
On my machine, I've simply uncommented the "0.0.0.0" entry by removing
the '#' from the front of the line.
-
and then
-
to bring up an editor window containing the file. You must consider
adjusting the following items in AGWConnect.pm:-
-
If all goes according to plan, you will see no output from this
program, and after a brief wait, your DOS prompt will be returned.
-
If you did everything you were told, your DOS window will now hold a
display which looks something like:-
-
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)
-
If you are running Windows NT, 2000 or XP then winclient.pl does not
work. We don't know why other than this seems to be some kind of
incomaptibility in perl. You can achieve the same thing by telnetting
-
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
-
You've arrived. Try some commands, and see how they feel. (In case you
were wondering, "Iain", "M0ADI" and "GB7SJP" all came from the version
of DXVars.pm that was on the machine when I started the winclient.pl)
-
-
The callsign involved will be the callsign of the cluster node you are
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
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
projects / spider.git / blobdiff