On Sat, 2021-03-27, Tauno Voipio wrote:
> On 26.3.2021 22:46 PM, Harold Johanssen wrote:
>> I have a Linux system connected to a gigabit Internet provider.
>> In this system I have the netdata application - in essence, a monitoring
>> application to assess the resources usage and general health of the
>> system.
>>
>> When I use any of the speed testing utilities available online,
>> netdata informs me about the following:
>>
>> ipv4.tcphandshake
>> 10s ipv4 tcp resets sent = 228.4 tcp resets/s
>>
>> Why is this happening? Can I tune my system to prevent this from
>> happening?
>
>
> A TCP reset is sent by a TCP peer when it is not happy with the
> incoming segment.
That doesn't ring quite true: if a TCP endpoint -- I mean the TCP
implementation in the networking stack -- doesn't like a segment it
doesn't have to do anything. It can just sit there, passive-
agressively, and wait for a good segment, or for either application to
give up. Maybe ACKing what it already has in the meantime.
I associate RST more with quick and dirty termination of a TCP
connection or connect attempt. An application can emit one by
calling shutdown(2), or simply by exiting.
> If the sender is your end of the test, the reset
> may be from your firewall not happy with the tester attempting to
> open a TCP connection.
Perhaps that's the most likely cause, yes (although I don't fully
understand the OP's description). Perhaps the firewall runs out of
some resource? Personally I don't know firewalls and NAT devices very
well. They seem to frequently break old TCP/IP conventions.
> A tcpdump / Wireshark trace could provide some light inti the details.