From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Liping Zhang <zlpnobody@163.com>
Cc: 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: Mon, 20 Jun 2016 12:48:29 -0300 [thread overview]
Message-ID: <20160620154829.GD18341@localhost.localdomain> (raw)
In-Reply-To: <1466429188-3942-1-git-send-email-zlpnobody@163.com>
Hi Liping,
On Mon, Jun 20, 2016 at 09:26:28PM +0800, Liping Zhang wrote:
> From: Liping Zhang <liping.zhang@spreadtrum.com>
>
> In iptables, if the user add a rule to send tcp RST and specify the
> non-TCP protocol, such as UDP, kernel will reject this request. But
> in nftables, this validity check only occurs in nft tool, i.e. only
> in userspace.
>
> This means that user can add such a rule like follows via nfnetlink:
> "nft add rule filter forward ip protocol udp reject with tcp reset"
>
> This will generate some confusing tcp RST packets. So we should send
> tcp RST only when it is TCP packet.
>
> Signed-off-by: Liping Zhang <liping.zhang@spreadtrum.com>
> ---
> net/ipv4/netfilter/nf_reject_ipv4.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/net/ipv4/netfilter/nf_reject_ipv4.c b/net/ipv4/netfilter/nf_reject_ipv4.c
> index b6ea57e..fd82202 100644
> --- a/net/ipv4/netfilter/nf_reject_ipv4.c
> +++ b/net/ipv4/netfilter/nf_reject_ipv4.c
> @@ -24,6 +24,9 @@ const struct tcphdr *nf_reject_ip_tcphdr_get(struct sk_buff *oldskb,
> if (ip_hdr(oldskb)->frag_off & htons(IP_OFFSET))
> return NULL;
>
> + if (ip_hdr(oldskb)->protocol != IPPROTO_TCP)
> + return NULL;
> +
> oth = skb_header_pointer(oldskb, ip_hdrlen(oldskb),
> sizeof(struct tcphdr), _oth);
> if (oth == NULL)
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.
Marcelo
next prev parent reply other threads:[~2016-06-20 15:48 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 [this message]
2016-06-21 1:35 ` Liping Zhang
2016-06-21 19:03 ` Marcelo Ricardo Leitner
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=20160620154829.GD18341@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 \
/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).