VPN'ed Server that Still Services Clients on Remote LAN

[mache]

Hi I am new to forum.

I have DD-WRT on a home router with OpenVPN running as a server. I link to it with my laptop running in client mode when I travel. I want to link a single Linux server on a remote LAN to that DD-WRT router via OpenVPN. While I still want the server able to service its clients on the remote LAN, I do want to be able to access the remote server from home via SSH to do maintenance. I do not anyone on the remote LAN to access resources on my home LAN.

What is the best way to do this?

Thanks,

-- Mache

[mache]

Basically what I want to do is have the remote Linux server as represented by this config

client
keepalive 3 10
remote xy.com 1194
tls-auth static.key 1
dev tap
comp-lzo
proto udp
resolv-retry infinite
nobind
persist-key
persist-tun
tls-client
cipher AES-256-CBC
ns-cert-type server
ca ca.crt
cert client2.crt
key client2.key

VPN into OpenVPN on my home DD-WRT router as represented by the config

tls-server
push "route-gateway 192.168.1.1"
push "dhcp-option DNS 192.168.1.1"
dev tap0
proto udp
port 1194
mode server
tls-auth static.key 0
client-to-client
persist-key
persist-tun
comp-lzo
cipher AES-256-CBC
daemon
verb 5
keepalive 3 10
dh dh2048.pem
ca ca.crt
cert server.crt
key server.key
management localhost 5001

I want the remote Linux server to be able to continue serving clients on the remote LAN and I want to be log into the remote server from my laptop on my home LAN. I also want to continue being able to VPN to my home LAN while traveling with my laptop as represented by this config.

client
keepalive 3 10
remote x.y.com 1194
tls-auth static.key 1
dev tap
comp-lzo
proto udp
resolv-retry infinite
nobind
persist-key
persist-tun
tls-client
cipher AES-256-CBC
ns-cert-type server
ca ca.crt
cert client1.crt
key client1.key

Will these configurations do that, and if not, what should I change to make it so.

-- Mache

[janjust]

add something like

Code: Select all

server 10.8.0.0 255.255.255.0

to the server config - the VPN needs to be assigned a virtual IP range.

After that, restart the server and clients , reconnect and then look carefully at the logs on both ends