Help - system(telnet) on WinXP (ssh too)

Hi
I am very new at this. Did some C 15 years ago but not an expert, then or now :)
Have Watcom C free compiler on XP.

Trying to write something (C/PERL/EXPECT ?) that will telnet to a (list of later) device (cisco router) pass my username and password to the device to log in, do some things by passing commands to the telnet window, and, if possible read the screen generated, and decide what to do or not do from that screen. I have a small program telneting to one box working with system("telnet x.x.x.x"); and I can initialize and define char variables with
char *name; and
name="smith";

but I am stuck after this !

example:
telnet a.b.c.d
pass name and password
enable
pass password
show ver
if screen shows IOS is version (have to search for a string) xxx, then do these commands, else, do some others.

Also, does Watcom (or?) have their own telnet or ssh so I don't need to use the system's ?

Well, Telnet is just a raw text-based protocol. Perhaps build your own simple "client"? And write your own telnet doolacky program,

See: http://en.wikipedia.org/wiki/TELNET

I would say this is easier & cleaner than trying to invoke Microsofts Telnet client and read from it...

Look at Winsock (since your on Windows, MSDN is also going to be a valuable guide.)

hth.

Telnet is going away in our environment, so writing a telnet client which I can't take the time learning, is not a good way to spend my time. Telnet is being replaced by ssh, so if I were to write a client, it would be ssh. It would be more likely for me to get a PO approved for someone to write what I need than spend months doing it.

I have hundreds of devices that I can either snmp-configure (which works most of the time) or write something in C or PERL/expect/tcl? I'd prefer C, but I need help obviously. I know my C abilities, and even 15 years ago when I was using Borland C, I was a novice even though I wrote the fastest file finder I knew of. I used to write assy too, but better at reading a PC's BIOS than writing it.

I have to use MSoft's telnet for now, and I will need a command line ssh too. Seems to me someone must have written a real nice telnet/ssh client !

Yes its called Putty :)

http://www.chiark.greenend.org.uk/~sgtatham/putty/

I was -just- about to post that I figured out putty.exe can be used command line....

However, I still need to do a lot of other things....C or PERL or ?

Before I even get to putty I need to determine if the host can run ssh, by telneting then...

I need to tell putty to ignore the fact that the host key is not in the registry (press left arrow then enter).

Then I need to send a password to putty.exe, etc etc...

SMALLSTEP:
How can I send a username and password to Win-telnet used as system ("telnet host"); ?
BTW, these are mostly cisco devices, and 'telnet host -l username' does not work.

Rather than writting a program to control another program, Perhaps edit Putty? After all it is open source... You could easily edit it do get your job done.

From the putty help

Quote:

---

Originally Posted by putty help

Plink (PuTTY Link) is a command-line connection tool similar to UNIX ssh. It is mostly used for automated operations, such as making CVS access a repository on a remote server.

---

> However, I still need to do a lot of other things....C or PERL or ?
Unless you don't know perl at all, or are a C wizard, I'd say perl.

It seems on the face of it that you'll be doing an awful lot of string work, which is super basic stuff in perl, but the same thing in C can be tedious and error prone. Once you've gotten over the initial "hump" of the perl "camel" book, you should be able to do quite a lot quite quickly.

Also, you might also find something which goes some way to solving the problem here - http://www.cpan.org/

Sounds fairly easy. Use netcat to communicate with the remote host, and expect to control the session. Both tools are available on practically any platform.

I'm not keen on perl but after reading for the past 3 hours at perl.org I have yet to find a way to call telnet and pass parameters to it. I'd prefer C. Perl seems to be about the same level as BASIC...

Quote:

---

Perl seems to be about the same level as BASIC...

---

How do you figure that?

Quote:

---

Originally Posted by Mikey

I'm not keen on perl but after reading for the past 3 hours at perl.org I have yet to find a way to call telnet and pass parameters to it. I'd prefer C. Perl seems to be about the same level as BASIC...

---

There's sure nothing like spending 3 hours investigating an entirely new language when the problem could be solved in ten minutes using the tools I mentioned...

I see perl as, not C, not assy, not machine language (1/0)...and like other higher level languages which can -almost- do whatever it is you need, perl/they have loads of extensions, more libraries of functions that might do what you need, all for the same reason is that they don't interact at a low enough level to be able to really do almost everything, like C does. BASIC I see the same way as perl. Just MHO.

You won't start a war with me, I'm not anal about that kind of stuff. ;) I just wanted to know what your reasoning was because I'd never heard that comparison before.

Here's the problem - you're a carpenter, and the only tool in your toolbox is a hammer.

Unable to choose the right tool, you continue to bludgeon the task until it roughly fits the parameters of the problem.

I should point out again that I am not a 'programmer' per se...my goal is to get 500 devices configured, not build the roads so UPS can get them to their destination :) When netcat is suggested it just puts me further behind as I try to download it, recfg my antivirus so it won't boot it off (may not be possible) and then I need to learn expect too...

I am 'back to C' - how can I use windows telnet, and 'win' putty.exe, and pass parameters to them ? Please remember I'm a novice and the learning curve is always steep in the beginning like any language. I don't know how to use expect within a C program even...sorry.

Quote:

---

Originally Posted by Mikey

I should point out again that I am not a 'programmer' per se...my goal is to get 500 devices configured, not build the roads so UPS can get them to their destination :) When netcat is suggested it just puts me further behind as I try to download it, recfg my antivirus so it won't boot it off (may not be possible) and then I need to learn expect too...

---

When you referred to "C/PERL/EXPECT" I assumed that meant you could use expect.

But you make it sound like you don't actually have any experience of any one of them. So out of the three, you are choosing C of all things?

I'm beginning to think that Mikey has 'chosen' C already, and is looking for validation for that decision. Certainly, any attempt to suggest any of the alternatives is met with back peddling.

C might be giving you the most progress on day 1, but it is far from the ideal choice for the whole project.

None of your "problem" needs any of the capabilities of C (the low level kind of stuff), it's all string bashing of one sort or another or managing running various external programs. This puts you into expect or perl territory.

Unless you're seriously considering that this will only take 'a few days', then some time to at least more thoroughly research alternatives (more than a few hours) could be time well spent.
You did say 'months' in an earlier post.

Try as a trivial exercise - should take no more than a day for all 4.
Take the output of "ls" and find all the "file.c" files. Do a "wc -l file.c" on each one of them, then "gcc -c file.c" on the one with the most lines.
Try it in
- C
- perl
- bash
- expect

> I should point out again that I am not a 'programmer' per se
Then you really ought to give this more consideration then
"It would be more likely for me to get a PO approved for someone to write what I need than spend months doing it."

What I like about C is that it is -clear- ... you do something and you know what it going on. With PERL, who knows, does anyone know what the perl interpreter was written in, or, I tried to download perl but what I got was expect and tcl and who knows what else. Seems to me perl if for those that can't or don't want to C.

I suppose if I knew perl and C perl would be easier than C. I also think assy is easier than both as I -know- what is going on !