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: kern/5896: FreeBSD -> FreeBSD network writes fail while others succeed Message-ID: <y9lwwedy1mb.fsf@modas.informatik.uni-tuebingen.de>
next in thread | raw e-mail | index | archive | help
>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: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Mar 1 23:50:00 PST 1998 >Last-Modified: >Originator: Mike Sperber >Organization: WSI, University of Tübingen, Germany >Release: FreeBSD 2.2.5-RELEASE i386 >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, Völkerverständigung und überhaupt blabla >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?y9lwwedy1mb.fsf>