OpenVPN LAN Traffic Routing Issues
-
Hi Community,
Below is my current setup
Setup:
WAN: 1.2.3.4
FW IP: 172.16.2.1
LAN: 172.16.2.X/24
OpenVPN Tunnel IP: 10.1.10.0/24
OpenVPN IPV4 Local Networks: 172.31.0.0/20, 172.16.2.0/24
2nd LAN via AWS VPN configuration: 172.31.0.0/20
AWS Server IP 172.31.1.20
DHCP Handout: Firewall-172.16.2.1
DNS Server: AWS Server-172.31.1.20I am having some issues with OpenVPN not allowing routing between both LANS. I recently moved our server to AWS and everything is working properly in the office. Computers can ping devices on the LAN and route to the AWS Server.
When Users attempt to use OpenVPN to access a shared folder on the server they are unable to communicate with the server on 172.31.1.20.
OpenVPN configuration server is setup
OpenVPN Tunnel IP: 10.1.10.0/24
to connect to LAN networks
OpenVPN IPV4 Local Networks: 172.31.0.0/20, 172.16.2.0/24
( I have tried swapping those around)I spoke with AWS support, We worked together and were able to have OpenVPN users connect to our server on 172.31.1.20 however by doing so it breaks the Local LAN at the office. You can only seem to have one or the other but not both. I was told everything on AWS side is good and referred me to contact Netgate for support.
I have tried setting OpenVPN to redirect all traffic through the tunnel, enabling DNS default settings and DNS Server settings, and tried to rebuild the OpenVPN server from scratch.
Does anyone have any suggestions?
Thanks,
Aaron
-
Anyone have any suggestions?