<title>The DXSpider Installation and Administration Manual</title>
<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)</author>
-<date>$Date$ $Revision$</date>
+<date>Version 1.47 (Revision 1.30), April 2001</date>
+
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
</abstract>
called <em>client</em>. Leave it in this directory.
-<sect>Quick installation guide
+<sect>Quick installation guide (Linux version)
<P>
This section is designed for experienced Spider sysops who want to install
default * * * * * * - sysop /spider/src/client client %s ax25
</verb></tscreen>
-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
-owuld probably be better to use the first example and then add a specific line for that
-node like this:
+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:
<tscreen><verb>
GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25
<sect1>Allowing telnet connects from users
<P>
-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.
+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.
<P>
Allowing telnet connections is quite simple. Firstly you need to add a line
in /etc/services to allow connections to a port number, like this ....
<tscreen><verb>
-spdlogin 7300/tcp # spider anonymous login port
+spdlogin 8000/tcp # spider anonymous login port
</verb></tscreen>
Then add a line in /etc/inetd.conf like this ....
Assuming all is well, then try a telnet from your linux console ....
<tscreen><verb>
-telnet localhost 7300
+telnet localhost 8000
</verb></tscreen>
<P>
<sect1>Setting up telnet connects (from 1.47 onwards)
<P>
-From version 1.47 you can chose to allow the perl cluster.pl program to
-allow connections direct (i.e. not via the <tt>/spider/src/client</tt>
+From version 1.47 you can choose to allow the perl cluster.pl program to
+allow connections directly (i.e. not via the <tt>/spider/src/client</tt>
interface program). If you are using Windows then this is the only method
available of allowing incoming telnet connections.
killall -HUP inetd
</verb></tscreen>
-<p>
+<P>
to make the change happen...
-<p>
-Having done that then you need to copy the file
-<tt>/spider/perl/Listeners.pm</tt> to <tt>/spider/local</tt> and
+<P>
+Having done that, you need to copy the file
+<em>/spider/perl/Listeners.pm</em> to <em>/spider/local</em> and
then edit it. You will need to uncomment the line containing &dquot;0.0.0.0&dquot;
and select the correct port to listen on. So that it looks like this:-
<tscreen><verb>
@listen = (
- ["0.0.0.0", 7300],
+ ["0.0.0.0", 8000],
);
</verb></tscreen>
-<p>As standard, the listener will listen on all interfaces simultaniously. If you require more
-control than this, you can specify each interface individually:-
+<P>
+As standard, the listener will listen on all interfaces simultaneously.
+If you require more control than this, you can specify each interface
+individually:-
<tscreen><verb>
@listen = (
- ["gb7baa.dxcluster.net", 7300],
+ ["gb7baa.dxcluster.net", 8000],
["44.131.16.2", 6300],
);
</verb></tscreen>
-<p>This will only be successful if the IP addresses on each interface are static.
-If you are using some kind of dynamic IP addressing then the 'default' method is the
-only one which will work.
+<P>
+This will only be successful if the IP addresses on each interface are static.
+If you are using some kind of dynamic IP addressing then the 'default' method
+is the only one that will work.
<P>
Restart the cluster.pl program to enable the listener.
<P>
-One important difference with the internal listener is that no echoing is done by the
-cluster program. Users will need to set 'local-echo' on in their telnet clients if
-it isn't set automatically (as per the standards). Needless to say this will probably
-only apply to Windows users.
+One important difference with the internal listener is that no echoing
+is done by the cluster program. Users will need to set 'local-echo' on in
+their telnet clients if it isn't set automatically (as per the standards).
+Needless to say this will probably only apply to Windows users.
<sect1>Setting up for AGW Engine (1.47 onwards)
-<p>AGW Engine is a Windows based ax25 stack. You can connect to an AGW engine from Linux
-as well as Windows based machines.
+<P>
+AGW Engine is a Windows based ax25 stack. You can connect to an AGW engine
+from Linux as well as Windows based machines.
-<p>In order to enable access to an AGW Engine you need to copy <tt>/spider/perl/AGWConnect.pm</tt>
-to <tt>/spider/local</tt> and edit it. Specifically you must:-
+<P>
+In order to enable access to an AGW Engine you need to copy
+<em>/spider/perl/AGWConnect.pm</em> to <em>/spider/local</em> and edit it.
+Specifically you must:-
<itemize>
<item> set <tt>$enable</tt> to 1.
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
for more information.
+<sect1>show/configuration (0)
+
+<P>
+<tt>
+<bf>show/configuration [<node>]</bf> Show all visible nodes and their users
+</tt>
+
+<P>
+This command allows you to see all the users that can be seen
+and the nodes to which they are connected. With the optional <em>node</em>,
+you can specify a particular node to look at.
+
+This command is normally abbreviated to: sh/c
+
+BE WARNED: the list that is returned can be VERY long
+
+<sect1>show/configuration/node (0)
+
+<P>
+<tt>
+<bf>show/configuration/node</bf> Show all the nodes connected
+</tt>
+
+<P>
+Show all the nodes connected locally and the nodes they have connected.
+
+<sect1>show/connect (1)
+
+<P>
+<tt>
+<bf>show/connect</bf> Show all the active connections
+</tt>
+
+<P>
+This command shows information on all the active connections known to
+the node. This command gives slightly more information than WHO.
+
<sect1>show/date (0)
<P>
projects / spider.git / blobdiff