From owner-freebsd-questions  Sun Jan  9 18:11:50 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30])
	by hub.freebsd.org (Postfix) with ESMTP
	id A67A414DE8; Sun,  9 Jan 2000 18:11:43 -0800 (PST)
	(envelope-from Stanley.Hopcroft@ipaustralia.gov.au)
Received: (from smap@localhost)
	by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id NAA38145;
	Mon, 10 Jan 2000 13:09:30 +1100 (EST)
	(envelope-from Stanley.Hopcroft@ipaustralia.gov.au)
X-Authentication-Warning: pericles.IPAustralia.gov.au: smap set sender to <Stanley.Hopcroft@ipaustralia.gov.au> using -f
Received: from noteshub01.aipo.gov.au(10.0.100.21) by pericles.IPAustralia.gov.au via smap (V2.0)
	id xma038141; Mon, 10 Jan 00 13:09:27 +1100
Received: by noteshub01.aipo.gov.au(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999))  id 4A256862.001160BA ; Mon, 10 Jan 2000 13:09:48 +1000
X-Lotus-FromDomain: IP_AUSTRALIA
From: Stanley.Hopcroft@ipaustralia.gov.au
To: questions@freebsd.org
Cc: isp@freebsd.org, grog@lemis.com
Message-ID: <4A256862.00115FA7.00@noteshub01.aipo.gov.au>
Date: Mon, 10 Jan 2000 13:09:45 +1000
Subject: Getting TCP connections prematurely FINned with duplxity mismatch
	 - was read() fails (called from apache 1.3.9) on FreeBSD 3.2
	-RELEASE 
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


To:   questions@freebsd.org
cc:   isp@freebsd.org, grog@lemis.com


Dear Ladies and Gentlemen,

I am writing to say the question recently asked about read() failing
intermittently when called by apache 1.3.9 (and only with an RFC 1867 file
upload) has an answer (courtesy Mr Carl Makin).

Browser clients would report "connection reset by browser" when the browser
attempted to upload a file over about one megabyte.

tcpdump shows the FreeBSD/apache host sending a FIN packet (then a couple of
RESEST) to the browsers TCP connection before the file upload is done.

The problem seems not to be caused by

. RFC 1323 extensions
. RFC 1646 extensions

It apparently *is* caused by a duplexity mismatch between the FreeBSD box and
the adjacent (FreeBSD) router via a cross over cable.

ifconfig fxp1 media 100baseTX mediaopt full-duplex

removes all signs of the problem

So, if anyone asks what causes read() on a socket to fail, you won't get fooled
(like me).

I suppose netstat -i fxp1 -w 1 when the problem was happening might have helped.

Thank you,

Yours sincerely,







To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message