Jump to content

a huge packet loss


watmes
 Share

You are about to reply to a thread that has been inactive for 2359 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

hello.

About a month ago I started getting a 100%+ packet loss. It is making sl very unplayable: I lose messages, I can't wear anything, and my avatar takes ages to load. I logged in sl and used the mtr program to detect the problem and this was the report (sl lag meter was showing around 50% packet loss during this testt:

$ mtr -r lindenlab.com
Start: Sun Apr 3 15:30:37 2016
HOST: dhcppc1 Loss% Snt Last Avg Best Wrst StDev
1.|-- gateway 0.0% 10 0.5 0.6 0.5 1.0 0.0
2.|-- (my nearest telephone centeral) 50.0% 10 535.6 495.1 97.6 1512. 595.6
3.|-- host-163.121.228.198.teda 80.0% 10 117.2 110.2 103.2 117.2 9.9
4.|-- host-163.121.228.197.teda 20.0% 10 44.6 68.6 6.5 160.2 49.4
5.|-- host-163.121.238.121.teda 40.0% 10 48.5 114.8 35.5 389.7 137.2
6.|-- 10.37.242.181 20.0% 10 32.8 91.9 15.3 337.4 109.4
7.|-- 10.37.242.169 10.0% 10 132.2 113.3 83.4 149.9 21.0
8.|-- sw-core1-85.phx.lindenlab 70.0% 10 181.4 2132. 181.4 5039. 2566.5
9.|-- 10.37.241.17 30.0% 10 22.7 43.7 12.2 63.0 20.3
10.|-- 213.242.116.45 20.0% 10 63.4 60.1 38.5 69.4 9.4
11.|-- ae-1-8.bar1.Phoenix1.Leve 50.0% 10 4.5 194.0 4.5 522.7 209.3
12.|-- 10.37.242.181 10.0% 10 188.1 366.8 8.7 1390. 456.8
13.|-- LINDEN-RESE.bar1.Phoenix1 30.0% 10 286.5 274.2 98.2 462.4 112.9
14.|-- sw-core1-85.phx.lindenlab 30.0% 10 279.2 239.6 79.3 279.2 71.9
15.|-- host-163.121.228.198.teda 0.0% 10 292.5 274.7 43.4 751.6 192.8
16.|-- sw-core1-85.phx.lindenlab 20.0% 10 7.9 90.6 2.5 270.0 102.0
17.|-- vip.lindenlab-phx.lindenl 20.0% 10 2.2 203.8 2.2 317.9 92.4

I called the isp to report this problem, and they sent me a technician. he changed the telephone wire from my house to the cabin, and supposdly fixed the "unstability" in my connection at the centeral. however, nothing have changed :X . the packet loss is still the same. so i called the isp and complained, but they told me they don't support online games problems. what can i do about this ? i was thinking of buying a new router, but i want to make sure i won't waste my money on a new one while the current is still functioning.

here are more mtr reports with google host name:

https://justpaste.it/swgx

 

Link to comment
Share on other sites

If you use wifi, stop that, and use wired, than test your router by contacting your machine directly to the modem. If it's ok with that, your router is most likely ready for replacement.

SL often doesn't like wifi. It can work but some regions/brands give problems. It's also recommended by LL to use wired.

 

If these things still aren't any help, your isp is the only one who can test your connection.

 

 

Link to comment
Share on other sites

That 0.0% packet loss at step 15 looks pretty suspicious to me... like maybe your ISP is rate-limiting your connection and an SL session uses enough bandwidth to trigger the throttle. Because they don't want to deal with games, can you maybe get similar measurements from a bunch of simlutaneous video streams from YouTube or Netflix or wherever?

Link to comment
Share on other sites

Hmm. Yeah, probably won't work. Especially the torrents should push the rate limits (more than normal video streaming, now that I think about it), so if mtr is consistently clean while torrenting, I really have no idea what's going on. I still kinda suspect your ISP is up to something naughty, but I'm not sure how to prove it.

(What you're seeing is obviously far from normal for SL use, so we need somebody with a bright idea about why it's so very broken for you. That "somebody" isn't me, sorry to admit.) 

Link to comment
Share on other sites

Thank you for trying :)

I got a new router, it fixed the huge packet loss in the first hop, but the average packet loss in sl now is around 50%. thats very playable compared to before. here is aonther report with teh new router

mtr -r lindenlab.com
Start: Tue Apr 5 22:26:17 2016
HOST: dhcppc1 Loss% Snt Last Avg Best Wrst StDev
1.|-- gateway 0.0% 10 0.4 0.5 0.4 0.8 0.0
2.|-- (my nearest centeral) 0.0% 10 26.0 35.7 24.6 125.4 31.5
3.|-- host-163.121.228.198.teda 10.0% 10 30.9 37.9 28.1 105.5 25.4
4.|-- host-163.121.228.197.teda 20.0% 10 28.4 35.5 27.6 61.4 12.6
5.|-- host-163.121.235.61.tedat 10.0% 10 30.0 32.9 29.2 41.8 3.9
6.|-- 10.37.242.185 90.0% 10 49.5 49.5 49.5 49.5 0.0
7.|-- 10.37.242.173 10.0% 10 27.7 39.4 27.7 82.9 19.0
8.|-- 10.37.241.25 30.0% 10 53.2 44.4 31.1 55.5 8.6
9.|-- 213.242.116.45 20.0% 10 63.8 63.3 61.9 65.2 0.8
10.|-- ae-1-8.bar1.Phoenix1.Leve 20.0% 10 206.2 211.8 203.6 257.0 18.3
11.|-- LINDEN-RESE.bar1.Phoenix1 0.0% 10 205.8 215.2 205.8 233.5 11.6
12.|-- sw-core1-85.phx.lindenlab 20.0% 10 209.1 240.9 207.1 457.2 87.5
13.|-- vip.lindenlab-phx.lindenl 10.0% 10 205.7 216.9 205.7 253.9 19.3

Link to comment
Share on other sites

I've had similar problems for the last 4 years when I moved to a new state.  After have repair people out about 6 times a year I finally had one tell me our neighborhood has old wiring and there is no plan to ever replace it.  Doing some research on line shows that many cable and phone company's are not going to even fix these problems as most are looking at going wireless in the next 10 years.   

here just one example

https://gigaom.com/2012/11/07/heres-atts-14b-plan-to-kill-its-copper-network-and-leave-rural-america-behind/

 

Link to comment
Share on other sites

some of my friends are telling me they are suffering in other online games. this problems seems to affect everyone using the same isp as me. i read somewhere that the isp is "blocking the online games ports". is that actually possible ?

Link to comment
Share on other sites


Nalates Urriah wrote:

The odd part is you are having packet loss all along the route. I would check that is really the case. There should be no loss within the SL network. If SL was dropping packets we would all be seeing it.

I'm no expert (and you may be just such an expert) but mtr reports seem tricky to interpret because they measure loss of packets with intentionally truncated Time-To-Live. Based on that linked guide, I'm puzzled by intermediate hops showing zero lost packets adjacent multiple hops with high packet loss hops, and not interpreting the lost packets nearer LL's network to be something the broader base of users would experience. But I could be wrong.

As to whether the ISP can block ports: technically it's trivial to block or delay transmission to specific ports; they can even use something called "deep packet inspection" to classify traffic on the same port for different service quality packet-by-packet in real time, but that may or may not be legal, depending on the jurisdiction. Usually, though, there's some reference to "network management" that lets ISPs get away with anything, at least until challenged in court.

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 2359 days.

Please take a moment to consider if this thread is worth bumping.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...