Since he has much faster upload speed it is beneficial for us when he hosts the game.
If I host the game, everything works fine, but it takes ages to download the map for him, as my upload is about 500 kbps.
If he hosts the map, I can connect and download the map at a much higher speed, but the "Server is not responding" bar will appear frequently and move a little bit and then disappear. Almost consistently after downloading about 5-6 megabytes of the map (now only about 10% of total), the bar will not disappear and will keep moving all the way over to the right, while the map is being downloaded at a decent and consistent speed. The connection to the server is not actually lost, but the game will be lead to think so, complain about it and force me to start over. This is of course useless, and just as frustrating as you can imagine.
I have tried to play with traffic shaping policies on my Edge router:
This is the shaper I have set up now:
set traffic-policy shaper shaper1 bandwidth 10mbit
set traffic-policy shaper shaper1 description FactorioFirst
set traffic-policy shaper shaper1 class 2 priority 1
set traffic-policy shaper shaper1 class 2 match port_34197_source ip source port 34197
set traffic-policy shaper shaper1 class 2 bandwidth 0%
set traffic-policy shaper shaper1 class 2 ceiling 100%
set traffic-policy shaper shaper1 class 3 priority 1
set traffic-policy shaper shaper1 class 3 match port_34197_destination ip destination port 34197
set traffic-policy shaper shaper1 class 3 bandwidth 0%
set traffic-policy shaper shaper1 class 3 ceiling 100%
set traffic-policy shaper shaper1 default priority 7
set traffic-policy shaper shaper1 default bandwidth 5%
set traffic-policy shaper shaper1 default ceiling 100%
I have tried all sorts of reduction of these numbers, but to no effect.
I'm not a network expert.
My idea is to prioritize the "pinging" of the server (the connection checking algorithm) over the downloading of the map. This has however not worked so far.
If my friend limits the uploading of the map, my downloading slows down. We tried this to the extreme, causing it to take 10 times longer for me to download the map, but it still fails after about the same time (aka less megabytes). So this does not work.
I notice that for some odd reason, I'm using all my upload speed on my Internet while downloading the map, which doesn't make sense to me. And it seems to be the transmission of the "keep-alive" or connection-check which fails, but that is just a good guess.
What port does Factorio use to send the map to the client? Does it use the same port for both the "Server is responding" check and sending the map?
Does anyone have a solution to this problem?
QoS exists on my router, but seems very tricky to set up for this purpose.
I've got a EdgeRouter X with firmware v1.10.7
I have searched around a bit, and there are a few people who have exactly the same problem, but I have not found any solution to it.
Here's an extract from my log:
616.556 Info ClientRouter.cpp:238: ConnectionAccepted
616.573 Info ClientMultiplayerManager.cpp:886: Disconnect notification for peer (5)
619.623 Info ClientMultiplayerManager.cpp:745: Received mapReadyForDownload
619.623 Downloading file C:\Users\Ingvar\AppData\Roaming\Factorio\temp\mp-download.zip (65628831 B, 130475 blocks)
619.647 Info ClientMultiplayerManager.cpp:573: MapTick(4294967295) changing state from(ConnectedWaitingForMap) to(ConnectedDownloadingMap)
619.647 Warning ClientMultiplayerManager.cpp:767: receivedScriptChecksums isn't empty when download starting.
640.924 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (24727) outside latency window [24744, 25344)
640.924 Info UnparsedNetworkMessage.cpp:102: Message data: 07 00 97 60 00 00
642.373 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (24746) outside latency window [24778, 25378)
642.373 Info UnparsedNetworkMessage.cpp:102: Message data: 07 00 aa 60 00 00
645.991 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (24795) outside latency window [24829, 25429)
645.991 Info UnparsedNetworkMessage.cpp:102: Message data: 07 00 db 60 00 00
650.091 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (24829) outside latency window [24846, 25446)
650.091 Info UnparsedNetworkMessage.cpp:102: Message data: 27 00 fd 60 00 00
675.840 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26012) outside latency window [25411, 26011)
675.840 Info UnparsedNetworkMessage.cpp:102: Message data: 27 00 9c 65 00 00
675.957 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26015) outside latency window [25411, 26011)
675.957 Info UnparsedNetworkMessage.cpp:102: Message data: 07 00 9f 65 00 00
676.174 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26021) outside latency window [25411, 26011)
676.174 Info UnparsedNetworkMessage.cpp:102: Message data: 27 01 a5 65 00 00 01 66 8b 05 75
676.340 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26027) outside latency window [25411, 26011)
676.340 Info UnparsedNetworkMessage.cpp:102: Message data: 27 00 ab 65 00 00
676.390 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26028) outside latency window [25411, 26011)
676.390 Info UnparsedNetworkMessage.cpp:102: Message data: 07 00 ac 65 00 00
676.440 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26030) outside latency window [25411, 26011)
676.440 Info UnparsedNetworkMessage.cpp:102: Message data: 27 00 ae 65 00 00
676.524 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26032) outside latency window [25411, 26011)
676.524 Info UnparsedNetworkMessage.cpp:102: Message data: 27 00 b0 65 00 00
676.541 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26033) outside latency window [25411, 26011)
676.541 Info UnparsedNetworkMessage.cpp:102: Message data: 27 00 b1 65 00 00
676.590 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26034) outside latency window [25411, 26011)
676.590 Info UnparsedNetworkMessage.cpp:102: Message data: 27 01 b2 65 00 00 01 b7 8b 05 75
676.639 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26036) outside latency window [25411, 26011)
676.639 Info UnparsedNetworkMessage.cpp:102: Message data: 07 00 b4 65 00 00
676.740 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26039) outside latency window [25411, 26011)
676.740 Info UnparsedNetworkMessage.cpp:102: Message data: 07 01 b7 65 00 00 02 78 8b 05 75 ab 8b 05 75
676.840 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26042) outside latency window [25411, 26011)
676.840 Info UnparsedNetworkMessage.cpp:102: Message data: 07 01 ba 65 00 00 02 9c 8b 05 75 ae 8b 05 75
676.907 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26043) outside latency window [25411, 26011)
676.907 Info UnparsedNetworkMessage.cpp:102: Message data: 27 00 bb 65 00 00
676.990 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26045) outside latency window [25411, 26011)
676.990 Info UnparsedNetworkMessage.cpp:102: Message data: 27 00 bd 65 00 00
677.024 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26046) outside latency window [25411, 26011)
677.024 Info UnparsedNetworkMessage.cpp:102: Message data: 27 01 be 65 00 00 02 b1 8b 05 75 c3 8b 05 75
677.039 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26047) outside latency window [25411, 26011)
677.039 Info UnparsedNetworkMessage.cpp:102: Message data: 07 00 bf 65 00 00
677.074 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({69.11.101.159:34197}): heartbeat sequence number (26048) outside latency window [25411, 26011)
677.074 Info UnparsedNetworkMessage.cpp:102: Message data: 27 01 c0 65 00 00 02 2d 8b 05 75 b4 8b 05 75
Is there a way to increase or adjust the latency window? The data likely eventually gets there...
Any other ideas or tips?
Thanks!
