Revision 7.10
2/28/2012
When the Glider initially makes an Iridium connection via the “
traditional”
PSTN or
RUDICS, it examines the contents of the Glider file:
\config\loginexp.0
This file contains an list of expected lines of text from the Dock Server and what text the
Glider should emit when it sees the expected text. This file must be altered to comply
with the selected authentication method. IF THE GLIDER DOESN'T HEAR WHAT IT
EXPECTS.....IT DISCONNECTS. Consider well the ramifications of that fact. If the
Glider is in the middle of the ocean and there is a bug in the script, or the
loginexp.0
file gets corrupted, or the Dock Server login sequence changes, or ....... you'll never
hear from that Glider again over Iridium.
The default
loginexp.0
that is shipped with the Glider has a commented out script
designed to handle local username/password PAM authentication with:
Glider Username: slocum
Password: WideOpen
The latest shipping version of
loginexp.0
is available at:
The relevant
snippet
of
loginexp.0
is shown below. The comment characters (
#
) in
BOLD
must be removed to activate the script, as the Glider silently ignores any
loginexp.0
that only contains comment lines.
### 2008.07.10 changed example for RUDICS network connection
### with default username/password
# send the required first line to start authentication dialog
#
send 60 "\rAuth\r"
#
expect 60 "login:"
### # send the user_id
#
send 60 "slocum\r"
### # send the password
#
expect 60 "Password:"
#
send 60 "WideOpen\r"
### If we get here the iridium will become a 2nd console
### for the shore-based system's use.
Page 160 of 228
