Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
To get to the bottom of this, you need to understand what "packet loss" is :
now, when playing a game (csgo) your computer communicates with the game server via udp 27015 most likely.
The tcp connection constantly does send and receive packets, those packets are 100%. If of course some are missing, then you have a loss.
same if you send off a "ping google.com" command from the cli , it also tells you :
4 packets sent
4 packets received
100 %
most likely.
Now, if you claim to unplug your eth cable and replug it, which seemed to be the solution, then it most certainly looks like an issue on your end.
To troubleshoot :
https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Troubleshooting_Packet_Loss_Between_Devices
run : "ping -n 10 192.168.1.1" (or whatever the address of your gateway is)
This will ping the address provided 10 times and provide :
if you already see packet loss there, swap the cable.
If you do not have packet loss there ... tough
(I did it with the same ip as you too)
here are the results:
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Ping statistics for 192.168.1.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 6ms, Average = 3ms
now if i do it with my ip:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
so I don't see what is wrong with my connection.
I am about to do a router reset so hopefully it will be fine.
Thanks for the help :)
what do you mean??
128000 i believe.
Is this important?