From owner-freebsd-questions@FreeBSD.ORG Fri Jan 7 14:52:28 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D105E16A4CE for ; Fri, 7 Jan 2005 14:52:28 +0000 (GMT) Received: from votris.mrdata.com (votris.mrdata.com [216.61.45.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0750343D3F for ; Fri, 7 Jan 2005 14:52:28 +0000 (GMT) (envelope-from blakef@votris.mrdata.com) Received: from votris.mrdata.com (localhost.mrdata.com [127.0.0.1]) by votris.mrdata.com (8.12.2/8.12.5) with ESMTP id j07EqQ8A031347 for ; Fri, 7 Jan 2005 08:52:26 -0600 (CST) Received: (from blakef@localhost) by votris.mrdata.com (8.12.2/8.12.1/Submit) id j07EqQ2A031346 for freebsd-questions@freebsd.org; Fri, 7 Jan 2005 08:52:26 -0600 (CST) From: Blake Freeburg Message-Id: <200501071452.j07EqQ2A031346@votris.mrdata.com> To: freebsd-questions@freebsd.org Date: Fri, 7 Jan 2005 08:52:26 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Subject: network slows 1000x X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 14:52:28 -0000 Hello, I have a Duron based FreeBSD box (4.10-current) that I am using as a nat box. Kernel is recompiled with options. When a lot of traffic flows across the interface from internal to external networks, I find that the natd appears to get congested, making ping times to the next hop (still on my network) go from .1 ms to 1000s of ms. Rebooting fixes it Nothing is reported in dmesg (I upgraded from 4.6 where I saw this problem) then there would be this message about queue lengths... The relavent devices are... xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xc800-0xc83f irq 5 at device 11.0 on pci0 vr0: port 0xe400-0xe4ff mem 0xe0117000-0xe01170ff irq 11 at device 18.0 on pci0 This happens once a day there abouts (depends on what's been moved between internal and external networks. Any ideas? Blake Freeburg