-<P>Cluster links in particular suffer greatly from the presence of telnet echo. This is caused
-by the telnet negotiation itself and can create at worst severe loops. At best it creates
-unnecessary bandwidth and large logfiles! There are things that can be done to limit this
-problem but will not always work dependent on the route taken to connect.
-<P>
-<P>Telnet echo itself should only be a problem if the connection is being made to the telnet
-port (23). This port uses special rules that include echo negotiation. If the connection
-is to a different port, such as 8000, this negotiation does not happen and therefore no
-echo should be present.
-<P>
-<P>Sometimes it is not possible to make a direct connection to another node and this can
-cause problems. There is a way of trying to suppress the telnet echo but this will not
-always work, unfortunately it is difficult to be more specific. Here is an example
-of what I mean ...
+<P>Cluster links in particular suffer greatly from the presence of telnet echo.
+This is caused by the telnet negotiation itself and can create at worst severe
+loops. At best it creates unnecessary bandwidth and large logfiles! There are
+things that can be done to limit this problem but will not always work dependent
+on the route taken to connect.
+<P>
+<P>Telnet echo itself should only be a problem if the connection is being made to
+the telnet port (23). This port uses special rules that include echo negotiation.
+If the connection is to a different port, such as 8000, this negotiation does
+not happen and therefore no echo should be present.
+<P>
+<P>Sometimes it is not possible to make a direct connection to another node and this
+can cause problems. There is a way of trying to suppress the telnet echo but
+this will not always work, unfortunately it is difficult to be more specific.
+Here is an example of what I mean ...