From: Shivani Bhardwaj <shivanib134@gmail.com>
To: Laura Garcia Liebana <nevola@gmail.com>
Cc: Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>,
outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [PATCH] extensions: libipt_LOG: Avoid to print the default log level in the translation
Date: Fri, 11 Mar 2016 00:02:25 +0530 [thread overview]
Message-ID: <CAKHNQQGPvSmQP9R3omAuo1hbnOHPrsWhxkmsB7npxKM97v++Fw@mail.gmail.com> (raw)
In-Reply-To: <20160310181537.GA16699@sonyv>
On Thu, Mar 10, 2016 at 11:45 PM, Laura Garcia Liebana <nevola@gmail.com> wrote:
> Avoid to print the log level in the translation when the level is the
> default value.
>
> Example:
>
> $ sudo iptables-translate -t filter -A INPUT -m icmp ! --icmp-type 10 -j LOG
> nft add rule ip filter INPUT icmp type != router-solicitation counter log
>
Looks good. Don't forget to send a patch for libip6t_LOG too.
Same is the case with reject as well. When I did the translations, I
left its default nature intact.
$ sudo ip6tables-translate -A FORWARD -p TCP --dport 22 -j REJECT
nft add rule ip6 filter FORWARD tcp dport 22 counter reject with
icmpv6 type port-unreachable
Pablo, should this be corrected too?
Laura, may be you can send more patches depending on his response.
Thanks.
> Signed-off-by: Laura Garcia Liebana <nevola@gmail.com>
> ---
> extensions/libipt_LOG.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/extensions/libipt_LOG.c b/extensions/libipt_LOG.c
> index f3875b6..216b1ca 100644
> --- a/extensions/libipt_LOG.c
> +++ b/extensions/libipt_LOG.c
> @@ -194,7 +194,8 @@ static int LOG_xlate(const struct xt_entry_target *target,
> xt_xlate_add(xl, "prefix \\\"%s\\\" ", loginfo->prefix);
>
> for (i = 0; i < ARRAY_SIZE(ipt_log_xlate_names); ++i)
> - if (loginfo->level == ipt_log_xlate_names[i].level) {
> + if (loginfo->level != LOG_DEFAULT_LEVEL &&
> + loginfo->level == ipt_log_xlate_names[i].level) {
> xt_xlate_add(xl, "level %s ",
> ipt_log_xlate_names[i].name);
> break;
> --
> 2.7.0
>
next prev parent reply other threads:[~2016-03-10 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 18:15 [PATCH] extensions: libipt_LOG: Avoid to print the default log level in the translation Laura Garcia Liebana
2016-03-10 18:32 ` Shivani Bhardwaj [this message]
2016-03-10 18:37 ` Pablo Neira Ayuso
2016-03-10 18:36 ` Pablo Neira Ayuso
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=CAKHNQQGPvSmQP9R3omAuo1hbnOHPrsWhxkmsB7npxKM97v++Fw@mail.gmail.com \
--to=shivanib134@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=nevola@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).