|
|
jessica six wrote:
--- Charles Duffy <cduffy@xxxxxxxxxxx> wrote:
There's another approach which doesn't require modifying the
routing tables on your internal systems: Your site's default
gateway can have the route to the VPN server. That way, instead of
modifying the configuration of the internal machines, you simply
route packets host->gateway->vpn.
Problem with that is the default gateway is already used to get
between different offices.
This VPN is intended for road warriors, right? So if you're using a
tun-based VPN and have OpenVPN set to provide a completely different IP
range to your road warriors (say, 172.16.250.*), the gateway can clearly
disambiguate between traffic to be forwarded to the VPN server (and thus
the road warriors) versus traffic to be sent to the other office.
Or am I misunderstanding your objection?
______________________
OpenVPN mailing lists
https://lists.sourceforge.net/lists/listinfo/openvpn-users
Warning: require_once(../../../archive_common.php) [function.require-once]: failed to open stream: No such file or directory in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2006-05/msg00090.html on line 189
Fatal error: require_once() [function.require]: Failed opening required '../../../archive_common.php' (include_path='/usr/local/lib/php') in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2006-05/msg00090.html on line 189
|