Date: Sun, 24 Jan 2021 15:43:44 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 250499] [tcp] Should we reject the packet with timestamp if no timestamp in SYN and SYN_ACK? Message-ID: <bug-250499-7501-glE78zAkFL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-250499-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-250499-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250499 --- Comment #6 from Michael Tuexen <tuexen@freebsd.org> --- (In reply to Roman Bogorodskiy from comment #5) Hi Roman, I introduced a regression, which was fixed in https://cgit.FreeBSD.org/src/commit/?id=3Dcc3c34859eab1b317d0f38731355b53f7= d978c97 and MFCed to stable/12 in https://cgit.FreeBSD.org/src/commit/?id=3Dd05d908d6d3c85479c84c707f93114843= 9ae826b. This was affecting the handling of received TCP RST segments. Does this fix your issue? In bug #252449 it was reported that there are broken TCP stacks, which negotiate TCP timestamp support but then don't behave as required. To deal with such broken implementations I added a sysctl variable in https://cgit.FreeBSD.org/src/commit/?id=3Dd2b3ceddccac60b563f642898e3a31464= 7666a10 , which was MFCed to stable/12 in https://cgit.FreeBSD.org/src/commit/?id=3De82353f84c58da9a5c38bd471a09936c1= 6a5b6ea. In this case you can set the sysctl variable net.inet.tcp.tolerate_missing_= ts to 1. I would be interested to now which stack is broken and it would be gr= eat if you could provide a .pcap file of the failing TCP connection. Does this fix your issue? --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250499-7501-glE78zAkFL>