<P>This is dealt with in the previous section</P>
-<H2><A NAME="ss4.2">4.2</A> <A HREF="installation_en.html#toc4.2">Allowing telnet connects from users </A>
+<H2><A NAME="ss4.2">4.2</A> <A HREF="installation_en.html#toc4.2">Setting up telnet connects (from 1.47 onwards)</A>
</H2>
-<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.</P>
+<P>>From version 1.47 you can choose to allow the perl cluster.pl program to
+allow connections directly (i.e. not via the <CODE>/spider/src/client</CODE>
+interface program). If you are using Windows then this is the only method
+available of allowing incoming telnet connections.</P>
-<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 ....</P>
+<P>to make the change happen...</P>
+
+<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 "0.0.0.0"
+and select the correct port to listen on.</P>
+<P>It comes out of the box looking something like:-</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
-spdlogin 8000/tcp # spider anonymous login port
+@listen = (
+# ["0.0.0.0", 7300],
+);
</PRE>
</CODE></BLOCKQUOTE>
</P>
-
-<P>Then add a line in /etc/inetd.conf like this ....</P>
+<P>Change it so that it looks like this:-</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
-spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
+@listen = (
+ ["0.0.0.0", 7300],
+);
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<P>Once this is done, you need to restart inetd like this ....</P>
+<P>Later versions have more comments in the Listeners.pm file that
+are designed to help you remove the correct '#' character.</P>
+
+<P>As standard, the listener will listen on all interfaces simultaneously.
+If you require more control than this, you can specify each interface
+individually:-</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
-killall -HUP inetd
+@listen = (
+ ["gb7baa.dxcluster.net", 7300],
+ ["44.131.16.2", 6300],
+);
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<P>Now login as <EM>sysop</EM> and cd spider/src. You can test that spider
-is accepting telnet logins by issuing the following command ....</P>
+<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>
+
+<P>Restart the cluster.pl program to enable the listener.</P>
+
+<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. </P>
+
+<H2><A NAME="ss4.3">4.3</A> <A HREF="installation_en.html#toc4.3">Allowing telnet connects from users (before version 1.47 or for special purposes)</A>
+</H2>
+
+<P>
+>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.</P>
+
+<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 ....</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
-./client login telnet
+spdlogin 8000/tcp # spider anonymous login port
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<P>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.</P>
-
-<P>Assuming all is well, then try a telnet from your linux console ....</P>
+<P>Then add a line in /etc/inetd.conf like this ....</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
-telnet localhost 8000
+spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<P>You should now get the login prompt and be able to login as before.</P>
-
-<H2><A NAME="ss4.3">4.3</A> <A HREF="installation_en.html#toc4.3">Setting up telnet connects (from 1.47 onwards)</A>
-</H2>
-
-<P>>From version 1.47 you can choose to allow the perl cluster.pl program to
-allow connections directly (i.e. not via the <CODE>/spider/src/client</CODE>
-interface program). If you are using Windows then this is the only method
-available of allowing incoming telnet connections.</P>
-
-<P>To do this you need first to remove any line that you may previously have set
-up in /etc/inetd.conf. Remember to:-</P>
+<P>Once this is done, you need to restart inetd like this ....</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
</CODE></BLOCKQUOTE>
</P>
-<P>to make the change happen...</P>
-
-<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 "0.0.0.0"
-and select the correct port to listen on. So that it looks like this:-</P>
+<P>Now login as <EM>sysop</EM> and cd spider/src. You can test that spider
+is accepting telnet logins by issuing the following command ....</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
-@listen = (
- ["0.0.0.0", 8000],
-);
+./client login telnet
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<P>As standard, the listener will listen on all interfaces simultaneously.
-If you require more control than this, you can specify each interface
-individually:-</P>
+<P>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.</P>
+
+<P>Assuming all is well, then try a telnet from your linux console ....</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
-@listen = (
- ["gb7baa.dxcluster.net", 8000],
- ["44.131.16.2", 6300],
-);
+telnet localhost 8000
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<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>
-
-<P>Restart the cluster.pl program to enable the listener.</P>
+<P>You should now get the login prompt and be able to login as before.</P>
-<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. </P>
<H2><A NAME="ss4.4">4.4</A> <A HREF="installation_en.html#toc4.4">Setting up for AGW Engine (1.47 onwards)</A>
</H2>
projects / spider.git / blobdiff