... strange behavior with Wireguard ...

[spaccabits]

that I do not understand and for which I cannot find the solution

I have configured two WireGurad interfaces and the "peer" needed for each, make the connection, I can ping/traceroute both on external and internal LAN IPs (2 "hops" on the LAN as you would expect, the necessary on external addresses/ domains; tracepath does not get to conclusion and on the LAN stops at the first "hop"), but as soon as I try to access anything (both external Domains/ IP, both internal IP to the LAN), it blocks everything and remains (Would loop) to wait you do not know what, examples:
1) wanting to access the WEB interface of the printer that is in LAN or the WEB interface of OPNsense, accesses, the browser - I tried both Google Chrome and Mozilla Firefox - sends an unrecognized certificate notice, I accept the risk and hangs up waiting for you do not know what;
2) wanting to access through SFTP/SSHFS to a shared resource, it regularly accepts the command, but it remains in an endless waiting (and, from terminal, it is not even possible to interrupt the command);
3) the same thing happens if I attempt SSH access.
from the logs that I was able to set and consult no "strange" activity results
... but the strangest/curious thing of all is that from any Android everything works regularly, while from PC (all GNU/Linnux Debian systems or derivatives).

what can it be? or, alternatively, where can I try to look to figure out what’s going on? and most importantly, how could I try to fix it?
you have to consider that until the previous version of OPNSense (23.7), everything worked regularly, the solution is to return to that version?

OPNsense version
OPNsense 24.1.1-amd64
FreeBSD 13.2-RELEASE-p9
OpenSSL 3.0.13

waiting for ideas or solutions
greetings