Date: Sun, 23 Jun 2019 06:31:43 +0000 From: bugzilla-noreply@freebsd.org To: ipfw@FreeBSD.org Subject: [Bug 238694] Configuring & using a customized IPFW rule set now causes additional rules to be (involuntarily) added Message-ID: <bug-238694-8303-kvZQtnXtVP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238694-8303@https.bugs.freebsd.org/bugzilla/> References: <bug-238694-8303@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238694 --- Comment #14 from rkoberman@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 actua= lly 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 starti= ng 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. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238694-8303-kvZQtnXtVP>