[Bug 238694] Configuring & using a customized IPFW rule set now causes additional rules to be (involuntarily) added

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Jun 23 06:31:46 UTC 2019


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238694

--- Comment #14 from rkoberman at gmail.com ---
9.1 is years newer than this change. You would have to go back to 7.2 or 6.3 to
predate the IPFW rule inclusion and much older, probably to at least 2.2, to
predate the loopback insertion.

I suspect that ipv6_available was set to '0' when the network startup actually
brought up an IPv6 connection, but I have yet to find any code to that does so.

Back a few years ago the loopback stuff was changed from using rules starting
will 1000 and incrementing by 1000 for wash run to starting with 100 and
incrementing vy 100. Initially only the first rule was added and later the
rules at 2000 and 3000 ere added. Those are now at 200 and 300. Nothing has
changed in the firewall rules insertions between 9.1 and 12.0. I am trying to
track down where ipv6_available might have been in 11.2. Guess I'll need to
look back a lot further... but not tonight.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ipfw mailing list