[Bug 238694] Configuring & using a customized IPFW rule set now causes additional rles to be (involuntarily) added
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Jun 19 16:09:58 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238694
Rodney W. Grimes <rgrimes at FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rgrimes at FreeBSD.org
Keywords| |regression
--- Comment #1 from Rodney W. Grimes <rgrimes at FreeBSD.org> ---
I concur that this is in fact a bug in the /etc/rc.firewall script. It is NOT
a bug in the documentation. The documentation is correct, the behavior of the
script is wrong.
I suggest that the "mandatory" stuff that is always done is simply wrong to be
always done, if in fact a file type script is being invoked I may very much
want those "mandatory" rules in a different place and shall be allowed to do
so.
Further this is a change in past behavior causing a POLA violation.
Had I been using firewall_type rather than firewall_script to point to my
custom firewall this would of bit me too, and in not very pleasant ways.
Besides, they are not actually mandatory from anything I can even remotely
imagine. Technically you should even be able to remove lo0, but *sigh* that
has also degerated over the years, as has hard coded 127.0.0.1 and ::1, which
is a royal PITA for some.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ipfw
mailing list