I've setup a OpenVPN server using tun and udp and enabled the options for redirecting all internet traffic and pushing lan to clients.

In the HOST NETWORK The OpenVPN Server is configured to dish out 10.8.0.x network addresses for OpenVPN clients where as the LAN clients are in the 192.168.x network.

It looks something like this.

|            HOST NETWORK               |
|     LAN Clients    +  OpenVPN Server  |
|     192.168.1.x          10.8.0.x     |
            |     INTERNET     |
 |           REMOTE NETWORK             |
 |          OpenVPN Clients             |
 |      Local Network 192.168.1.x       |

The problem is when the REMOTE NETWORK OpenVPN client are connecting from a remote network but they themselves have a local address range of 192.168.1.x

In this scenario not all packets are sent over the tunnel. e.g. If the REMOTE NETWORK has a machine at and after establishing the OpenVPN tunnel the remote OpenVPN client tries to access it goes to the REMOTE NETWORK's machine rather than the HOST NETWORK's machine.

How do I tell/configure the remote OpenVPN client to send ALL traffic over the tunnel ignoring whatever the local network routes/addresses are?

I've searched all over and tried the remote-gateway def1/autolocal options but nothing seems to work, it's always sending the packets to the REMOTE NETWORK machine instead of the HOST NETWORK machine.

This is my client config:

dev tun
proto udp
remote hostnetwork.com 1194
ncp-ciphers AES-128-GCM:AES-256-GCM:AES-128-CBC:AES-256-CBC
cipher AES-128-CBC
comp-lzo adaptive
keepalive 15 60
remote-cert-tls server
resolv-retry infinite
redirect-gateway autolocal

marked as duplicate by Zoredache, Mike, womble Sep 13 '17 at 0:02

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 3
    You learned an important lesson on the reason to never use common private /24s that consumer equipment uses on the remote side – Mike Sep 12 '17 at 22:32
  • 1
    see the following serverfault.com/questions/548888/… – Mike Sep 12 '17 at 22:33
  • 3
    This is simply not a problem with openvpn. It must be solved by re-numbering, or as the linked question mentions, some really ugly NAT hacks. – Zoredache Sep 12 '17 at 22:58
  • Not possible. It's a routing issue, not an OpenVPN issue. – Appleoddity Sep 12 '17 at 23:22