Jump to content
Sign in to follow this  
Bold Baddingham

Packet loss

Recommended Posts

Hi for the last week i been suffering bad packet loss which is causing me problems in world i searched the wiki and dowloaded the winMTR and this is what it shows

 

|------------------------------------------------------------------------------------------||                                      WinMTR statistics                                   ||                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last ||------------------------------------------------|------|------|------|------|------|------||                             192.168.0.1 -    0 |  112 |  112 |    0 |    0 |    1 |    0 ||          lo98.gr-acc-bras-15.as9105.net -    0 |  112 |  112 |   15 |   16 |   20 |   16 ||                             10.72.4.229 -    0 |  114 |  114 |   16 |   18 |   24 |   17 ||                             10.72.9.223 -    0 |  113 |  113 |   16 |   20 |   81 |   16 ||       xe-8-3-0.bragg002.loh.as13285.net -    0 |  113 |  113 |   16 |   19 |   86 |   17 ||         xe-5-3-0.scr001.loh.as13285.net -    0 |  114 |  114 |   17 |   19 |   49 |   20 ||       Opal-ge-2.2.0.mpr1.lhr3.above.net -    0 |  114 |  114 |   17 |   20 |   63 |   20 ||         so-0-1-0.mpr2.dca2.us.above.net -    0 |  114 |  114 |   93 |  101 |  124 |  102 ||          xe-0-3-0.cr2.dca2.us.above.net -    0 |  114 |  114 |  100 |  105 |  165 |  101 ||         xe-0-0-0.mpr1.iad6.us.above.net -    2 |  106 |  104 |   96 |  100 |  149 |   98 ||        64.124.65.122.customer.above.net -    2 |  106 |  104 |   94 |  106 |  201 |  104 ||           sw-core0-78.dca.lindenlab.com -    1 |  112 |  111 |   97 |   98 |  112 |   98 ||             sim20550.agni.lindenlab.com -    5 |   98 |   94 |    0 |  101 |  108 |  106 ||________________________________________________|______|______|______|______|______|______|   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

I was using homewifi to connect and was told without doubt that would be the issue so i had a new telephone socket installed and hardwired via ethernet to my router and nothing has changed (above winMTR report was while wired not wifi and is same result as i was getting from wifi)

i only see packet loss when inworld or when doiing the winMTR to LL

it looks to be the last 4 hops that i get the packet loss so is this a  LL issue?

Share this post


Link to post
Share on other sites

Those generally occur from the delivery network.  It could be peering, Level (3) who provides SL's bandwidth or your local ISP.  It is more than likely not your PC or the Viewer.  One way to fix this would be to find a new route.  You can do this by resetting your modem and your router as DHCP can find a new route with a new IP address.

From the look of your trace route, it looks like it's happening over the last mile, aka your ISP.

Share this post


Link to post
Share on other sites

sorry when i say last for 4 i meant in the list 

 Host              -   %  | Sent | Recv 

192.168.0.1 -    0 |  112 |  112 

lo98.gr-acc-bras-15.as9105.net -    0 |  112 |  112 

10.72.4.229 -    0 |  114 |  114

10.72.9.223 -    0 |  113 |  113

xe-8-3-0.bragg002.loh.as13285.net -    0 |  113 |  113 

xe-5-3-0.scr001.loh.as13285.net -    0 |  114 |  114

Opal-ge-2.2.0.mpr1.lhr3.above.net -    0 |  114 |  114

so-0-1-0.mpr2.dca2.us.above.net -    0 |  114 |  114

 xe-0-3-0.cr2.dca2.us.above.net -    0 |  114 |  114

 xe-0-0-0.mpr1.iad6.us.above.net -    2 |  106 |  104

64.124.65.122.customer.above.net -    2 |  106 |  104

sw-core0-78.dca.lindenlab.com -    1 |  112 |  111

sim20550.agni.lindenlab.com -    5 |   98 |   94 

 

i dont get any loss untill it reaches us.above.net  as im in the uk would this still be my isp?

 

Share this post


Link to post
Share on other sites

The last two hops seem to be occuring in the LL server network.  I could mean it's a regional problem within SL proper.  File a ticket with LL and enclude your report with the ticket.  The other two hops are outside the LL network which is not LL's problem (though they may have a contract with the providers on that portion of the Internet........a ticket might alert LL to the problem so that, if they do have some control over that part of the Internet, they can get it resolved by whoever maintains those two servers/lines.

 

It's not your ISP and it's not a widespread problem (I wouldn't think since there are not a lot of complaints).  As it is right now, there's nothing you can do to work around the problem.  That 5% packet loss is bad.........way more than any IT would allow on a network.

Share this post


Link to post
Share on other sites

It amazes me how as soon as someone criticizes LL or offers proof there is a problem, up jumps an apologist with hundreds of entries on the forum to suggest that this really is the persons computer or ISP.  This kind of misinformation has been typical of LL for far too long and is a major source of the general player mistrust among those who have actually put time in SL that prevades this game.  LLs mantra seems to be if it is not a third party viewer, it is your computer or ISP, and the other day one of the apologists suggested that all would be well if the person complaining had an "adequate" computer with 16meg of memory like they had.  I had to laugh when I checked the recommended standards for running SL and found that LL still considered 1meg of memory optimun.  I realize there is a huge information gap between LL and the playing public but that is a bit beyond even what I would expect, though it may in fact reflect the conditions under which this code is tested and reflect why it fails so frequently under normal gaming conditions.

Share this post


Link to post
Share on other sites

Is it too much to ask, after two weeks of constant restarts, how much longer this process will go on and what if any advantages the playing public can expect to get from it?

Share this post


Link to post
Share on other sites

of course what's not amazing is that the moment someone misreads something (like the awful mess that the form made of the first post) some person with a miniscule amount of entries jumps in to accuse them of being an apologist (and by extension a liar). Then goes on to accuse the company that is supposedly being apologized for of some sort of conspiracy for using basic common sense business practices (like not running support for other peoples products, or targeting the most common and easy to check problems first). and of course there's the obligatory top it all if by citing some vague reference to an elitist nut job.

meanwhile back in reality, the trace shows evidence of problems at a backbone or near backbone gateway, possibly due to flooding, and anything past that in the trace can't be trusted since it's likely to use the same route. if the trace show the same things consistently over time the issue is probably at the first bad gateway (more likely) or between it and the last good one (very unlikely with gateways that high on the chain). if it only show at specific cyclic times it's very likely a flooding issue at peak usage. there is a small  but real chance depending on the connection type of intermittent hardware issues caused by physical effects such as weather (although again highly unlikely that high up the chain where everything should be fiber)

Share this post


Link to post
Share on other sites

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.0.1 0 104 104 0 0 2 0
lo98.gr-acc-bras-10.as9105.net 0 104 104 16 16 22 16
10.72.4.171 0 104 104 16 16 32 16
10.72.9.223 0 104 104 16 21 72 17
xe-10-3-0.bragg001.loh.as13285.net 0 104 104 16 20 84 17
xe-7-0-0.scr001.log.as13285.net 0 104 104 17 21 71 23
xe-7-0-0.edge4.London2.Level3.net 0 104 104 18 26 109 27
ae-32-54.ebr2.London2.Level3.net 0 104 104 26 37 61 36
ae-3-3.ebr1.London1.Level3.net 0 104 104 22 30 53 27
vlan101.ebr2.London1.Level3.net 0 104 104 18 22 38 27
ae-44-44.ebr1.NewYork1.Level3.net 0 104 104 94 97 110 98
ae-10-10.ebr2.Washington12.Level3.net 0 104 104 93 95 109 93
ae-2-52.edge1.Washington12.Level3.net 3 96 94 94 95 111 94
LINDEN-RESE.edge1.Washington12.Level3.net 0 104 104 96 102 135 98
sw-core0-81.dca.lindenlab.com 0 104 104 98 102 119 102
sim20336.agni.lindenlab.com 5 88 84 97 98 122 99

Its a constant problem ,never goes away last trace was done at 6am slt but as im a basic account member im not sure how to get the info to LL or get the problem fixed

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...