From: Florian Westphal <fw@strlen.de>
To: xietangxin <xietangxin@h-partners.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Phil Sutter <phil@nwl.cc>, Simon Horman <horms@kernel.org>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Victor Nogueira <victor@mojatatu.com>,
gaoxingwang <gaoxingwang1@huawei.com>,
huyizhen <huyizhen2@huawei.com>
Subject: Re: [PATCH net v2] netfilter: nf_nat: recalculate TCP TS offset when snat change sport
Date: Thu, 9 Jul 2026 15:30:42 +0200 [thread overview]
Message-ID: <ak-igtwiaPIi9o_w@strlen.de> (raw)
In-Reply-To: <20260709131216.2189210-1-xietangxin@h-partners.com>
xietangxin <xietangxin@h-partners.com> wrote:
> v1: https://lore.kernel.org/all/20260629093408.3927103-1-xietangxin@h-partners.com/
> ---
> net/netfilter/nf_nat_core.c | 103 +++++++++++++++++++++++++++++++++++-
> 1 file changed, 102 insertions(+), 1 deletion(-)
>
> diff --git a/net/netfilter/nf_nat_core.c b/net/netfilter/nf_nat_core.c
> index 63ff6b4d5d21..9d0b316fa3c7 100644
> --- a/net/netfilter/nf_nat_core.c
> +++ b/net/netfilter/nf_nat_core.c
> @@ -16,6 +16,8 @@
> #include <linux/siphash.h>
> #include <linux/rtnetlink.h>
>
> +#include <net/tcp.h>
> +#include <net/secure_seq.h>
> #include <net/netfilter/nf_conntrack_bpf.h>
> #include <net/netfilter/nf_conntrack_core.h>
> #include <net/netfilter/nf_conntrack_helper.h>
> @@ -894,6 +896,99 @@ static bool in_vrf_postrouting(const struct nf_hook_state *state)
> return false;
> }
>
> +static __be32 *nf_nat_tcp_ts_option_ptr(const struct sk_buff *skb)
> +{
> + struct tcphdr *th;
> + unsigned char *ptr;
> + unsigned char opcode;
> + unsigned char opsize;
> + unsigned int optlen, offset;
> +
> + offset = 0;
> + th = tcp_hdr(skb);
> + optlen = (th->doff - 5) * 4;
> + ptr = (unsigned char *)(th + 1);
Hmm, I don't think we should assume its in linear
area. In future someone might re-use this for forwarded
packets too.
Given you munge the packet, I think you could just call
skb_ensure_writable() early to assert entire tcp header
including options is in linear area.
> + while (offset < optlen) {
> + opcode = ptr[offset];
> + if (opcode == TCPOPT_EOL)
> + break;
> +
> + if (opcode == TCPOPT_NOP) {
> + offset++;
> + continue;
> + }
> +
> + if (offset + 1 >= optlen)
> + break;
> +
> + opsize = ptr[offset + 1];
> + if (opsize < 2 || offset + opsize > optlen)
> + break;
> + if (opcode == TCPOPT_TIMESTAMP && opsize == TCPOLEN_TIMESTAMP)
> + return (__be32 *)(ptr + offset + 2);
Maybe add a comment here that says that this is only for locally
generated packets and that linux tcp will always align the tsval.
Else, write needs put_unaligned_be32() instead of direct assign.
> +static void nf_nat_update_tcp_ts_offset(struct nf_conn *ct, struct sk_buff *skb)
> +{
> + __be32 *tsptr;
> + struct net *net;
> + struct tcphdr *th;
> + struct tcp_sock *tp;
> + union tcp_seq_and_ts_off st;
> + struct nf_conntrack_tuple *orig_tuple;
> + struct nf_conntrack_tuple *reply_tuple;
Could reorder this for reverse x-mas tree (i.e. invert
the above order...).
> + orig_tuple = &ct->tuplehash[IP_CT_DIR_ORIGINAL].tuple;
> + reply_tuple = &ct->tuplehash[IP_CT_DIR_REPLY].tuple;
> + if (orig_tuple->src.u.tcp.port == reply_tuple->dst.u.tcp.port)
> + return;
Maybe add a comment like /* no port rewrite? No need to update anything */
> + th = tcp_hdr(skb);
> + if (!th || !th->syn || th->ack)
> + return;
> +
> + net = nf_ct_net(ct);
> + if (READ_ONCE(net->ipv4.sysctl_tcp_timestamps) != 1)
> + return;
> +
Maybe add a comment that above check avoid bogus tsoff update for
non-randomized tcp timestamps?
> + if (!skb->sk)
> + return;
> +
I suggest to do this first, so that its obvious this function
is only for locally generated packets.
> + tsptr = nf_nat_tcp_ts_option_ptr(skb);
> + if (!tsptr)
> + return;
> +
> + switch (nf_ct_l3num(ct)) {
> + case NFPROTO_IPV4:
> + st = secure_tcp_seq_and_ts_off(net, reply_tuple->dst.u3.ip,
> + reply_tuple->src.u3.ip,
> + reply_tuple->dst.u.tcp.port,
> + reply_tuple->src.u.tcp.port);
> + break;
> +#if IS_ENABLED(CONFIG_IPV6)
> + case NFPROTO_IPV6:
> + st = secure_tcpv6_seq_and_ts_off(net, reply_tuple->dst.u3.ip6,
> + reply_tuple->src.u3.ip6,
> + reply_tuple->dst.u.tcp.port,
> + reply_tuple->src.u.tcp.port);
> + break;
> +#endif
> + default:
> + return;
> + }
> +
> + tp = tcp_sk(skb->sk);
> + *tsptr = htonl(tcp_skb_timestamp_ts(tp->tcp_usec_ts, skb) + st.ts_off);
>
> unsigned int
> nf_nat_inet_fn(void *priv, struct sk_buff *skb,
> const struct nf_hook_state *state)
> @@ -937,8 +1032,14 @@ nf_nat_inet_fn(void *priv, struct sk_buff *skb,
> state);
> if (ret != NF_ACCEPT)
> return ret;
> - if (nf_nat_initialized(ct, maniptype))
> + if (nf_nat_initialized(ct, maniptype)) {
> + if (state->hook == NF_INET_POST_ROUTING &&
I wonder if this should be LOCAL_OUT. I do understand that many
people use SNAT/MASQUERADE from postrouting to deal with both local and
forwarded traffic at the same time, so more of a open question.
prev parent reply other threads:[~2026-07-09 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 13:12 [PATCH net v2] netfilter: nf_nat: recalculate TCP TS offset when snat change sport xietangxin
2026-07-09 13:30 ` Florian Westphal [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=ak-igtwiaPIi9o_w@strlen.de \
--to=fw@strlen.de \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gaoxingwang1@huawei.com \
--cc=horms@kernel.org \
--cc=huyizhen2@huawei.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--cc=victor@mojatatu.com \
--cc=xietangxin@h-partners.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.