Score:0

OpenVPN AMI instance - routing doesn't work

us flag

I have an OpenVPN AMI instance and an Ubuntu micro behind it on AWS. The configuration is correct when I use NAT on OpenVPN. I can reach the Ubuntu micro through the tunnel and I have NAT gateway configured for that server. The OpenVPN configuration allows only the VPC traffic to go through the VPN. However, when I switch to Routing, I cannot access the Ubuntu micro any more. I've done the following:

  1. OVPN VPN Settings: Use NAT and allowed subnet 172.31.0.0/16 (which is my range on VPC). Unchecked "Should client Internet traffic be routed through the VPN?"
  2. OVPN Advanced VPN Server Config: push "route 172.31.0.0 255.255.0.0"
  3. OVPN client config: Use Routing and allowed networks 172.31.0.0/16
  4. VPC: On all network interfaces and instances stopped source/destination checking
  5. ACL allows all inbound and outband traffic with source 0.0.0.0/0
  6. Security groups also allows traffic with source 0.0.0.0/0
  7. VPC Routing tables: 172.31.0.0/16 -> local and 0.0.0.0/0 to NAT or Internet gateway
  8. tracert from my Windows VPN client shows

1 18 ms 18 ms 18 ms 172.27.232.1 2 * * * Request timed out.

Just by switching from Routing to NAT in the OpenVPN admin interface, without changing anything else, everything works fine. But I just cannot make the Routing to work.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.