netdev - Re: IP_FRAG_TIME Default Too Large

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <7b77831a-68d5-a1fb-5481-b6516db5cf37@bluematt.me>
Date:   Mon, 29 Mar 2021 22:52:53 -0400
From:   Matt Corallo <linux-net@...tcorallo.com>
To:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: IP_FRAG_TIME Default Too Large



On 3/29/21 20:04, Matt Corallo wrote:
> This issue largely goes away when setting net.ipv4.ipfrag_time to 0/1.
Quick correction - the issue is reduced when set to 1 (as you might expect, you don't see as much loss if you wipe the 
fragment buffer every second) but if you set it to zero hosts randomly hang after some time (presumably when the buffer 
fills)? Either way, 0 should probably not be an allowed value for net.ipv4.ipfrag_time.

Matt