Date: Thu, 19 Jun 2025 12:22:28 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 287229] IP reassembly issue in FreeBSD 14.1 Message-ID: <bug-287229-7501-d1nD5ol4Dl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-287229-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-287229-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=3D287229 --- Comment #17 from Olivier Cochard <olivier@freebsd.org> --- (In reply to Lucas Aubard from comment #15) Using multiple VMs on a lab, then having to reduce the amount of available = RAM to a level not commonly found in today's real hardware is indeed a common pitfall that many have encountered before. However, I have reviewed what is currently available on the market: - Raspberry Pi current version (5) come with 2GB RAM; - The smallest AWS EC2 instances have 4GB RAM; - But on Google and Microsoft Azure we can have 1GB RAM instance; Thus, this reassembly issue is expected behavior in low-RAM scenarios, but = how critical is it? (This is a question for Lucas.) I mean, is it worth adding a warning message if net.inet.ip.maxfragbucketsi= ze is configured to 1, or do we need to find a more complex solution?" --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-287229-7501-d1nD5ol4Dl>