From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Leblond <eric@regit.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [RFC PATCHv3 2/2] netfilter: nft: reject support for IPv6 and TCP reset
Date: Mon, 30 Dec 2013 18:18:31 +0100 [thread overview]
Message-ID: <20131230171831.GB21208@localhost> (raw)
In-Reply-To: <1388316494-1194-3-git-send-email-eric@regit.org>
On Sun, Dec 29, 2013 at 12:28:14PM +0100, Eric Leblond wrote:
> This patch moves nft_reject_ipv4 to nft_reject and adds support
> for IPv6 protocol. This patch uses functions included in nf_reject.h
> to implement reject by TCP reset.
>
> The code has to be build as a module if NF_TABLES_IPV6 is also a
> module to avoid compilation error due to usage of IPv6 functions.
> This has been done in Kconfig by using the construct:
> depends on NF_TABLES_IPV6 || !NF_TABLES_IPV6
> This seems a bit weird in term of syntax but works perfectly.
Also applied, thanks.
next prev parent reply other threads:[~2013-12-30 17:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 0:42 [RFC PATCH 0/2] nft: improve reject support Eric Leblond
2013-12-11 0:42 ` [PATCH 1/2] netfilter: REJECT: separate reusable code Eric Leblond
2013-12-11 0:42 ` [PATCH 2/2] netfilter: nft: reject support for IPv6 and TCP reset Eric Leblond
2013-12-12 7:44 ` [RFC PATCH 0/2] nft: finish reject support Eric Leblond
2013-12-12 7:44 ` [PATCH 1/2] netfilter: REJECT: separate reusable code Eric Leblond
2013-12-20 9:50 ` Pablo Neira Ayuso
2013-12-27 14:51 ` Eric Leblond
2013-12-29 11:28 ` [RFC PATCHv3 finish reject support] Eric Leblond
2013-12-29 11:28 ` [RFC PATCHv3 1/2] netfilter: REJECT: separate reusable code Eric Leblond
2013-12-30 17:18 ` Pablo Neira Ayuso
2013-12-29 11:28 ` [RFC PATCHv3 2/2] netfilter: nft: reject support for IPv6 and TCP reset Eric Leblond
2013-12-30 17:18 ` Pablo Neira Ayuso [this message]
2013-12-12 7:44 ` [PATCH " Eric Leblond
2013-12-12 7:55 ` Tomasz Bursztyka
2013-12-12 7:57 ` Tomasz Bursztyka
2013-12-12 8:14 ` Eric Leblond
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=20131230171831.GB21208@localhost \
--to=pablo@netfilter.org \
--cc=eric@regit.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.