From: Lubomir Rintel <lkundrak@v3.sk>
To: Neal Murphy <neal.p.murphy@alum.wpi.edu>
Cc: netfilter@vger.kernel.org
Subject: Re: conntrack GRE behaves differently in 3.17 / 3.18
Date: Mon, 27 Apr 2015 15:47:47 +0200 [thread overview]
Message-ID: <1430142467.3948.14.camel@v3.sk> (raw)
In-Reply-To: <1430142363.3948.12.camel@alum.wpi.edu>
On Thu, 2015-01-22 at 18:51 +0000, Neal Murphy wrote:
> On Thursday, January 22, 2015 10:40:20 AM Eliezer Croitoru wrote:
...
> >
> First deal with packets that are always blocked or may be blocked depending on
> the current time. REL/EST that get past that are accepted. The remainder are
> NEW and can be handled as slowly and excruciatingly as desired. Of course, you
> DROPped INVALID packets very early, in mangle:PREROUTING; it isn't worth
> wasting even one extra CPU cycle to process those since netfilter has no idea
> why it received them and has no idea what to do with them. "Thentuwion! Thwow
> it to the gwound!"
Ah, about eleven, sir!
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2015-04-27 13:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1430142363.3948.12.camel@alum.wpi.edu>
2015-04-27 13:47 ` Lubomir Rintel [this message]
2015-01-19 13:04 conntrack GRE behaves differently in 3.17 / 3.18 Jan Niggemann
2015-01-21 2:01 ` Eliezer Croitoru
2015-01-21 13:19 ` Jan Niggemann
2015-01-21 14:33 ` Mart Frauenlob
2015-01-21 19:03 ` Jan Niggemann
2015-01-21 23:21 ` Pascal Hambourg
2015-01-22 7:55 ` Jan Niggemann
2015-01-22 10:10 ` Mart Frauenlob
2015-01-22 15:40 ` Eliezer Croitoru
2015-01-22 18:51 ` Neal Murphy
2015-01-22 20:33 ` Pascal Hambourg
2015-01-22 21:51 ` Jan Niggemann
2015-01-22 22:28 ` Neal Murphy
2015-01-23 23:20 ` Mart Frauenlob
2015-01-24 7:44 ` Jan Niggemann
2015-01-24 15:28 ` Mart Frauenlob
2015-01-24 20:07 ` Pascal Hambourg
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=1430142467.3948.14.camel@v3.sk \
--to=lkundrak@v3.sk \
--cc=neal.p.murphy@alum.wpi.edu \
--cc=netfilter@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 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.