Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to build a VPN setup, where there are several Road-Warriors (various OSes) want to communicate to internal network behind a VPN gateway. The key facts are these:

  • Internal network is
  • No DHCP
  • Internal hosts are all RHEL/CentOS 6
  • Road-Warriors are assigned virtual addresses within
  • VPN gateway is a RHEL 6 box with:
    • Internal address
    • External address X.X.X.X
  • VPN gateway is NOT the default gateway for internal hosts
  • VPN is implemented using Strongswan

So far Road-Warriors successfully connect to VPN gateway. The issue is that on every internal host I have to setup routing tables to send traffic through if I want them be accessible for RWs.

What are other options? How can I centrally manage routing info so that it is autodiscovered by internal hosts?

share|improve this question

There's a few ways. The easiest way is to set up an intermediate router (that acts as the default gateway for both networks) with the two subnets on different interfaces. The VPN server could be behind one of them, it doesn't have to act as one.

So something like this:

RWs - VPN Server -default gateway for vpn server- Router -default gateway- Internal network

And the router would have third interface that hooks up with the WAN

Alternatively you could have a log on script runs on the local boxes that adds the route with the gateway. This one could get complicated if they don't all have the same interface number for internal traffic.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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