Funnily enough, Russia’s packet loss issue resolved itself when I ported my 80GB SATA over to my 1TB SATA hard disk, but the ping is still an absolute nightmare. Here’s what the SC_Active_Srv_nettest.cmd script said:
Quote
*********************************************************
* Last servers used *
* [parsed from latest game.log] *
*********************************************************
17:06:41 2019-03-19 (Tue Mar 2019) Malay Peninsula Standard Time UTC+08:00
LoadBalancer [RU] 95.213.156.195
Shard [RU] 188.93.18.238
Chat [RU] 188.93.18.235
Dedicated [RU] 5.178.86.30
[INFO] check MSS with 1472 byte nofrag packets…FAILED
[WARN] your MSS is squeezed.
[INFO] check MSS with 1432 byte nofrags…OK
[FIX] ----[FIX]-----[FIX]-----[FIX]-----[FIX]-----[FIX]-----[FIX]-----[FIX]
use the following command to fix your networking issues
Netsh int ipv4 set sub “INTERFACE_NAME” mtu=1460 store=persistent
,where INTERFACE_NAME is one of the shown below.
usually its Local Area Connection - for cable
Wireless Network Connection - for Wi-Fi
for example (note the quotes):
Netsh int ipv4 set sub “Local Area Connection” mtu=1460 store=persistent
Use correct interface name from the rightmost column to fix MTU with netsh:
MTU MediaSenseState Bytes In Bytes Out Interface
------ --------------- --------- --------- -------------
4294967295 1 0 97895 Loopback Pseudo-Interface 1
1460 1 149085492 48759942 Local Area Connection
1460 5 0 0 Local Area Connection 2
[WARNING] WinMtr NOT Found. Will use windows utilities instead
**************************************************
* You are suggested to put winmtr.exe nearby
* please get it from http://winmtr.net
**************************************************
[INFO] Display back-resolved hops…
Tracing route to node07st-ru.star-conflict.com [5.178.86.30]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 42.189.255.254
2 179 ms 179 ms 206 ms 10.55.74.17
3 3 ms 5 ms 4 ms 10.55.68.0
4 183 ms 183 ms 183 ms 10.55.200.99
5 192 ms 192 ms 192 ms ams-ix.retn.net [80.249.209.216]
6 234 ms 222 ms 222 ms ae6-6.RT.SL.SPB.RU.retn.net [87.245.232.141]
7 291 ms 291 ms 291 ms GW-Selectel.retn.net [87.245.228.222]
8 293 ms 292 ms 292 ms 127.spb.net.selectel.ru [188.93.17.127]
9 293 ms 293 ms 293 ms node07st-ru.star-conflict.com [5.178.86.30]
Trace complete.
[INFO] Checking Nodes and Links packet losses…
Tracing route to 5.178.86.30 over a maximum of 30 hops
0 192.168.1.45
1 42.189.255.254
2 10.55.74.17
3 10.55.68.0
4 * 10.55.200.99
5 80.249.209.216
6 * 87.245.232.141
7 * 87.245.228.222
8 * 188.93.17.127
9 * 5.178.86.30
Computing statistics for 225 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.45
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 42.189.255.254
60/ 100 = 60% |
2 — 100/ 100 =100% 40/ 100 = 40% 10.55.74.17
0/ 100 = 0% |
3 — 100/ 100 =100% 40/ 100 = 40% 10.55.68.0
0/ 100 = 0% |
4 — 100/ 100 =100% 40/ 100 = 40% 10.55.200.99
0/ 100 = 0% |
5 — 100/ 100 =100% 40/ 100 = 40% 80.249.209.216
0/ 100 = 0% |
6 — 100/ 100 =100% 40/ 100 = 40% 87.245.232.141
0/ 100 = 0% |
7 — 100/ 100 =100% 40/ 100 = 40% 87.245.228.222
0/ 100 = 0% |
8 299ms 60/ 100 = 60% 0/ 100 = 0% 188.93.17.127
1/ 100 = 1% |
9 292ms 61/ 100 = 61% 0/ 100 = 0% 5.178.86.30
Trace complete.
last map: avgPing 296.1/0.6; avgPacketLoss 0.2/0.4%; avgSnapshotLoss 0.0/0.0%, MTU 1200
17:11:21 2019-03-19 (Tue Mar 2019) Malay Peninsula Standard Time UTC+08:00
My LAN connection speed is 100Mbit/s, which equals to about 12MB/s (Ookla Speedtest).
Specs:
Processor: Intel(R) Core™ it-3570 CPU @ 3.40GHz
Installed memory (RAM): 4.00 GB (3.89 GB usable)
OS: Windows 7 64-bit (Service Pack 1)
GPU: Intel(R) HD Graphics (1696 MB)