Repository navigation
TCP FIN packets are delayed #6736
DmitryPan
started this conversation in
Performance
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
On short-term requests (e.g. WHOIS) the TCP FIN packet arrives with a 2-second delay. This happens regardless of the inbound (socks, tun or tunnel) and the VLESS transport (TCP or XHTTP). This can be observed using Wireshark or the following command.
time curl -x "socks5://127.0.0.1:10800" telnet://whois.eu:43 <<< ikea.euPlease note that the data is received instantly, but the curl exits 2 seconds later.
On the client side you can set policy.levels.0.uplinkOnly=0 and on server side policy.levels.0.downlinkOnly=0 and this fixes the problem - the TCP FIN packet will be received instantly after the data (TCP PSH). If we set uplinkOnly=0 only on client side, the delay will be reduced to 1 second. Is there a workaround on client side to reduce the delay if there we have no access to server to set downlinkOnly=0?
All reactions