Date: Thu, 20 Jun 2019 13:39:16 +0000 From: bugzilla-noreply@freebsd.org To: ipfw@FreeBSD.org Subject: [Bug 238694] Configuring & using a customized IPFW rule set now causes additional rles to be (involuntarily) added Message-ID: <bug-238694-8303-d6apCGaIrn@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 karl@denninger.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |karl@denninger.net --- Comment #6 from karl@denninger.net --- Just a quick note on practicality in the real world. If you don't have an "ipfw -f flush" as the *first* element in your custom script file you're eventually going to get a nasty and unwanted surprise. = If you *do* have such as the first element of your custom script then whatever= was there before it executes is gone. I use the custom script myself and have since forever as my configuration in places where I need ipfw is quite complex, and when I moved to 12.x I noted= no change in behavior.... likely for this reason. --=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-d6apCGaIrn>