Date: Sat, 24 Apr 2021 06:39:40 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 255104] FreeBSD 13.0-RELEASE panic/crash with ipfw/dummynet/divert & wlan Message-ID: <bug-255104-227-ZE9lqc5XTD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255104-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104 --- Comment #9 from Michael Meiszl <michael@meiszl.de> --- yeah, I was too optimistic :-( It worked, but only unless I did a firewall_enable="YES" into rc.conf and rebootet :-( Soon after the reboot the machine got locked up again, only the reset key helped me out (even the console was dead). But, what is really strange, it works if I use firewall_enable="NO", reboot, log in manually and do a "service ipfw onestart". Then it runs for hours and honors all those rules. I don't see the real difference in those two starting methods, only that everything is up and running already if I start the fw later on. Maybe there is a strange and yet unknown dependency in 13??? -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255104-227-ZE9lqc5XTD>