1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
4 <title>The Standard Client</title>
5 <meta name="Keywords" content="DX Cluster, DXSpider, Spider, Packet Cluster, DXCluster, Pavillion Software, AK1A, AX25, AX.25, WWV, Packet Radio, Amateur Radio, Propagation, DX, DXing, G1TLH, GB7TLH, Dirk Koopman, Mailing list, Linux, RedHat, PERL">
6 <meta name="Description" content="Software and systems for realtime digital communications between amateur radio stations for the provision of information on propagation conditions and stations operating">
7 <meta name="Author" content="Dirk Koopman G1TLH">
10 <body TEXT="#000000" LINK="#0000ff" VLINK="#800080" BGCOLOR="#FFFFFF">
11 <FONT COLOR="#606060">
13 <h2>The Standard Client</h2>
18 <address><a href="mailto:djk@tobit.co.uk">Dirk Koopman G1TLH</a></address>
20 <!-- Created: Sun Dec 13 20:25:14 GMT 1998 -->
22 Last modified: Wed Dec 23 16:08:12 GMT 1998
27 The standard client program is written in perl and lives in <tt>/spider/perl/client.pl</tt>.
28 It performs the interface function
29 between the cluster daemon (<tt>/spider/perl/cluster.pl</tt>) and
30 AX25 or Telnet connections, both incoming and outgoing.
34 The client itself is a rather rudimentary program which really only deals with
35 things like line end conventions and noticing when a connection goes away. It is
36 envisaged that at some time in the nearish future this program will be written in
37 C and thus become considerably smaller. But, for the moment and whilst this area
38 is under some development, it will remain in perl for ease of change.
40 <P>The client can take up two arguments: a "callsign" and a connection type.
42 <p>The "callsign" can have the following values:-
44 <p><li>A real callsign (!).
46 <P>For incoming connections it is important to make sure that
47 the callsign passed <b>DOES NOT</b> have an SSID (use the %u
48 or %U in <tt>ax25d.conf</tt>). The DXSpider system largely
49 ignores what it regards as 'duplicate' callsigns (and that
50 includes those with SSIDs) except in certain <a
51 href="#special">special</a> cases.
53 <P><li>The name of a <a href="connect.html">connect</a> script.
55 <p><li><b>login</b> This will cause a unix like <tt>login:</tt> and
56 <tt>password:</tt> phase to be run. With version 1.13 the password isn't
57 checked unless there is a password recorded in the user file - but you have
58 no means of recording a password! (unless you have created a local <tt>set/password</tt>
59 command - please donate a copy it you have)
61 <p>Also in 1.13 only existing users can enter via this means. This will probably
62 change, but please discuss this in the <a href="../lists/dxspider-support/index.html">support</a>
67 <p>The connection type can be:-
69 <p><li><b>ax25</b> This tells the client to use ax25 line conventions.
71 <p><li><b>telnet</b> This tells the client to use normal unix line conventions.
73 <p><li><b>connect</b> Start an outgoing <a href="connect.html">connect</a> script.
74 Use the line conventions in that script.
77 <p>The connection type can be missing in which case the default is unix line conventions.
79 <p>If both the callsign and the connection are missing then it is
80 assumed that the client is the sysop and uses the callsign set in
81 your local copy of <a href="install.html#dxvar">DXVars.pm</a>.
83 <h4>Considerations</h4>
85 <a name="special"></a>As mentioned earlier, SSIDs are generally stripped from
86 callsigns except in two cases:
88 <p><li>For Cluster node callsigns. Although here in the UK we are issued with
89 special callsigns to run cluster nodes and BBSs, this is not universal. Therefore
90 by marking a callsign as a node you disable SSID checking. You will have to treat
91 incoming cluster callsigns specially in <tt>ax25d.conf</tt> to use this feature (i.e
92 you will have to set up a line specially for that callsign with a %s or %S for the
93 callsign substitution [better just put the callsign you want!]).
95 <p><li>The sysop callsign set up in your local copy of
96 <a href="install.html#dxvar">DXVars.pm</a>. You must call <tt>client.pl</tt> with
97 no parameters for this to work.
102 The client only uses files when in the <b>login</b> phase. It
103 prints the <tt>/spider/data/issue</tt> file, if it is present, to
104 the user before issuing the <tt>login:</tt> prompt. After a callsign
105 and password is entered it uses
106 the standard cluster user file to check them.
108 <p>Having said all of that the client <em>appears</em> to use the following files and
109 sends them to the user if they are present:-
111 <li><b>/spider/data/motd</b> which is sent to the user on normal user startup.
112 <li><b>/spider/data/logout</b> which is sent to user on disconnection.
113 <li><b>/spider/data/offline</b> which is sent to the user if the cluster daemon
117 <!-- Standard Footer!! -->
120 <FONT COLOR="#606060"><hr></font>
121 <font color="#FF0000" size=-2>
122 Copyright © 1998 by Dirk Koopman G1TLH. All Rights Reserved<br>
124 <font color="#000000" size=-2>$Id$</font>