"
I've the same problem using "OPNsense 21.1.4-amd64" with "os-wireguard v1.5".
I can establish a working connection to wireguard with ease when connecting via LAN but not via WAN coming from the internet (tested with muliple devices). I see the connection initialisation package from the remote client on my WAN Interface when capturing packages. I see something happening on server-side, but internet-clients do not recieve a single package in response and thus there is no handshake - also no traffic on the wireguard interface. I triple-checked the inbound rule on the WAN-interface with the port in use, but I don't find the issue. Debug/logging capabilities on wireguard are somewhere between bad and non-existent.
Has anyone found the root cause of this problem? I don't want to start from scratch without indication to succeed.
EDIT: Problem solved. Outbound traffic was routed through wrong/different WAN interface and couldn't reach target.
I can establish a working connection to wireguard with ease when connecting via LAN but not via WAN coming from the internet (tested with muliple devices). I see the connection initialisation package from the remote client on my WAN Interface when capturing packages. I see something happening on server-side, but internet-clients do not recieve a single package in response and thus there is no handshake - also no traffic on the wireguard interface. I triple-checked the inbound rule on the WAN-interface with the port in use, but I don't find the issue. Debug/logging capabilities on wireguard are somewhere between bad and non-existent.
Has anyone found the root cause of this problem? I don't want to start from scratch without indication to succeed.
EDIT: Problem solved. Outbound traffic was routed through wrong/different WAN interface and couldn't reach target.
