X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=sgml%2Finstallation.sgml;h=cb47fc549ab098f65ebe920b153c44535c232729;hb=5b621c40fa6165a9f0eaf592d24a63a174e4b902;hp=286a8f8bd6f2ec93e317845d9d52e844e6bf2b4a;hpb=7e16f0c1dcaef94c54a04fa4355d9741cd46f7cb;p=spider.git diff --git a/sgml/installation.sgml b/sgml/installation.sgml index 286a8f8b..cb47fc54 100644 --- a/sgml/installation.sgml +++ b/sgml/installation.sgml @@ -4,10 +4,11 @@ -
-This section describes the installation of DX Spider v1.47 on a
+This section describes the installation of DX Spider v1.50 on a
I am assuming a general knowledge of Linux and its commands. You should
@@ -43,7 +41,7 @@ in the development of Spider.
In addition to the standard Red Hat distribution you will require the
-following modules from
@@ -108,6 +107,13 @@ Log in as 'root', and make sure you're at '/root' before you continue. Here are
# 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 ..
@@ -120,7 +126,7 @@ nearly are! Pay particular attention to the instructions of IO, above.
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.
Login as root and create a user to run the cluster under.
-For SUSE distributions, the command would be ..
+For SuSE distributions, the command would be ..
+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
+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
+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...
+
+
+
+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 ...
+
+
-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 ...
+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 ..
-or, if you wish your users to be able to use SSID's on their callsigns ..
+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
+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
-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.
@@ -481,7 +940,7 @@ You should now get the login prompt and be able to login as before.
-From version 1.47 you can choose to allow the perl cluster.pl program to
+>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.
@@ -863,7 +1322,7 @@ DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/t
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 ...
+7.0. From SuSE 7.1 you need to add runlevels 2 and 5 like this ...
+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
@@ -894,12 +1357,9 @@ you should find everything running nicely.
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
+to 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:-
+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.
+The only difference between "CVSlatest.tgz" and the latest
+"official" release version is that it is more up to date. You will need
+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
+(
-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:-
@@ -1100,7 +1575,7 @@ copy c:\spider\perl\DXVars.pm.issue
c:\spider\local\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
+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:-
If your machine is connected to the internet
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:-
+to interface your radios to the cluster, it would be a good idea to
+download the Packet Engine software! You can get this software from:
+
+
@@ -1227,8 +1721,8 @@ If you did everything you were told, your DOS window will now
hold a display which looks something like:-
Anyway, if you are rewarded with a display which looks something like:-