Date: Thu, 07 Oct 2021 14:57:24 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 258732] [tcp] TCP_MAXSEG does not work Message-ID: <bug-258732-7501-cHp8ANfXOH@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 #6 from zhh0000zhh <me@zhh0000zhh.com> --- My Code: int mss; socklen_t mss_size; mss_size =3D sizeof(mss); getsockopt(fd, IPPROTO_TCP, TCP_MAXSEG, &mss, &mss_size); //mss <1460 setsockopt(fd2, IPPROTO_TCP, TCP_MAXSEG, &mss, mss_size); //need same mss for more ,you can search "TCP_MAXSEG site:github.com" in google. in rfc793 page 19, Section 3.1, "This field must only be sent in the initial connection request (i.e., in segments with the SYN control bit set)." https://datatracker.ietf.org/doc/html/rfc793#section-3.1 I think this is bug, not feature. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D144000 is not true. --=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-cHp8ANfXOH>