X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fconnect.html;h=4a4eaa3cd86dadb7e583a7e3b9d7b6b58964982c;hb=refs%2Fheads%2Fnewusers;hp=c6bb4e27be877c2633744d79493055eee19b75ed;hpb=a46e7e063c95e0dc3a470f91568cedb58290769c;p=spider.git diff --git a/html/connect.html b/html/connect.html index c6bb4e27..4a4eaa3c 100644 --- a/html/connect.html +++ b/html/connect.html @@ -64,7 +64,7 @@ Last modified: Sun Sep 2 22:02:36 BST 2001 client gb7djk telnet -

a ax25 example (connecting from GB7DJK, to GB7DXM via my local BPQ node and one X1J intermediate node):- +

An ax25 example (connecting from GB7DJK, to GB7DXM via my local BPQ node and one X1J intermediate node):-

     timeout 60
@@ -86,7 +86,7 @@ Last modified: Sun Sep  2 22:02:36 BST 2001
 	for the final "connect" string from the BPQ node that directly connects you to the
 	cluster node itself.

-

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

+

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

     timeout 60
@@ -213,17 +213,16 @@ Last modified: Sun Sep  2 22:02:36 BST 2001
 		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).
+		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! + 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. -

+ from 1) and the callsign of the first "hop" along the way.

  • ' is the delimiting character for a word or phrase of an expect/When the left hand string has found what it is expecting (if + it is) then the right hand string is sent to the connection.

    -

    When the left hand string has found what it is expecting (if - it is) then the right hand string is sent to the connection. +

    If the left hand + string is empty then it doesn't read or wait for anything, it + simply sends whatever is on the right hand side.

    -

    If the right hand string is empty ('') then nothing is sent, the +

    All comparisons are done ignoring case.

    + +

    If the right hand string is empty ('') then nothing is sent, the script simply moves onto the next line.

    -

    This process is repeated for every line of chat script. -

    +

    This process is repeated for every line of chat script.

    -
  • client starts the connection, put the arguments +
  • 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