Quote from: viragomann on August 21, 2025, 03:32:17 PMI am talking about the server. I guess, it has the first OPNsense as gateway as well.The Problem has be sort of fixed.
But if you want to access it from "outside" over the second, it sense responses to the second.
You can go with this setup with masquerading the traffic to the server as well, however.
To do so go the NAT > Outbound.
Enable the hybrid mode.
Add a rule:
interface: the one facing to the server
source: OpenVPN tunnel network
destination: any
translation: interface address
TLDR: The VPN to the main OPNSense instance now works, even RDP works, but I have a weird Port Forwarding Rule to it's own interface now that is needed.
I have never done that on other systems and this 'ghost' IP issue seems to be the root cause I think.
It only works with this rule in place.
You cannot view this attachment.
.53 is not the OPNSense's IP, neither WAN (192.168.178.2) nor LAN (192.168.153.254).
But in order for the VPN connection to work I need to have this rule to forward the 'ghost' IP .53 to it's own LAN interface.... God knows why
Do you have any idea what could be the problem here?