Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ucla-cs!zen!ucbvax!SUN.COM!nowicki
From: nowicki@SUN.COM (Bill Nowicki)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Telnet, <CR><LF>, etc.
Message-ID: <8708070054.AA08618@speed.sun.com>
Date: Thu, 6-Aug-87 20:54:57 EDT
Article-I.D.: speed.8708070054.AA08618
Posted: Thu Aug  6 20:54:57 1987
Date-Received: Sun, 9-Aug-87 12:38:50 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 29

My two cents worth on this subject:

In SunOS 3.4 I changed the telnet daemon to send \r instead of \n to
the pty when it gets <CR><LF>.  However, this broke the local line edit
mode.  In SunOS 4.0 I originally put in a check to see if local editing
was being done, and if so sent \n to the pty, otherwise \r.  Steve
Casner's message, however, convinced me that a slightly cleaner fix
would be to just keep the pty in the mode that treats \r as \n when
doing local editing.  I don't understand the rationale behind the code
that explicitly cleared it.  

The change is simple (your line numbers may vary).  In the function
dontoption():

922,927c924,925
<     case TELOPT_ECHO:         
<         /*
<          * we should stop echoing, since the client side will be doing it,
<          * but keep mapping CR since CR-LF will be mapped to it.
<          */
<       mode(0, ECHO);
---
>     case TELOPT_ECHO:         /* we should stop echoing */
>       mode(0, ECHO|CRMOD);

This, in combination with the change from \n to \r for incoming <CR><LF>s
seems to work for most telnets in both line and character modes.

	- WIN