From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: Patrick McHardy <kaber@trash.net>,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
mph@one.com, as@one.com
Subject: Re: [nf-next PATCH] netfilter: SYNPROXY let unrelated packets continue
Date: Wed, 4 Sep 2013 14:56:26 +0200 [thread overview]
Message-ID: <20130904125626.GA4520@localhost> (raw)
In-Reply-To: <20130829101625.14346.41071.stgit@dragon>
On Thu, Aug 29, 2013 at 12:18:46PM +0200, Jesper Dangaard Brouer wrote:
> Packets reaching SYNPROXY were default dropped, as they were most
> likely invalid (given the recommended state matching). This
> patch, changes SYNPROXY target to let packets, not consumed,
> continue being processed by the stack.
>
> This will be more in line other target modules. As it will allow
> more flexible configurations of handling, logging or matching on
> packets in INVALID states.
Applied, thanks.
prev parent reply other threads:[~2013-09-04 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 10:18 [nf-next PATCH] netfilter: SYNPROXY let unrelated packets continue Jesper Dangaard Brouer
2013-08-29 10:11 ` Patrick McHardy
2013-09-04 12:56 ` Pablo Neira Ayuso [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=20130904125626.GA4520@localhost \
--to=pablo@netfilter.org \
--cc=as@one.com \
--cc=brouer@redhat.com \
--cc=kaber@trash.net \
--cc=mph@one.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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.