This is dealt with in the previous section
-->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 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.
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 ....
+to make the change happen...
+ +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.
+It comes out of the box looking something like:-
-spdlogin 8000/tcp # spider anonymous login port
+@listen = (
+# ["0.0.0.0", 7300],
+);
Then add a line in /etc/inetd.conf like this ....
+Change it so that it looks like this:-
-spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
+@listen = (
+ ["0.0.0.0", 7300],
+);
Once this is done, you need to restart inetd like this ....
+Later versions have more comments in the Listeners.pm file that +are designed to help you remove the correct '#' character.
+ +As standard, the listener will listen on all interfaces simultaneously. +If you require more control than this, you can specify each interface +individually:-
-killall -HUP inetd
+@listen = (
+ ["gb7baa.dxcluster.net", 7300],
+ ["44.131.16.2", 6300],
+);
Now login as sysop and cd spider/src. You can test that spider -is accepting telnet logins by issuing the following command ....
+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.
+ ++>From version 1.47 there is a new (more efficient) way of doing this +(see previous 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 ....
-./client login telnet
+spdlogin 8000/tcp # spider anonymous login port
You should get a login prompt and on issuing a callsign, you will be given -access to the cluster. Note, you will not get a password login. There seems -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 ....
+Then add a line in /etc/inetd.conf like this ....
-telnet localhost 8000
+spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
You should now get the login prompt and be able to login as before.
- ->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.
To do this you need first to remove any line that you may previously have set -up in /etc/inetd.conf. Remember to:-
+Once this is done, you need to restart inetd like this ....
@@ -99,46 +119,31 @@ killall -HUP inetd
to make the change happen...
- -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:-
+Now login as sysop and cd spider/src. You can test that spider +is accepting telnet logins by issuing the following command ....
-@listen = (
- ["0.0.0.0", 8000],
-);
+./client login telnet
As standard, the listener will listen on all interfaces simultaneously. -If you require more control than this, you can specify each interface -individually:-
+You should get a login prompt and on issuing a callsign, you will be given +access to the cluster. Note, you will not get a password login. There seems +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 ....
-@listen = (
- ["gb7baa.dxcluster.net", 8000],
- ["44.131.16.2", 6300],
-);
+telnet localhost 8000
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.
+You should now get the login prompt and be able to login as before.
-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.