Date: Thu, 07 Oct 2021 17:43:23 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 258732] [tcp] TCP_MAXSEG does not work Message-ID: <bug-258732-7501-gOCEC8PTzf@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-258732-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-258732-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=3D258732 --- Comment #7 from Michael Tuexen <tuexen@freebsd.org> --- (In reply to zhh0000zhh from comment #6) But why do you need to synchronise two TCP sockets. TCP provides a byte str= eam service. So why do you bother what the MSS is? It is clear that the MSS option is only present in SYN and SYN ACK segments. But this has no relation to the question whether an application should have= an way to impact the announcement of the MSS to the peer. The argument that this is no a bug is that the code behaves as documented in the man page. After connection setup, you can query what the MSS used by the local endpoint is in send direction. You can even reduce them. Linux also allows you set limit the MSS used by the peer. FreeBSD doesn't a= llow this right now. So you are asking for this feature to be added. However, I don't understand why you need this feature. TCP is a byte stream protocol. So why do you want to limit the MSS used by your peer? --=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-7501-gOCEC8PTzf>