dlyxzen
Hi everyone,
We currently have an OpenVPN node in AWS operating in NAT mode. We have recently been asked to change it to routing mode for the sake of end to end IP visibility.
The VPC being used was pre-built with a number of subnets already existing. The whole VPC CIDR block is a /21 with a number of small /27's being used as subnets (OpenVPN is in one of these subnets).
There is a /22 available from this /21 we would like to use for the end-user client range when flipping to routing mode. The issue we are having though is I am unable to add a route for the /22 to the OpenVPN instance itself (as suggested by the documentation).
Update your private subnets’ routing tables to let the internal VPC router know which subnets are reachable via the Access Server (i.e., VPN client subnets)
AWS is complaining that the /22 is more specific then the already existing /21 local route in the route table and I am unable to add the route in.
I was wondering if anybody has this setup working in AWS (OpenVPN with routed mode) and if so, what is your VPC/Subnet configuration like?
It may be the case that we have to deploy an entirely new VPC to house the OpenVPN instance, with a single subnet using the entire VPC range.
Has anybody got OpenVPN working in AWS correctly using routing mode?
Thanks,
Dennis
