From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Recommended VPN Tunnel client?
Date: Fri, 10 Feb 2012 10:12:35 -0500 [thread overview]
Message-ID: <CA+czFiAU9TbxdpNeyMu90EkwTtAESB4P=+CMxDzyEGqHA5Zwow@mail.gmail.com> (raw)
In-Reply-To: <CAA2qdGUVF7Vx+=kqU97j3qbjN0oRw-0dEqbOc4ffzJpY_dQneA@mail.gmail.com>
On Thu, Feb 9, 2012 at 10:48 PM, Pandu Poluan <pandu@poluan.info> wrote:
> Scenario: I have a server in the cloud that needs to connect to an internal
> server in the office. There are 2 incoming connections into my office, ISP
> "A" and ISP "B". The primary connection is A, but if A goes down, we can use
> B. The app running on the cloud server has no automatic failover ability
> (i.e., if A goes down, someone must change the app's conf to point to B).
>
> My thought: If I can make a tunnel from the server to the FortiGate firewall
> currently guarding the HQ, the cloud app can simply be configured to connect
> to the internal IP address of the internal server. No need to manually
> change the app's conf.
>
> The need: a VPN client that:
> + can selectively send packets fulfilling a criteria (in this case, dest= IP
> address of internal server)*
> + has automatic failover and failback ability
>
> *solutions involving iptables and iproute2 are also acceptable
>
> Can anyone point me to the right direction re: what package and the relevant
> howto?
>
> Thanks in advance.
>
> Rgds,
Not exactly what you're looking for, but this might help:
http://www.ntop.org/products/n2n/
That would set up reliable visibility on layer 2. You probably want to
employ something like 802.1x on top of it.
--
:wq
prev parent reply other threads:[~2012-02-10 15:13 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
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 ` Michael Mol [this message]
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='CA+czFiAU9TbxdpNeyMu90EkwTtAESB4P=+CMxDzyEGqHA5Zwow@mail.gmail.com' \
--to=mikemol@gmail.com \
--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