netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed

From: Rvfg <i@rvf6.com>
To: netfilter@vger.kernel.org
Subject: ct state vmap no longer works on 6.3 kernel
Date: Mon, 1 May 2023 21:58:52 +0800	[thread overview]
Message-ID: <a2c6386f-d339-9774-387a-f20fa8aa28e6@rvf6.com> (raw)

Hi. I recently upgraded to 6.3 kernel and I noticed my nftables starts 
dropping incoming ipv6 router advertisement packets. Here is my input 
chains:

|chain input {||
||        type filter hook input priority filter; policy drop;||
||        iifname "lo" accept comment "trusted interfaces"||
||        ct state vmap { invalid : drop, established : accept, related 
: accept, * : jump input-allow }||
||}||
||
||chain input-allow {||
||        meta l4proto ipv6-icmp meta nftrace set 1||
||        tcp dport { 22, 22000 } accept||
||        udp dport { 21027, 22000 } accept||
||        icmp type echo-request limit rate 20/second accept comment 
"allow ping"||
||        icmpv6 type != { nd-redirect, 139 } accept||
||        ip6 daddr fe80::/64 udp dport 546 accept comment "DHCPv6 client"||
||}|

This setup used to work fine. But now RA packets never go through the 
input-allow chain (not show up in nftrace). Something must be wrong in 
the "ct state vmap" rule. I'm able to work around this by adding a "jump 
input-allow" rule at the ending of "chain input".

I found 
https://github.com/torvalds/linux/commit/d9e7891476057b24a1acbf10a491e5b9a1c4ae77 
might be relevant (not tested yet). I'm not very familiar with the 
kernel. But the return NFT_BREAK in nft_ct_fast.c caught my eye. Is this 
the cause?

Thanks.

next             reply	other threads:[~2023-05-01 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01 13:58 Rvfg [this message]
2023-05-03  6:19 ` ct state vmap no longer works on 6.3 kernel Pablo Neira Ayuso
2023-05-03  7:49   ` Rvfg
2023-05-03  8:19     ` Florian Westphal
2023-05-03 11:33       ` Rvfg

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=a2c6386f-d339-9774-387a-f20fa8aa28e6@rvf6.com \
    --to=i@rvf6.com \
    --cc=netfilter@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

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 read-only IMAP folder(s) and NNTP newsgroup(s).