pfsense reboot randomly on vmware
-
@stephenw10 said in pfsense reboot randomly on vmware:
Did you actually disable WireGuard befe those crashes? One pf them is in the wg process shortly before it crashes.
It would still be a good test to switch to e1000.
no disabled now ... monitoring wireguard tunnels without traffic .. switching to e1000 a big job .. i'll make a vm clone and then convert everything
-
Yes, it's a significant task. But it would prove the issue is in the vmxnet3 driver. Or disprove it.
-
I will definitely do it. my steps are
- wireguard down for two days and see if problem backup job
- change e1000
I will give feedback. if a solution is found in the meantime I would be happy
-
@stephenw10 in this moment 20 hours without reboot .
wireguard is up but without backup running . low traffic transit . -
@security_sharezone said in pfsense reboot randomly on vmware:
one day up e running .. today night switch on e1000 network
-
Cool. One of our devs is digging into this. He may reach out to you with a diagnostic kernel.
-
@stephenw10
maximum availability to support you and the community -
i think that for 2 Days 14 Hours 08 Minutes 08 Seconds the firt point of step 1. ( wireguard down for two days and see if problem backup job ) is done
today renable backup job and resubmit result . if crach disable vmxnet3 and enable e1000 -
system crashed after enable backup copy with vpn wireguard dump_1212_2023.txt
-
another crash Crash report begins. Anonymous mac.txt
-
Hmm, interesting.
Are you able to upgrade to 2.7.2 and confirm it also happens there?
-
I performed update before re-enabling backup jobs
-
@stephenw10
you thinh that is keepalive the problem ?now for all vpn is set to 25 second
-
It's shouldn't be. You should not be able to panic the kernel by changing the keep-alive time!
-
@stephenw10
so far it has not rebooted I am waiting for tonight's backups . I will update you tomorrow morning -
So that's using vmxnet3 NIC in pfSense 2.7.2 b ut with WireGuard disabled?
-
@stephenw10 said in pfsense reboot randomly on vmware:
So that's using vmxnet3 NIC in pfSense 2.7.2 b ut with WireGuard disabled?
i use vmxnet3 NIC in pfSense 2.7.2 with #3 vpn WireGuard . only one vpn have traffic copy backup
-
Ok great so WireGuard is still up but not passing traffic?
-
@stephenw10 said in pfsense reboot randomly on vmware:
Ok great so WireGuard is still up but not passing traffic?
wireguard has always been active. traffic always goes to the remote point, but when I activate the backup that has the remote point as a second copy pfsense crashes
-
Great we're trying to replicate it here.
