topic Re: Telneting within a script in Operating System - HP-UX

Telneting within a script

Philip Lunney — Fri, 26 Apr 2002 09:06:09 GMT

I have a script to telnet from one server to another...looks something like this:

#!/bin/ksh
REMOTE=server2
(sleep 1
echo username
sleep 2
echo password) | telnet $REMOTE

It works between some servers but not all and when it fails it kicks you out with the message " Connection closed by foreign host."

You can telnet normally between the servers but for some reason it doesn't like my script. Anyone know of any settings that might be preventing this??

Thanks Barbara.

Re: Telneting within a script

Deepak Extross — Fri, 26 Apr 2002 09:11:23 GMT

Just a shot in the dark, but try increasing the sleep period. Maybe it takes a little longer for some machines to prompt for the username / password.
And consider using Expect. Quite a handy tool for such stuff.

Re: Telneting within a script

Philip Lunney — Fri, 26 Apr 2002 09:16:07 GMT

Deepak

Thanks but I tried increasing the sleep but it doesn't even seem to get as far as the password, it returns the connection closed straight away! Any other ideas?

Also what is Expect??

Re: Telneting within a script

U.SivaKumar_2 — Fri, 26 Apr 2002 09:20:43 GMT

hi,
i think the problem is with carriage return
try putting ; at the end of all your script
shell commands.

regards,
U.SivaKumar

Re: Telneting within a script

Paula J Frazer-Campbell — Fri, 26 Apr 2002 09:31:28 GMT

HI

Run it

ksh -x ./<script name>

and watch it run, it may give you and indication as to where the problem is.

Paula

Re: Telneting within a script

Deepak Extross — Fri, 26 Apr 2002 09:31:34 GMT

Barbara,

See http://expect.nist.gov/

Does the account get locked after a few failed logins attempts, by any chance?

Re: Telneting within a script

Volker Borowski — Fri, 26 Apr 2002 09:42:56 GMT

Hi,

I found that this works with HPUX (at least 10.20 and 11.00) but i.e. not with a linux telnet.

Obviously it depends on the security thinking of the programmer. Now linux guys are hardliners in this case, so I found in linux programs that they flush the input stream before they ask for a password (to avoid, that you mistype something and the password appears in cleartext on the screen).

Such a program will never be able to be scripted in this way, because the entire pipe stream is flushed. HP-UX is more tolerant with this, but I do not know if this has been changed in 11.11 or so.

Hope this helps
Volker

Re: Telneting within a script

Frank Slootweg — Fri, 26 Apr 2002 12:39:07 GMT

The problem is (non) handshaking/timing. I.e. normally when you use telnet interactively, you *wait* for a certain prompt/reaction and *then* give the next command. In a script that does not happen, because the script does not wait. You can *try* to workaround that with sleeps, but, *if* it works at all, such scripts will fail at some time, often with obscure results. I have had such scripts which failed *years* after working 'correctly'.

The solution is the mentioned "expect" program, which was especially designed for problems like this.

Re: Telneting within a script

Craig Rants — Fri, 26 Apr 2002 12:43:33 GMT

I agree with Frank, expect is usually the way to go with telnet and ftp connections in scripts. I personally would look at setting up secure shell trusts, thus protecting your password from running in the clear and negating the use of expect.

GL,
C

Re: Telneting within a script

A. Clay Stephenson — Fri, 26 Apr 2002 13:27:51 GMT

I don't do this in the shell anymore at all. Instead I use the Perl Net::Telnet which is available from www.perl.org/CPAN.

Here is a simple example extracted from the man pages:

use Net::Telnet ();
my $username = "Clay";
my $passwd = "TOPSECRET";
my $remote_host = "bugs";
$t = new Net::Telnet (Timeout => 30,
Prompt => '/sh\$ $/');
$t->open($remote_host);
$t->login($username,$passwd);
@lines = $t->cmd("/usr/bin/ls -l /etc");
print @lines;

The beauty of this method is that it becomes trivially easy to add error checking.

Re: Telneting within a script

Mark Greene_1 — Fri, 26 Apr 2002 15:30:01 GMT

the problem is telnet is designed to want a tty on the originating end of the connection. You can try wrapping this around your script:

mknod pipe p
executable_file < pipe | telnet nnn.nnn.nnn.nnn > pipe 2>telnet.log
rm pipe

HTH
mark

Re: Telneting within a script

Ron Kinner — Fri, 26 Apr 2002 19:23:16 GMT

This is from a script that I use to talk to a 3Com switch. I don't need the \r to talk to a Cisco router but the 3Com seems to require the \r after each line in order to work. You also may need a little extra sleep time at the beginning to make sure the connection is up before you try to logon. The first empty echo is required by the 3Com to wake it up.

(sleep 5
echo "\r"
sleep 1
echo "login\r"
sleep 1
echo "password\r"
sleep 2
echo "\r") |telnet $REMOTE

Ron

Re: Telneting within a script

Ryan Moore — Tue, 30 Apr 2002 15:11:25 GMT

Try,

#!/bin/ksh
REMOTE=server2
(sleep 1
echo username
sleep 2
echo password
sleep 5) | telnet $REMOTE

Your subshell was ending and dropping the telnet connection.

Hope this helps,

rhino

Re: Telneting within a script

Vincent Fleming — Tue, 30 Apr 2002 16:00:10 GMT

I like my old shell trick... it doesn't require any sleeps at all:

telnet $server <

Re: Telneting within a script

Ryan Moore — Tue, 30 Apr 2002 19:54:45 GMT

I tried this on Solaris 8 in bourne shell and Linux 7.0 with bash and bourne shell and this does not work for me.

What system and shell did you use to make this work?

Thanks,

rhino