OpenVPN Access Server inside AWS VPC client routing question

[shivdeepak]

I am working on setting up an OpenVPN access server inside our AWS VPC. This OpenVPN access server is located running inside a public subnet within the VPC and users can connect to the VPC by connecting to the Access Server.

The current set-up allows users to connect to OpenVPN access server and the SSH into the servers inside the VPC. I also have a use-case where servers inside VPC to be able to SSH into the OpenVPN Connected Clients.

For Example,

Network topology:
Image for reference: https://imgur.com/a/m3MqHji

AWS VPC Subnet: 10.1.x.x

Code: Select all

# Public Subnet: 10.1.1.x

    # OpenVPN Access Server
    Public IP: 20.30.40.50
    Private IP: 10.1.1.2
    OpenVPN Gateway IP: 10.10.1.1
        
    # EC2 Instance No. 1
    Private IP: 10.1.1.3

# Private Subnet: 10.1.2.x

    # EC2 Instance No. 2
    Private IP: 10.1.2.3

Home Network: 192.168.0.x

Code: Select all

# User Laptop with OpenVPN Client
Private IP: 192.168.0.2
OpenVPN Client IP: 10.10.1.3  

I have User Laptop - 192.168.0.2 connected to OpenVPN Access Server - 10.1.1.2.

From User Laptop - 192.168.0.2 I can SSH into EC2 Instance No 1 - 10.1.1.3 and EC2 Instance 2 - 10.1.2.3.

From EC2 Instance No 1 - 10.1.1.3 I can SSH into EC2 Instance 2 - 10.1.2.3 but I cannot SSH into User Laptop - 192.168.0.2.

I would like EC2 Instance No 1 - 10.1.1.3 or EC2 Instance 2 - 10.1.2.3 to be able to SSH into User Laptop - 192.168.0.2.

How can I make that Happen?

[novaflash]

You will need to look into this:
https://docs.openvpn.net/connecting/rea ... e-network/