+ 6.9. Connecting logging programs
+
+ There appear to be very few logging programs out there that support
+ telnet especially the popular ones like LogEQF, Turbolog etc. This
+ can make it difficult to connect to your own cluster! The way to do
+ it is to make the logging program think it has a TNC attached to a com
+ port on the logging PC and 'push' a linux login out to it. This is
+ achieved very simply by the use of agetty.
+
+
+ All that is required is to add a line in /etc/inittab to have the
+ client ready for a connection on the com port of your choice.
+ Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1
+ for com2 etc.
+
+
+
+ c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
+
+
+
+ Add this after the standard runlevel lines in /etc/inittab. The above
+ line works on ttyS1 (com2). Now as root, issue the command telinit q
+ and it should be ready for connection. All that is required is a 3
+ wire serial lead (tx, rx and signal ground). Tell you logging program
+ to use 8n1 at 9600 baud and you should see a Linux login prompt.
+ Login as normal and then telnet from there to the cluster.
+
+
+ 7. Java Web applet
+
+ In the spider tree will be a directory spider-web. This is a neat
+ little java web applet that can be run from a website. The applet
+ must run on the same machine as the cluster. The included README file
+ is shown below.
+
+
+ I should comment here that the applet is precompiled, that is, ready
+ to go. It was compiled using JDK1.3.1. If your version is earlier
+ than this then it may not work. Should that be the case you need to
+ recompile or update your JDK. To recompile do the following ...
+
+
+
+ cd /spider/spider-web
+ rm *.class
+ /usr/bin/javac spiderclient.java
+
+
+
+ I have used /usr/bin/javac as an example, your path to javac may be
+ different.
+
+
+ Spider-WEB v0.6b
+
+ Completely based on a clx web client written in Java by dl6dbh
+ (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
+
+ The webserver has to run on the same machine as your DxSpider software!
+
+ It is assumed that you have Java installed. You need JDK1.3.1 at least.
+
+ Installation instructions (Performed as root):
+
+ Put all the files in the spider-web directory into a newly created directory
+ under the DocumentRoot of your websever for instance 'client'. In my case
+ this is: /home/httpd/html/client/ although ymmv. For Suse the correct
+ path should be /usr/local/httpd/htdocs/client/ for example.
+
+ Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
+ /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
+ /usr/local/httpd/cgi-bin/ for example.
+
+ Change the permissions of the files to ensure they are correct, obviously you
+ will need to use the correct path the the files according to your system:
+
+ chmod 755 /home/httpd/html/cgi-bin/spider.cgi
+ chmod -R 755 /home/httpd/html/client/
+
+ By default the spider.cgi script should pick up your hostname (As long as this
+ is set correctly). If it does not or your hostname differs from the name that
+ you attach to the public address that you are using, then edit spider.cgi :
+
+ # Uncomment and set the hostname manually here if the above fails.
+ # $HOSTNAME = "gb7mbc.spoo.org" ;
+ $PORT = "8000" ;
+
+
+ telnet (see Listeners.pm)
+
+ NOTE: If you can start the console but cannot connect to the cluster from it,
+ then it is possible that the machine you are on cannot resolve the hostname of
+ your cluster machine. If this is the case, you need to set your hostname
+ manually as above.
+
+ You also need to set the $NODECALL variable. This prints the name of your
+ choosing (probably your cluster callsign) on the html page.
+
+ You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
+
+
+
+ 8. Web based statistics
+
+ From version 1.50, you can use the freeware software MRTG to produce
+ really nice graphical statistics on your web site. For an example try
+ http://www.gb7mbc.net/mrtg/stats.html.
+
+
+ The following should help you get it all working.
+
+
+ First you need to download the latest version of MRTG from
+ http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need
+ the following files..
+
+
+
+ libpng-1.0.14.tar.gz
+ zlib-1.1.4.tar.gz
+ gd-1.8.3.tar.gz
+
+
+
+ Login to your machine as the root user, put all the downloaded files
+ in /usr/local/src/ (or wherever you prefer) and untar and compile
+ them. All the information to compile and install these sources come
+ with them. After compilation and installation, you will find MRTG in
+ /usr/local/mrtg-2.
+
+
+ Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
+ /spider/html/mrtg/
+
+
+ You now need to make 2 symbolic links like below...
+
+
+
+ ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
+ ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
+
+
+
+ Now login to the cluster with your sysop callsign and run the command
+ "mrtg all".
+
+
+ Now you are nearly there! Login as the sysop user and change to the
+ /spider/html/mrtg/ directory. Now run the command indexmaker as shown
+ below...
+
+
+
+ indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
+
+
+
+ Changing the callsign for your own cluster callsign of course!
+
+
+ And finally you need to login as the root user and create one last
+ symbolic link. Where this points will depend on where your html
+ documents are kept. For RedHat systems you use...
+
+
+
+ ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
+
+
+
+ and for SuSE systems...
+
+
+
+ ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
+
+
+
+ If you now point your browser to your website as below it should all
+ be happening!
+
+
+
+ http://www.xxx.xxx/mrtg/stats.html
+
+
+
+ Of course, to get the stats to update, you need to add some
+ information in the spider crontab file as below...
+
+
+
+ # Update stats for mrtg on website
+ 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
+
+
+
+ This will update the site every 5 minutes.
+
+
+ 9. Security
+
+ From version 1.49 DXSpider has some additional security features.
+ These are not by any means meant to be exhaustive, however they do
+ afford some security against piracy. These two new features can be
+ used independently of each other or in concert to tighten the
+ security.
+
+
+ 9.1. Registration
+
+ The basic principle of registration is simple. If a user is not
+ registered by the sysop, then they have read-only access to the
+ cluster. The only thing they can actually send is a talk or a message
+ to the sysop. In order for them to be able to spot, send announces or
+ talks etc the sysop must register them with the set/register command,
+ like this ...
+
+
+
+ set/register g0vgs
+
+
+
+ The user g0vgs can now fully use the cluster. In order to enable
+ registration, you can issue the command ...
+
+ set/var $main::reqreg = 1
+
+
+
+ Any users that are not registered will now see the motd_nor file
+ rather than the motd file as discussed in the Information, files and
+ useful programs section.
+
+
+ Entering this line at the prompt will only last for the time the
+ cluster is running of course and would not be present on a restart.
+ To make the change permanent, add the above line to
+ /spider/scripts/startup. To read more on the startup file, see the
+ section on Information, files and useful programs.
+
+
+ To unregister a user use unset/register and to show the list of
+ registered users, use the command show/register.
+
+
+ 9.2. Passwords
+
+ At the moment, passwords only affect users who login to a DXSpider
+ cluster node via telnet. If a user requires a password, they can
+ either set it themselves or have the sysop enter it for them by using
+ the set/password command. Any users who already have passwords, such
+ as remote sysops, will be asked for their passwords automatically by
+ the cluster. Using passwords in this way means that the user has a
+ choice on whether to have a password or not. To force the use of
+ passwords at login, issue the command ...
+
+
+
+ set/var $main::passwdreq = 1
+
+
+
+ at the cluster prompt. This can also be added to the
+ /spider/scripts/startup file as above to make the change permanent.
+
+
+ Of course, if you do this you will have to assign a password for each
+ of your users. If you were asking them to register, it is anticipated
+ that you would ask them to send you a message both to ask to be
+ registered and to give you the password they wish to use.
+
+
+ Should a user forget their password, it can be reset by the sysop by
+ first removing the existing password and then setting a new one like
+ so ...
+
+
+
+ unset/password g0vgs
+ set/password g0vgs new_password
+
+
+
+ 10. CVS
+
+
+
+ 10.1. CVS from a Linux platform