Date: 11 Aug 2003 11:27:48 -0400 From: Christopher Nehren <apeiron@comcast.net> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: current@freebsd.org Subject: Re: PLIP transmit timeouts -- any solutions? Message-ID: <1060615668.1613.15.camel@prophecy.velum> In-Reply-To: <200308110925.aa06499@salmon.maths.tcd.ie> References: <200308110925.aa06499@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1060615668.1613.15.camel>