Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!noao!arizona!arizona.edu!leonard From: leonard@arizona.edu Newsgroups: comp.protocols.tcp-ip Subject: new telnet client swallows CRLF's? Summary: new telnet client seems to CRLF's; MultiNet users suffer Keywords: telnet Message-ID: <1990Jul11.223443.1@arizona.edu> Date: 12 Jul 90 05:34:43 GMT Sender: news@cs.arizona.edu Lines: 27 We have seen a problem with recent implementations of telnet client talking to VMS/MultiNet. What happens is that, in some cases, output lines echo terminated by rather than with - in other words, multiple lines overwrite one on top of the other. We have experienced the problem running telnet from a VAX running the Dec. '89 release of Mt Xinu 4.3BSD into VAXen running MultiNet V2.1 and 2.2. This problem did not manifest in prior releases of the Mt Xinu software, nor does it appear in telnets from the Mt Xinu machine into other systems. Telnet FROM MultiNet into Mt Xinu works fine, as does rlogin from Mt Xinu into MultiNet. Disconcertingly, the most recent software release from Sequent is also seen to manifest the problem (Dynix V3.0.12[?].) (That is, its telnet client behaves the same as Mt Xinu's does.) I infer from this that the problem has crept into the most recent BSD "standard" telnet, and is now appearing in vendors' products. It appears that what happens is this: the MultiNet side issues a sequence at the end of the line. While this is clearly not optimal (TGV says that this is a problem with the VMS terminal driver), one would think that the second should be an esthetic noop. The new telnet clients, however, output the line modulo the CRLF, so that such lines echo with only the CR. This seems wrong to me, and is painful to our users. Can anyone verify or rebut my analysis, or offer a workaround?