Date: Thu, 30 Mar 2017 18:21:09 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken Message-ID: <bug-173444-2472-2sr0xdcQqG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-173444-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-173444-2472@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=3D173444 Andrey V. Elsukov <ae@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ae@FreeBSD.org --- Comment #7 from Andrey V. Elsukov <ae@FreeBSD.org> --- (In reply to marka from comment #6) > (In reply to Hiren Panchasara from comment #5) > My test system died years ago but I believe that it still is a problem. >=20 > It should be trivial to check. >=20 > create a IPv6 TCP socket. > set IPV6_USE_MIN_MTU=3D1 using setsockopt > connect to a data sink > write 1400 bytes to the socket in a single operation >=20 > Examine the packets sent with tcpdump. There should be no fragmented > packets being sent as TCP is supposed to take into account MTU > information. According to RFC3542 this is what the kernel should do - do IP fragmentatio= n as application requested. https://tools.ietf.org/html/rfc3542#section-11.1 "If the packet is larger than the minimum MTU and this feature has been ena= bled the IP layer will fragment to the minimum MTU." --=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-173444-2472-2sr0xdcQqG>