-Last modified: Sun Sep 2 21:33:58 BST 2001 +Last modified: Sun Sep 2 22:02:36 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 @@ -64,7 +64,7 @@ Last modified: Sun Sep 2 21:33:58 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 21:33:58 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
@@ -167,17 +167,20 @@ Last modified: Sun Sep 2 21:33:58 BST 2001
route that you are going to take to the destination, so this will be typically the callsign
of your local node.
- You will notice that the script waits until it sees the left hand string
- of the pair and only then does it send the,
- string on the right
- hand side. This is called a State Machine.
-
- A state machine "walks" through a conversation (in this case) looking
- for "states" (in this case particular strings) and then performs some
- "action" (usually some kind of connect command for the type of system
- you are trying to navigate). When one "state" "fires" (detects the string
- are looking for), it sends the command associated with that state and then
- moves onto the next "state", in our case: the next line.
+ You will notice that the script waits
+ until it sees the left hand string of the pair and only
+ then does it send the string on the
+ right hand side. This is called a State Machine.
+
+ A state machine "walks" through a conversation (in this
+ case) looking for "states" (in this case
+ particular strings) and then performs some "action" (usually some kind of connect command
+ for the type of system you are trying to navigate). When one
+ "state" "fires"
+ (detects the string are looking for), it sends the command
+ associated with that state and then moves onto the next "state", in our case: the next line.
PLEASE NOTE: the colouration in the above example is for illustrative purposes
only, the debug output is all one colour.
@@ -210,17 +213,16 @@ Last modified: Sun Sep 2 21:33:58 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.
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.
-