From: Reindl Harald <h.reindl@thelounge.net>
To: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Cc: Jakub Jankowski <shasta@toxcorp.com>
Subject: Re: [PATCH nf] netfilter: conntrack: always store window size un-scaled
Date: Sat, 27 Jul 2019 14:15:28 +0200 [thread overview]
Message-ID: <7d4a847d-5e8e-b5a1-0324-85f3b82f60fd@thelounge.net> (raw)
In-Reply-To: <20190711222905.22000-1-fw@strlen.de>
this seemed to be fixed in 5.1.19 but not announced in
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.1.19 and after
update to 5.1.20 last night the freezes of a ssh-tunneled vnc session
are starting again without exclude "lo" while the session was stable 3 days
see topic "Connection timeouts due to INVALID state rule"
Am 12.07.19 um 00:29 schrieb Florian Westphal:
> Jakub Jankowski reported following oddity:
>
> After 3 way handshake completes, timeout of new connection is set to
> max_retrans (300s) instead of established (5 days).
>
> shortened excerpt from pcap provided:
> 25.070622 IP (flags [DF], proto TCP (6), length 52)
> 10.8.5.4.1025 > 10.8.1.2.80: Flags [S], seq 11, win 64240, [wscale 8]
> 26.070462 IP (flags [DF], proto TCP (6), length 48)
> 10.8.1.2.80 > 10.8.5.4.1025: Flags [S.], seq 82, ack 12, win 65535, [wscale 3]
> 27.070449 IP (flags [DF], proto TCP (6), length 40)
> 10.8.5.4.1025 > 10.8.1.2.80: Flags [.], ack 83, win 512, length 0
>
> Turns out the last_win is of u16 type, but we store the scaled value:
> 512 << 8 (== 0x20000) becomes 0 window.
>
> The Fixes tag is not correct, as the bug has existed forever, but
> without that change all that this causes might cause is to mistake a
> window update (to-nonzero-from-zero) for a retransmit.
>
> Fixes: fbcd253d2448b8 ("netfilter: conntrack: lower timeout to RETRANS seconds if window is 0")
> Reported-by: Jakub Jankowski <shasta@toxcorp.com>
> Tested-by: Jakub Jankowski <shasta@toxcorp.com>
> Signed-off-by: Florian Westphal <fw@strlen.de>
> ---
> net/netfilter/nf_conntrack_proto_tcp.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/net/netfilter/nf_conntrack_proto_tcp.c b/net/netfilter/nf_conntrack_proto_tcp.c
> index 7ba01d8ee165..9fe1d5e46249 100644
> --- a/net/netfilter/nf_conntrack_proto_tcp.c
> +++ b/net/netfilter/nf_conntrack_proto_tcp.c
> @@ -475,6 +475,7 @@ static bool tcp_in_window(const struct nf_conn *ct,
> struct ip_ct_tcp_state *receiver = &state->seen[!dir];
> const struct nf_conntrack_tuple *tuple = &ct->tuplehash[dir].tuple;
> __u32 seq, ack, sack, end, win, swin;
> + u16 win_raw;
> s32 receiver_offset;
> bool res, in_recv_win;
>
> @@ -483,7 +484,8 @@ static bool tcp_in_window(const struct nf_conn *ct,
> */
> seq = ntohl(tcph->seq);
> ack = sack = ntohl(tcph->ack_seq);
> - win = ntohs(tcph->window);
> + win_raw = ntohs(tcph->window);
> + win = win_raw;
> end = segment_seq_plus_len(seq, skb->len, dataoff, tcph);
>
> if (receiver->flags & IP_CT_TCP_FLAG_SACK_PERM)
> @@ -658,14 +660,14 @@ static bool tcp_in_window(const struct nf_conn *ct,
> && state->last_seq == seq
> && state->last_ack == ack
> && state->last_end == end
> - && state->last_win == win)
> + && state->last_win == win_raw)
> state->retrans++;
> else {
> state->last_dir = dir;
> state->last_seq = seq;
> state->last_ack = ack;
> state->last_end = end;
> - state->last_win = win;
> + state->last_win = win_raw;
> state->retrans = 0;
> }
> }
>
next prev parent reply other threads:[~2019-07-27 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 22:29 [PATCH nf] netfilter: conntrack: always store window size un-scaled Florian Westphal
2019-07-12 10:50 ` Jozsef Kadlecsik
2019-07-16 11:23 ` Pablo Neira Ayuso
2019-07-27 12:15 ` Reindl Harald [this message]
2019-08-13 8:47 ` Thomas Jarosch
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=7d4a847d-5e8e-b5a1-0324-85f3b82f60fd@thelounge.net \
--to=h.reindl@thelounge.net \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=shasta@toxcorp.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).