*BSD News Article 39067


Return to BSD News archive

Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!agate!howland.reston.ans.net!swrinde!pipex!uunet!deshaw.com!christos
From: christos@deshaw.com (Christos Zoulas)
Subject: Re: telnetd CR-LF translations
Message-ID: <D0FstD.KnD@deshaw.com>
Sender: usenet@deshaw.com
Nntp-Posting-Host: cs4
Organization: D. E. Shaw & Co.
References: <3c2e34$i8e@golf.ustores.missouri.edu> <3c2g2c$me@ici-paris.ensta.fr>
Date: Wed, 7 Dec 1994 10:51:12 GMT
Lines: 29

In article <3c2g2c$me@ici-paris.ensta.fr> bouyer@ensta.fr (Manuel Bouyer) writes:
>In article <3c2e34$i8e@golf.ustores.missouri.edu>, johnam@dsusmai.dsus.datastorm.com writes:
>> Strange problem from Telnet.  We here at Datastorm have developed and are
>> releasing a Telnet module for Procomm Plus for Windows 2.1.  While I was
>> working on this project, I installed and used NetBSD 0.9 for testing.  I
>> must say I have been very happy with it.  One problem we encountered with
>> X,Y and Zmodem testing was uploading and downloading.
>> The downloading problem we fixed simply by issuing an 8-bit data option
>> before a transfer and then reverting at the end of a xfer.
>> However, if we are uploading, this helps BUT we still have problems.  We
>> discovered that text file containing <CR><LF> pairs ended up on the host
>> with just <CR> after a painful transfer.
>
>I had the same kind of problem when i was doing a telnet from a sun to a NetBSD
>host. Starting telnetd whith the -k option on the NetBSD box solved the problem
>for me. (in inetd.conf, change:
>telnet          stream  tcp     nowait  root    /usr/libexec/telnetd    telnetd
>to:
>telnet          stream  tcp     nowait  root    /usr/libexec/telnetd    telnetd -k
>).
>

I think that this subject has been beaten to death. If the telnet client does
not negotiate LINEMODE correctly, then you get this problem. If you start
telnetd with -k (KLUDGELINEMODE) you are just hiding and thus perpetuating
the client's problem. The correct fix is to fix the client to negotiate
LINEMODE correctly. This should be a part of some FAQ somewhere.

christos