From: Mohan Sundaram <mohan.tux@gmail.com>
To: lartc@vger.kernel.org
Subject: [Fwd: Re: [LARTC] custom route for forwarded traffic]
Date: Wed, 31 Oct 2007 02:59:54 +0000 [thread overview]
Message-ID: <4727ECDA.3090009@vsnl.com> (raw)
Aleksander Kamenik wrote:
> Hi,
> If I add a rule to the main routing table in the users network's
> firewall for servers network's external IP to go through the VPN, I will
> break the VPN connection (kind of like the chicken and egg problem).
>
This true only for cases like L3 IPSec where traffic to be encrypted is
based on src/dst IP combo. If you had a VPN virtual interface, this
should not be a problem. You can choose to route traffic of your choice.
Good examples is OpenVPN and L2 IPSec.
Mohan
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2007-10-31 2:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4727ECDA.3090009@vsnl.com \
--to=mohan.tux@gmail.com \
--cc=lartc@vger.kernel.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