<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">
<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">
<meta name="Author" content="Dirk Koopman G1TLH">
+ <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
</head>
<body TEXT="#000000" LINK="#0000ff" VLINK="#800080" BGCOLOR="#FFFFFF">
<p>
<!-- Created: Sun Dec 13 20:25:14 GMT 1998 -->
<!-- hhmts start -->
-Last modified: Wed Dec 23 16:08:12 GMT 1998
+Last modified: Sun Apr 1 18:18:19 BST 2001
<!-- hhmts end -->
<h4>Introduction</h4>
- The standard client program is written in perl and lives in <tt>/spider/perl/client.pl</tt>.
+ The standard client program is written in C and lives in <tt>/spider/src</tt>.
It performs the interface function
between the cluster daemon (<tt>/spider/perl/cluster.pl</tt>) and
- AX25 or Telnet connections, both incoming and outgoing.
+ AX25 or Telnet connections for incoming connections.
+
+ <p>There is a related program called <tt>/spider/perl/console.pl</tt> which,
+ as of version 1.30, is the standard sysop or full duplex telnet user
+ connected interface program. This is a simple screen oriented program
+ that has a bash or shell like command history editing facility as well
+ as a scrolling cluster window with colouration of particular lines of
+ interest (such as DX spots, Announces etc).
+
- <h4>client.pl</h4>
+ <h4>client</h4>
- The client itself is a rather rudimentary program which really only deals with
- things like line end conventions and noticing when a connection goes away. It is
- envisaged that at some time in the nearish future this program will be written in
- C and thus become considerably smaller. But, for the moment and whilst this area
- is under some development, it will remain in perl for ease of change.
+ The client itself is a rather rudimentary program which really
+ only deals with things like line end conventions and noticing when
+ a connection goes away. It is written in C and thus become
+ considerably smaller.
<P>The client can take up two arguments: a "callsign" and a connection type.
<ol>
<p><li>A real callsign (!).
- <P>For incoming connections it is important to make sure that
+ <P>For normal incoming ax25 connections it is important to make sure that
the callsign passed <b>DOES NOT</b> have an SSID (use the %u
or %U in <tt>ax25d.conf</tt>). The DXSpider system largely
ignores what it regards as 'duplicate' callsigns (and that
includes those with SSIDs) except in certain <a
href="#special">special</a> cases.
- <P><li>The name of a <a href="connect.html">connect</a> script.
-
- <p><li><b>login</b> This will cause a unix like <tt>login:</tt> and
- <tt>password:</tt> phase to be run. With version 1.13 the password isn't
- checked unless there is a password recorded in the user file - but you have
- no means of recording a password! (unless you have created a local <tt>set/password</tt>
- command - please donate a copy it you have)
+ <p><li><b>login</b> This will cause a unix like
+ <tt>login:</tt> phase to be run.
- <p>Also in 1.13 only existing users can enter via this means. This will probably
- change, but please discuss this in the <a href="../lists/dxspider-support/index.html">support</a>
- mailing list.
-
</ol>
<p>The connection type can be:-
<p><li><b>ax25</b> This tells the client to use ax25 line conventions.
<p><li><b>telnet</b> This tells the client to use normal unix line conventions.
-
- <p><li><b>connect</b> Start an outgoing <a href="connect.html">connect</a> script.
- Use the line conventions in that script.
</ol>
<p>The connection type can be missing in which case the default is unix line conventions.
The client only uses files when in the <b>login</b> phase. It
prints the <tt>/spider/data/issue</tt> file, if it is present, to
the user before issuing the <tt>login:</tt> prompt. After a callsign
- and password is entered it uses
- the standard cluster user file to check them.
+ is entered it uses
+ the standard cluster user file to check it.
<p>Having said all of that the client <em>appears</em> to use the following files and
sends them to the user if they are present:-
<ul>
+ <li><b>/spider/data/issue</b> which is sent before a login prompt.
+ <li><b>/spider/data/connect</b> which is sent immediately after a successful login.
<li><b>/spider/data/motd</b> which is sent to the user on normal user startup.
<li><b>/spider/data/logout</b> which is sent to user on disconnection.
<li><b>/spider/data/offline</b> which is sent to the user if the cluster daemon
projects / spider.git / blobdiff