Well, the "other side" is connected directly to a cable modem, and the
Rogers@Home network isn't exactly congestion-free, so I couldn't be sure if
my machine was the problem, or if it was the cable network.  However, when
I can take the network down for a few hours, I'm planning on hooking it up
to a couple of NetBSD boxes and then test the throughput under different
conditions.  One problem though is that I'd have to be able to rule out the
network performance of the clients.  Since this is just my home network
(shared with 8 of my friends), I don't have many high quality ethernet
cards that I can be sure aren't causing a problem.

Thanks for the suggestion about ttcp though, I'll give it a try anyway -
see what kind of bandwidth it says I have and compare that to a friend
who's also on the @Home network.

Thanks,
	Rick

David Brownlee wrote:
> 
>         Have you tried using something like ttcp from pkgsrc to get some
>         idea of network speed between a machine on the inside and the
>         NAT box, and if you can find a friendly machine on the outside,
>         between them?
> 
>                 David/absolute
> 
> On Sun, 24 Oct 1999, Rick Byers wrote:
> 
> > The card that I think is causing the problem is a Racal NI6510 which is a
> > NE2100 clone (uses the nele driver).  The other card is a 3Com 3C509B (ep
> > driver).  I'm using 10BaseT links.  The NetBSD version didn't change, but I
> > did compile a new kernel (with all the PCI bus stuff etc.).  Actually, I
> > did compile MROUTING into the kernel for the first time, could that be
> > causing performance problems?  The only other software thing that changed
> > is that I upgraded the version of ipfilter to 3.2.10, but I did that a few
> > days before the hardware upgrade and people didn't start complaining until
> > JUST after the hardware upgrade.  The only other services that run on the
> > box are named, sendmail, imapd, samba, and apache, but all of those are
> > barely used at all (just my e-mail, the occasional DNS lookup, and the
> > occasional connection to the HTTP server for netscape Roaming Profile
> > stuff).  The 386 was running all those services too (although MUCH slower).
> >
> > Any of this sound like it could be causing a problem?  Thor told me that
> > ISA DMA on PCI machines gets a low priority and is probably what's causing
> > the slowdown.  I plan on picking up a few PCI network cards sometime soon -
> > hopefully that'll fix the problem.
> >
> > Thanks!
> >       Rick
> >
> >
> >
> > Ross Harvey wrote:
> > >
> > > > [ network is slow after 386/25 -> P90 upgrade ]
> > >
> > > You said you were using the same ISA network cards. But which card? What's
> > > the speed of the links? Did the NetBSD version change? And what version?
> > > You said you are compiling things. A new kernel? Do any services run on it
> > > besides packet forwarding?
> >
> > --
> > =========================================================================
> > Rick Byers                       University of Waterloo, Computer Science
> > rickb@iaw.on.ca                               http://www.iaw.on.ca/rickb/
> >

-- 
=========================================================================
Rick Byers                       University of Waterloo, Computer Science
rickb@iaw.on.ca                               http://www.iaw.on.ca/rickb/