From owner-freebsd-current@FreeBSD.ORG Mon Aug 11 08:27:50 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D27AB37B401 for ; Mon, 11 Aug 2003 08:27:50 -0700 (PDT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0109843FBD for ; Mon, 11 Aug 2003 08:27:50 -0700 (PDT) (envelope-from apeiron@comcast.net) Received: from [192.168.0.5] (pcp02833519pcs.levtwn01.pa.comcast.net[68.80.216.187](untrusted sender)) by comcast.net (sccrmhc13) with SMTP id <2003081115274801600gur1se>; Mon, 11 Aug 2003 15:27:48 +0000 From: Christopher Nehren To: Ian Dowse In-Reply-To: <200308110925.aa06499@salmon.maths.tcd.ie> References: <200308110925.aa06499@salmon.maths.tcd.ie> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-zxBzr95/d+KaUz8cn6+u" Message-Id: <1060615668.1613.15.camel@prophecy.velum> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 11 Aug 2003 11:27:48 -0400 cc: current@freebsd.org Subject: Re: PLIP transmit timeouts -- any solutions? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2003 15:27:51 -0000 --=-zxBzr95/d+KaUz8cn6+u Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2003-08-11 at 04:25, Ian Dowse wrote: > Try the following patch. I can't remember if all the changes in > this are necessary, but I think I found it fixed problems when > interoperating with a Linux-like PLIP implementation. Unfortunately, it doesn't work -- just prolongs the time it takes for a timeout to occur. Being that it's a transmit timeout, rather than a receive timeout, it's making me think that the Linux laptop (which is significantly slower) isn't able to keep up with sending ACKs or something similar to the FreeBSD machine. Is there any sort of user or kernel -space utility to configure the timeouts on the FreeBSD side? The way I see it, if I can slow down the FreeBSD end, the Linux side should be able to talk at something close to "native" speed. I've been thinking about using dummynet to simulate latency, but I'm not really sure of how much to simulate -- even connections of 10 kB/sec (limited via scp's -l option) cause timeouts, whereas I've had other (small) things download at around 50 without a problem. --=-zxBzr95/d+KaUz8cn6+u Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQA/N7X0UdqurN0fljsRAsh+AJ4t368K1Ku0xZZGDKKU1ajzfZ3RfgCgms81 piF2EPFlFhuunr5awUTd85c= =MkAj -----END PGP SIGNATURE----- --=-zxBzr95/d+KaUz8cn6+u--