TCP IDLE TIMEOUT
10 months ago
Hey,
ich habe seit neuem Probleme mit der Verbindung in PUBG. Vielleicht kennt jemand den Fehler. Ich bin nach dem Match gefangen in dem grauen Smokescreen (den Bug gibts schon ewig). Ich bin seit über 2 Wochen im Austausch mit den Entwicklern. Leider hat jeder Lösungsansatz nicht zum Ziel geführt. Von einfachen Sachen wie Treibern, bis zu CMD Sachen... Dann habe ich das Spiel auf 2 weiteren Geräten in meinem Netzwerk getestet. Der Bug tritt auch da auf. Nach sehr langer Suche auf Google, Reddit, Steam etc hab ich nun den Fehler gefunden. Scheinbar liegt es an dem Folgendem.
[PUBG BATTLEGROUNDS]
Finally, after a 3 month research I found the root cause for smoke screen loading issue when Exit to lobby is clicked after a match. Here are the details: -
Tslgame.exe establishes/handshake a TCP connection to akamai endpoint(e9466.d.akamaiedge.net) in the beginning.
When user plays the game, this connection is IDLE until match ends, and when user clicks on Exit to Lobby/Leave Match then again Tslgame.exe tries to connect to same endpoint with tcp payload of 355 bytes.
But many ISPs has TCP IDLE TIMEOUT set to 4 mins on their router/firewall. Hence the ISP router/firewall deletes/kills the IDLE connection if there is no conversation between client and server. (as each match is being played more than 4 mins, and Tslgame.exe doesn't send any packets within the match time hence ISP firewall kills the connection after 4 mins of idle time)
When the match is ended, and you click on exit to lobby the client tries to reconnect to the endpoint multiple times with the 1st handshake and fails as there is no connection to the server at this point due to ISP idle timeout, (this is where you see the black smoke screen) and in the end (after 3 retires) establishes a new connection/handshake (SYN/ACK).
Hence if a user plays a match for more than 4 mins, they see this issue after match ends.
SOLUTION #1 - Raise a ticket with your ISP to increase the TCP IDLE TIMEOUT to at least 1 hr (section 5 of RFC 5382, https://www.rfc-editor.org/rfc/rfc5382#section-5 it should be set to 2 hours 4 minutes/7204 seconds).
SOLUTION #2 - To resolve the issue, the application (Tslgame.exe) needs to send some occasional byte of data/empty packets to e9466.d.akamaiedge.net every now and then to be disregarded by the peer. [FIX NEEDS TO BE DONE BY PUBG DEV TEAM]
I have used wireshark to capture and research all the packets.
How will you test your ISP idle timeout value: -
Download and install postman(https://www.postman.com/downloads/)
File > New > WebSocket
Enter URL - wss://echo.websocket.in
Message Section, enter "Hello World"
Click on "Connect"
And after 4 mins click on "Send" button and see if you get response from server.(Next time click on send after an incremental value(5 min, 6 min, 7 min etc..) if you get a response)
If your ISP has the 4 mins timeout set, your connection will disconnect.
Nun meine Frage könnte die Telekom das bei mir hochstellen? Wenn mehr Infos benötigt werden, werde ich euch die natürlich zur Verfügung stellen! Und noch eine Info, sobald ich einen VPN von Nordvpn über zb Berlin nehme lädt es ohne Probleme! Vielleicht gibs ein Problem mit der Route die meine Daten nehmen?
DAAAAANKE
622
0
19
This could help you too
5 years ago
910
0
3
3 years ago
248
0
2
12 years ago
25775
0
128
You might also be interested in
Request purchasing advice
Fill out our online contact form quickly and easily so that we can advise you personally in a timely manner.
View offers
Informieren Sie sich über unsere aktuellen Internet-Angebote.