integrated

[ipfw.git] / ipfw / ipfw.8

diff --git a/ipfw/ipfw.8 b/ipfw/ipfw.8
index f488723..b1ec24d 100644 (file)
--- a/ipfw/ipfw.8
+++ b/ipfw/ipfw.8
@@ -1,7 +1,7 @@
 .\"
 .\"

-.\" $FreeBSD: head/sbin/ipfw/ipfw.8 205372 2010-03-20 14:42:16Z gavin $
+.\" $FreeBSD: head/sbin/ipfw/ipfw.8 211936 2010-08-28 16:32:01Z brucec $

 .\"
 .\"

-.Dd March 20, 2010
+.Dd July 27, 2010

 .Dt IPFW 8
 .Os
 .Sh NAME
 .Dt IPFW 8
 .Os
 .Sh NAME


@@ -859,9 +859,7 @@ accepted or continues with the next rule, depending on
 sysctl variable.
 .It Cm ngtee Ar cookie
 A copy of packet is diverted into netgraph, original
 sysctl variable.
 .It Cm ngtee Ar cookie
 A copy of packet is diverted into netgraph, original

-packet is either accepted or continues with the next rule, depending on
-.Va net.inet.ip.fw.one_pass
-sysctl variable.
+packet continues with the next rule.

 See
 .Xr ng_ipfw 4
 for more information on
 See
 .Xr ng_ipfw 4
 for more information on


@@ -1919,7 +1917,7 @@ and
 .Pp
 The SCHED_MASK is used to assign flows to one or more
 scheduler instances, one for each
 .Pp
 The SCHED_MASK is used to assign flows to one or more
 scheduler instances, one for each

-value of the packet's 5-fuple after applying SCHED_MASK.
+value of the packet's 5-tuple after applying SCHED_MASK.

 As an example, using ``src-ip 0xffffff00'' creates one instance
 for each /24 destination subnet.
 .Pp
 As an example, using ``src-ip 0xffffff00'' creates one instance
 for each /24 destination subnet.
 .Pp


@@ -2100,7 +2098,7 @@ with either delay or probability first, according
 to the chosen format.
 The unit for delay is milliseconds.
 Data points do not need to be sorted.
 to the chosen format.
 The unit for delay is milliseconds.
 Data points do not need to be sorted.

-Also, tne number of actual lines can be different
+Also, the number of actual lines can be different

 from the value of the "samples" parameter:
 .Nm
 utility will sort and interpolate
 from the value of the "samples" parameter:
 .Nm
 utility will sort and interpolate


@@ -2305,7 +2303,7 @@ Information necessary to route link-local packets to an
 interface is not available after processing by
 .Nm dummynet
 so those packets are dropped in the output path.
 interface is not available after processing by
 .Nm dummynet
 so those packets are dropped in the output path.

-Care should be taken to insure that link-local packets are not passed to
+Care should be taken to ensure that link-local packets are not passed to

 .Nm dummynet .
 .Sh CHECKLIST
 Here are some important points to consider when designing your
 .Nm dummynet .
 .Sh CHECKLIST
 Here are some important points to consider when designing your