From owner-freebsd-bugs  Mon Oct  9 18:30:02 1995
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id SAA00874
          for bugs-outgoing; Mon, 9 Oct 1995 18:30:02 -0700
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id SAA00868
          ; Mon, 9 Oct 1995 18:30:01 -0700
Date: Mon, 9 Oct 1995 18:30:01 -0700
Message-Id: <199510100130.SAA00868@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: uhclem%nemesis@fw.ast.com (Frank Durda IV)
Subject: re: bin/771: telnet - FDIV035
Reply-To: uhclem%nemesis@fw.ast.com (Frank Durda IV)
Sender: owner-bugs@FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/771; it has been noted by GNATS.

From: uhclem%nemesis@fw.ast.com (Frank Durda IV)
To: wollman@lcs.mit.edu, FreeBSD-gnats-submit@freebsd.org
Cc:  Subject: re: bin/771: telnet - FDIV035
Date: Mon, 9 Oct 95 20:21 WET DST

 [0]The problems you report are very likely due to broken option
 [0]negotiation on the part of the server TELNET, particularly for mode
 [0](3) which a lot of implementations have wrong or obsolete versions of
 [0]if they implement it at all.  The only way for anyone to diagnose this
 [0]problem and determine which piece of software is at fault is to get a
 [0]complete trace of options negotiation, which can be enabled by a
 [0]`toggle opt' command at the TELNET prompt BEFORE opening the
 [0]connection.
 
 Ok, then I say that the negotiation in 2.1.0 and in 2.0.5 is broken.  It
 works under 1.1.5.1.  Still, the ability to telnet is broken in 2.1.0
 badly enough to limit its use.  Here are the configurations I know about:
 
 	1.1.5.1 -> 1.1.5.1 worked
 	2.0.5	-> 1.1.5.1 worked
 
 	2.1.0	-> 2.0.5   fails
 	2.0.5	-> 2.0.5   fails
 	2.1.0   -> 2.1.0   fails
 
 	1.1.5.1 -> SCO 	   worked
 	2.1.0	-> SCO	   fails
 
 	1.1.5.1 -> SUN OS  worked
 	2.1.0   -> SUN OS  fails
 
 
 (Sorry, but not every possible combination is available to me at
 this time.  But it should be pretty obvious from the examples that something
 changed in 2.0.5 and something broke in 2.1.0, and that 2.0.5 telnetting
 to itself and 2.1.0 telnetting to itself.) 
 
 I am not saying everything fails in the 2.0.x and 2.1.x versions,
 but at least one item mentioned in the problem report.
 
 
 [0]The only way for anyone to diagnose this problem and determine which
 [0]piece of software is at fault is to get a complete trace of options
 [0]negotiation, which can be enabled by a `toggle opt' command at the
 [0]TELNET prompt BEFORE opening the connection.
 
 I will do this.  Are you the person who is going to research this problem
 that I should send this information to?
 If so, I will also send the sample executable that demonstrates the
 failed [ENTER] operation.   You can assist by selecting the configurations
 and combinations that are "interesting", although it seems that most of the
 failing ones can be easily checked by anybody.
 
 
 [0]What's `FDIV035' supposed to indicate?
 
 That is my own problem report tracking code.  It helps me track down
 old problems I have reported that show up in the "currently open" list, and
 I will re-test on receipt of new releases and quite frequently close them,
 rather than forget about them and let them hang around longer than they
 should.   So, it is for my information, that's all.
 
 
 Frank Durda IV <uhclem%nemesis@fw.ast.com>  |"The Knights who say LETNi
 or uhclem@nemesis.lonestar.org		    | demand...  A SEGMENT REGISTER!!!"
 ...uhclem@lerctr.lonestar.org 		    |"A what?"
 ...decvax!fw.ast.com!nemesis!uhclem         |"LETNi! LETNi! LETNi!"  - 1983