|
Lines 151-162
Link Here
|
| 151 |
<acronym>PF</acronym>). &os; also has two built in packages for |
151 |
<acronym>PF</acronym>). &os; also has two built in packages for |
| 152 |
traffic shaping (basically controlling bandwidth usage): |
152 |
traffic shaping (basically controlling bandwidth usage): |
| 153 |
&man.altq.4; and &man.dummynet.4;. Dummynet has traditionally been |
153 |
&man.altq.4; and &man.dummynet.4;. Dummynet has traditionally been |
| 154 |
closely tied with <acronym>IPFW</acronym>, and |
154 |
closely tied with <acronym>IPFW</acronym>, while |
| 155 |
<acronym>ALTQ</acronym> with |
155 |
<acronym>ALTQ</acronym> may be used with <acronym>PF</acronym>. |
| 156 |
<acronym>IPF</acronym>/<acronym>PF</acronym>. IPF, |
156 |
Traffic shaping can currently be achieved with |
| 157 |
IPFW, and PF all use rules to control the access of packets to and |
157 |
<acronym>IPFILTER</acronym> by using <acronym>IPFILTER</acronym> |
| 158 |
from your system, although they go about it different ways and |
158 |
for filtering and NAT in conjunction with <acronym>IPFW</acronym> |
| 159 |
have different rule syntaxes.</para> |
159 |
and dummynet <emphasis>or</emphasis> <acronym>PF</acronym> with |
|
|
160 |
<acronym>ALTQ</acronym> for traffic shaping. IPF IPFW, and PF all |
| 161 |
use rules to control the access of packets to and from your system, |
| 162 |
although they go about it different ways and have different rule |
| 163 |
syntaxes.</para> |
| 160 |
|
164 |
|
| 161 |
<para>The reason that &os; has multiple built in firewall packages |
165 |
<para>The reason that &os; has multiple built in firewall packages |
| 162 |
is that different people have different requirements and |
166 |
is that different people have different requirements and |