From owner-freebsd-questions  Tue Dec 14 19:30: 7 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from saarinen.org (saarinen.org [203.79.82.14])
	by hub.freebsd.org (Postfix) with ESMTP id 3B88A15094
	for <questions@freebsd.org>; Tue, 14 Dec 1999 19:30:03 -0800 (PST)
	(envelope-from juha@saarinen.org)
Received: from dendennis.saarinen.org ([192.168.1.2] helo=DENDENNIS)
	by vimfuego with smtp (Exim 3.03 #1)
	id 11y4cP-000L5Z-00; Wed, 15 Dec 1999 15:56:45 +1300
Reply-To: <juha@saarinen.org>
From: "Juha Saarinen" <juha@saarinen.org>
To: "Mike Tancsa" <mike@sentex.net>
Cc: <questions@freebsd.org>
Subject: RE: Not such good networking performance with FreeBSD
Date: Wed, 15 Dec 1999 15:54:30 +1300
Message-ID: <LNBBIBDBFFCDPLBLLLHFEEALGGAA.juha@saarinen.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-reply-to: <3856fea7.1645869304@mail.sentex.net>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600
Importance: Normal
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi Mike,

> Are you sure its not a duplex issue with your network card ?

Don't think so -- upon boot-up, the card (a DEC 21140 10/100 clone) is being
put into 100Mbps full duplex. At least that's what the system tells me.
Ifconfig -a seems to imply it's only running in 100BaseTX mode:

de0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
        ether 00:00:e8:4a:bf:96
        media: autoselect (100baseTX) status: active
        supported media: autoselect 100baseTX <full-duplex> 100baseTX
10baseT/UTP <full-duplex> 10baseT/UTP



> If thats not
> the case, it might be that if you are getting a lot of errors on your xDSL
> connection. FreeBSD does not seem to fair well where there are a lot of
> errors.  Have a look through the archives, there was a discussion about
> this a few months ago.

Thanks -- the RADSL line here is reasonably free from errors, thank
goodness. I've got an external router connected to a switch to which the
rest of my small LAN is hooked up as well.

I thought it might be the low values for the TCP receive and send buffers --
16KB by default. I upped them to 65K with:

sysctl -w net.inet.tcp.recvspace=65536
sysctl -w net.inet.tcp.sendspace=65536

but it didn't really make any difference.

Going through the sysctl options, I noticed several which may or may not
affect performance:

Don't know what these do, but I presume they're for LANS:

	net.local.stream.sendspace: 8192
	net.local.stream.recvspace: 8192
	net.local.dgram.maxdgram: 2048
	net.local.dgram.recvspace: 4096

Could this one have anything to do with IP routing:

	net.inet.ip.fastforwarding: 0

RFC 1323 extensions are useful for me:

	net.inet.tcp.rfc1323: 1

Is this the default maximum segment size?

	net.inet.tcp.mssdflt: 512

The TCP send and receive buffers:

	net.inet.tcp.sendspace: 65536
	net.inet.tcp.recvspace: 65536

Hmmm... Delayed ACKs?

	net.inet.tcp.delayed_ack: 1

UDP datagram sizes?

	net.inet.udp.maxdgram: 9216
	net.inet.udp.recvspace: 41600

Now what's this then? I increased the raw.recvspace, but I'm not sure what
good it would do:

	net.inet.raw.maxdgram: 8192
	net.inet.raw.recvspace: 65536

Where are all these options described? The man page isn't much use.


Cheers,

-- Juha



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message