From owner-freebsd-ipfw Tue Apr 2 11:55:10 2002 Delivered-To: freebsd-ipfw@freebsd.org Received: from mailgw3a.lmco.com (mailgw3a.lmco.com [192.35.35.24]) by hub.freebsd.org (Postfix) with ESMTP id F2EE637B41B for ; Tue, 2 Apr 2002 11:55:05 -0800 (PST) Received: from emss01g01.ems.lmco.com ([129.197.181.54]) by mailgw3a.lmco.com (8.11.6/8.11.6) with ESMTP id g32Jt3530298 for ; Tue, 2 Apr 2002 14:55:04 -0500 (EST) Received: from CONVERSION-DAEMON by lmco.com (PMDF V5.2-33 #38886) id <0GTY00001HZQO6@lmco.com> for freebsd-ipfw@freebsd.org; Tue, 2 Apr 2002 11:55:02 -0800 (PST) Received: from lmco.com ([129.197.20.43]) by lmco.com (PMDF V5.2-33 #38886) with ESMTP id <0GTY00E79HZLTM@lmco.com> for freebsd-ipfw@freebsd.org; Tue, 02 Apr 2002 11:54:58 -0800 (PST) Date: Tue, 02 Apr 2002 11:52:37 -0800 From: rick norman Subject: dummynet pipes To: freebsd-ipfw@freebsd.org Message-id: <3CAA0C05.5062D5A7@lmco.com> MIME-version: 1.0 X-Mailer: Mozilla 4.79 [en] (WinNT; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en 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 What is the best way to remove a dummynet pipe once it is installed ? Is it neccessary to issue an 'ipfw pipe n delete' ? Does 'ipfw -f -flush' remove the pipes as well as the rules ? Thanks, Rick Norman rick.norman@lmco.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message From owner-freebsd-ipfw Tue Apr 2 12: 3:12 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 3532037B41E for ; Tue, 2 Apr 2002 12:03:06 -0800 (PST) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g32K33n87840; Tue, 2 Apr 2002 12:03:03 -0800 (PST) (envelope-from rizzo) Date: Tue, 2 Apr 2002 12:03:03 -0800 From: Luigi Rizzo To: rick norman Cc: freebsd-ipfw@FreeBSD.ORG Subject: Re: dummynet pipes Message-ID: <20020402120303.A87723@iguana.icir.org> References: <3CAA0C05.5062D5A7@lmco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CAA0C05.5062D5A7@lmco.com> 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 On Tue, Apr 02, 2002 at 11:52:37AM -0800, rick norman wrote: > What is the best way to remove a dummynet pipe once it is installed ? > Is it neccessary to issue an 'ipfw pipe n delete' ? Does 'ipfw -f > -flush' > remove the pipes as well as the rules ? "ipfw pipe flush" deletes all pipes. "ipfw pipe N delete" deletes one pipe. luigi > > Thanks, > Rick Norman > rick.norman@lmco.com > > > 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 From owner-freebsd-ipfw Tue Apr 2 17:16:41 2002 Delivered-To: freebsd-ipfw@freebsd.org Received: from mailgw1a.lmco.com (mailgw1a.lmco.com [192.31.106.7]) by hub.freebsd.org (Postfix) with ESMTP id EBCB537B416 for ; Tue, 2 Apr 2002 17:16:36 -0800 (PST) Received: from emss01g01.ems.lmco.com (relay1.ems.lmco.com [129.197.181.54]) by mailgw1a.lmco.com (8.11.6/8.11.6) with ESMTP id g331GYf03303; Tue, 2 Apr 2002 18:16:35 -0700 (MST) Received: from CONVERSION-DAEMON by lmco.com (PMDF V5.2-33 #38886) id <0GTY00101WMD3P@lmco.com>; Tue, 2 Apr 2002 17:11:01 -0800 (PST) Received: from lmco.com ([129.197.20.43]) by lmco.com (PMDF V5.2-33 #38886) with ESMTP id <0GTY00E48WM8IL@lmco.com>; Tue, 02 Apr 2002 17:10:56 -0800 (PST) Date: Tue, 02 Apr 2002 17:08:38 -0800 From: rick norman Subject: Re: dummynet pipes To: Luigi Rizzo Cc: freebsd-ipfw@FreeBSD.ORG Message-id: <3CAA5615.21490755@lmco.com> MIME-version: 1.0 X-Mailer: Mozilla 4.79 [en] (WinNT; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en References: <3CAA0C05.5062D5A7@lmco.com> <20020402120303.A87723@iguana.icir.org> 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 I'm running 4.3 so I don't know if that makes a difference, but there are somethings I don't understand about the commands. If the command 'ipfw add pipe 1 ip from ...' is executed, I get a rule 00100 number added with the pipe number requested according to 'ipfw list'. The command 'ipfw pipe 1 delete' then gives a setsockopt err. 'ipfw pipe flush' returns successfully but when I list the rules, nothing is gone. 'ipfw delete 100' deletes the rule and the pipe is no longer visible. Apparently I don't understand how pipe numbers relate to rule numbers. I've read what I could find, any help or reading reccomendations are appreciated. thanks Rick Norman Luigi Rizzo wrote: > On Tue, Apr 02, 2002 at 11:52:37AM -0800, rick norman wrote: > > What is the best way to remove a dummynet pipe once it is installed ? > > Is it neccessary to issue an 'ipfw pipe n delete' ? Does 'ipfw -f > > -flush' > > remove the pipes as well as the rules ? > > "ipfw pipe flush" deletes all pipes. > "ipfw pipe N delete" deletes one pipe. > > luigi > > > > > Thanks, > > Rick Norman > > rick.norman@lmco.com > > > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message From owner-freebsd-ipfw Tue Apr 2 19:15:48 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 F093537B405 for ; Tue, 2 Apr 2002 19:15:43 -0800 (PST) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g333Ff790536; Tue, 2 Apr 2002 19:15:41 -0800 (PST) (envelope-from rizzo) Date: Tue, 2 Apr 2002 19:15:41 -0800 From: Luigi Rizzo To: rick norman Cc: freebsd-ipfw@FreeBSD.ORG Subject: Re: dummynet pipes Message-ID: <20020402191541.A90506@iguana.icir.org> References: <3CAA0C05.5062D5A7@lmco.com> <20020402120303.A87723@iguana.icir.org> <3CAA5615.21490755@lmco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CAA5615.21490755@lmco.com> 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 rules are rules, and pipes are pipes. Two different objects, two different namespaces. ipfw pipe flush deletes pipes, ipfw flush deletes rules. cheers luigi On Tue, Apr 02, 2002 at 05:08:38PM -0800, rick norman wrote: > I'm running 4.3 so I don't know if that makes a difference, but there are > somethings I don't understand about the commands. > If the command 'ipfw add pipe 1 ip from ...' is executed, I get a > rule 00100 number added with the pipe number requested according to 'ipfw > list'. > The command 'ipfw pipe 1 delete' then gives a setsockopt err. 'ipfw pipe > flush' > returns successfully but when I list the rules, nothing is gone. 'ipfw > delete 100' > deletes the rule and the pipe is no longer visible. Apparently I don't > understand > how pipe numbers relate to rule numbers. I've read what I could find, any > help > or reading reccomendations are appreciated. > thanks > Rick Norman > > Luigi Rizzo wrote: > > > On Tue, Apr 02, 2002 at 11:52:37AM -0800, rick norman wrote: > > > What is the best way to remove a dummynet pipe once it is installed ? > > > Is it neccessary to issue an 'ipfw pipe n delete' ? Does 'ipfw -f > > > -flush' > > > remove the pipes as well as the rules ? > > > > "ipfw pipe flush" deletes all pipes. > > "ipfw pipe N delete" deletes one pipe. > > > > luigi > > > > > > > > Thanks, > > > Rick Norman > > > rick.norman@lmco.com > > > > > > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message From owner-freebsd-ipfw Wed Apr 3 1:42:56 2002 Delivered-To: freebsd-ipfw@freebsd.org Received: from smtp07.wxs.nl (smtp07.wxs.nl [195.121.6.39]) by hub.freebsd.org (Postfix) with ESMTP id 973AF37B400 for ; Wed, 3 Apr 2002 01:42:51 -0800 (PST) Received: from Alex ([213.10.151.186]) by smtp07.wxs.nl (Netscape Messaging Server 4.15) with ESMTP id GTZKBD01.DDG; Wed, 3 Apr 2002 11:42:49 +0200 Date: Wed, 3 Apr 2002 11:42:46 +0200 From: Alex X-Mailer: The Bat! (v1.53d) Reply-To: Alex X-Priority: 3 (Normal) Message-ID: <1182697969.20020403114246@dds.nl> To: rick norman Cc: freebsd-ipfw@FreeBSD.ORG Subject: Re[2]: dummynet pipes In-Reply-To: <3CAA5615.21490755@lmco.com> References: <3CAA0C05.5062D5A7@lmco.com> <20020402120303.A87723@iguana.icir.org> <3CAA5615.21490755@lmco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Hello rick, Wednesday, April 03, 2002, 3:08:38 AM, you wrote: rn> I'm running 4.3 so I don't know if that makes a difference, but rn> there are somethings I don't understand about the commands. If rn> the command 'ipfw add pipe 1 ip from ...' is executed, I get a rn> rule 00100 number added with the pipe number requested according rn> to 'ipfw list'. The command 'ipfw pipe 1 delete' then gives a rn> setsockopt err. 'ipfw pipe flush' returns successfully but when I rn> list the rules, nothing is gone. 'ipfw delete 100' deletes the rn> rule and the pipe is no longer visible. Apparently I don't rn> understand how pipe numbers relate to rule numbers. I've read rn> what I could find, any help or reading reccomendations are rn> appreciated. thanks rn> Rick Norman 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 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 From owner-freebsd-ipfw Thu Apr 4 10:42:39 2002 Delivered-To: freebsd-ipfw@freebsd.org Received: from mailgw3a.lmco.com (mailgw3a.lmco.com [192.35.35.24]) by hub.freebsd.org (Postfix) with ESMTP id 8EAC237B417 for ; Thu, 4 Apr 2002 10:42:32 -0800 (PST) Received: from emss01g01.ems.lmco.com ([129.197.181.54]) by mailgw3a.lmco.com (8.11.6/8.11.6) with ESMTP id g34IgT529419; Thu, 4 Apr 2002 13:42:29 -0500 (EST) Received: from CONVERSION-DAEMON by lmco.com (PMDF V5.2-33 #38886) id <0GU200J013YQBQ@lmco.com>; Thu, 4 Apr 2002 10:42:29 -0800 (PST) Received: from lmco.com ([129.197.20.43]) by lmco.com (PMDF V5.2-33 #38886) with ESMTP id <0GU200IDN3YOCT@lmco.com>; Thu, 04 Apr 2002 10:42:24 -0800 (PST) Date: Thu, 04 Apr 2002 10:39:21 -0800 From: rick norman Subject: Re: dummynet pipes To: Luigi Rizzo Cc: Alex , freebsd-ipfw@FreeBSD.ORG Message-id: <3CAC9DD9.4F136FF2@lmco.com> MIME-version: 1.0 X-Mailer: Mozilla 4.79 [en] (WinNT; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en References: <3CAA0C05.5062D5A7@lmco.com> <20020402120303.A87723@iguana.icir.org> <3CAA5615.21490755@lmco.com> <1182697969.20020403114246@dds.nl> <20020403015059.A92886@iguana.icir.org> 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 Thanks for the efforts to clarify. It is still not quite there though. If I create a pipe via 'ipfw add pipe n from any to any', I get both a rule and a pipe. If I then do 'ipfw pipe flush', from what you said, the pipe goes away but the rule remains, just dumping the pkts since the pipe is gone. ' ipfw list' looks the same before and after the pipe flush. How does one detect the difference ? 'ipfw pipe list' doesn't show me anything before or after, 'ipfw list' shows me the same list before and after. Rick Norman Luigi Rizzo wrote: > 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 From owner-freebsd-ipfw Thu Apr 4 10:46:20 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 B31C037B416 for ; Thu, 4 Apr 2002 10:46:14 -0800 (PST) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g34Ik9h08914; Thu, 4 Apr 2002 10:46:09 -0800 (PST) (envelope-from rizzo) Date: Thu, 4 Apr 2002 10:46:09 -0800 From: Luigi Rizzo To: rick norman Cc: Alex , freebsd-ipfw@FreeBSD.ORG Subject: Re: dummynet pipes Message-ID: <20020404104609.A8785@iguana.icir.org> References: <3CAA0C05.5062D5A7@lmco.com> <20020402120303.A87723@iguana.icir.org> <3CAA5615.21490755@lmco.com> <1182697969.20020403114246@dds.nl> <20020403015059.A92886@iguana.icir.org> <3CAC9DD9.4F136FF2@lmco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CAC9DD9.4F136FF2@lmco.com> 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 On Thu, Apr 04, 2002 at 10:39:21AM -0800, rick norman wrote: > Thanks for the efforts to clarify. It is still not quite there though. > If I create a pipe via 'ipfw add pipe n from any to any', I get both no, you create a rule but do not create the pipe. luigi > a rule and a pipe. If I then do 'ipfw pipe flush', from what you said, > the pipe goes away but the rule remains, just dumping the pkts since > the pipe is gone. ' ipfw list' looks the same before and after the pipe > flush. > How does one detect the difference ? 'ipfw pipe list' doesn't show me > anything before or after, 'ipfw list' shows me the same list before and > after. > Rick Norman > > Luigi Rizzo wrote: > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message