Wireguard wont reconnect after losing gateway access till pfsense reboot

[ipeh]

Wireguard wont reconnect after losing gateway access till pfsense reboot.

If I am using my cable internet gateway and the connection goes down I lose connection with wireguard even after connection is restored till I reboot pfsense at my main location.

Currently using 2.6.0 pfsense with wireguard 1.6_2 at both locations for site to site.

remote site doesn't have to be rebooted but the main site pfsense does when the cable connection goes down at main site.

Does anyone have a work around other than rebooting pfsense?

[t4chik0ma]

Seeing the same behavior here on 2.6.0-RELEASE (amd64)
and WG 0.1.6_2

In my case, this tunnel goes out to a cloud provider, and the PF instance is a VM which sits behind a physical PFsense box. I seem to run into this scenario if the vm PFsense is ever paused/hibernated and then brought back up, though I feel like I've also come across it when the VM is just idle/unused for long enough. Restarting the WG service on the VM doesn't seem to help. I do see the TX counter increment on the WG tunnel, though I don't see any attempts to connect outbound to the cloud provider (watching logs on the physical box in front of it) until I reboot the VM pfsense. Once it's been rebooted, the WG tunnel will establish and I'm able to pass traffic back and forth through it again.

[ipeh]

I have two internet connections on my pfsense.
I also noticed sometimes the VPN connection stays up but it stops routing data over the wireguard link till i restart the wireguard service.