[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] ACK missing after SYN, strange high Ack Num

From: Indan Zupancic
Subject: Re: [lwip-users] ACK missing after SYN, strange high Ack Num
Date: Thu, 02 Jun 2022 12:52:43 +0200
User-agent: Roundcube Webmail/1.3.16

On 2022-06-02 12:16, Jochen Strohbeck wrote:
Do you know which timeout value is responsible for keeping recently
used port numbers?

Mostly TCP_MSL. But even better would be to let the client
close the connection first.

Reducing TCP_MSL is needed if you run out of sockets or memory
and want to cleanup things quicker.

For my testing I'm using Python requests which is doing up to 3 retries,
which may cause an probably unwanted long delay in the response if
retries are done in case the above port reuse problem occurs.

The port re-use should not add much extra delay, the RST is sent
immediately. Only if you ran out of sockets because they are all
hogged for TIME WAIT will you get extra delay.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]