Date: Sun, 25 Apr 2021 05:14:09 +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-l5oRZppoRG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255104-227@https.bugs.freebsd.org/bugzilla/> References: <bug-255104-227@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=3D255104 --- Comment #11 from Michael Meiszl <michael@meiszl.de> --- Update: started manually, the machine ran for 24hrs like a charm! maybe somebody else should try this simple trick (set firewall to NO in rc.conf, reboot, login in and do "service ipfw onestart") and check if it w= orks for him too? This morning, I was curious and thought, maybe I could get the same effect = if I delay the firewall loading at boot time by editing the /etc/rc.d/ipwf file.= I have tried "Required: LOGIN" and rebootet. Sadly, it did not work, the machine crashed after 2mins again :-( Turning it off and started it manually like described above worked once mor= e, it is up and running for over an hour now already (and I dont expect it to crash anymore). But of course, this is not really an option. Usually the box runs forever unless a major update comes in and brings a new kernel. Then it reboots automatically and I now always have to remember to start the firewall afterwards by hand. I have supplied the latest kernel crash listing here as an attachment, maybe somebody can take a look at it and find out what is happening? I have some = more boxes to update but I wont start unless this bug is fixed. --=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-255104-227-l5oRZppoRG>