SV: telnetd problem?

["Johnny Billquist" <bqt%softjar.se@localhost>]

The client is not sending the telnet newline command when you press enter. 
Instead it sends a cr and probably a nl. The netbsd system expects just the nl. 
Using the telnet newline command would make it right. Instead you see the 
unknown command error for the cr. Pressing a ^j before hitting enter means you 
get nl+cr+nl in the stream.

You need to get the telnet client to behave better.

One easy way to see what is happening is just to do hexdump -C on the command 
line.

Johnny
--
From mobile

----Originalmeddelande----
Från:Scrap Happy
Sänt: 2012-01-19, 13:29 
Till:NetBSD Users's Discussion List
Ämne:telnetd problem?


Hi,

I had to use a client's machine to telnet into a 3.1(x86)
box, yesterday.  His telnet client (<mumble> running
under XP) gave me fits trying to login.

Eventually, I *stumbled* into the machine.  Then, found
damn near every command I tried to type (at sh prompt)
met by ": not found".

Long story short:  it appears that the ENTER key is
sending something unusual.

If I preface ENTER with ^J, I am able to get commands
to be recognized -- at least, they are *executed*!
But, each command's output is eventually followed by
": not found".

A quick poke through the telnet client's menus
didn't seem to turn up anything -- but, I was more
interested in getting out of there than solving
*that* problem.

Now, I'm trying to think of ways I can diagnose
what is happening -- hopefully, entirely on the
NetBSD side of the interface (so I don't have to
try to understand this wonky telnet client!).

Suggestions?

I figure possibly arranging for the session to be
"raw" and just try to capture keystrokes to a file (?).
Then, examine the file's contents with a "working"
telnet client (or, at the console, etc.)

<frown>  Annoying little problem!

Thanks!
--don