From owner-freebsd-bugs  Sat Mar  9 17:10:32 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA11165
          for bugs-outgoing; Sat, 9 Mar 1996 17:10:32 -0800 (PST)
Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA11159
          for <bugs@freebsd.org>; Sat, 9 Mar 1996 17:10:30 -0800 (PST)
Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.7.4) id RAA15496; Sat, 9 Mar 1996 17:10:27 -0800 (PST)
Received: from localhost by newport.ece.uci.edu (8.7.4) id RAA06886; Sat, 9 Mar 1996 17:10:24 -0800 (PST)
Message-Id: <199603100110.RAA06886@newport.ece.uci.edu>
To: bugs@freebsd.org
Subject: TCP loss?
Date: Sat, 09 Mar 1996 17:10:22 -0800
From: Steven Wallace <swallace@ece.uci.edu>
Sender: owner-bugs@freebsd.org
X-Loop: owner-bugs@FreeBSD.ORG
Precedence: bulk


I am experiencing TCP freezup on FreeBSD to FreeBSD connection.
Sometimes when I'm sending large amounts of text on a pty on my
FreeBSD 2.1R machine (connected via ethernet) stops sending
its data to my 2.2-Nov21st machine (connected via SLIP).  Now
I know packets get dropped from time to time over my link,
but it should be able to recover and send again.  On the 2.1R
machine, it says that there is nothing in its Send-Q.
The link still receives okay though (observing idle time and tcpdump
watch), but the text is stuck and it never resends anything.

Anybody else experienced probs like this?  Has it been fixed?

Steven