Packet loss Options

[Sir Robin (not s...]

Hi, I got notified today by one of the server admins, that I have a constant packet loss of about 30% for the 64 slot limited archer server. I tried to see the problem from my end but couldn't reproduce it.

Here is what I got:

CODE

$ mtr -c 100 -r -n 31.186.251.152
Start: Wed Mar  9 15:33:07 2016
  1.|-- 192.168.2.1                0.0%   100    1.2   1.6   0.8  13.5   1.7
  2.|-- 85.14.x.x                 0.0%   100    2.5   2.0   1.2  11.7   1.4
  3.|-- 85.14.21.105               0.0%   100    2.2   2.3   1.5  13.6   1.7
  4.|-- 85.14.2.135                0.0%   100    1.7  15.9   1.4 188.8  39.6
  5.|-- 46.33.95.225               0.0%   100    1.7   4.4   1.6  71.9   8.7
  6.|-- 141.136.110.173            0.0%   100   33.8  35.3  33.6  62.3   4.6
  7.|-- 77.67.73.166               0.0%   100   36.5  36.1  34.3  45.7   1.6
  8.|-- 95.172.67.72               0.0%   100   34.2  34.5  33.7  44.9   1.4
  9.|-- 31.186.251.152             0.0%   100   34.2  35.3  33.7  59.3   3.3

I also tried to google for packet loss problems, but basically all I found was not to use wifi, but it's not an option for me.

Any advise?

[Sir Robin (not s...]

Thank you all for the advice. I think the problem is, that I'm on linux and chiv client is probably a bit less developed for it. So what happens is, that initially I do see a big packet loss (and I have to wait a bit before I can join the game). But after that it's working fine.

But the value that's shown in the player list isn't updated very often. It stays the same for at least 10 minutes or more, so what you see is the value from my initial packet loss. On longer maps, like Belmez, I started with packet loss of around 70. I checked it during the game (when I got killed mostly), and it was the exact same number, which can't be true, right? I mean it stayed something like 70.5242 for more than 10 minutes. And near the end it suddenly fell to around 3. I think it's just a buggy stat for the linux client.

I'll try two more things tonight:
1. I'll connect with wired net and see how it goes
2. I'll try both wired and wifi on windows and check that as well