X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Fadminmanual.sgml;h=39ec64313b937908ad8d4ef2e42b24baf9191516;hb=161019eb8c45394eb742fe22826ee997f8d81c73;hp=6f807633730f90a06f42da62daa854351afde06c;hpb=cfde73187c90e1c260c2339332b7773ecfbb8309;p=spider.git diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 6f807633..39ec6431 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -6,7 +6,8 @@ The DXSpider Installation and Administration Manual Ian Maude, G0VGS, (ianmaude@btinternet.com) -$Date$ $Revision$ +Version 1.47 (Revision 1.30), April 2001 + A reference for SysOps of the DXSpider DXCluster program. @@ -254,7 +255,7 @@ should see the output on your screen and hopefully now have a small C program called client. Leave it in this directory. -Quick installation guide +Quick installation guide (Linux version)

This section is designed for experienced Spider sysops who want to install @@ -328,10 +329,10 @@ or, 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 -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: GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25 @@ -341,15 +342,16 @@ default * * * * * * - sysop /spider/src/client client %u ax25 Allowing telnet connects from users

-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.

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 .... -spdlogin 7300/tcp # spider anonymous login port +spdlogin 8000/tcp # spider anonymous login port Then add a line in /etc/inetd.conf like this .... @@ -381,7 +383,7 @@ no good reason for a password prompt to be given so it is not asked for. Assuming all is well, then try a telnet from your linux console .... -telnet localhost 7300 +telnet localhost 8000

@@ -390,8 +392,8 @@ You should now get the login prompt and be able to login as before. Setting up telnet connects (from 1.47 onwards)

-From version 1.47 you can chose to allow the perl cluster.pl program to -allow connections direct (i.e. not via the /spider/src/client +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 interface program). If you are using Windows then this is the only method available of allowing incoming telnet connections. @@ -403,51 +405,57 @@ up in /etc/inetd.conf. Remember to:- killall -HUP inetd -

+

to make the change happen... -

-Having done that then you need to copy the file -/spider/perl/Listeners.pm to /spider/local and +

+Having done that, you need to copy the file +/spider/perl/Listeners.pm to /spider/local 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:- @listen = ( - ["0.0.0.0", 7300], + ["0.0.0.0", 8000], ); -

As standard, the listener will listen on all interfaces simultaniously. If you require more -control than this, you can specify each interface individually:- +

+As standard, the listener will listen on all interfaces simultaneously. +If you require more control than this, you can specify each interface +individually:- @listen = ( - ["gb7baa.dxcluster.net", 7300], + ["gb7baa.dxcluster.net", 8000], ["44.131.16.2", 6300], ); -

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. +

+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.

Restart the cluster.pl program to enable the listener.

-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. 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. +

+AGW Engine is a Windows based ax25 stack. You can connect to an AGW engine +from Linux as well as Windows based machines. -

In order to enable access to an AGW Engine you need to copy /spider/perl/AGWConnect.pm -to /spider/local and edit it. Specifically you must:- +

+In order to enable access to an AGW Engine you need to copy +/spider/perl/AGWConnect.pm to /spider/local and edit it. +Specifically you must:- set $enable to 1. @@ -4172,6 +4180,43 @@ for more information. Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER for more information. +show/configuration (0) + +

+ +show/configuration [<node>] Show all visible nodes and their users + + +

+This command allows you to see all the users that can be seen +and the nodes to which they are connected. With the optional node, +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 + +show/configuration/node (0) + +

+ +show/configuration/node Show all the nodes connected + + +

+Show all the nodes connected locally and the nodes they have connected. + +show/connect (1) + +

+ +show/connect Show all the active connections + + +

+This command shows information on all the active connections known to +the node. This command gives slightly more information than WHO. + show/date (0)