Date: Mon, 9 Oct 1995 10:00:01 -0700 From: "Garrett A. Wollman" <wollman@lcs.mit.edu> To: freebsd-bugs Subject: bin/771: telnet character mode not set and broken when set - FDIV034 Message-ID: <199510091700.KAA16083@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/771; it has been noted by GNATS. From: "Garrett A. Wollman" <wollman@lcs.mit.edu> To: uhclem%nemesis@fw.ast.com Cc: FreeBSD-gnats-submit@freebsd.org Subject: bin/771: telnet character mode not set and broken when set - FDIV034 Date: Mon, 9 Oct 1995 12:53:36 -0400 <<On Sat, 7 Oct 95 22:29 WET DST, uhclem%nemesis@fw.ast.com said: > 1. Between 1.1.5.1 and 2.0.5, telnet changed to default to non-raw > operating state to line-mode instead of character-at-a-time > mode. Wrong. TELNET negotiates what mode to use with the other end of the connection. There are three possible modes: 1) DONT LINEMODE, WILL ECHO - old character-at-a-time mode 2) DONT LINEMODE, WONT ECHO - old line-at-a-time mode 3) DO LINEMODE, WONT ECHO - new line-at-a-time mode The problems you report are very likely due to broken option negotiation on the part of the server TELNET, particularly for mode (3) which a lot of implementations have wrong or obsolete versions of if they implement it at all. The only way for anyone to diagnose this problem and determine which piece of software is at fault is to get a complete trace of options negotiation, which can be enabled by a `toggle opt' command at the TELNET prompt BEFORE opening the connection. What's `FDIV035' supposed to indicate? -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510091700.KAA16083>