Date: Sat, 13 Feb 2021 07:28:59 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 253476] ipfw keepalive: tcp_do_segment: Timestamp missing, segment silently dropped Message-ID: <bug-253476-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253476 Bug ID: 253476 Summary: ipfw keepalive: tcp_do_segment: Timestamp missing, segment silently dropped Product: Base System Version: 13.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: shoesoft@gmx.net After upgrading from 12.2 to 13.0-BETA1 TCP connections can no longer trans= fer data after being idle. git bisect revealed the regression was introduced in 283c76c7c3f2f634f19f303a771a3f81fe890cab The problem is that the keepalive packets for keep-state rules are dropped. Dynamic rules are removed and the existing connections no longer work. As a workaround net.inet.tcp.tolerate_missing_ts=3D1 can be used. How to reproduce: The test setup uses epair for network communication to rule out a faulty 3rd party TCP stack. I can also reproduce the problem with real network hosts. Tested with 13.0-BETA1 amd64 VM-image in virtualbox. Terminal 1: kldload ipfw sysctl net.inet.tcp.log_debug=3D1 sysctl net.inet.ip.fw.dyn_ack_lifetime=3D60 # optional, speeds up testing ipfw add allow tcp from me to any setup keep-state ifconfig epair0 create ifconfig epair0a 10.0.0.101 up ifconfig epair0b 10.0.0.102 up while true; do ipfw -Da list; sleep 1; done # list dynamic rules, sh syntax Terminal 2: nc -l 10.0.0.101 12345 Terminal 3: nc -s 10.0.0.102 10.0.0.101 12345 With TCP debug enabled, I can see the following log entry: TCP: [10.0.0.102]:13140 to [10.0.0.101]:12345 tcpflags 0x10<ACK>; tcp_do_segment: Timestamp missing, segment silently dropped The timer of the dynamic rule expires and is removed. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-253476-227>