[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

Re: [Openvpn-users] office-to-office connections


  • Subject: Re: [Openvpn-users] office-to-office connections
  • From: "Patrick Marquetecken" <patrick.marquetecken@xxxxxxxxxx>
  • Date: Wed, 1 Jun 2005 12:20:43 +0200 (CEST)
  • Importance: Normal

> Office-to-Office VPN, do you mean Lan-to-LAN, right?
>
> I suggest you use OpenVPN as 1.6 configuration, for more than 2 office,
> multiple tun's should be up with routes to make fail over
>
> LD
Whats exectly the difference between the 2.0 config and the 1.6 in this
setup. If I look at the examples on the site i see no difference.

Patrick

>
> Le Lundi 30 Mai 2005 12:45, Florin Andrei a écrit :
>> Connecting a bunch of clients to an OpenVPN server is easy and works
>> amazingly well. This leads to a "wheel-hub and spokes" topology.
>>
>> But what if you have to connect two such "wheels" together? (office to
>> office connection)
>> Or more than two wheels?
>> What do y'all have as a matter of guidelines in such a situation?
>>
>> The tunnel between offices per se pretty much has to be in TUN mode,
>> except in some weird situations. But the offices can be in either TUN or
>> TAP, with different networks attached, etc. It's pretty crazy.
>> One thing that I can think of is to leave the two "wheels" untouched and
>> just bring up one more OpenVPN server on both sides and use these
>> supplemental servers to establish the tunnel. Routing's gonna be weird.
>> Non-standard ports must be used.
>> In this case, connecting more than two offices pretty much has to be
>> done by defining one of them as "master" and the others as "slaves",
>> essentially replicating the "wheel-hub and spokes" topology at a higher
>> level.
>>
>> Thoughts?
>>
>> Anyone tried a hybrid approach? I.e. use OpenVPN to connect clients to
>> the office, and use IPSec to connect the offices together. I know, after
>> working with OpenVPN, IPSec is such a pain, but in some cases it might
>> make sense (some offices already use an IPSec-based VPN).
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> Openvpn-users mailing list
> Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/openvpn-users
>
>


-- 
aaaaa



-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr_______________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
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/2005-06/msg00002.html on line 239

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/2005-06/msg00002.html on line 239