From owner-freebsd-net Tue Jan 16 13:49:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from atro.pine.nl (atro.pine.nl [213.156.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 2103D37B402 for ; Tue, 16 Jan 2001 13:49:19 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by atro.pine.nl (8.11.1/8.11.1) with ESMTP id f0GLnDs15710; Tue, 16 Jan 2001 22:49:14 +0100 (MET) Date: Tue, 16 Jan 2001 22:49:13 +0100 (MET) From: Mark Lastdrager To: Ted Wisniewski Cc: Subject: Re: Bridging-Firewall/bandwith limit problem In-Reply-To: <200101161813.f0GID7k32443@ness.plymouth.edu> Message-ID: X-NCC-RegID: nl.pine MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At Tue, 16 Jan 2001, owner-freebsd-net@FreeBSD.ORG wrote: > >We have a FreeBSD 4.2-STABLE machine running as a Bridging Firewall >and we are having some difficulties, can anyone give me a pointer, >or outright help... figuring out what is the problem? Details >below. Problem repeatable using different network cards (fxp or xl) > >FreeBSD 4.2 stable ipfw/dummynet issues (Kernel Config Below): > >Sending selected TCP ports, or selected subnets through dummynet pipes >for bandwidth control, the pipes sometimes get "clogged up", causing all >packets going through the pipe to be dropped. Deleting and re-creating >the pipe clears it up. We had exactly the same problem with 4.1-STABLE or 4.0-STABLE (don't remember) a while ago. A 'downgrade' to 3.4-RELEASE fixed it, 3.4-STABLE had the same problem. Not much of a solution, but it may be helpful for the developers. Mark Lastdrager -- Pine Internet BV :: tel. +31-70-3111010 :: fax. +31-70-3111011 PGP 92BB81D1 fingerprint 0059 7D7B C02B 38D2 A853 2785 8C87 3AF1 Today's excuse: had to use hammer to free stuck disk drive heads. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message