On 3/29/21 20:04, Matt Corallo wrote:
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.This issue largely goes away when setting net.ipv4.ipfrag_time to 0/1.
Matt
