From: Steven Kath <steven.kath@vyatta.com>
To: Ryan Whelan <rcwhelan@gmail.com>
Cc: Petr Pisar <petr.pisar@atlas.cz>, netfilter@vger.kernel.org
Subject: Re: Reject non-ipsec traffic
Date: Thu, 21 Jul 2011 12:01:21 -0700 [thread overview]
Message-ID: <1311274881.1484.49.camel@lt> (raw)
In-Reply-To: <CAM3m09Rf7zEQ4TL5PbfT7NHF5gq24o7E-Pbq_wcwbJ25ym6Dww@mail.gmail.com>
On Thu, 2011-07-21 at 13:05 -0400, Ryan Whelan wrote:
> The issue is that IPSec is protecting a GRE tunnel and if IPSec fails
> for some reason, GRE will be happy to work without it; tunnelling
> everything in the clear. I was just hoping to put some kind of fail
> safe in place so if IPSec stopped working or failed to start,
> unencrypted traffic wouldn't be transmitted.
You could create a private loopback address on each endpoint, and use
those loopback addresses in the encryption policy. The only way the
loopback addresses can reach each other is while the IPsec associations
are up. Then set up the GRE tunnel with the loopbacks as its endpoints.
That way, when the IPsec tunnel is down, GRE will no longer be happy to
work without it.
next prev parent reply other threads:[~2011-07-21 19:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 19:20 Reject non-ipsec traffic Ryan Whelan
2011-07-20 19:56 ` Jan Engelhardt
2011-07-20 20:13 ` Ryan Whelan
2011-07-20 20:30 ` Jan Engelhardt
2011-07-20 20:33 ` Ryan Whelan
2011-07-20 20:34 ` Jan Engelhardt
2011-07-21 0:09 ` Ryan Whelan
2011-07-21 16:55 ` Petr Pisar
2011-07-21 17:05 ` Ryan Whelan
2011-07-21 19:01 ` Steven Kath [this message]
2011-07-21 19:29 ` Jan Engelhardt
2011-07-22 5:15 ` Petr Pisar
2011-07-24 22:40 ` Greg Scott
2011-07-25 0:32 ` Jan Engelhardt
2011-07-25 0:47 ` Jan Engelhardt
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=1311274881.1484.49.camel@lt \
--to=steven.kath@vyatta.com \
--cc=netfilter@vger.kernel.org \
--cc=petr.pisar@atlas.cz \
--cc=rcwhelan@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.