1
General Discussion / Re: Issues trying to route traffic over a VPN connection
« on: October 20, 2020, 01:03:14 am »
Thanks Gauss, After reviewing I found I was missing a few things from the VPN Client config and now the VPN server hosted at 104.237.XXX.XXX is able to forward the traffic from ports 80,443,32400 that are back on my home network/OPNsense. I guess at this point is there a way to force all WAN traffic for a specific client through the VPN connection, specifically my Plex Server(10.10.10.201)? It needs to register the correct WAN address. I wont bother posting the VPN Server config as all seems to be good from that side, but it running on debian 9 and I just used PiVPN to sertup if it matters. Here are a few screenshots of my OPNsense setup.
Client Connection Status
Interfaces
Rules that would need to go over VPN, these obviously need to be set to VPNNET vs WAN and I have tested this and can access the services from VPN now.(Just need to get the plex server to show the VPN Servers wan address)
Rule on VPNNET
Current Plex IP and It showing running under the external
Client Connection Status
Interfaces
Rules that would need to go over VPN, these obviously need to be set to VPNNET vs WAN and I have tested this and can access the services from VPN now.(Just need to get the plex server to show the VPN Servers wan address)
Rule on VPNNET
Current Plex IP and It showing running under the external