Since upgrading to 25.7.6, my wireguard connections seem to work fine for a while then, either
i) not pass any traffic yet appear connected with a handshake,
ii) wireguard status icon turning into a black question mark, and no traffic.
iii) Go down completely.
As I have a couple of WG connections in a Group gateway that has a final fallback to the WAN connection, the fallback to the WAN is messy. So, I ran a machine on a single WG connection by itself, and the same issue appears.
Release notes for 25.7.6 state the update introduced wireguard: add debug option to instances. Nothing in particular stands out in the messaging. The dpinger on the other hand reports losses and gateway fallover works.
Then, there are times when the dpinger reports the connection is up, & WG status reports a handshake and some little traffic. But, when I try to do a traceroute, all the traffic stops at the gateway.
I've had to delete & recreate all WG connections at the service provider & on opnsense, and change the IP-address scheme. Then, they would work for 2 days and crash again.
My configuration and setup had been stable, without any changes for quite sometime, 6+ months....Any thoughts whether this could just be an opnsense bug? If so, how do we report it, and what diagnostic report, or testing do we submit.
Seconded on wanting an answer. I upgraded to 25.10 last night and poof, all tunnels are broken.