pfsense reboot randomly on vmware

stephenw10

Hmm, interesting.

Are you able to upgrade to 2.7.2 and confirm it also happens there?

security_sharezone

@stephenw10

I performed update before re-enabling backup jobs

security_sharezone

@stephenw10
you thinh that is keepalive the problem ?

now for all vpn is set to 25 second

stephenw10

It's shouldn't be. You should not be able to panic the kernel by changing the keep-alive time!

security_sharezone

@stephenw10
so far it has not rebooted I am waiting for tonight's backups . I will update you tomorrow morning

stephenw10

So that's using vmxnet3 NIC in pfSense 2.7.2 b ut with WireGuard disabled?

security_sharezone

@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

stephenw10

Ok great so WireGuard is still up but not passing traffic?

security_sharezone

@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

stephenw10

Great we're trying to replicate it here.

security_sharezone

@stephenw10

if desired we can make a wireguard vpn pfsense to my router and give you an nfs endpoint to simulate the backup repository and test traffic

marcosm

I was unable to make it panic. I set up a WireGuard tunnel between two 23.09.1 ESXi (7.0.3) VMs and tried to reproduce this in a couple ways. First with the iperf3 client/server on the firewalls themselves, then second with the iperf3 client/server on hosts behind the firewalls. Both were TCP tests, no NAT, which ran for over 8 hours each.

stephenw10

@security_sharezone If you're able to test this with iperf and still trigger it that then points to the ESXi version difference.

security_sharezone

@stephenw10

i have done various tests to isolate the problem and i think at this point it is the nfs outbound protocol. this is because from another true pfsense location always nfs but this time inbound i have no problems

security_sharezone

@stephenw10
nothing continuos crash. you have idea ?

dump_22_12.txt

stephenw10

I don't personally. I don't run VMWare at all though. I know several of our devs do though and are not hitting it. Yet.