Hi,
I've tried to use a Access server (at AWS) to be able to connect from my Client Network to the AWS server private networks using the VPN Gateway.
Heres the setup:
Other Client network systems 10.68.94.x
|
v
OpenVPN Client Linux 10.68.94.77 (connecting with user gateway)
|
|
VPN
|
V
EIP 50.193.21.79 OpenVPN (internal ip 10.12.125.108)
with internal 10.12.112.0/20 network
|
v
Second Linux 10.12.118.165 (i.e. server internal system)
The configuration:
Created user "gateway" with:
1) static ip 172.27.226.5
2) Access control 10.12.112.0/20 allow all (ROUTING)
- allow access to all server side networks and clients
3) VPN gateway 10.68.94.0/24
(OpenVPN Access Config - VPN settings:)
Dynamic ip 172.27.224.0/23
static ip 172.27.226.0 /24
Group pool 172.27.240.0/23
Setting static routing on local Client systems :
route add -net 10.12.0.0 … gw 10.68.94.77)
AND
setting static routes at server internal systems:
route add -net 10.68.94.0 netmask 255.255.255.0 gw 10.12.125.108
route add -net 172.27.226.0 netmask 255.255.255.0 gw 10.12.125.108
will allow all Client side systems to connect to the server side networks
BUT
ONLY the VPN server itself is able to connect to the VPN Client, all server interns systems cannot connect to the Client NOR could the OpenVNP server connect to any other "Client-side" system.
From OPENVPN Server
ping 10.68.94.77 OK
ping 10.68.94.67 failed
from server internal system
ping 172.27.226.5 OK (i.e. the virtual ip of the OPENVPN client)
ping 10.68.94.77 failed
The question:
- How to trace this down. I really need to connect from the Server-side networks to the client network, not only vice versa.
Any suggestion is very much appreciated.
Bernd
