I'm trying to set up an OpenVPN AS server in AWS that uses advanced routing versus NAT. NAT works well enough, but I'd like to be able to use IP ranges in security groups as well as have the IPs show up in various logs on other servers for easier tracking.
I'm able to set up the server to assign an IP easily enough, but it would appear that routing outside of the openVPN server is an issue. I've tried using IPs assigned within the VPC, but when adding routes to the AWS routing tables, I get an error that I can't add more specfic routes. If I use an IP range not within the VPC, AWS doesn't seem to transit the traffic.
Does this work in AWS? Or am I stuck with NAT?
2 posts • Page 1 of 1
- OpenVPN Expert
- Posts: 436
- Joined: Fri Apr 13, 2012 8:43 pm
Routing is possible, and the problem is entirely within the configuration of the AWS security settings and routing tables. Kindly make sure reciprocating routes are present and that source checking is disabled, or else AWS will just filter the traffic from the VPN clients away.