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:
@@ -51,15 +51,16 @@ default * * * * * * - sysop /spider/src/client client %u ax25
-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 ....
@@ -95,7 +96,7 @@ no good reason for a password prompt to be given so it is not asked for.
-telnet localhost 7300
+telnet localhost 8000
@@ -104,8 +105,8 @@ telnet localhost 7300
3.3 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.
@@ -120,50 +121,52 @@ 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 "0.0.0.0"
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.
+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.
3.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.
+
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.