Tracert / LL Server DC Issues

[johnnychipello]

Does this look okay?...or " normal"..and could this cause issues, freezing up of the viewers or disconnecting from server issues?

This is the tracert from Ll server 31.557694

1    <1 ms    <1 ms    <1 ms  ...*...1.1 (left blank intentional)
  2    19 ms    21 ms   183 ms  cpe-45-37-192-1.nc.res.rr.com [45.37.192.1]
  3    18 ms    14 ms    22 ms  cpe-174-111-106-050.triad.res.rr.com [174.111.106.50]
  4    30 ms    13 ms     9 ms  cpe-024-025-062-150.ec.res.rr.com [24.25.62.150]
  5    20 ms    22 ms    23 ms  be31.chrcnctr01r.southeast.rr.com [24.93.64.186]
  6    28 ms    22 ms    22 ms  66.109.7.196
  7    28 ms    29 ms    19 ms  66.109.9.103
  8    31 ms    30 ms    23 ms  ae-10.edge4.Atlanta2.Level3.net [4.68.37.73]
  9     *      119 ms     *     ae-1-3116.ear4.Frankfurt1.Level3.net [4.69.210.62]
 10   114 ms   123 ms   112 ms  195.122.183.218
 11   186 ms   182 ms   175 ms  95.167.95.199
 12   179 ms   184 ms   183 ms  95.167.125.17
 13   180 ms   177 ms   174 ms  h83-174-195-9.static.bashtel.ru [83.174.195.9]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

 

This is the trace at 4 hop limit

 

 

[Nova Convair]

Servers are not obliged to answer ping or trace requests and as you see - some don't answer.

So what you see is normal.

[johnnychipello]

So in other words, this would not be the reason for any LL server disconnection issues?

[Fritigern Gothly]

8 hours ago, johnnychipello said:

  2    19 ms    21 ms   183 ms  cpe-45-37-192-1.nc.res.rr.com [45.37.192.1]
  8    31 ms    30 ms    23 ms  ae-10.edge4.Atlanta2.Level3.net [4.68.37.73]
  9     *      119 ms     *     ae-1-3116.ear4.Frankfurt1.Level3.net [4.69.210.62]
 13   180 ms   177 ms   174 ms  h83-174-195-9.static.bashtel.ru [83.174.195.9]

Okay, I am puzzled by this trace (and I have seen many of them)
You start in North Carolina (hop 2) which is fine, then you hit Atlanta (hop 8 ) because that is part of the Internet backbone. But then hop 9 (also the backbone) sends you to Frankfurt in Germany, and after 2 unidentified hops the trace suddenly leads you to Russia after which the nodes stop responding to the pings.

Here's what I don't get, the Amazon CDN servers are (if I recall correctly) located in Atlanta and that is were the trace should have ended.

What was the IP or URL that you tried to trace? I would like to see if I get similar results.

[Ardy Lay]

VPN?  (Very Puzzling Network)

[Ardy Lay]

9 hours ago, johnnychipello said:

This is the tracert from Ll server 31.557694

To what IPv4 address or hostname were your tracing?  You do not say so this is not really something we can help you evaluate.  

If what you intend to say is you ran "tracert 31.557694" then you did indeed run off into the weeds as 31.557694 transforms into 31.8.130.126.

C:\Users\ardyl>tracert 31.557694

Tracing route to 31.8.130.126 over a maximum of 30 hops

 

Edited April 28, 2021 by Ardy Lay

[Ardy Lay]

9 hours ago, johnnychipello said:

Does this look okay?...or " normal"..and could this cause issues, freezing up of the viewers or disconnecting from server issues?

This is the tracert from Ll server 31.557694

1    <1 ms    <1 ms    <1 ms  ...*...1.1 (left blank intentional)
  2    19 ms    21 ms   183 ms  cpe-45-37-192-1.nc.res.rr.com [45.37.192.1]
  3    18 ms    14 ms    22 ms  cpe-174-111-106-050.triad.res.rr.com [174.111.106.50]
  4    30 ms    13 ms     9 ms  cpe-024-025-062-150.ec.res.rr.com [24.25.62.150]
  5    20 ms    22 ms    23 ms  be31.chrcnctr01r.southeast.rr.com [24.93.64.186]
  6    28 ms    22 ms    22 ms  66.109.7.196
  7    28 ms    29 ms    19 ms  66.109.9.103
  8    31 ms    30 ms    23 ms  ae-10.edge4.Atlanta2.Level3.net [4.68.37.73]
  9     *      119 ms     *     ae-1-3116.ear4.Frankfurt1.Level3.net [4.69.210.62]
 10   114 ms   123 ms   112 ms  195.122.183.218
 11   186 ms   182 ms   175 ms  95.167.95.199
 12   179 ms   184 ms   183 ms  95.167.125.17
 13   180 ms   177 ms   174 ms  h83-174-195-9.static.bashtel.ru [83.174.195.9]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

 

This is the trace at 4 hop limit

 

 

[animats]

1 hour ago, Ardy Lay said:

To what IPv4 address or hostname were your tracing?  You do not say so this is not really something we can help you evaluate.  

What you're showing looks like a traceroute from some home on Road Runner to some server in Russia, with zero Linden Lab or Amazon involvement.

[Ardy Lay]

1 minute ago, animats said:

What you're showing looks like a traceroute from some home on Road Runner to some server in Russia, with zero Linden Lab or Amazon involvement.

31.557694 is equal to 31.8.130.126 so that is exactly what they did.

[Fritigern Gothly]

2 hours ago, Ardy Lay said:

31.557694 is equal to 31.8.130.126 so that is exactly what they did.

Why not 31.81.130.126?

[Logan Elf]

31.557694 to me looks like the last part of the SLS server version, and not the server's IP address. Methinks they've been tracing the wrong thing.

ETA: most regions are running server version 2021-03-31.557694

Edited April 28, 2021 by LoganPryor
add server version

[Ardy Lay]

6 hours ago, Fritigern Gothly said:

Why not 31.81.130.126?

Because that is not how IPv4 address representation works.  

- or -

Because 31.5341822 is not currently a Second Life Server version.

[Fritigern Gothly]

5 hours ago, Ardy Lay said:

Because that is not how IPv4 address representation works.  

Actually, it would be a perfectly valid IPv4 address.

[Ardy Lay]

1 minute ago, Fritigern Gothly said:

Actually, it would be a perfectly valid IPv4 address.

Yes, it would be a valid IPv4 address.  It would not be equal to 31.557694, because that is not how the math works when calculating addresses.  31 is the "network", 557694 is "the rest" of the address.  The address you posted would work out to be 31.5341822 in network.rest representation, which is neither the IPv4 host the original poster traced to nor is it a current Second Live Simulator version.