Mailing List Archive

It sounds like your TTY may be set for "local echo"... if you
have NOTHING connected to the port, and use telnet to connect,
and then type, you see the characters, correct? The 'double
characters' come from your terminal displaying what you type,
and then the character is returned from the remote device...

In normal operation, you would NOT see what you typed...it
would only be sent to the 'far end', and you would rely on the
far device to return your keystrokes...

To test this theory, conect it to something that wants a password
to log in...type the username as norlam (you will see the double
characters, but the far end will only see one of each)...when you
type the password, one character will be "clear text", and the other
will be an asterisk (*, if the system masks the input), or you may
only see the single clear-text password if the system doesn't show
any masking characters.

Take a look at your termcap?

-Z-
_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users

Hi David,



Thanks for your help.



As soon as I connect (after "^Ec;"), when I press enter once the remote system CLI (Command Line Interface) of the switch will send a "login:" prompt. However, it shows it twice like if I had pressed enter twice. So I can't login because the same happens to the passord...



I am trying to "buy" a dynamic DNS to give public access to my lab, so anyone can come in, check it, change it, try it, etc. By the way, I forgot to mention that I am using getty as the Telnet client. So the full lab environment is:



An Intel IBM-PC;

CentOS 4.2 (Linux kernel 2.6);

The standard IBM PC serial pors (COM1, COM2);

The config I published in my first e-mail;

Getty as the Telnet client;

Logging in as "root";

An Alcatel switch and a 3Com ADSL modem as console to be remotely accessed;



Any help will be appreciated!



Thanks,



Moacir Ferreira


________________________________

From: David K. Z. Harris on behalf of David K. Z. Harris
Sent: Mon 9/4/2006 7:58 PM
To: Moacir Ferreira; users@conserver.com
Subject: Re: Telnet, again...



It sounds like your TTY may be set for "local echo"... if you
have NOTHING connected to the port, and use telnet to connect,
and then type, you see the characters, correct? The 'double
characters' come from your terminal displaying what you type,
and then the character is returned from the remote device...

In normal operation, you would NOT see what you typed...it
would only be sent to the 'far end', and you would rely on the
far device to return your keystrokes...

To test this theory, conect it to something that wants a password
to log in...type the username as norlam (you will see the double
characters, but the far end will only see one of each)...when you
type the password, one character will be "clear text", and the other
will be an asterisk (*, if the system masks the input), or you may
only see the single clear-text password if the system doesn't show
any masking characters.

Take a look at your termcap?

-Z-

> However, when I start using the connection it works like if I where =
> pressing the enter key twice... This happens only when I connect to any =
> equipment console.

There's a telnet option which maps EOL to <CR><LF>; You'll want to
turn that off for certain consoles. E.g. for Unix-based telnet client,
it's probably "unset crlf", or something similar.

Regards,

Marion



_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users

Sorry for my late answers but I am at London time...

I have tested it using Tera Term, Putty, Microsoft Telnet (Windows XP) and Linux telnet. Tera Term won't work. Linux Telenet will get "loose" once I try to connect (after "^Ec;"), Putty and Microsoft Telnet works like the same, after "^Ec;" when I press enter I get the "login:" message twice. I wish I can make my test lab public so you can come in and check what is wrong.

If anyone reading this thread has already faced this problem, please let me know how to overcome it! It must be something I am doing wrong... Conserver is already a "mature" product so it must be my fault...

Moacir

________________________________

From: users-bounces@conserver.com on behalf of Marion Hakanson
Sent: Tue 9/5/2006 6:12 PM
To: Moacir Ferreira
Cc: David K. Z. Harris; users@conserver.com
Subject: Re: Telnet, again...



> However, when I start using the connection it works like if I where =
> pressing the enter key twice... This happens only when I connect to any =
> equipment console.

There's a telnet option which maps EOL to <CR><LF>; You'll want to
turn that off for certain consoles. E.g. for Unix-based telnet client,
it's probably "unset crlf", or something similar.

Regards,

Marion



_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users

MFerreira@comstore.pt said:
> I have tested it using Tera Term, Putty, Microsoft Telnet (Windows XP) and
> Linux telnet. Tera Term won't work. Linux Telenet will get "loose" once I try
> to connect (after "^Ec;"), Putty and Microsoft Telnet works like the same,
> after "^Ec;" when I press enter I get the "login:" message twice. I wish I
> can make my test lab public so you can come in and check what is wrong.

I've used putty in this mode to connect to an IOLAN Rack+ (reverse telnet).
To get rid of the "double return" problem, after you've started the putty
connection, right-click on the top of the putty window, select the
"Change Settings" item, then "Telnet", then de-select the check-box
labelled "Return key sends Telnet New Line instead of ^M". Can't help
you with the other telnet clients.

Regards,

Marion



_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users

Thanks for your help Marion. I tested what you said using Putty and the behaviour has changed. I let Putty with its original setup up to the "^Ec;" sequence then I do what you say. Now when I press the return key Conserver I will get a single "^@login:" and it should be just "login:". Then I type the logon name (in my case "admin") and hit enter again and I will get a "admin" reply followed by a new line showing "^@login:" again and I can't login. Now I am sure that, for somehow, Conserver does not behave well when we connect to the server using Telnet. The first question I have is: Does anyone know any Telnet client that could be used in a Windows environment?



By other hand, it would be perfect if I let people login remotely to the Conserver box (lets say using Putty over SSH that is perfect for security reasons) and then let this user run the original Conserver console client. However, I am pretty dumb when it comes to configure Linux. I don't know how to configure it so the remote user could not mess with the server... So, alternatively to my question above, does anyone in this thread knows a "howto" for dummies for setting up this remote access without allowing a user to mess with the server?



Reading the e-mail threads about Telnet I could see that people does not understand why would someone use Telnet and Windows... I am trying to assemble a network lab where my clients could come in and do tests and configurations on my switches/routers for learning/testing proposes. Most of these clients are Windows oriented people. However, Putty is widely used tool, what would make my life very easy if I could use it as the remote client. Much better than this would be securing my system so my clients could Telnet over SSH, get a standard Linux console and use the original Conserver console client.



Thanks again!



________________________________

From: users-bounces@conserver.com on behalf of Marion Hakanson
Sent: Tue 9/5/2006 11:19 PM
To: Moacir Ferreira
Cc: David K. Z. Harris; users@conserver.com
Subject: Re: Telnet, again...



MFerreira@comstore.pt said:
> I have tested it using Tera Term, Putty, Microsoft Telnet (Windows XP) and
> Linux telnet. Tera Term won't work. Linux Telenet will get "loose" once I try
> to connect (after "^Ec;"), Putty and Microsoft Telnet works like the same,
> after "^Ec;" when I press enter I get the "login:" message twice. I wish I
> can make my test lab public so you can come in and check what is wrong.

I've used putty in this mode to connect to an IOLAN Rack+ (reverse telnet).
To get rid of the "double return" problem, after you've started the putty
connection, right-click on the top of the putty window, select the
"Change Settings" item, then "Telnet", then de-select the check-box
labelled "Return key sends Telnet New Line instead of ^M". Can't help
you with the other telnet clients.

Regards,

Marion



_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users