On a remote private network there are two servers -- a file server and a database server (these are both Win machines, in case it matters).

The file server has its own fairly robust authentication mechanisms, and allows me to connect directly from a remote location.

The database server uses a simple username and password, so to prevent unauthorized access, it's locked down to the local network -- external traffic is blocked.

To access the database server, I'm using the OpenVPN client on Windows to connect to a VPN server on the private network.

By default, OpenVPN routes all network packets destined for the remote network on which the VPN server resides, through the VPN. Unfortunately, accessing the file server through the VPN is extremely slow!


How can I configure the OpenVPN client to ONLY route traffic through the VPN that is destined for a single, specific IP address -- namely the database server??


The correct configuration for OpenVpn is:


These entries belong in your .ovpn file and will direct all 192.168.0.* subnet traffic through the VPN.

For one IP only (

  • We are mostly English speakers and don't necessarily know German. Please translate your answer. – gronostaj Aug 6 '13 at 8:44
  • 1
    +1. This is exactly what I needed. I am using ovpn clients on my linux and hence you answer just saved me. Thanks. – slayedbylucifer May 30 '14 at 8:33
  • Can i just route a website to vpn?For example just www.facebook.com – Nicola Peluchetti Oct 28 '14 at 22:15
  • In my case routing single ip through vpn seems to work ok. But when using subnet mask it does not work at all. Any ideas why? – running.t Dec 18 '14 at 14:40
  • I still dont know answer to my question (above), but I have done some investigation and created separate thread about it: superuser.com/questions/854194/… – running.t Dec 18 '14 at 16:06


  • Use the plain internet connection for all internet traffic by default, even when the VPN is connected.
  • Route traffic to one specific IP address through the VPN.


  1. Press Win + R and execute ncpa.cpl.

  2. Right-click the VPN connection and go to Properties → Networking.

  3. Select Internet Protocol Version 4 and go to Properties → Advanced....

  4. Uncheck Use default gateway on remote network and click OK.

  5. (optional) Repeat the previous steps for Internet Protocol Version 6.

  6. (Re)connect to your VPN.

  7. Open a command prompt and execute route print -4.

  8. Spot the VPN's interface in the Interface list and its gateway in the Active Routes.

    On my machine, I have:

    Interface List
     32...........................Super Free VPN
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
             On-link     31

    Here, the VPN's gateway is, since its the gateway for the 10.xxx.xxx.xxx block.

  9. Add a persistant route that will be appended to the active routes whenever there's a connection to the VPN:

    route -p add if 32

    In this example, is the IP of whatismyip.org, is the gateway's IP and 32 the number of the interface.

  10. (optional) Repeat the previous steps for route print -6.

  11. Test the setup.

    If everything worked out, whatismyip.org and www.whatismyip.cx will display different IPs now.

  • 1
    Surely there's a simpler way? – Brian Lacy Aug 7 '12 at 14:56
  • 1
    Do you know how to achieve this under Linux (Ubuntu)? – Елин Й. Mar 26 '14 at 11:49
  • 1
    @ЕлинЙ. if you're using Network Manager just select "Use this connection only for resources on this network". – leif81 Nov 8 '14 at 2:09
  • 1
    +1 ... but could golf this? – Olivier Dulac May 26 '16 at 17:50

To your OpenVPN client config, add a line like:

route The.IP.To.Go

(Where The.IP.To.Go is the IP you wish to route through the VPN)

This instructs OpenVPN to create the entry in your OS's routing table.

Alternatively, the OpenVPN server could be made to "push" this routing configuration down to clients, by adding to the server config:

push "route The.IP.To.Go"

EDIT: One thing I missed addressing--the default forwarding of all traffic... It could either be disabled on the server, or clients can elect to ignore "pushed" directives (so our second option "pushing" the route would not work) with:

route no-pull
iptables -A PREROUTING -t mangle -i <LAN_interface> \
-d <remote_network>/<remote_netmask> -j ROUTE --gw <openvpn_host_ip>
  • Please explain what this command does. Just one command without explanation is not that useful. Also check the formatting of your post—all the <brackets> are not visible if they're not marked as code. – slhck Feb 13 '15 at 10:44

Your Answer

By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.