From owner-freebsd-ipfw Wed Apr 3 1:51: 8 2002 Delivered-To: freebsd-ipfw@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 8530337B400 for ; Wed, 3 Apr 2002 01:51:04 -0800 (PST) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g339p0a92948; Wed, 3 Apr 2002 01:51:00 -0800 (PST) (envelope-from rizzo) Date: Wed, 3 Apr 2002 01:50:59 -0800 From: Luigi Rizzo To: Alex Cc: rick norman , freebsd-ipfw@FreeBSD.ORG Subject: Re: dummynet pipes Message-ID: <20020403015059.A92886@iguana.icir.org> References: <3CAA0C05.5062D5A7@lmco.com> <20020402120303.A87723@iguana.icir.org> <3CAA5615.21490755@lmco.com> <1182697969.20020403114246@dds.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1182697969.20020403114246@dds.nl> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG While I appreciate the attitude to help, how about trying things before mailing out incorrect explainations ? You do not need to remove the rule before the pipe, because enforcing this would be a nightmare when you want to reconfigure pipes or in general your ipfw configuration. Instead, you can have rules which point to non-existing pipes (which can be a temporary or permanent condition). When such a rule matches, and the pipe is not existing, the packet is just dropped. cheers luigi On Wed, Apr 03, 2002 at 11:42:46AM +0200, Alex wrote: .... > Consider something like this: > > ipfw pipe 1 config bw 100kb/s > ipfw pipe 2 config bw 200kb/s > ipfw add 100 pipe 1 ip from any to any > > A pipe gets connected to ip-packets via rules. In this case you may > need to remove the rule before you remove the pipe because of the > dependency between them. > > 1) ipfw pipe flush > 2) ipfw flush > 3) ipfw pipe flush > > 1) Pipe 1 still has a dependency. So you should be only able to remove > pipe 2, as this isn't connected to anything > 2) This will remove all rules, thus removing the connections between > all pipes. > 3) This will remove any remaining pipes. This could also be done at > 2 if ipfw remembers you want to remove the pipes. > > I didn't try this out, it just seem logical to me this way. I hope > this is any help. > > -- > Best regards, > Alex mailto:freebsd@akruijff.dds.nl > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-ipfw" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message