Attachment 78934 Details for Bug 113464 – firewall-chapter.sgml.patch

[patch] firewall-chapter.sgml.patch

firewall-chapter.sgml.patch (text/plain; charset=us-ascii), 1.43 KB, created by Marc Silver on 2008-01-10 07:46:38 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Marc Silver

Created: 2008-01-10 07:46:38 UTC

Size: 1.43 KB

patch

obsolete

>--- chapter.sgml.orig	2008-01-10 08:46:33.000000000 +0200
>+++ chapter.sgml	2008-01-10 09:35:19.000000000 +0200
>@@ -151,12 +151,16 @@
>       <acronym>PF</acronym>).  &os; also has two built in packages for
>       traffic shaping (basically controlling bandwidth usage):
>       &man.altq.4; and &man.dummynet.4;.  Dummynet has traditionally been
>-      closely tied with <acronym>IPFW</acronym>, and
>-      <acronym>ALTQ</acronym> with
>-      <acronym>IPF</acronym>/<acronym>PF</acronym>.  IPF,
>-      IPFW, and PF all use rules to control the access of packets to and
>-      from your system, although they go about it different ways and
>-      have different rule syntaxes.</para>
>+      closely tied with <acronym>IPFW</acronym>, while
>+      <acronym>ALTQ</acronym> may be used with <acronym>PF</acronym>.  
>+      Traffic shaping can currently be achieved with 
>+      <acronym>IPFILTER</acronym> by using <acronym>IPFILTER</acronym> 
>+      for filtering and NAT in conjunction with <acronym>IPFW</acronym> 
>+      and dummynet <emphasis>or</emphasis> <acronym>PF</acronym> with 
>+      <acronym>ALTQ</acronym> for traffic shaping.  IPF IPFW, and PF all 
>+      use rules to control the access of packets to and from your system, 
>+      although they go about it different ways and have different rule 
>+      syntaxes.</para>
> 
>     <para>The reason that &os; has multiple built in firewall packages
>       is that different people have different requirements and

Actions: View | Diff

Attachments on bug 113464: 78934