Document that net.inet.ip.fw.one_pass only affects dummynet(4).

Noticed by:	Peter Jeremy<peter.jeremy@alcatel.com.au>
This commit is contained in:
ru 2000-09-29 08:39:06 +00:00
parent 4a01729c28
commit 105baa72f0
3 changed files with 7 additions and 5 deletions

View File

@ -1043,9 +1043,11 @@ meaning:
Controls debugging messages produced by
.Nm ipfw .
.It Em net.inet.ip.fw.one_pass : No 1
When set, permits only one pass through the firewall.
Otherwise, after a pipe or divert action, the packet is
reinjected in the firewall starting from the next rule.
When set, the packet exiting from the
.Xr dummynet 4
pipe is not passed though the firewall again.
Otherwise, after a pipe action, the packet is
reinjected into the firewall at the next rule.
.It Em net.inet.ip.fw.verbose : No 1
Enables verbose messages.
.It Em net.inet.ip.fw.enable : No 1

View File

@ -91,7 +91,7 @@ At the output from the second queue packets
are reinjected into the protocol stack at the same point they came
from (i.e. ip_input(), ip_output(), bdg_forward() ).
Depending on the setting of the sysctl variable
.Ql net.inet.ipfw.one_pass ,
.Ql net.inet.ip.fw.one_pass ,
packets coming from a pipe can be either forwarded to their
destination, or passed again through the
.Nm ipfw

View File

@ -95,7 +95,7 @@ SYSCTL_INT(_net_inet_ip_fw, OID_AUTO, enable, CTLFLAG_RW,
&fw_enable, 0, "Enable ipfw");
SYSCTL_INT(_net_inet_ip_fw, OID_AUTO,one_pass,CTLFLAG_RW,
&fw_one_pass, 0,
"Only do a single pass through ipfw when using divert(4)/dummynet(4)");
"Only do a single pass through ipfw when using dummynet(4)");
SYSCTL_INT(_net_inet_ip_fw, OID_AUTO, debug, CTLFLAG_RW,
&fw_debug, 0, "Enable printing of debug ip_fw statements");
SYSCTL_INT(_net_inet_ip_fw, OID_AUTO, verbose, CTLFLAG_RW,