From owner-freebsd-hardware Thu Jul 6 22:25:54 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 1C61A37BC65 for ; Thu, 6 Jul 2000 22:25:46 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id BAA02365; Fri, 7 Jul 2000 01:25:24 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Fri, 7 Jul 2000 01:25:24 -0400 (EDT) From: Adam To: steinyv@skyweb.net Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Intel EtherExpress Pro/100B In-Reply-To: <011401bfe6b3$8018b2e0$82571c18@austin.rr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 5 Jul 2000, Brandon S. DeYoung wrote: >> >Hey all, I just received the critically acclaimed nics yesterday, I >popped >> >them in and it works. I have 2 questions. Is there a way to find out at >> >what speed is the network working at (just to be sure that its at least >> >near or at 100Mb). > >You can also use the "time" comand in conjuction with your favorite transfer >protocol (ftp, scp, etc...) if you make a 400Mbit file and time it's >transfer, that'll tell you what's really going on with the network. >syntax example: > ># time scp ./somefile somecomputer.somedomain.com:/usr/tmp > >~Brandon Just keep in mind ftp would include the slower of the two storage medias involved, and scp would also involve the cpu speed of both. If you want actual wire speed, try something like netperf or ttcp. >> >Hey all, I just received the critically acclaimed nics yesterday, I >popped >> >them in and it works. I have 2 questions. Is there a way to find out at >> >what speed is the network working at (just to be sure that its at least >> >near or at 100Mb). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message