Date: Sun, 26 Sep 2021 09:20:58 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 258732] TCP_MAXSEG does not work Message-ID: <bug-258732-227-P1ICITQYgj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-258732-227@https.bugs.freebsd.org/bugzilla/> References: <bug-258732-227@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=3D258732 zhh0000zhh <me@zhh0000zhh.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|MSS |TCP_MAXSEG does not work --- Comment #1 from zhh0000zhh <me@zhh0000zhh.com> --- https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D144000 Now, TCP_MAXSEG needs to be called after connect to succeed, but this can o= nly affect the local socket, not the remote MSS, because the MSS is already negotiated at connect, and by tcpdump catch the packet, the MSS value is not negotiate after TCP_MAXSEG is set at the local socket by setsockopt. --=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-258732-227-P1ICITQYgj>