1
General Discussion / Traffic from WG peer is skipping WG Interface
« on: April 05, 2024, 11:41:50 pm »
Hello community. Seeking for advice here. I have working WG VPN tunnel between my and remote location. My local OPNsense is using 10.100.10.1/29 and remote (WG running on Unraid) is using 10.100.10.2/29.
I have communication working between my local LAN and remote LAN and this is all working fine.
On my OPNsense i have enabled interface for this wg0 tunnel just to be able to sort rules easily on specific interface. But I am facing one issue.
When the traffic is coming from remote LAN (say 192.168.1.0/24), it naturally hits my wg0 interface on "in" direction.
But when I initiate traffic from Unraid server - I assume that due to the fact that it runs wireguard, traffic originating from that server hitting my LAN is show as coming from peer ip 10.100.10.2 0 and here is my problem - this traffic is never seen on wg0 interface, only and exclusively on LAN interface direction "out".
I am aware that I can still filter it respectively (using IP/objects on LAN direction "out"), but maybe I am just missing something here? Is there a way I can force OPNsense to see traffic coming from peer IP to actually be processed on wg0 "in" interface?
I have communication working between my local LAN and remote LAN and this is all working fine.
On my OPNsense i have enabled interface for this wg0 tunnel just to be able to sort rules easily on specific interface. But I am facing one issue.
When the traffic is coming from remote LAN (say 192.168.1.0/24), it naturally hits my wg0 interface on "in" direction.
But when I initiate traffic from Unraid server - I assume that due to the fact that it runs wireguard, traffic originating from that server hitting my LAN is show as coming from peer ip 10.100.10.2 0 and here is my problem - this traffic is never seen on wg0 interface, only and exclusively on LAN interface direction "out".
I am aware that I can still filter it respectively (using IP/objects on LAN direction "out"), but maybe I am just missing something here? Is there a way I can force OPNsense to see traffic coming from peer IP to actually be processed on wg0 "in" interface?