+<sect1>Setting up telnet connects (from 1.47 onwards)
+
+<P>
+>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.
+
+<P>
+to make the change happen...
+
+<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.
+
+It comes out of the box looking something like:-
+
+<tscreen><verb>
+@listen = (
+# ["0.0.0.0", 7300],
+);
+</verb></tscreen>
+
+Change it so that it looks like this:-
+
+<tscreen><verb>
+@listen = (
+ ["0.0.0.0", 7300],
+);
+</verb></tscreen>
+
+<p>
+Later versions have more comments in the Listeners.pm file that
+are designed to help you remove the correct '#' character.
+
+<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],
+ ["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 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.
+
+<sect1>Allowing telnet connects from users (before version 1.47 or for special purposes)