<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>
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).</p>
<p>In the case of an <b>ax25</b> session then this would
normally be a call to <tt>/usr/sbin/ax25_call</tt> or
<tt>/usr/sbin/netrom_call</tt> 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!</p>
<p>For <b>agw</b> connections you will need a port number (starting
- from 1) and the callsign of the first "hop" along the way.
- <br><br>
+ from 1) and the callsign of the first "hop" along the way.</p>
<li><b>'</b> is the delimiting character for a word or phrase
of an <span class=expect>expect</span>/<span
in pairs, but either can be empty. Each line reads input from
the connection until it sees the string (or perl regular
expression) that
- is 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.
+ is contained in the left hand string.
+
+ <p>When the <span class=expect>left hand string</span> has found what it is <span class=expect>expecting</span> (if
+ it is) then the <span class=send>right hand string</span> is <span class=send>sent</span> to the connection.</p>
- <p>When the left hand string has found what it is <span class=expect>expecting</span> (if
- it is) then the right hand string is <span class=send>sent</span> to the connection.
+ <p>If the <span class=expect>left hand
+ string</span> is empty then it doesn't read or wait for anything, it
+ simply <span class=send>sends</span> whatever is on the <span class=send>right hand side</span>.</p>
- <p>If the right hand string is empty ('') then nothing is <span class=send>sent</span>, the
+ <p>All comparisons are done ignoring case.</p>
+
+ <p>If the <span class=send>right hand string</span> is empty ('') then nothing is <span class=send>sent</span>, the
script simply moves onto the next line.</P>
- <p>This process is repeated for every line of <tt>chat</tt> script.
- <br><br>
+ <p>This process is repeated for every line of <tt>chat</tt> script.</p>
- <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
projects / spider.git / blobdiff