Re: Intersite VPN
- From: Christophe Vandeplas <christopheSPAM@xxxxxxxxxxxxx>
- Date: Wed, 03 Oct 2007 21:37:20 +0200
Bryhhh wrote:
<snip>
Or, would the Site B server be presented with an interface on
192.168.16.0/24, and the site B server was left to deal with routing
between the two? If this was the case though, how would I route back
in the other direction? Surely the site A server must have a virtual
interface of some description too?
Usually we use ipsec tunnels between sites. With an ipsec tunnel you
don't have that .18 network needed. I'm not a site-to-site ssl-vpn
expert, but I have already configured client-ssl-vpn's in a not to
distant past.
Depending on your distro you will have more or less tutorials with the
installation and configuration instructions.
Don't forget you'll have to generate SSL certificates for both sides.
(self-signed is perfect)
btw: You'll probably want a routed tunnel.
A good place to start is: http://openvpn.net/howto.html
Also look at your favorite encyclopedia: http://en.wikipedia.org/wiki/OpenVPN
But remember this: The advantage of OpenVPN is you can do many many
things with it. And the disadvante of OpenVPN is that you can do many
many things with it.
You'll probably really understand this after playing a few hours with it
while digging the net for good tuts.
--
mailto:christophe@xxxxxxxxxxxxx
http://christophe.vandeplas.com
.
- References:
- Re: Intersite VPN
- From: Bryhhh
- Re: Intersite VPN
- From: Bryhhh
- Re: Intersite VPN
- Prev by Date: Re: Intersite VPN
- Next by Date: Re: Would a firewall have protected Jammie Thomas from being sued by the RIAA Safenet
- Previous by thread: Re: Intersite VPN
- Next by thread: Re: Would a firewall have protected Jammie Thomas from being sued by the RIAA Safenet
- Index(es):
Relevant Pages
|
