Bug 13907
| Summary: | dummynet.4 correction, rc addition of | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | emoc the phearless <emoc> | ||||||||
| Component: | conf | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||||||
| Status: | Closed FIXED | ||||||||||
| Severity: | Affects Only Me | ||||||||||
| Priority: | Normal | ||||||||||
| Version: | 3.3-STABLE | ||||||||||
| Hardware: | Any | ||||||||||
| OS: | Any | ||||||||||
| Attachments: |
|
||||||||||
On Wed, 22 Sep 1999 16:53:02 -0400, emoc the phearless wrote:
> + # Unset one_pass if requested
> + if [ "x$firewall_one_pass" = "xNO" ]; then
> + /sbin/sysctl -w net.inet.ip.fw.one_pass=0
> + fi
> +
> + ############
Note to anyone committing this to CURRENT:
Make sure you stick to the new style, using ``case'' instead of
``if''.
Thanks,
Sheldon.
State Changed From-To: open->closed Fixed in revision 1.5 and 1.4.2.1 of dummynet.4. Submitter (were his mail address not bouncing) could use /etc/sysctl.conf for sysctl manipulation. |
dummynet.4 has the incorrect sysctl listed to disable one_pass rc.firewall and defaults/rc.conf are modified to enable disabling one_pass by setting net.inet.ip.fw.one_pass to 0 one_pass is used with dummynet in order to define whether packets are accepted once they match a pipe (this is the default behavior). If one_pass is set to 0, the packet is reinjected into the rules immediately following the pipe that it matched and will be tested against the remainder of the ruleset.