X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fconnect.html;h=76ec9df48552aad974da50227104d91536ac13d2;hb=63b5e2134b2ffba051682618f88b09d5ee5457c7;hp=cb349e6ccefaabd04e77b04fe2b50a823d34f1c7;hpb=69c8aeb338cc485103e289fbab7ec4e7e056ed20;p=spider.git diff --git a/html/connect.html b/html/connect.html index cb349e6c..76ec9df4 100644 --- a/html/connect.html +++ b/html/connect.html @@ -5,6 +5,7 @@ + @@ -19,7 +20,7 @@

-Last modified: Thu Dec 17 00:06:40 GMT 1998 +Last modified: Tue Apr 10 00:21:34 BST 2001

At the moment, anybody can connect inwards at any time from outside, either by ax25 or by telnet (assuming you have followed the instructions in installation @@ -28,29 +29,66 @@ Last modified: Thu Dec 17 00:06:40 GMT 1998

Connect scripts live in the /spider/connect directory and are simple ascii scripts that are written using a normal editor. There are a couple of examples in the issue directory. -

Here are a couple of basic types, first a telnet connection:- +

Here are a few of basic types, first a telnet connection where the + client is set up in the passwd file thus:- +

+    gb7djk:x:1372:1291::/home/gb7djk:/usr/bin/perl /spider/perl/client.pl gb7djk telnet
+

+ and the connect script would be:-

     timeout 15
     # this is a comment
     connect telnet dirkl.tobit.co.uk
     'login' 'gb7djk'
     'word' 'gb7djk'
-    client gb7djk-1 telnet
+    client gb7djk telnet

and an ax25 example:- +

For a connect that requires a login and execution of the programs + from a normal shell, do:- + +

+    timeout 15
+    connect telnet dirkl.tobit.co.uk
+    'login' 'gb7djk'
+    'word' 'gb7djk'
+    '\$' 'cd /spider/perl'
+    # set the line to prevent echoing, leaving this out will
+    # confuse whole networks for hours!
+    '\$' 'stty -echo raw'
+    # tell GB7DJK that you are GB7DJK-1
+    '\$' '/spider/src/client gb7djk-1 telnet'
+    # tell GB7DJK-1 that it is connected to GB7DJK
+    # you can leave this out if you call this script 'gb7djk'
+    client gb7djk telnet
+

+ +

a ax25 example:-

     timeout 60
     abort (Busy|Sorry|Fail)
     # don't forget to chmod 4775 netrom_call!
-    connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
+    connect ax25 /usr/sbin/netrom_call bbs gb7djk-0 g1tlh-0
+    'Connect' ''
+    'Connect' 'c np7'
+    'Connect' 'c gb7dxm'
+    'Connect' ''
+

+ + The -0 ssid is important if you want it to work reliably. Obviously if you are + using a different ssid then you would use that. + +

A AGW Engine example would be very similar and look like this:- +

+    timeout 60
+    abort (Busy|Sorry|Fail)
+    connect agw 2 g1tlh
     'Connect' ''
     'Connect' 'c np7'
     'Connect' 'c gb7dxm'
     'Connect' ''
-    client gb7dxm ax25

A connection is started manually by typing in connect on a sysop enabled +

A connection is started manually by typing in connect <scriptname> on a sysop enabled client.pl session. For example:-

     G1TLH de GB7DJK 13-Dec-1998 2041Z > connect gb7djk-1
@@ -58,7 +96,8 @@ Last modified: Thu Dec 17 00:06:40 GMT 1998
     G1TLH de GB7DJK 13-Dec-1998 2043Z >

You can watch the progress of the connection (if you have the standard debugging enabled) on the +

You can watch the progress of the connection (if you have connect + debugging enabled [set/debug connect]) on the cluster.pl screen and you should see something like this:-

     <- D G1TLH connect gb7djk-1
@@ -90,31 +129,69 @@ Last modified: Thu Dec 17 00:06:40 GMT 1998
     etc

The connect scripts consist of lines which start with the following keywords or symbols:- +

The connect scripts consist of lines which start with the + following keywords or symbols:- +

# All lines starting with a # are ignored, as are wholly blank lines. -
timeout followed by a number is the number of seconds to wait for a command - to complete. If there is no timeout specified in the script then the default is 60 seconds. -
abort is a regular expression containing one or more strings to look for to abort a - connection. This is a perl regular expression and is executed ignoring case. -
connect followed by ax25 or telnet and some type dependent information. In - the case of a telnet connection, there can be up to two parameters, the first is the ip - address or hostname of the computer you wish to connect to and the second is the port number you - want to use (this can be left out if it is a normal telnet session). -
In the case of an ax25 session then this would normally be a call to ax25_call - or netrom_call as in the example above. It is your responsibility to get your node - and other ax25 parameters to work before going down this route! -
' or " are the delimiting characters for a chat type script. They normally - come in pairs, either can be empty. Each line reads input from the connection until it sees the string - (or perl regular expression) contained in the left hand string. If the left hand string is empty then - it doesn't read or wait for anything. The comparison is done ignoring case. -
When the left hand string has found what it is looking (if it is) then the right hand string is - sent to the connection. + +
# All lines starting with a # are + ignored, as are wholly blank lines. +

+ +
timeout followed by a number is the number of + seconds to wait for a command to complete. If there is no + timeout specified in the script then the default is 60 + seconds. +

+ +
abort is a regular expression containing one or + more strings to look for to abort a connection. This is a perl + regular expression and is executed ignoring case. +

+ +
connect followed by ax25, telnet or agw + and some type dependent information. + +
In the case of a + telnet connection, there can be up to two parameters, + the first is the ip address or hostname of the computer you + wish to connect to and the second is the port number you want + to use (this can be left out if it is a normal telnet + session). + +
In the case of an ax25 session then this would + normally be a call to /usr/sbin/ax25_call or + /usr/sbin/netrom_call as in the example above. It is your + responsibility to get your node and other ax25 parameters to + work before going down this route! + +
For agw connections you will need a port number (starting + from 1) and the callsign of the first "hop" along the way. +

+ +
' is the delimiting character for a word or + phrase of an expect/send line in a chat type + script. The words/phrases normally come in pairs, either can + be empty. Each line reads input from the connection until it + sees the string (or perl regular expression) contained in the + left hand string. If the left hand string is empty then it + doesn't read or wait for anything. The comparison is done + ignoring case. + +
When the left hand string has found what it is looking (if + it is) then the right hand string is sent to the connection. +
This process is repeated for every line of chat script. -
client starts the connection, put the arguments you would want here if you were - starting the client program manually. You only need this if the script has a different name to - the callsign you are trying to connect to (i.e. you have a script called other which actually - connects to GB7DJK-1 [instead of a script called gb7djk-1]). +

+ +
client starts the connection, put the arguments + you would want here if you were starting the client program + manually. You only need this if the script has a different + name to the callsign you are trying to connect to (i.e. you + have a script called other which actually connects to + GB7DJK-1 [instead of a script called + gb7djk-1]). +