X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=txt%2Finstallation.txt;h=e3f7eb757d3ceca6a3b924ce46d9cdf032761b86;hb=8b89a9f5ce05bee89e83d68a75da9e73f560ee67;hp=a555718bac3803d3248b10d4768c595a42a39086;hpb=8e862ce4b386889bc91c34ec788df0bd1a062c6c;p=spider.git diff --git a/txt/installation.txt b/txt/installation.txt index a555718b..e3f7eb75 100644 --- a/txt/installation.txt +++ b/txt/installation.txt @@ -1,7 +1,7 @@ - The DXSpider Installation Manual v1.49 + The DXSpider Installation Manual v1.50 Iain Philipps, G0RDI (g0rdi@77hz.com) and Ian Maude, G0VGS, - (ianmaude@btinternet.com) - December 2001 revision 1.1 + (g0vgs@gb7mbc.net) + July 2002 revision 0.3 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -9,6 +9,61 @@ Table of Contents + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 1. Linux Installation 1.1 Introduction @@ -20,37 +75,50 @@ 2. Linux quick installation guide - 3. Configuration + 3. Setting up the AX25 Utilities - 3.1 Allowing ax25 connects from users - 3.2 Allowing telnet connects from users - 3.3 Setting up telnet connects (from 1.47 onwards) - 3.4 Setting up for AGW Engine (1.47 onwards) - 3.5 Setting up node connects - 3.6 Connection scripts - 3.7 Starting the connection - 3.8 Telnet echo - 3.9 Autostarting the cluster + 3.1 Getting Started + 3.2 The kernel + 3.3 Installing the RPM's + 3.4 Configuration + 3.5 axports + 3.6 nrports + 3.7 nrbroadcast + 3.8 ax25d.conf + 3.9 node.conf + 3.10 Getting it all running - 4. Microsoft Windows Installation + 4. Configuration - 4.1 Introduction - 4.2 The requirements - 4.3 The system - 4.4 Perl - 4.5 Additional packages - 4.6 Getting Spider + 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.4 Setting up for AGW Engine (1.47 onwards) + 4.5 Setting up node connects + 4.6 Connection scripts + 4.7 Starting the connection + 4.8 Telnet echo + 4.9 Autostarting the cluster - 5. Installing the software + 5. Microsoft Windows Installation - 5.1 The AGW packet engine - 5.2 Setting up the initial user files - 5.3 Incoming telnets - 5.4 Connecting to other clusters + 5.1 Introduction + 5.2 The requirements + 5.3 The system + 5.4 Perl + 5.5 Additional packages + 5.6 Getting Spider - 6. General Information + 6. Installing the software - 6.1 The crontab file + 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 ______________________________________________________________________ @@ -59,14 +127,9 @@ 1.1. Introduction - This section describes the installation of DX Spider v1.47 on a RedHat + 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 do not intend to try and cover - the installation of Linux or the setup of the AX25 utilities. If you - need help on this then read Iains original installation guide that - comes with the Spider distribution. - - + 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. @@ -79,11 +142,11 @@ In addition to the standard Red Hat distribution you will require the - following modules from http://www.cpan.org/CPAN.html , please note - however that with later versions of perl, some of these modules may be - included with the distribution. Get the modules anyway and try to - install as below. If they complain, they are probably already a part - of your perl distribution. + following modules from http://www.cpan.org/modules/by-module/ , please + note however that with later versions of perl, some of these modules + may be included with the distribution. Get the modules anyway and try + to install as below. If they complain, they are probably already a + part of your perl distribution. @@ -99,6 +162,8 @@ o Time-HiRes-01.20.tar.gz + o Digest-SHA1-2.01.tar.gz + Copy the CPAN modules listed above to a convenient place on your computer. One good place would be /usr/local/packages, and the @@ -128,6 +193,7 @@ + # tar xvfz /usr/local/packages/Data-Dumper-2.10.tar.gz @@ -171,6 +237,13 @@ # 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 .. @@ -185,7 +258,7 @@ 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. @@ -196,13 +269,14 @@ your own choice. + # adduser -m sysop - For SUSE distributions, the command would be .. + For SuSE distributions, the command would be .. @@ -233,7 +307,7 @@ # cd ~sysop - # tar xvfz spider-1.47.tar.gz + # tar xvfz spider-1.50.tar.gz # ln -s ~sysop/spider /spider # groupadd -g 251 spider (or another number) @@ -262,6 +336,8 @@ 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 {} \; @@ -318,7 +394,6 @@ - This is the call sign of your cluster. If you use an SSID then include it here also. @@ -328,6 +403,8 @@ + + This is the sysop user callsign, normally your own. @@ -340,243 +417,820 @@ any section. Some of the lines look a little odd. Take this line for example .... - $myemail = "ianmaude\@btinternet.com"; + $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 + + + parameters 1 10 * * * 3 * + NOCALL * * * * * * L + default * * * * * * - sysop /spider/src/client client %u ax25 + + + 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 ... + + + + + + + + + + + + + + + + + + + + + + + + - 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 + # /etc/ax25/node.conf - LinuxNode configuration file + # + # see node.conf(5) + # Idle timeout (seconds). + # + IdleTimeout 1800 - 1.5. The client program + # Timeout when gatewaying (seconds). + # + ConnTimeout 40000 - 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. + # Visible hostname. Will be shown at telnet login. + # + HostName gb7mbc.ampr.org + # ReConnect flag. + # + ReConnect off + # "Local" network. + # + #LocalNet 44.139.8.48/32 - 1.6. Starting up for the first time + # Command aliases. See node.conf(5) for the meaning of the uppercase + # letters in the name of the alias. + # + ##Alias CAllbook 'telnet %{2:44.17.0.53} 1235 %1 s' + #Alias CONVers 'telnet %{2:oh2ti} 3600 "/n %u %{1:139}\n/w *"' + #Alias CLuster 'c hkiclh' + Alias CONV "telnet lurpac 3600" + Alias BBS "c 70cm gb7crv" + Alias DXC "telnet localhost 9000" + Alias MUD "telnet homer 4000" + ##Alias TEMP "finger temp@mary.g6phf" + ##Alias TNOS "c ip1 gb7mbc-5" + ##Alias TUtor "telnet gb7mbc 3599" + + # Hidden ports. + # + #HiddenPorts 2 - We can now bring spider up for the first time and see if all is well - or not! It should look something like this ... + # External commands. See node.conf(5) for the meaning of the uppercase + # letters in the name of the extcmd. + # + # Flags: 1 Run command through pipe + # 2 Reconnected flag + # + #ExtCmd TPM 3 nobody /usr/bin/finger finger tpm + #ExtCmd ECho 1 nobody /bin/echo echo \%U \%u \%S \%s \%P \%p \%R \%r \%T \%t \%\% \%0 \%{1:foobar} \%{2} \%3 \%4 \%5 + # Node ID. + # + NodeId "\nBARE:GB7MBC-1" + #NodeId \033[01;31m***\033[0m + # Netrom port name. This port is used for outgoing netrom connects. + # + NrPort netrom + # Logging level + # + LogLevel 3 - $ ./cluster.pl - DXSpider DX Cluster Version 1.47 - 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 ... + # The escape character (CTRL-T) + # + EscapeChar ^T + # Resolve ip numbers to addresses? + # + ResolveAddrs off + # Node prompt. + # + #NodePrompt "\n" + #NodePrompt "%s@%h \%i> " + NodePrompt "\nBARE:GB7MBC-1 \%i > " + #NodePrompt "\a\033[36m%U\033[0m de \033[01;32m#LNODE\033[0m:\033[01;33mOH2BNS-10\033[0m> " - 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 be fairly obvious I hope. - $ ./client + 3.10. Getting it all running + 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. - 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 .... + You now use the 'kissattach' command to connect the TNC's to the + system like this ... - G0VGS de GB7MBC 19-Nov-1999 2150Z > + kissattach /dev/ttyS0 2m 44.131.96.199 + kissattach /dev/ttyS1 4m 44.131.96.199 - 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 .... + 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 + ... - shutdown + kissparms -p 2m -t 150 -l 150 -s 50 -r 50 + kissparms -p 4m -t 150 -l 150 -s 50 -r 50 - and both the cluster and the client should return to Linux prompts. + The command 'man kissparms' will give you the explanation of the + switches. - 2. Linux quick installation guide + Now we need to attach the NET/ROM ports in the same way ... - 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 + nrattach netrom + nrattach netrom2 - o Get the additional CPAN modules and install them (root) + 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. - o Create the "sysop" user and set a password (root) - o Put the Spider tarball in sysop and untar it (root) + Now you can start the daemons that set everything in motion ... - 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) + ax25d + netromd -i - 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) + 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. - o mkdir local_cmd (sysop) - o cp perl/DXVars.pm.issue local/DXVars.pm (sysop) + First edit /etc/services and add - o cd to /spider/local and edit DXVars to set your details (sysop) - o cd ../perl (sysop) - o ./create_sysop.pl (sysop) + node 3000/tcp #OH2BNS's Node Software - o ./cluster.pl (sysop) - Spider should now be running and you should be able to login using the - client program. - o Login as root + Assuming you want it to run on port 3000 - o Enter the correct line in ax25d.conf (root) - o Enter the correct line in /etc/services (root) + Now cd /etc/xinetd.d and edit a new file called node. It should look + like this ... - o Enter the correct line in /etc/inetd.conf (root) - o killall -HUP inetd (root) + # default: on + # unencrypted username/password pairs for authentication. + service node + { + socket_type = stream + wait = no + user = root + server = /usr/sbin/node + log_on_failure += USERID + disable = yes + } - 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) + You now need to restart the xinetd daemon. First find out what the + PID is like so .. - o Write any connect scripts (sysop) - o Edit /spider/crontab as required (sysop) - o Edit any other files as necessary (sysop) + ps auxw |grep xinetd - o Set filters, hops and forwarding files (sysop) - o Login as root - o Enter the correct line in /etc/inittab (root) + You will get a reply something like this ... - 3. Configuration - 3.1. Allowing ax25 connects from users - 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 ... + root 592 0.0 0.1 2256 620 ? S Feb07 0:00 xinetd -stayalive -reuse -pidfile /var/run/xinetd.pid - default * * * * * * - sysop /spider/src/client client %u ax25 + The PID or Process ID is 592 in this case so now we can issue the + command ... - or, if you wish your users to be able to use SSID's on their callsigns - .. + kill -HUP 592 - default * * * * * * - sysop /spider/src/client client %s ax25 + 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 ... - 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: + telnet localhost 3000 + - GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25 - default * * * * * * - sysop /spider/src/client client %u ax25 + 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. + 4. Configuration + 4.1. Allowing ax25 connects from users - 3.2. Allowing telnet connects from users + This is dealt with in the previous section + + + 4.2. Allowing telnet connects from users From version 1.47 there is a new (more efficient) way of doing this @@ -592,10 +1246,12 @@ spdlogin 8000/tcp # spider anonymous login port - Then add a line in /etc/inetd.conf like this .... + + Then add a line in /etc/inetd.conf like this .... + spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet @@ -642,7 +1298,7 @@ You should now get the login prompt and be able to login as before. - 3.3. Setting up telnet connects (from 1.47 onwards) + 4.3. Setting up telnet connects (from 1.47 onwards) 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 @@ -658,6 +1314,10 @@ killall -HUP inetd + + + + to make the change happen... @@ -706,7 +1366,7 @@ users. - 3.4. Setting up for AGW Engine (1.47 onwards) + 4.4. Setting up for AGW Engine (1.47 onwards) AGW Engine is a Windows based ax25 stack. You can connect to an AGW engine from Linux as well as Windows based machines. @@ -732,7 +1392,7 @@ - 3.5. Setting up node connects + 4.5. Setting up node connects In order to allow cluster node connections, spider needs to know that the connecting callsign is a cluster node. This is the case whether @@ -817,7 +1477,7 @@ - 3.6. Connection scripts + 4.6. Connection scripts Because DXSpider operates under Linux, connections can be made using just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all @@ -927,7 +1587,7 @@ directory. - 3.7. Starting the connection + 4.7. Starting the connection You start the connection, from within a sysop enabled cluster login, by typing in the word connect followed by a script name like this .... @@ -1000,7 +1660,7 @@ - 3.8. Telnet echo + 4.8. Telnet echo Cluster links in particular suffer greatly from the presence of telnet echo. This is caused by the telnet negotiation itself and can create @@ -1045,7 +1705,7 @@ - 3.9. Autostarting the cluster + 4.9. Autostarting the cluster Ok, you should now have DXSpider running nicely and allowing connects by cluster nodes or users. However, it has to be shutdown and @@ -1073,7 +1733,7 @@ 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 + SuSE up to 7.0. From SuSE 7.1 you need to add runlevels 2 and 5 like this ... @@ -1099,14 +1759,19 @@ restart it should it crash for any reason. + 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 you should find everything running nicely. - 4. Microsoft Windows Installation + 5. Microsoft Windows Installation - 4.1. Introduction + 5.1. Introduction IMPORTANT: @@ -1131,7 +1796,7 @@ connections. - 4.2. The requirements + 5.2. The requirements The very first things you're going to need are (in order of importance):- @@ -1150,7 +1815,7 @@ o Plenty of good, strong tea - 4.3. The system + 5.3. The system The platform I used to generate these instructions was a "vanilla" Microsoft Windows Me 4.90.3000 system, with a 700MHz AMD Athlon @@ -1173,7 +1838,7 @@ zero intention of trying to make them say otherwise. - 4.4. Perl + 5.4. Perl Install your chosen Perl environment. Unless you have a very good reason for not doing so, I strongly suggest that you use ActivePerl @@ -1204,7 +1869,7 @@ passed. Assuming it did work, you may now move on. - 4.5. Additional packages + 5.5. Additional packages Some extensions ("packages") need to be added to the base Perl distribution, and we'll do this next. If you're using the Perl I @@ -1237,21 +1902,30 @@ - D:\ppm>ppm install Data-Dumper.ppd - Installing package 'Data-Dumper.ppd' - Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs - Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll - Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp - Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib - Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html - Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm - Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist - D:\ppm> + + + + + + D:\ppm>ppm install Data-Dumper.ppd + Installing package 'Data-Dumper.ppd' + Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs + Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll + Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp + Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib + Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html + Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm + Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist + D:\ppm> + + + + I'm not going to bother you with exhaustive details of the rest of them, but suffice it to say you need to: @@ -1273,35 +1947,47 @@ because it suits me. - 4.6. Getting Spider + 5.6. Getting Spider 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:- + is, then it isn't for you) or get the latest "official" release from:- - http://www.dcc.rsgb.org/WinSpider.zip + http://www.dxcluster.org/download/index.html - or if you want the lastest CVS version (which is produced every night) + or if you want the lastest snapshot of CVS version (which is produced + every night):- http://www.dxcluster.org/download/CVSlatest.tgz - If you went down the CVS route, then everything will be nicely set out - on your local disk. If you got the ZIP file, unpack it to somewhere + This is generally the best one to go for as it is completely up to + date. However, there is always the very slight chance that it might + unstable. Generally, there will be a note on the website if this is + the case. + + + 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. - - NOTE: This distribution method will go away as soon as the first v1.47 - tarball is released. You can use WinZip to unpack that, and my life - will be made easier by not needing to keep this .ZIP file updated. + You will need winzip to manipulate the TGZ files (they are bit like + ZIP files) if you are not using CVS. - 5. Installing the software + 6. Installing the software - 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:- @@ -1318,7 +2004,7 @@ - cd \spider\local + cd \spider\local @@ -1342,12 +2028,70 @@ o $myalias - the SysOp's callsign. Cannot be the same as $mycall! - You really also ought to update the $mylatitude, $mylongitude, $myqth - and $myemail variables. And unless you are absolutely certain you know - what you're doing, you should change nothing else in this file. + o $myqth - The station's geographical location (QTH). + + o $mylatitude - The station latitude in degrees and decimal fractions + + o $mylongitude - The station longitude in degrees and decimal + fractions + + o $mylocator - The Maidenhead (or QRA) locator of the station + + You really also ought to update the $myqth and $myemail variables. And + unless you are absolutely certain you know what you're doing, you + should change nothing else in this file. Note that if you use an "@" + or a "$" character in one of the above strings (typically in $myemail) + you must write them as "\@" or "\$". + + + 6.1. Incoming telnets + + 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:- + + + + copy \spider\perl\Listeners.pm \spider\local + cd \spider\local + notepad listeners.pm + + + + + The following lines need attention:- + + + + ["0.0.0.0", 7300], + + + + + On my machine, I've simply uncommented the "0.0.0.0" entry by removing + the '#' from the front of the line. + + You MUST carry out this step if you are running on a Windows NT, 2000 + or XP based system + + If you don't have a static hostname for your machine, and you intend + to allow folk to connect to your machine across the internet, then I'd + suggest you pay a visit to www.dyndns.org and create one for yourself. + While it's free, it will take a modest an amount of effort on your + part to read, understand and implement what needs to be done to set + this up. + + + If your machine is connected to the internet and you don't want to + allow your machine to be visible to the outside world you should + change the "0.0.0.0" to "127.0.0.1" [which is "localhost"]. This will + then only allow connections from inside your machine. As was said + earlier: if you aren't running Win9x (or you want to use DXTelnet or + somesuch), then you need to have the machine listening at least to + "127.0.0.1" ("0.0.0.0" means all IP addresses). - 5.1. The AGW packet engine + 6.2. The AGW packet engine 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 @@ -1365,7 +2109,8 @@ - notepad AGWConnect.pm + + notepad AGWConnect.pm @@ -1382,9 +2127,7 @@ o $passwd - password that matches $login - - - 5.2. Setting up the initial user files + 6.3. Setting up the initial user files Next you need to create the initial user files, etc. A tool is supplied which will do this for you. To run the tool:- @@ -1415,99 +2158,111 @@ - DXSpider DX Cluster Version 1.47 - Copyright (c) 1998-2001 Dirk Koopman G1TLH - loading prefixes ... - loading band data ... - loading user file system ... - starting listeners ... - Internal port: localhost 27754 - load badwords: Ok - reading in duplicate spot and WWV info ... - reading existing message headers ... - load badmsg: Ok - load forward: Ok - load swop: Ok - @msg = 0 before delete - @msg = 0 after delete - reading cron jobs ...v cron: reading /spider/cmd/crontab - cron: adding 1 0 * * 0 - DXUser::export("$main::data/user_asc") - reading database descriptors ... - doing local initialisation ... - orft we jolly well go ... - queue msg (0) - 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) - To access your new cluster (from the local machine) find yourself - another "DOS box" and do the following:- - cd \spider\perl - perl winclient.pl - If you are rewarded with a display which looks something like:- - Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.47 - Cluster: 1 nodes, 1 local / 1 total users Max users 2 Uptime 0 00:00 - M0ADI de GB7SJP 4-Mar-2001 1511Z > + DXSpider DX Cluster Version 1.47 + Copyright (c) 1998-2001 Dirk Koopman G1TLH + loading prefixes ... + loading band data ... + loading user file system ... + starting listeners ... + Internal port: localhost 27754 + load badwords: Ok + reading in duplicate spot and WWV info ... + reading existing message headers ... + load badmsg: Ok + load forward: Ok + load swop: Ok + @msg = 0 before delete + @msg = 0 after delete + reading cron jobs ...v cron: reading /spider/cmd/crontab + cron: adding 1 0 * * 0 + DXUser::export("$main::data/user_asc") + reading database descriptors ... + doing local initialisation ... + orft we jolly well go ... + queue msg (0) - 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) - 5.3. Incoming telnets + 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 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:- + If you are running Windows 9x you can access your new cluster (from + the local machine) by finding yourself another "DOS box" and doing the + following:- - copy \spider\perl\listeners.pm \spider\local - cd \spider\local - notepad listeners.pm + cd \spider\perl + perl winclient.pl - The following lines need attention:- + 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 + to the port you defined in Listeners.pm (7300 as default), thus:- - ["0.0.0.0", 7300], + Menu->Start->Run + telnet localhost 7300 - On my machine, I've simply uncommented the "0.0.0.0" entry by removing - the '#' from the front of the line. + 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 + that which comes with windows (I use PuTTY). + + + Anyway, if you are rewarded with a display which looks something + like:- + + + Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.47 + Cluster: 1 nodes, 1 local / 1 total users Max users 2 Uptime 0 00:00 + M0ADI de GB7SJP 4-Mar-2001 1511Z > + + + + + 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) - If you don't have a static hostname for your machine, and you intend - to allow folk to connect to your machine across the internet, then I'd - suggest you pay a visit to www.dyndns.org and create one for yourself. - While it's free, it will take a modest an amount of effort on your - part to read, understand and implement what needs to be done to set - this up. + 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 DXTelnet. - 5.4. Connecting to other clusters + + 6.4. Connecting to other clusters 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 @@ -1516,13 +2271,14 @@ connected to anything particularly useful at any given moment. Contact me by Email if you want me to set up a connection for you. - 6. General Information + + 7. General Information The following relates to all versions of DXSpider and is not platform related. - 6.1. The crontab file + 7.1. The crontab file Login as sysop and create a file in /spider/local_cmd called crontab. Edit it with your favourite editor and add a line like this (I have @@ -1552,33 +2308,3 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -