Problems using TP-Link for Second Life

[Leda Sands]

I live on a boat and have two options to get on line, both wireless. One is the marina wifi, the other is my TP-Link M7350 mobile data dongle using an EE sim. The marina wifi is relatively slow and occasionally drops completely for time, which is a major annoyance, but when it's up it works ok with Second Life. The TP-Link is much faster, seems not to drop the connection, but often the viewer stalls loading textures and sometimes makes me crash when tp'ing. The firmware for the dongle is up to date. I've changed many of its settings (band, channel, mode) without success. On my phone the Wifi Analyser app shows a much stronger signal for the dongle than the marina wifi and the channels automatically selected are rated good.

I have just now tried tracert with the following result for the dongle:

Tracing route to sim10091.agni.lindenlab.com [216.82.48.157]
over a maximum of 30 hops:

 1     5 ms     3 ms     5 ms  192.168.0.1 (the dongle IP address)
  2     *        *        *     Request timed out.
  3    90 ms    34 ms    37 ms  10.248.27.149 (local IP address)
  4   107 ms    35 ms    36 ms  10.247.84.163 (local IP address)
  5     *        *        *     Request timed out.
  6    56 ms    36 ms    38 ms  10.247.84.113 (local IP address)
  7    91 ms    36 ms    48 ms  10.247.84.142 (local IP address)
  8   115 ms    39 ms    33 ms  87.237.20.152 (EE address)
  9    60 ms    23 ms    37 ms  87.237.20.73 (EE address)
 10    20 ms    38 ms    36 ms  lag-107.ear1.London1.Level3.net [212.187.166.145]
 11     *        *        *     Request timed out.
 12   283 ms   158 ms   155 ms  LINDEN-RESE.bar1.Phoenix1.Level3.net [4.53.104.14]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15  2698 ms   148 ms   146 ms  sim10091.agni.lindenlab.com [216.82.48.157]

Link to screenshot of stats https://prnt.sc/tr3rv6

There are many local stages and two timeouts in this route. Could that be the problem? Any suggestions what to do about it please?

 

Edited July 30, 2020 by Leda Sands
Forgot to put the link to the stats in

[Nick0678]

1 hour ago, Leda Sands said:

*        *        *     Request timed out.

Those hops simply don't allow ICMP packets. Your tracert seems to be fine , those 172ms are OK and your packet loss at 0.1% is good too.

Maybe when your viewer stalls the signal is breaking up..  Have a look at it when that happens and tell us.

[Leda Sands]

Thanks,

14 minutes ago, Nick0678 said:

Those hops simply don't allow ICMP packets. Your tracert seems to be fine , those 172ms are OK and your packet loss at 0.1% is good too.

Maybe when your viewer stalls the signal is breaking up..  Have a look at it when that happens and tell us.

Thanks, it's reassuring to know it's not the gaps in the routing.  I'll follow your advice and get back when I have any more information.

 

[Profaitchikenz Haiku]

It could be a form of throttling over mobile networks if they're allocating maximum chunks of data at a time, so when you visit a new region and have to cache in the new textures you are being forced to wait for the rush. If you have some regions you know you've visited on the other connection so the cached data for them is up to date, see if visiting those regions does not show up the issues.

I had similar experiences myself when I was using mifi in a caravan for a week, and ended up just sticking to the places I knew had everything in cache.

[Leda Sands]

Thanks for the replies. I'll just have to persist and try to pinpoint the issues.