Date: Thu, 20 Jun 2019 15:46:01 +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-Wjg3XxqdXe@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 #10 from karl@denninger.net --- (In reply to Rodney W. Grimes from comment #9) I agree it's a regression and is easily fixed -- and thus should be. IMHO if you set up a script that doesn't provide IPv6 rules, and DOES wind = up blocking them (e.g. via the default at the end), and that stops the network from coming up (or even hangs the system waiting for it during boot) that's= on you. There are myriad non-default things you can do with the configuration that = will result in having to ^C the startup from the console or even panic the box... --=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-Wjg3XxqdXe>