I've tried various kernel versions. 4.15, 4.19.44, 5.0.0, the issue persists in all of those. Interestingly enough, it does not persist on my desktop linux which is kernel 5.2. I will try and find a way to update the server to 5.1 at least, but sadly debian is shipping only up to 5.0 with experiemntal repos. On Friday, August 2, 2019 2:44 PM, Florian Westphal <fw@xxxxxxxxx> wrote: > Nik nik_cro@xxxxxxxxxxxxxx wrote: > > > I am using kernel 4.19 > > This is the result: > > > > conntrack -L -s 127.0.0.1 > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D > > > > tcp 6 431940 ESTABLISHED src=3D127.0.0.1 dst=3D127.0.0.1 sport=3D53668= dport=3D9100 src=3D127.0.0.1 dst=3D127.0.0.1 sport=3D9100 dport=3D53668 [= ASSURED] mark=3D0 use=3D1 > > udp 17 0 src=3D127.0.0.1 dst=3D127.0.0.1 sport=3D60961 dport=3D53 src=3D= 127.0.0.1 dst=3D127.0.0.1 sport=3D53 dport=3D60961 [ASSURED] mark=3D0 us= e=3D1 > > tcp 6 431987 ESTABLISHED src=3D127.0.0.1 dst=3D127.0.0.1 sport=3D46510= dport=3D9014 src=3D127.0.0.1 dst=3D127.0.0.1 sport=3D9014 dport=3D46510 [= ASSURED] mark=3D0 use=3D1 > > conntrack v1.4.4 (conntrack-tools): 3 flow entries have been shown. > > Can you update to 4.19.17 or higher? > > 4.19 is known to have problems with connlimit.
