Hi Guys and Gals,
I've got a VPS which is running as my 'Wireguard VPN gateway', which is connected (through WireGuard) to a VM on site, running as my 'Wireguard VPN client'.
The client has three interfaces
- eth0 - 'The internet' - 192.168.249.100 - this is behind bother router which I cannot control.
- eth1 - The connection to the PFSense WAN interface (not yet addressed)
- wg0 - The WireGuard interface - 10.0.0.2
The server has two interface
- I enp0s25 - public facing - 5.5.5.5
- wg0 - The WireGuard interface - 10.0.0.1
Essentially what I'm trying to do is give PFSense a VPN connection to my remote VPS because it is behind a NAT and I cannot do any port forwarding to access services that are behind it.
I have the VPN connection setup perfectly. No issues there. My question is routing, so when a request hits 5.5.5.5 I immediately want this to forward to the WireGuard client (10.0.0.2) which then forwards this onto PFSense, so then it can do all of its normal routing internally. I also want all LAN devices of PFSense to also be router though the WireGuard VPN, so if a device were to do a 'what is my IP' they would get 5.5.5.5 for example.
I'm unsure of the routing, and how I can get this to work, I presume IP Tables can do this? Im up to the stage where the two VPN peers are connected. If someone can point me in the right direction.
Cheers
No comments:
Post a Comment