X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Finstallation.sgml;h=086cdb3883431bfcad47e26127bfa96b14ce7c0e;hb=9cfd05889c539c625a4fb3ee9fdbc0fea847452c;hp=2818cb06af529f9550f9ab078f8385c409f1a7ab;hpb=ad09cf7c29d54881a3e1bb4b8e5da30c2f58c4b6;p=spider.git diff --git a/sgml/installation.sgml b/sgml/installation.sgml index 2818cb06..086cdb38 100644 --- a/sgml/installation.sgml +++ b/sgml/installation.sgml @@ -4,10 +4,10 @@ -
In addition to the standard Red Hat distribution you will require the
-following modules from
+In addition to the standard Red Hat distribution you will require the
+following modules from
-Do get the latest versions of these packages and install them
-but use the above list as the earliest versions usable.
+Copy the CPAN modules listed above to a convenient place on your computer. One good
+place would be /usr/local/packages, and the instructions which follow will assume that
+that's where you have put them.
+
+
+Log in as 'root', and make sure you're at '/root' before you continue. Here are exactly the commands you must issue next: -
+
+
+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 ...
@@ -100,6 +163,7 @@ permissions. Copy the tarball to /home/sysop and do the following.
# groupadd -g 251 spider (or another number)
+
If you do not have the command groupadd available to you simply
add a line in /etc/group by hand.
@@ -107,6 +171,7 @@ add a line in /etc/group by hand.
# 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 in /etc/group
should look something like this
@@ -156,11 +221,31 @@ $ vi DXVars.pm (or your favourite editor)
Using the distributed DXVars.pm as a a template, set your cluster callsign,
-sysop callsign and other user info to suit your own environment. Note that
-this a perl file which will be parsed and executed as part of the cluster. If
-you get it wrong then perl will complain when you start the cluster process.
-It is important only to alter the text of any section. Some of the lines look
-a little odd. Take this line for example ....
+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.
+
+
+
+Note that this a perl file which will be parsed and executed as part of the
+cluster. If you get it wrong then perl will complain when you start the cluster
+process. It is important only to alter the text of any section. Some of the
+lines look a little odd. Take this line for example ....
$myemail = "ianmaude\@btinternet.com";
@@ -170,8 +255,6 @@ $myemail = "ianmaude\@btinternet.com";
There appears to be an extra slash in there. However this has to be there
for the file to work so leave it in.
-
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
@@ -193,6 +276,18 @@ the sysop.
$ ./create_sysop.pl
+
+In earlier versions of Spider, all the processes were Perl scripts. This
+was fine but with a lot of users your computer memory would soon be used up.
+To combat this a new client was written in "C". This client only works for
+incoming connects at the moment. Before you can 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.
+
+
@@ -230,6 +325,7 @@ was set as GB7MBC. You should therefore see this when you login ....
G0VGS de GB7MBC 19-Nov-1999 2150Z >
+
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 ....
@@ -241,17 +337,6 @@ shutdown
and both the cluster and the client should return to Linux prompts.
-
-In earlier versions of Spider, all the processes were Perl scripts. This
-was fine but with a lot of users your computer memory would soon be used up.
-To combat this a new client was written in "C". This client only works for
-incoming connects at the moment. Before you can 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.
-
Spider should now be running and you should be able to login using the
client program.
@@ -293,6 +379,7 @@ client program.
Spider should now be able to accept logins via telnet, netrom and ax25.
+The aim of this section is not to fully cover the installation
+and configuration of all the possible ax25 modules. I will
+attempt to cover a simple installation and configure 2 serial
+ports as if they had TNC's on them. I will also show what
+additional configuration the DXSpider program requires.
+
+
+Please bear in mind that I am basing this section on a RedHat
+7.1 distribution, if you are using SuSe or any other distibution
+then your mileage may vary. I will be happy to make any changes
+and additions if you email me any errors or distribution specific
+requirements.
+
+
+You would probably benefit from reading the
-As stated previously, the aim of this document is not to tell you how to
-configure Linux or the ax25 utilities. However, you do need to add a line
-in your ax25d.conf to allow connections to DXSpider for your users. For
-each interface that you wish to allow connections on, use the following format ...
+The following files are extracts from the working files at GB7MBC and
+are in daily use. However, there are many ways that you can configure the
+ax25 utils, this is just the one I use, it does not mean it is necessarily
+the best or for that matter, the right way!
+
+
+There are 2 things you need to do initially. You need to get the
+3 files required for the ax25 installation and you need to make
+some changes to the kernel configuration.
+
+
+The first thing is to get the versions of the ax25 utils that match
+your kernel. You may also wish to get a node package of some kind.
+There are 2 main node packages in use of which I shall keep to the
+original by Tomi Manninen, OH2BNS as this is included in the ax25
+rpms as standard. The other is
+For 2.4 kernels you need these files...
+
+
+
+First you need to add Amateur Radio Support to your kernel. This is
+a main menu item and should be easily found. Within this header you
+will find lots of options. For our purposes you need to enable
+Amateur Radio AX.25 Level 2 Protocol, NET/ROM and the Serial Port
+KISS Driver. For the purposes of this document I will work under the
+assumption that you include them in the kernel fully, ie not as modules.
+If you need to look at compiling your kernel for ax25 more fully, I would
+refer to the excellent
+
+I should say at this stage that NET/ROM is not mandatory. If you do not use it
+simply ignore any instruction concerning it.
+
+
+Now recompile your kernel in the normal way and reboot your system.
+
+
+Now install the RPM's you downloaded, libax25 first, then ax25-tools,
+then ax25-apps.
+You will find the configuration files in /etc/ax25. These consist of
+several files ...
+
+
+These are the main files. You will find other files but they do not
+have any use unless you are wanting to use that particular protocol,
+Rose or axip for example.
+
+
+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.
+
+
+This file sets up the ax25 ports you want to use. An example is below
+for a standard TNC2 ...
+
+
+Note that the portnames have to be unique.
+
+
+The file headings are as follows ...
+
+
+This file sets up the netrom ports you want to use. An example is below
+and includes a port for both cluster and node. You will see why we need
+2 ports later ...
+
+
+Note that the portnames have to be unique.
+
+
+The file headings are as follows ...
+
+
+This file sets up the netrom broadcast qualities. An example is below ...
+
+
+The file headings are as follows ...
+
+
+This file controls any incoming ax25 and NET/ROM connections and steers
+them to the relevant program. There are lots of configuration options
+you can set here, however they are well covered in the AX25-HOWTO. For
+our purposes I will show a typical set of parameters. An example is
+below ...
+
+
+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 their callsign in a TNC and tries to connect with the standard
+NOCALL set into their TNC will not connect, the 'L' means 'lockout'.
+Lastly and importantly, notice the order of the sections. They are
+all done in interface order.
+
+
+You should be able to see that the normal line for access to the
+cluster is like this ..
+
+
+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 first example and
+in. In this case it would probably be better to use the first example and
then add a specific line for that node like this:
+For those of you that wish to run the node, you need to set up the
+node.conf file. There are a couple of additional files, node.perms is
+very similar to the way ftp permissions are set up in NOS systems and
+node.motd is the message anyone logging into the node will get.
+The node.conf file sets all the parameters of the node as you would
+expect. An example is below ...
+
+
+This should be fairly obvious I hope.
+
+
+Ok, now we have all the relevant files configured, the next step is to get
+it all running.
+
+
+The first thing to do is attach the TNC's. Your TNC's should be in KISS mode
+and connected to the serial ports involved.
+
+
+You now use the 'kissattach' command to connect the TNC's to the system like this ...
+
+
+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.
+
+
+Now we need to attach the NET/ROM ports in the same way ...
+
+
+All of the above can be put in a file and called from /etc/rc.d/rc.local. Put all
+the above commands in a file called rc.ax25 and put a line in rc.local to call it.
+
+
+Now you can start the daemons that set everything in motion ...
+
+
+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. There are 2 files that need to be edited.
+
+
+First edit /etc/services and add
+
+
+Assuming you want it to run on port 3000
+
+
+Now cd /etc/xinetd.d and edit a new file called node. It should look like this ...
+
+
+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.
+
+
+This is dealt with in the previous section
Then add a line in /etc/inetd.conf like this ....
Now login as sysop and cd spider/src. You can test that spider
+
+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 not asked for.
@@ -586,7 +1126,7 @@ or symbols:-
connects to GB7DJK-1 [instead of a script called gb7djk-1]).
-
+
There are many possible ways to configure the script but here are three examples,
one for a NETRom/AX25 connect, one for AGW engines and one for tcp/ip.
@@ -645,6 +1185,7 @@ connection to GB7DJK-1 started
G0VGS de GB7MBC 13-Dec-1998 2043Z >
+
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 set/debug connect first.
@@ -737,6 +1278,7 @@ connect telnet mary.lancs.ac.uk
'connect' ''
+
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 connection. Once connected to
@@ -776,7 +1318,7 @@ This line works fine for RedHat distributions. It is also fine for SuSE up to
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.
@@ -962,31 +1504,43 @@ do it that way because it suits me.
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; either get a CVS update from sourceforge (if you don't know
-what this is, then it isn't for you) or get my package from:-
+what this is, then it isn't for you) or get the latest "official"
+release from:-
- 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 "C:\", for convenience.
- You will need
-Ensure that your CVS session or your unZIPped file have left you
-with a directory "C:\spider\local"; if not, go to "C:\spider\"
-and create one. If "C:\spider" is missing, go back and figure out
-why, because it shouldn't be.
+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.
Now create your own local copy of the DXVars.pm file by:-
@@ -1015,12 +1569,59 @@ minimum you must adjust the following items in DXVars.pm:-
+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:-
+
+ If your machine is connected to the internet I would recommend Anyway, if you are rewarded with a display which looks something like:-
-If you want to enable inbound "TELNET" connections, you've got a
-little more work to do. From a handy "DOS box" that's not doing
-anything else, do the following:-
-
- The interface is very basic. It is a simple command line. There are
+better looking interfaces. Most of the "standard" logging and DX
+Cluster access programs that are capable of connecting via a TCP or
+telnet connection will work as a "Sysop Console" client. You connect
+to "localhost" on the port that you defined in Listeners.pm (usually
+7300). I recommend packages like
-If you want to connect this to another cluster, then you'll want
-to negotiate a link with someone. For experimental purposes, I'm
-happy to allow folk to connect to GB7DXA (spud.ath.cx), on the
-understanding that the system may or may not be there and may or
-may not be connected to anything particularly useful at any given
-moment. Contact me by Email if you want me to set up a connection
-for you.
+If you want to connect this to another cluster, then you'll want to
+negotiate a link with someone. For experimental purposes, I'm happy to
+allow folk to connect to GB7DXA (spud.ath.cx), on the understanding
+that the system may or may not be there and may or may not be
+connected to anything particularly useful at any given moment. Contact
+me by