<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider User Manual v1.49: Logins and logouts.</TITLE>
+ <TITLE>The DXSpider User Manual v1.50: Logins and logouts.</TITLE>
<LINK HREF="usermanual-3.html" REL=next>
<LINK HREF="usermanual-1.html" REL=previous>
<LINK HREF="usermanual.html#toc2" REL=contents>
<H2><A NAME="ss2.3">2.3 Telnet logins.</A>
</H2>
-<P>Because DXSpider runs under the Linux operating system, it is possible to
-make a direct telnet connection into the cluster. With telnet
-connections, the source callsign is not seen by DXSpider, so you will be
-asked to login with your callsign.
+<P>With telnet connections, the source callsign is not seen by DXSpider, so
+you will be asked to login with your callsign.
To telnet to DXSpider, you would connect to a specific port. There is no
standard at the moment for a cluster telnet port but ask the sysop if
you are unsure.
command if you are connected via telnet.
If you do not log out gracefully using one of the above commands,
you may find you are unable to get a full connect next time. This
-may also happen if a NETRom connection drops. You may get connected,
+may also happen if a netrom connection drops. You may get connected,
but nothing else will happen because the program thinks you are still
connected and will not let you connect twice under the same call.
However you could reconnect by adding a number to the end of your call,
-for example G0YLM2.
+for example G0YLM-2.
This can be done by either altering your MYCALL setting in the TNC or
by altering your program configuration.
<P>
projects / spider.git / blobdiff