From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Laura Garcia Liebana <nevola@gmail.com>
Cc: netfilter-devel@vger.kernel.org, shivanib134@gmail.com,
outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] extensions: libipt_REJECT: Avoid to print the default reject with value in the translation
Date: Tue, 15 Mar 2016 01:24:02 +0100 [thread overview]
Message-ID: <20160315002402.GA9588@salvia> (raw)
In-Reply-To: <20160312172929.GA15987@sonyv>
On Sat, Mar 12, 2016 at 06:29:32PM +0100, Laura Garcia Liebana wrote:
> Avoid to print the reject with value in the translation when the value is the default.
>
> Before this patch:
>
> $ sudo iptables-translate -A FORWARD -p TCP --dport 22 -j REJECT
> nft add rule ip filter FORWARD tcp dport 22 counter reject with icmp type port-unreachable
>
> After this patch:
>
> $ sudo iptables-translate -A FORWARD -p TCP --dport 22 -j REJECT
> nft add rule ip filter FORWARD tcp dport 22 counter reject
>
> Signed-off-by: Laura Garcia Liebana <nevola@gmail.com>
> ---
> extensions/libipt_REJECT.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/extensions/libipt_REJECT.c b/extensions/libipt_REJECT.c
> index 4148776..0e9b7d7 100644
> --- a/extensions/libipt_REJECT.c
> +++ b/extensions/libipt_REJECT.c
> @@ -17,6 +17,8 @@
> #define IPT_ICMP_ADMIN_PROHIBITED IPT_TCP_RESET + 1
> #endif
>
> +#define DEFAULT_REJECT_WITH IPT_ICMP_PORT_UNREACHABLE
This code is rather easy to read so I'd suggest no need to add this
new definition, instead use IPT_ICMP_PORT_UNREACHABLE.
Thanks.
prev parent reply other threads:[~2016-03-15 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 17:29 [PATCH] extensions: libipt_REJECT: Avoid to print the default reject with value in the translation Laura Garcia Liebana
2016-03-15 0:24 ` 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=20160315002402.GA9588@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=nevola@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=shivanib134@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.