The Standard Client

From: djk Date: Mon, 21 Dec 1998 12:32:06 +0000 (+0000) Subject: added client file X-Git-Tag: R_1_13~1 X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=commitdiff_plain;h=c4284750b659c9f1ce58119a13daf4c52e3c1e38;p=spider.git added client file --- diff --git a/html/client.html b/html/client.html new file mode 100644 index 00000000..b63ec801 --- /dev/null +++ b/html/client.html @@ -0,0 +1,119 @@ + + + + The Standard Client + Connecting to other Clusters + + + + + + + +

The Standard Client

+ + + +

Dirk Koopman G1TLH

+ + +Last modified: Mon Dec 21 12:26:18 GMT 1998 + + +

Introduction

+ + The standard client program is written in perl and lives in /spider/perl/client.pl. + It performs the interface function + between the cluster daemon (/spider/perl/cluster.pl) and + AX25 or Telnet connections, both incoming and outgoing. + +

client.pl

+ + 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 can take up two arguments: a "callsign" and a connection type. + +

The "callsign" can have the following values:- +

A real callsign (!). + +
For incoming connections it is important to make sure that + the callsign passed DOES NOT have an SSID (use the %u + or %U in ax25d.conf). The DXSpider system largely + ignores what it regards as 'duplicate' callsigns (and that + includes those with SSIDs) except in certain special cases. + +
The name of a connect script. + +
login This will cause a unix like login: and + password: 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 set/password + command - please donate a copy it you have) + +
Also in 1.13 only existing users can enter via this means. This will probably + change, but please discuss this in the support + mailing list. + +

+ +

The connection type can be:- +

ax25 This tells the client to use ax25 line conventions. + +
telnet This tells the client to use normal unix line conventions. + +
connect Start an outgoing connect script. + Use the line conventions in that script. +

+ +

The connection type can be missing in which case the default is unix line conventions. + +

If both the callsign and the connection are missing then it is + assumed that the client is the sysop and uses the callsign set in + your local copy of DXVars.pm. + +

Considerations

+ + As mentioned earlier, SSIDs are generally stripped from + callsigns except in two cases: +

For Cluster node callsigns. Although here in the UK we are issued with + special callsigns to run cluster nodes and BBSs, this is not universal. Therefore + by marking a callsign as a node you disable SSID checking. You will have to treat + incoming cluster callsigns specially in ax25d.conf to use this feature (i.e + you will have to set up a line specially for that callsign with a %s or %S for the + callsign substitution [better just put the callsign you want!]). + +
The sysop callsign set up in your local copy of + DXVars.pm. You must call client.pl with + no parameters for this to work. +

+ +

Files

+ + The client only uses files when in the login phase. It + prints the /spider/data/issue file, if it is present, to + the user before issuing the login: prompt. After a callsign + and password is entered it uses + the standard cluster user file to check them. + + + +

+ + Copyright © 1998 by Dirk Koopman G1TLH. All Rights Reserved
+ + $Id$ + + diff --git a/html/hops.html b/html/hops.html index 5ffa84c3..1da20554 100644 --- a/html/hops.html +++ b/html/hops.html @@ -19,7 +19,7 @@

-Last modified: Sun Dec 20 18:15:15 GMT 1998 +Last modified: Mon Dec 21 11:57:54 GMT 1998

Introduction

@@ -120,7 +120,7 @@ $def_hopcount = 15; is working at least as well as advertised) you should keep the default hop counts down to the sort of levels shown above. -

Isolated Networks

It is possible to isolate networks from each other on a "gateway" node using the set/isolate <node call> command. diff --git a/html/index.html b/html/index.html index 72e277a5..f10c0265 100644 --- a/html/index.html +++ b/html/index.html @@ -18,7 +18,7 @@

-Last modified: Sun Dec 20 16:25:28 GMT 1998 +Last modified: Mon Dec 21 11:58:48 GMT 1998

The DXSpider dx cluster system is written in perl5 as an exercise in self-training for both protocol research and teaching myself perl. @@ -28,8 +28,9 @@ Last modified: Sun Dec 20 16:25:28 GMT 1998

Installation of the main cluster software.
Installing the lastest version of CPAN. +
Explaining the client.pl program.
Connecting to other clusters. -
Hop control, network isolation etc. +
Hop control, network isolation etc.
Download the software and any patches.

diff --git a/html/install.html b/html/install.html index 089854b7..753144b7 100644 --- a/html/install.html +++ b/html/install.html @@ -17,7 +17,7 @@

Iain Phillips G0RDI

-Last modified: Sun Dec 20 17:55:19 GMT 1998 +Last modified: Mon Dec 21 11:26:05 GMT 1998

This HOWTO describes the installation for DX Spider v1.11 on a "vanilla" RedHat 5.1 platform, @@ -246,7 +246,7 @@ default * * * * * * - sysop /spider/perl/client.pl client.pl %u ax25

This has to be done to allow you to specify the correct callsigns on outgoing connects -

Login to your computer as sysop, and create the initial DX Spider parameters necessary to start the cluster for the first time. +

Login to your computer as sysop, and create the initial DX Spider parameters necessary to start the cluster for the first time.

 $ startx			(much easier to use X)
 $ cd /spider