Return-Path: <ghudson@MIT.EDU>
Received: from pacific-carrier-annex.mit.edu by po11.mit.edu (8.9.2/4.7) id KAA00310; Sat, 29 Sep 2001 10:38:52 -0400 (EDT)
Received: from egyptian-gods.MIT.EDU (EGYPTIAN-GODS.MIT.EDU [18.101.0.162])
	by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id KAA29606
	for <sipb@mit.edu>; Sat, 29 Sep 2001 10:38:48 -0400 (EDT)
Received: (from ghudson@localhost) by egyptian-gods.MIT.EDU (8.9.3)
	id KAA22179; Sat, 29 Sep 2001 10:38:46 -0400
Message-Id: <200109291438.KAA22179@egyptian-gods.MIT.EDU>
To: sipb@MIT.EDU
Subject: "McNerney, Tim": RE: Who do I talk to about e19-rtr-backbone.mit.edu lossage?
Date: Sat, 29 Sep 2001 10:38:46 -0400
From: Greg Hudson <ghudson@MIT.EDU>


------- Forwarded Message

Return-Path: <TMcNerney@chipwrights.com>
Received: from fort-point-station.mit.edu by po12.mit.edu (8.9.2/4.7) id NAA15822; Fri, 28 Sep 2001 13:58:06 -0400 (EDT)
Received: from intranet.chipwrights.com (ipn2-a1131.net-resource.net [216.204.61.131])
	by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id NAA09569
	for <ghudson@MIT.EDU>; Fri, 28 Sep 2001 13:56:36 -0400 (EDT)
Received: by intranet with Internet Mail Service (5.5.2650.21)
	id <SVQAXPZR>; Fri, 28 Sep 2001 13:57:25 -0400
Message-ID: <93A4BBB9515ED411AE9D00508BD955A5198C35@intranet>
From: "McNerney, Tim" <TMcNerney@chipwrights.com>
To: "'Greg Hudson'" <ghudson@MIT.EDU>
Subject: RE: Who do I talk to about e19-rtr-backbone.mit.edu lossage?
Date: Fri, 28 Sep 2001 13:57:25 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"



- -----Original Message-----
From: Greg Hudson [mailto:ghudson@MIT.EDU]
Sent: Friday, September 28, 2001 1:40 PM
To: McNerney, Tim
Cc: 'sipb@mit.edu'
Subject: Re: Who do I talk to about e19-rtr-backbone.mit.edu lossage?

   > at least a solution that allows me to keep from losing my ssh/telnet
   > session several times a day.

   This may not be a problem with MIT's network.  A number of friends of
   mine have run into problems with firewalls or NAT gateways (on their
   end) which can lose track of TCP state and reset the connection the
   next time they receive a packet.  

I'll look into this, though it happens with some regularity both at
home (ATT@home "broadband"), and at work (and yes, we have a firewall).

   Characteristics of this lossage are:

   * You lose your connection instantly after typing or otherwise
     causing a packet to be sent, usually after a period of idle time.

Once a week I see something that fits this description.  
Mostly I see dropped connections during active sessions where I
am in the middle of typing.

   * Your sshd process on the MIT side is still around and is still
    waiting for data on the network socket.

How would I verify this?

   Of course, the second characteristic can also mean a network failure
   reported to the ssh client but not to the ssh server.

   > perhaps TCP (and its lame retransmit policy) is no longer "the right
   > thing."

   A more aggressive retransmit policy could degrade network performance
   for other users, so calling the TCP retransmit policy "lame" is
   probably prejudicial.

I agree, my wording is definitely prejudicial.  In the today's arguably 
overwhelmed network environment it is certainly an ineffective policy.
I probably should have more sympathy for other network users, but my
take is that most other users are getting a better deal: a network
that "works for the web" and one where bandwidth is mostly limited by
servers.

   > People have retorted that no one cares about telnet/ssh anymore, but
   > I think it is a sad state of affairs if "the net" has become a
   > "ground freight only" medium at the expense of "air-mail letters."
   > (i.e. lightweight, high-priority packets).

   I wouldn't say the web is "ground freight."

By this perhaps-inflamatory wording I meant: big heavy packets delivered
at an acceptible latency.

Maybe I'm the idiot for clinging to running emacs on remote servers and
expecting it to work as well as the "pre-web-net."

- --Tim

------- End of Forwarded Message

