<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>
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>" "<span class=send>fires</span>"
- (detects the string are looking for), it sends the command
+ "<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>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