Wireguard time.out

[spaccabits]

I have a problem with Wireguard: with one of the latest updates (OPNsense 24.1.8-amd64) has actually stopped working: it pings on any machine in the network, but nothing else works, it seems that everything hangs at the wireguard "card" level, neither you browse the Internet nor you can connect to any resource, what you get is always and only a time-out; do not even work traceroute and tracepath, even on the address of the router and even on the address of the Wireguard instance.
the most curious thing is that as an Android client everything works correctly, from PC (Debia 12 or Debian 12 based) nothing works.

trying to figure out what happens, I found this rule in the firewall with a "no redirect" of the NAT Port-forward on the LAN, wanting to change the rule refers me to "advanced setting" of the firewall, questions:
1) Who created this rule?
2) how to modify it? the documentation is not at all clear
3) Can it be necessary to create a firewall rule for port-forwarding the (or) instance (instances) Wireguard? used in "Road Warrior", the documentation is very poor
4) why does Android work and not on the PC (Linux)?

excuse my English
waiting for ideas
greetings

[BrakkeBezem]

I am having the same issues. After the last update (OPNsense 24.1.8-amd64) My wireguards instances do not work anymore. The once outgoing as well as the incoming server stopped working.
I have a protonVPN client connection, a Site to Site connection, and a server to connect to from outside. None of them seem functional now.

[BrakkeBezem]

I actually managed to get my client connection to work again by disabling the wireguard instance and reenabling it again.
the server and S2S do not seem to work (yet). the weird thing is that a reboot of the whole machine did not seem to fix it,