<p>
<!-- Created: Sun Dec 13 20:25:14 GMT 1998 -->
<!-- hhmts start -->
-Last modified: Sun Sep 2 21:33:58 BST 2001
+Last modified: Sun Sep 2 22:02:36 BST 2001
<!-- hhmts end -->
<p>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 <a href="install.html">installation</a>
<span class=cmd>client gb7djk telnet</span>
</pre>
- <p>a ax25 example (connecting from GB7DJK, to GB7DXM via my local BPQ node and one X1J intermediate node):-
+ <p>An ax25 example (connecting from GB7DJK, to GB7DXM via my local BPQ node and one X1J intermediate node):-
<pre>
<span class=cmd>timeout 60</span>
for the final "connect" string from the BPQ node that directly connects you to the
cluster node itself.</p>
- <p>A AGW Engine example would be very similar and look like this:-</p>
+ <p>An AGW Engine example would be very similar and look like this:-</p>
<pre>
<span class=cmd>timeout 60</span>
route that you are going to take to the destination, so this will be typically the callsign
of your local node.</p>
- <p>You will notice that the script waits until it sees the left hand string
- of the pair and <b>only then</b> does it send the,
- string on the right
- hand side. This is called a <i>State Machine</i>.</p>
-
- <p>A <i>state machine</i> "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.</p>
+ <p>You will notice that the script <span class=expect>waits</span>
+ until it sees the left hand string of the pair and <b>only
+ then</b> does it <span class=send>send</span> the string on the
+ right hand side. This is called a <i>State Machine</i>.</p>
+
+ <p>A <i>state machine</i> "walks" through a conversation (in this
+ case) looking for "<span class=expect>states</span>" (in this case
+ particular strings) and then performs some "<span
+ class=send>action</span>" (usually some kind of connect command
+ for the type of system you are trying to navigate). When one
+ "<span class=expect>state</span>" "fires"
+ (detects the string are looking for), it <span class=send>sends the command</span>
+ associated with that state and then moves onto the next "<span
+ class=expect>state</span>", in our case: the next line.</p>
<p><b>PLEASE NOTE</b>: the colouration in the above example is for illustrative purposes
only, the debug output is all one colour.</p>
<p>This process is repeated for every line of <tt>chat</tt> script.
<br><br>
- <li><b><span=cmd>client</span></b> starts the connection, put the arguments
+ <li><b><span class=cmd>client</span></b> 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