From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Liping Zhang <zlpnobody@gmail.com>
Cc: Liping Zhang <zlpnobody@163.com>,
pablo@netfilter.org, netfilter-devel@vger.kernel.org,
Liping Zhang <liping.zhang@spreadtrum.com>
Subject: Re: [PACTH nf-next] netfilter: nf_reject_ipv4: don't send tcp RST if the packet is non-TCP
Date: Tue, 21 Jun 2016 16:03:01 -0300 [thread overview]
Message-ID: <20160621190301.GI18341@localhost.localdomain> (raw)
In-Reply-To: <CAML_gOf0ofzsnsxP=8xW7tYfv+H91yMthLykUbOphBL0JEgJqQ@mail.gmail.com>
On Tue, Jun 21, 2016 at 09:35:55AM +0800, Liping Zhang wrote:
> Hi Marcelo,
>
> 2016-06-20 23:48 GMT+08:00 Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>:
> >
> > A different check/log is made for ip6:
> > nf_reject_ip6_tcphdr_get():
> > /* IP header checks: fragment, too short. */
> > if (proto != IPPROTO_TCP || *otcplen < sizeof(struct tcphdr)) {
> > pr_debug("proto(%d) != IPPROTO_TCP or too short (len = %d)\n",
> > proto, *otcplen);
> > return NULL;
> > }
> >
> > Would be nice to have some consistency on this log message as it
> > increases debug-ability.
> >
>
> Thanks for your opinion.
>
> But you can see, there are many inconsistent things between
> nf_reject_ip6_tcphdr_get and nf_reject_ip_tcphdr_get.
That's true, yet sooner or later we can catch up the differences.
>
> For example, when tcp->rst is set, reject_ip6 will call
> pr_debug("RST is set\n"), while there's nothing in reject_ip4.
>
> IMO, these debug informations are almost useless, so there's
> no need to add this debug info only for consistent with nf_reject_ip6.
Fair enough. Although I did the comment, I don't have a strong opinion
on this.
Thanks,
Marcelo
next prev parent reply other threads:[~2016-06-21 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 13:26 [PACTH nf-next] netfilter: nf_reject_ipv4: don't send tcp RST if the packet is non-TCP Liping Zhang
2016-06-20 15:48 ` Marcelo Ricardo Leitner
2016-06-21 1:35 ` Liping Zhang
2016-06-21 19:03 ` Marcelo Ricardo Leitner [this message]
2016-06-23 11:53 ` Pablo Neira Ayuso
2016-06-23 17:33 ` 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=20160621190301.GI18341@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=liping.zhang@spreadtrum.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=zlpnobody@163.com \
--cc=zlpnobody@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.