1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
4 <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
5 <TITLE>The DXSpider User Manual v1.50: Logins and logouts.</TITLE>
6 <LINK HREF="usermanual-3.html" REL=next>
7 <LINK HREF="usermanual-1.html" REL=previous>
8 <LINK HREF="usermanual.html#toc2" REL=contents>
9 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="usermanual-3.html">Next</A>
13 <A HREF="usermanual-1.html">Previous</A>
14 <A HREF="usermanual.html#toc2">Contents</A>
16 <H2><A NAME="s2">2.</A> <A HREF="usermanual.html#toc2">Logins and logouts.</A></H2>
18 <P>You might not think that there is a lot of point of including a
19 section on how to log in and out of DXSpider. However, you would be
20 suprised at the difficulties some people have in simply getting in
21 and out of the cluster!</P>
22 <P>There are several ways a login might be achieved, dependant on how
23 the sysop has DXSpider configured. It is impossible for me to cover all
24 variations but here are the basic ones.</P>
26 <H2><A NAME="ss2.1">2.1</A> <A HREF="usermanual.html#toc2.1">AX25 logins.</A>
29 <P>Simplicity itself. The usual <B>CONNECT</B> command will log you straight
30 into the cluster and you will not have to do anything else.
31 Obviously, you will have to connect to the correct callsign. Some
32 nodes use an SSID with their call so you would have to add that.</P>
33 <P><B>Examples:</B></P>
43 <H2><A NAME="ss2.2">2.2</A> <A HREF="usermanual.html#toc2.2">Netrom logins.</A>
46 <P>There are several possibilities here, dependant on how the sysop has
47 configured his system. If you are connecting via netrom then you are
48 most probably connecting from another station. Listing the nodes in
49 that station with the <B>NODES</B> command will tell you what callsign
50 or netrom alias to connect to. Then just issue the connect command
51 from there. It is possible that the netrom alias may connect you to
52 a node with an alias for the cluster, such as DXC. Just type this
53 and you will be connected.</P>
62 <H2><A NAME="ss2.3">2.3</A> <A HREF="usermanual.html#toc2.3">Telnet logins.</A>
65 <P>With telnet connections, the source callsign is not seen by DXSpider, so
66 you will be asked to login with your callsign.
67 To telnet to DXSpider, you would connect to a specific port. There is no
68 standard at the moment for a cluster telnet port but ask the sysop if
70 <P><B>Example:</B></P>
78 <P>All the above are possible ways of connecting to a DXSpider cluster. You
79 may have some or all of these available to you. There may be one or
80 two additional ways to connect dependant on the network local to you.
81 However I am sure you get the idea.</P>
83 <H2><A NAME="ss2.4">2.4</A> <A HREF="usermanual.html#toc2.4">Logouts.</A>
86 <P>Logging out can be done by simply issuing the standard <B>BYE</B>
88 <P>You could also send a disconnect if you are using AX25, or a <B>CLOSE</B>
89 command if you are connected via telnet.
90 If you do not log out gracefully using one of the above commands,
91 you may find you are unable to get a full connect next time. This
92 may also happen if a netrom connection drops. You may get connected,
93 but nothing else will happen because the program thinks you are still
94 connected and will not let you connect twice under the same call.
95 However you could reconnect by adding a number to the end of your call,
97 This can be done by either altering your MYCALL setting in the TNC or
98 by altering your program configuration. </P>
102 <A HREF="usermanual-3.html">Next</A>
103 <A HREF="usermanual-1.html">Previous</A>
104 <A HREF="usermanual.html#toc2">Contents</A>