-</pre>
-<P>Don't forget to give them a real password. This is really for network cluster logins. The telnet argument does two things, it sets the EOL convention to \n rather than AX25's \r and it automatically reduces the privilege of the <callsign> to a 'safe[r]' level.). </P>
-<LI>As mentioned earlier, for AX25 connections <B><I>you</B></I> are expected to have the AX25 utilities installed, setup, tested and working. See the AX25-HOWTO for more info on this - it really is beyond the scope of this document DX Spider uses ax25d for incoming connections. You need to have entries like this:- </LI>
-<PRE>
- [ether]
- NOCALL * * * * * * L
- default * * * * * * - sysop /spider/perl/client.pl client.pl %u ax25
- <bbs>
- NOCALL * * * * * * L
- default * * * * * * - sysop /spider/perl/client.pl client.pl %u ax25
-</PRE>
-<P>where 'ether' and 'bbs' are appropriate <B><I>KNOWN WORKING</B></I> axport and nrport names respectively. Obviously you can use different names, callsigns or whatever for your purposes, but it is up to you to get it to work. Note I use BPQ over ethernet which why I have the port names I have.</P>
-<LI>Find your <TT>netrom_call</TT> and <TT>ax25_call</TT> programs (which on my system live in <TT>/usr/sbin)</TT> and chmod them so that they are SUID <TT>root</TT> </LI>
-<PRE> # chown root ax25_call netrom_call
- # chmod 4775 ax25_call netrom_call</PRE>
-<P>This has to be done to allow you to specify the correct callsigns on outgoing connects</P>
-<LI>Login to your computer as sysop, and create the initial DX Spider parameters necessary to start the cluster for the first time.</LI>
-<PRE> $ startx			(much easier to use X)
- $ cd /spider
- $ mkdir local
- $ mkdir local_cmd
- $ cp perl/DXVars.pm local
- $ cd local
- $ vi DXVars.pm			(or 'joe DXVars.pm' if you're a WordStar fan ;-)
-</PRE>
-<P>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.</P>
-<B><P>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</P>
-</B><P>DON'T alter the DXVars.pm (or any other 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 whilst the cluster is running!</P>
-<PRE>
- :x
+ </pre>
+
+ Don't forget to give them a real password. The <tt>telnet</tt> argument
+ does two things, it sets the EOL convention to \n rather than
+ AX25's \r and it automatically reduces the privilege of the
+ <callsign> to a 'safe[r]' level.). If the user or other cluster
+ program requires AX25 conventions to operate then you can use
+ <tt>ax25</tt> instead.
+
+ <p>Another thing you can do is to get <tt>inetd</tt> to listen
+ on a specific port and then start the client up directly. To
+ do this, create an entry in <tt>/etc/services</tt> with a
+ port number > 1000 that isn't used elsewhere eg:-
+
+ <p><pre>
+gb7djk 8001/tcp
+gb7tlh 8002/tcp
+ </pre>
+
+ Then create some lines in <tt>/etc/inetd.conf</tt> that look
+ like this:-
+
+ <p><pre>
+gb7djk stream tcp nowait sysop /usr/sbin/tcpd /spider/src/client gb7djk telnet
+gb7tlh stream tcp nowait sysop /usr/sbin/tcpd /spider/src/client gb7tlh telnet
+ </pre>
+
+ Please <b>DON'T</b> run the client as <tt>root</tt> you will only
+ come to regret it later when the next person finds a security hole
+ in DX Spider (there are bound to be some although I have tried to
+ avoid the obvious ones I could think of).
+
+ <p>The only reason I would use this mechanism is for Internet connections
+ to other or from other clusters. Don't use this for normal users.
+
+ <p>In the example I have used <tt>tcpd</tt> as the access control
+ mechanism to the port. Don't (I can't be bothered to emphasize
+ it any more) run a system like this without one, you are asking
+ for trouble. In fact I use the <a href="http://www.tis.com">TIS
+ Firewall Toolkit</a> myself, you may find this more intuitive
+ to use. The point is that <tt>gb7djk</tt> would only be coming
+ from one IP address, if it coming from another, it is an imposter!
+
+ <p><b>You are responsible for arranging and looking after your
+ security - not me.</b>
+
+ <p><LI>As mentioned earlier, for AX25 connections <B><I>you</B></I> are expected to have the AX25 utilities installed, setup, tested and working. See the AX25-HOWTO for more info on this - it really is beyond the scope of this document DX Spider uses ax25d for incoming connections. You need to have entries like this:-
+ <PRE>
+[ether]
+NOCALL * * * * * * L
+default * * * * * * - sysop /spider/src/client client %u ax25
+<cluster>
+NOCALL * * * * * * L
+default * * * * * * - sysop /spider/src/client client %u ax25
+ </PRE>
+ <P>where 'ether' and 'bbs' are appropriate <B><I>KNOWN WORKING</B></I> axport and nrport names respectively. Obviously you can use different names, callsigns or whatever for your purposes, but it is up to you to get it to work. Note I use BPQ over ethernet which why I have the port names I have.
+
+ <p><LI>Find your <TT>netrom_call</TT> and <TT>ax25_call</TT> programs (which on my system live in <TT>/usr/sbin)</TT> and chmod them so that they are SUID <TT>root</TT>
+ <PRE>
+# chown root ax25_call netrom_call
+# chmod 4775 ax25_call netrom_call
+ </PRE>
+ <P>This has to be done to allow you to specify the correct callsigns on outgoing connects
+
+ <p><LI><a name="dxvar"></a>Login to your computer as sysop, and create the initial DX Spider parameters necessary to start the cluster for the first time.
+ <PRE>
+$ startx			(much easier to use X)
+$ cd /spider
+$ mkdir local
+$ mkdir local_cmd
+$ cp perl/DXVars.pm local
+$ cd local
+$ vi DXVars.pm			(or 'joe DXVars.pm' if you're a WordStar fan ;-)
+ </PRE>
+ <P>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.
+ <P><b>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</B>
+ <P>DON'T alter the DXVars.pm (or any other 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 whilst the cluster is running!
+ <PRE>
+:x