From sperber@informatik.uni-tuebingen.de  Sun Mar  1 23:48:50 1998
Received: from macon.informatik.uni-tuebingen.de (macon2.Informatik.Uni-Tuebingen.De [134.2.13.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28021
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 1 Mar 1998 23:48:47 -0800 (PST)
          (envelope-from sperber@informatik.uni-tuebingen.de)
Received: from modas.informatik.uni-tuebingen.de (modas.Informatik.Uni-Tuebingen.De [134.2.12.3]) by macon.informatik.uni-tuebingen.de (8.8.4/8.8.3/AIX-4.1/WSI-1.0) with SMTP id IAA12980 for <FreeBSD-gnats-submit@freebsd.org>; Mon, 2 Mar 1998 08:48:39 +0Received: by modas.informatik.uni-tuebingen.de (AIX 4.1/UCB 5.64/4.03)
          id AA23056; Mon, 2 Mar 1998 08:48:29 +0100
Message-Id: <y9lwwedy1mb.fsf@modas.informatik.uni-tuebingen.de>
Date: 02 Mar 1998 08:48:28 +0100
From: sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor])
To: FreeBSD-gnats-submit@freebsd.org
Subject: FreeBSD -> FreeBSD network writes fail while others succeed
X-Send-Pr-Version: 3.2

>Number:         5896
>Category:       kern
>Synopsis:       FreeBSD host can't network-write to other FreeBSD hosts
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Mar  1 23:50:00 PST 1998
>Closed-Date:    Thu Dec 24 22:16:37 PST 1998
>Last-Modified:  Thu Dec 24 22:17:50 PST 1998
>Originator:     Mike Sperber
>Release:        FreeBSD 2.2.5-RELEASE i386
>Organization:
WSI, University of Tbingen, Germany
>Environment:

        This is a vanilla fresh FreeBSD 2.2.5 install on a Pentium box
        with an ISA NE2000 board network clone.

>Description:

        The machine works flawlessly when connecting to anything but
        another FreeBSD host, both in the same subnet and remotely.
        However, when I connect to another FreeBSD host, network reads
        are fine, but writes consistently fill up the output buffers
        very quickly after which transfer come to a complete
        standstill.

        I've seen this connecting with four other FreeBSD hosts: one
        in the same subnet, one via PPP, cvsup.freebsd.org, and
        cvsup.de.freebsd.org (via CVSup).  

	Flawless network connects work to Solaris, AIX, and Linux
        boxes that we have here.

>How-To-Repeat:

        Engage in any network activity which involves having my
        machine network-writing to another FreeBSD host.  In
        particular, CVSup does the trick quite quickly.

>Fix:

	I've found no way around it.
	
-- 
Cheers =8-} Mike
Friede, Vlkerverstndigung und berhaupt blabla
>Release-Note:
>Audit-Trail:

From: Bill Fenner <fenner@parc.xerox.com>
To: <sperber@informatik.uni-tuebingen.de>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/5896: FreeBSD -> FreeBSD network writes fail while others succeed 
Date: Mon, 9 Mar 1998 11:24:02 PST

 It's likely that the ones via PPP are because your PPP server is broken
 and can't handle optioned TCP packets.  Try turning off TCP extensions.
 
 The communication failure on the local LAN is more interesting; can
 you "tcpdump -s 100 -v -S tcp and host1 and host2" and follow up to the
 PR?
 
 Thanks,
   Bill

From: skynyrd@opus.cts.cwu.edu
To: FreeBSD-gnats-submit@FreeBSD.org,
        sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]),
        skynyrd@opus.cts.cwu.edu
Cc:  Subject: Re: kern/5896: FreeBSD host can't network-write to other FreeBSD hosts
Date: Thu, 24 Dec 1998 21:06:31 -0800 (PST)

 Greetings - I am the administrator of cvsup.freebsd.org and notice in the logs that
 you are connecting fine now.  I'm going to close the PR and assume that something
 odd was happening with your local configuration at the time you filed.  Feel free
 to re-open it with me if there is still a problem.
 
 Regards,
 -Chris
 
 
State-Changed-From-To: open->closed  
State-Changed-By: cwt 
State-Changed-When: Thu Dec 24 22:16:37 PST 1998 
State-Changed-Why:  
We will assume that all is well now and that the filer will let us know 
if that is not thecase. 
>Unformatted:
