From owner-freebsd-hackers Wed Jul 31 14:20:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA00871 for hackers-outgoing; Wed, 31 Jul 1996 14:20:56 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA00851 for ; Wed, 31 Jul 1996 14:20:49 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA03869; Wed, 31 Jul 1996 15:20:38 -0600 (MDT) Date: Wed, 31 Jul 1996 15:20:38 -0600 (MDT) Message-Id: <199607312120.PAA03869@rocky.mt.sri.com> From: Nate Williams To: Thomas Graichen Cc: hackers@freebsd.org Subject: Re: tcp/ip over lp0 In-Reply-To: <199607311930.VAA01052@mordillo> References: <199607311930.VAA01052@mordillo> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > are there any parameters to play with for getting tcp/ip over the parallel > port working None that I'm aware of. > 4308 packets transmitted, 617 packets received, 85% packet loss That anything gets through implies that at least the software is setup correctly, so the remaining factor is hardware. > time ago - but now some parts of them have changed - and the cable was > different) ? - or can it be that the cable is too long (it's really long - > about 5 meters or so) ? That's a *really* long cable. Also, *MAKE SURE* that neither machine has another device using it's interrupt, and that there is a driver for all hardware that generate interrupts. If you happen to use the commonly-used IRQ 7 for the parallel port and something other than the parallel port either generates interrupts on 7 or one another unregistered port you'll have lots of problems. Make sure both machines have don't have IRQ conflicts and shorten the cable. Nate