From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] ipsec: Add block rules to avoid conntrack entries
Date: Sun, 04 Oct 2015 18:07:05 +0100 [thread overview]
Message-ID: <1443978425.18782.108.camel@ipfire.org> (raw)
In-Reply-To: <56115302.7020001@rymes.com>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
On Sun, 2015-10-04 at 12:25 -0400, Tom Rymes wrote:
> On 10/03/2015 5:31 PM, Michael Tremer wrote:
> > If an IPsec VPN connections is not established, there are
> > rare cases when packets are supposed to be sent through
> > that said tunnel and incorrectly handled.
>
> Michael, et. al.:
>
> I just posted a comment on the bug before I realized that e-mail
> would
> be more appropriate.
>
> My apologies for not being up to speed on this, but can you hold my
> hand
> on implementing this? I am simply not confident enough to apply these
> changes without a better understanding of what I am doing.
You got this already applied (at least the bare essence of that). I
think we should wait for someone else to confirm that this is not
crashing anything :)
Since I emailed this patch I am still wondering if we should not limit
this rule to the RED interface. We didn't do that when we tried all
this on one of your machines (
https://bugzilla.ipfire.org/show_bug.cgi?id=10908#c16). It is an easier
solution, but I am wondering if that does not have any side-effects...
@Timo: You should use the Reviewed-by: tag then.
Best,
-Michael
>
> Thank you,
>
> Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2015-10-04 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56115302.7020001@rymes.com>
2015-10-04 17:07 ` Michael Tremer [this message]
2015-10-08 17:11 ` Timo Eissler
2015-10-15 21:40 ` Michael Tremer
2015-10-03 21:31 Michael Tremer
2015-10-04 15:56 ` Timo Eissler
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=1443978425.18782.108.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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