From owner-freebsd-questions Mon Feb 6 20:40:10 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA05820 for questions-outgoing; Mon, 6 Feb 1995 20:40:10 -0800 Received: from zed.ludd.luth.se (root@zed.ludd.luth.se [130.240.16.33]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id UAA05800 for ; Mon, 6 Feb 1995 20:40:07 -0800 Received: from taurus.ludd.luth.se (taurus.ludd.luth.se [130.240.16.37]) by zed.ludd.luth.se (8.6.9/8.6.9) with ESMTP id FAA09717 for ; Tue, 7 Feb 1995 05:39:17 +0100 From: Andreas Johansson Received: (ajo@localhost) by taurus.ludd.luth.se (8.6.9/8.6.9) id FAA04070 for freebsd-questions@FreeBSD.ORG; Tue, 7 Feb 1995 05:39:19 +0100 Message-Id: <199502070439.FAA04070@taurus.ludd.luth.se> Subject: Re: Trouble sending via TCP To: freebsd-questions@FreeBSD.org Date: Tue, 7 Feb 1995 05:39:18 +0100 (MET) In-Reply-To: <199502070342.TAA00772@corbin.Root.COM> from "David Greenman" at Feb 6, 95 07:42:02 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2281 Sender: questions-owner@FreeBSD.org Precedence: bulk According to David Greenman: > > >I'm getting a similar problem with FreeBSD-current, ftp:ed > >src.doc.ic.ac.uk one week and a half ago perhaps. I'm using a 486/SX-25 with > >4Mb ram (yeck), an Etherlink 16 card connected directly to Internet via our > >campusnet. > > Etherlink 16? What driver does this use? The ie-driver. ie0 at 0x300-0x30f irq 10 maddr 0xd0000 msize 65536 on isa <3C507 R1> ethernet address 00:60:8c:5a:25:19 > >OK, the problem: > > > >I get serious trouble when ftp:ing files FROM the FreeBSD machine, typically > >5kb/sec against very fast machines. Receiving files to the FreeBSD machine > >works ok -- I have recieved files at >800k/s. > > I suspect the card/driver. If this is a 3c501, then the solution to the > problem is clear: get a different card. It only has space for either a > receive packet or a send packet, but not both (in other words, it's a piece > of junk that has no chance of working well). I think the 3c505 has similar > problems dealing with the real world. Nope, it's a 3c507. I didn't have any problems with TCP when I used Linux. (On the other hand Linux's NFS sucked so here we are...) When using some older kernels I got a lot of collisions when doing all kinds of communication, actually there were more collisions than ok packets. This behaviour disappeared when I got -current kernel. One more note about the system: I have another ethernet card (NE2000) that is connected to one machine only. This one seems to work ok, but then the connected machine is a VAX 8300 so you never know :) ed0 at 0x280-0x29f irq 5 on isa ed0: address 00:00:44:04:1a:b8, type NE2000 (16 bit) I am unable to switch cards for campusnet connection/vax connection since the vax is communicating via 10base2, campusnet with 10baseT and the 3c507 has only got a TP-tranceiver. > -DG -- <-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-> : E-mail: ajo@ludd.luth.se Amiga 4000 is it! : : S-mail: Andreas Johansson, Karhusvagen 5 6:618, 977 54 Lulea, SWEDEN : : There are two groups of people I'll _never_ understand: : : math-professors and women : <-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=->