From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Recommended VPN Tunnel client?
Date: Sat, 11 Feb 2012 00:29:45 +0700 [thread overview]
Message-ID: <CAA2qdGX7nf+5RDa-MMKy9JHCu+ZbyBFOoJ=NS_G5QL3Tx_ckTw@mail.gmail.com> (raw)
In-Reply-To: <4F355057.4050101@orlitzky.com>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
On Feb 11, 2012 12:16 AM, "Michael Orlitzky" <michael@orlitzky.com> wrote:
>
> On 02/10/12 11:46, Pandu Poluan wrote:
> >
> > On Feb 10, 2012 10:08 PM, "Mick" <michaelkintzios@gmail.com
> > <mailto:michaelkintzios@gmail.com>> wrote:
> >>
> >> > >
> >> > > The need: a VPN client that:
> >> > > + can selectively send packets fulfilling a criteria (in this
> > case, dest=
> >> > > IP address of internal server)*
> >>
> >> As far as I know typical VPNs require the IP address (or FQDN) of the
VPN
> >> gateway. If yours changes because ISP A goes down then the tunnel
> > will fail
> >> and be torn down.
>
> I must have missed the original message. OpenVPN can do this. Just
> specify multiple "remote vpn.example.com" lines in your client configs,
> one for each VPN server.
>
> It also handles updating the routing table for you. Rather than match
> "IP address of internal server," it will match "IP address on internal
> network" and route through the VPN automatically.
>
I'm still torn between OpenVPN and HAproxy. The former works with both TCP
and UDP, while the latter is lighter and simpler but works with TCP only*.
*The traffic will be pure TCP, but who knows I might need a UDP tunnel in
the future.
Any experience with either?
Do note that I don't actually need a strong security (e.g. IPsec); I just
need automatic failover *and* fallback.
Rgds,
[-- Attachment #2: Type: text/html, Size: 1966 bytes --]
next prev parent reply other threads:[~2012-02-10 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 3:48 [gentoo-user] Recommended VPN Tunnel client? Pandu Poluan
2012-02-10 4:42 ` [gentoo-user] " Pandu Poluan
2012-02-10 15:04 ` Mick
2012-02-10 16:46 ` Pandu Poluan
2012-02-10 17:13 ` Michael Orlitzky
2012-02-10 17:29 ` Pandu Poluan [this message]
2012-02-10 17:40 ` Michael Mol
2012-02-10 18:05 ` Pandu Poluan
2012-02-10 18:20 ` Michael Mol
2012-02-10 18:22 ` Todd Goodman
2012-02-10 19:07 ` Michael Mol
2012-02-10 19:21 ` Todd Goodman
2012-02-10 20:12 ` Michael Mol
2012-02-10 18:36 ` Michael Orlitzky
2012-02-10 20:14 ` Michael Orlitzky
2012-02-10 22:52 ` wdk@moriah
2012-02-10 15:12 ` [gentoo-user] " Michael Mol
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA2qdGX7nf+5RDa-MMKy9JHCu+ZbyBFOoJ=NS_G5QL3Tx_ckTw@mail.gmail.com' \
--to=pandu@poluan.info \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox