https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258732
zhh0000zhh <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|MSS |TCP_MAXSEG does not work --- Comment #1 from zhh0000zhh <[email protected]> --- https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144000 Now, TCP_MAXSEG needs to be called after connect to succeed, but this can only 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. -- You are receiving this mail because: You are the assignee for the bug.
