+ 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
+
+ spider:x:251:sysop,g0vgs,root
+
+
+ The next step is to set the permissions on the Spider directory tree
+ and files ....
+
+
+
+ # chown -R sysop.spider spider
+ # find . -type d -exec chmod 2775 {} \;
+ # find . -type f -exec chmod 775 {} \;
+
+
+
+
+
+ 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.
+
+
+ Finally, you need to fix the permissions on the ax25_call and
+ netrom_call programs. Check where they are with the locate command
+ and alter the permissions with the chmod command like this ..
+
+
+
+ # chown root ax25_call netrom_call
+ # chmod 4775 ax25_call netrom_call
+
+
+
+
+
+ 1.4. Setting callsigns etc
+
+ Now login to your machine as the user you created earlier. In my case
+ that user is called sysop. Once logged in, issue the following
+ commands ....
+
+
+
+ $ cd /spider
+ $ mkdir local
+ $ mkdir local_cmd
+ $ cp perl/DXVars.pm.issue local/DXVars.pm
+ $ cd local
+ $ 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.
+
+
+
+ $mycall = "GB7DJK";
+
+
+
+
+ This is the call sign of your cluster. If you use an SSID then
+ include it here also.
+
+
+
+ $myalias = "G1TLH";
+
+
+
+
+
+ This is the sysop user callsign, normally your own.
+
+
+ PLEASE USE CAPITAL LETTERS FOR CALLSIGNS
+
+
+ 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";
+
+
+ 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 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 ....
+
+
+
+ $ cd ../perl
+
+
+
+
+
+ Now type the following command which creates the basic user file with
+ you as the sysop.
+
+
+
+ $ ./create_sysop.pl
+
+
+
+
+
+ 1.5. The client program
+
+ 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.
+ 1.6. Starting up for the first time
+
+ We can now bring spider up for the first time and see if all is well
+ or not! It should look something like this ...
+
+
+
+ $ ./cluster.pl
+ DXSpider DX Cluster Version 1.50
+ Copyright (c) 1998 Dirk Koopman G1TLH
+ loading prefixes ...
+ loading band data ...
+ loading user file system ...
+ starting listener ...
+ reading existing message headers
+ reading cron jobs
+ orft we jolly well go ...
+
+
+
+
+
+ If all is well then login on another term or console as sysop and cd
+ to /spider/src. Now issue the following command ...
+
+
+
+ $ ./client
+
+
+
+
+
+ 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
+ this case we will assume that this 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 ....
+
+
+
+ shutdown
+
+
+
+
+
+ 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
+ install Spider from scratch. It is simply a check list of things that
+ need to be done without any explanations. The name in brackets at the
+ end of each line is the user that should be doing that process.
+
+
+ o Login as root
+
+ o Get the additional CPAN modules and install them (root)
+
+ o Create the "sysop" user and set a password (root)
+
+ o Put the Spider tarball in sysop and untar it (root)
+
+ o ln -s sysop/spider /spider (root)
+
+ o groupadd -g 251 spider (root)
+
+ o Add any more users you need to the group entry in /etc/group (root)
+
+ o Set the permissions on the spider tree (root)
+
+ o Fix permissions on ax25_call and netrom_call (root)
+
+ o Login as the sysop user
+
+ o cd to /spider (sysop)
+
+ o mkdir local (sysop)
+
+ o mkdir local_cmd (sysop)
+
+ o cp perl/DXVars.pm.issue local/DXVars.pm (sysop)
+
+ o cd to /spider/local and edit DXVars to set your details (sysop)
+
+ o cd ../perl (sysop)
+
+ o ./create_sysop.pl (sysop)
+
+ o ./cluster.pl (sysop)
+
+
+ Spider should now be running and you should be able to login using the
+ client program.
+
+
+ o Login as root
+
+ o Enter the correct line in ax25d.conf (root)
+
+ o Enter the correct line in /etc/services (root)
+
+ o Enter the correct line in /etc/inetd.conf (root)
+
+ o killall -HUP inetd (root)
+
+
+ Spider should now be able to accept logins via telnet, netrom and
+ ax25.
+
+
+ o Login as sysop
+
+ o Start the cluster (sysop)
+
+ o set/node and type for links (sysop)
+
+ o Write any connect scripts (sysop)
+
+ o Edit /spider/crontab as required (sysop)
+
+ o Edit any other files as necessary (sysop)
+
+ o Set filters, hops and forwarding files (sysop)
+
+ o Login as root
+
+ o Enter the correct line in /etc/inittab (root)
+
+
+ 3. Setting up the AX25 Utilities
+
+ 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 AX25-HOWTO which is much
+ more comprehensive and an interesting configuration program is also
+ available called ax25-config which may help you to configure things.
+
+
+ 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!
+
+
+ 3.1. Getting Started
+
+ 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 AWZNode by IZ5AWZ.
+
+
+ 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...
+
+
+
+
+ o libax25-0.0.7-7.i386.rpm
+
+ o ax25-tools-0.0.6-13.i386.rpm
+
+ o ax25-apps-0.0.4-9.i386.rpm
+
+
+ 3.2. The kernel
+
+ 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 AX25-HOWTO
+
+
+ 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.
+
+
+ 3.3. Installing the RPM's
+
+ Now install the RPM's you downloaded, libax25 first, then ax25-tools,
+ then ax25-apps.
+
+
+
+ rpm -ivh libax25-0.0.7-7.i386.rpm
+ rpm -ivh ax25-tool-0.0.6-13.i386.rpm
+ rpm -ivh ax25-apps-0.0.4-9.i386.rpm
+
+
+
+
+
+ 3.4. Configuration
+
+ You will find the configuration files in /etc/ax25. These consist of
+ several files ...
+
+
+ o axports
+
+ o nrports
+
+ o nrbroadcast
+
+ o ax25d.conf
+
+ o node.conf
+
+
+ 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.
+ 3.5. axports
+
+ This file sets up the ax25 ports you want to use. An example is below
+ for a standard TNC2 ...
+
+
+
+ #portname callsign baudrate paclen window description
+ 2m gb7mbc-2 19200 256 2 2m port on 144.900MHz
+ 4m gb7mbc-4 19200 256 2 4m port on 70.325MHz
+
+
+
+
+
+ Note that the portnames have to be unique.
+
+
+ The file headings are as follows ...
+
+
+ portname - The name you will refer to the port by
+ callsign - The ax25 callsign you want to assign to the port
+ baudrate - The speed you communicate between TNC and computer
+ paclen - The maximum packet length for ax25 connections
+ window - The ax25 window parameter. This is like 'maxframe'
+ description - A textual description of the port
+
+
+
+
+ 3.6. nrports
+
+ 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 ...
+
+
+
+ #portname callsign alias paclen description
+ netrom gb7mbc-8 BARE 236 Node Netrom Port
+ netrom2 gb7mbc-9 MBCDX 236 Cluster Netrom Port
+
+
+
+
+
+ Note that the portnames have to be unique.
+
+
+ The file headings are as follows ...
+
+
+ portname - The name you will refer to the port by
+ callsign - This is the callsign that NET/ROM traffic from this
+ port will use
+ alias - The NET/ROM alias this port will be assigned
+ paclen - The maximum size of NET/ROM frames transmitted
+ description - A textual description of the port
+
+
+
+
+
+
+
+ 3.7. nrbroadcast
+
+ This file sets up the netrom broadcast qualities. An example is below
+ ...
+
+
+
+ #axport min_obs def_qual worst_qual verbose
+ 4m 5 10 100 1
+
+
+
+
+
+ The file headings are as follows ...
+
+
+ axport - The port name in axports that you wish to broadcast
+ NET/ROM on.
+ min_obs - The minimum obsolescence value for the port
+ def_qual - The default quality for the port
+ worst_qual - The worst quality for the port. Any routes under
+ this quality will be ignored
+ verbose - This flag determines whether you will only broadcast
+ your own node (0) or all known nodes (1)
+
+
+
+
+ 3.8. ax25d.conf
+
+ 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 ...
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ [gb7mbc-0 via 2m]
+ parameters 2 1 6 900 * 15 0
+ NOCALL * * * * * * L
+ default * * * * * * - sysop /spider/src/client client %u ax25
+
+ [gb7mbc-1 via 2m]
+ parameters 2 1 6 900 * 15 0
+ NOCALL * * * * * * L
+ default * * * * * * 0 root /usr/sbin/node node
+
+ [gb7mbc-0 via 4m]
+ parameters 2 1 6 900 * 15 0
+ NOCALL * * * * * * L
+ default * * * * * * - sysop /spider/src/client client %u ax25
+
+ [gb7mbc-1 via 4m]
+ parameters 2 1 6 900 * 15 0
+ NOCALL * * * * * * L
+ default * * * * * * 0 root /usr/sbin/node node
+
+ <netrom2>
+ parameters 1 10 * * * 3 *
+ NOCALL * * * * * * L
+ default * * * * * * - sysop /spider/src/client client %u ax25
+
+ <netrom>
+ parameters 1 10 * * * 3 *
+ NOCALL * * * * * * L
+ default * * * * * * 0 root /usr/sbin/node node
+
+
+
+
+
+ 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 ..
+
+
+
+ default * * * * * * - sysop /spider/src/client client %u ax25
+
+
+
+
+
+ however, if you wish your users to be able to use SSID's on their
+ callsigns ..
+
+
+
+ default * * * * * * - sysop /spider/src/client client %s ax25
+
+
+
+
+
+
+ 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 then add a specific line for that node like this:
+
+
+
+ GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25
+ default * * * * * * - sysop /spider/src/client client %u ax25
+
+
+
+
+
+ 3.9. node.conf
+
+ 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 ...
+
+
+
+