From owner-freebsd-hackers Mon Jun 12 0:53:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from oskar.dev.nanoteq.co.za (oskar.nanoteq.co.za [196.7.114.5]) by hub.freebsd.org (Postfix) with ESMTP id EF7F037BC27 for ; Mon, 12 Jun 2000 00:53:44 -0700 (PDT) (envelope-from rbezuide@oskar.dev.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id JAA07838; Mon, 12 Jun 2000 09:53:28 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <200006120753.JAA07838@oskar.dev.nanoteq.co.za> Subject: Re: Fastforwarding In-Reply-To: <200006120705.JAA13935@info.iet.unipi.it> from Luigi Rizzo at "Jun 12, 2000 9: 5:52 am" To: luigi@info.iet.unipi.it (Luigi Rizzo) Date: Mon, 12 Jun 2000 09:53:28 +0200 (SAT) Cc: lists@security.za.net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Has anyone here tried setting net.inet.ip.fastforwarding on in a high > > traffic enviroment? > > > > This setting DRASTICALLY speeds up transfers between boxes talking through > > a freebsd gateway when you are using 2 100mbit interfaces, but it seems to > > kernel panic the system after a few minutes. > > can you quantify the "drastically" ? > > luigi > This also depends on what 100mbit cards you are using ... we had problems with the Intel ether express cards when using X-over cables (yes :) Intel specs that these cards should NOT be used with X-overs) ... this caused the cards to go in some reset stage where no packets are transfered and the mbufs heap up and eventually could cause a panic. this happend when configured as abridge and doing 100mbit full-duplex transfers, we fixed this by using a switch and removing the X-overs. Also have a look at increasing the mbufs .. I don't know if the mbuf exaustion panic has been fixed .. anyone ?? Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message