Routing errors at ISP?

Installing and Using OpenWrt Network and Wireless Configuration
1 
Tracing route to CENSORED BY ME (Public IP)
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  CENSORED BY ME (Local LAN IP)
  2    25 ms    26 ms    27 ms  CENSORED BY ME (Public IP)
  3     *        *        *     Request timed out.
  4    23 ms    23 ms    25 ms  58.71.243.49
  5    24 ms    23 ms    24 ms  58.71.244.246
  6    28 ms    31 ms    31 ms  58.71.241.21
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9    26 ms    24 ms    24 ms  172.22.144.146
 10    26 ms    26 ms    28 ms  ae-9.r20.kslrml02.my.bb.gin.ntt.net [203.78.193.237]
 11    99 ms    99 ms    99 ms  ae-11.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.2.25]
 12   200 ms   199 ms   202 ms  ae-4.r23.snjsca04.us.bb.gin.ntt.net [129.250.5.78]
 13   199 ms   201 ms   200 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
 14   201 ms   202 ms   202 ms  ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
 15   207 ms   206 ms   207 ms  xe-0.kpn-eurorings-klm.snjsca04.us.bb.gin.ntt.net [128.241.219.58]
 16   362 ms   372 ms   362 ms  lags-s1-rou-1041.US.eurorings.net [134.222.49.18]
 17   364 ms   363 ms   363 ms  dlls-s1-rou-1041.US.eurorings.net [134.222.49.20]
 18   361 ms   371 ms   361 ms  miaf-s1-rou-1041.US.eurorings.net [134.222.48.21]
 19   365 ms   365 ms   364 ms  nyk-s1-rou-1021.US.eurorings.net [134.222.48.32]
 20   361 ms   360 ms   360 ms  rt2-rou-1022.NL.eurorings.net [134.222.48.0]
 21   361 ms   361 ms   361 ms  asd2-rou-1044.NL.eurorings.net [134.222.48.208]
 22   366 ms   364 ms   365 ms  asd2-rou-1022.NL.eurorings.net [134.222.48.224]
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25   369 ms   369 ms   369 ms  CENSORED BY ME (Public IP)
 26   368 ms   368 ms   369 ms  CENSORED BY ME (Public IP)

the above is the traceroute from here to my server in Europe.

3     *        *        *     Request timed out.
  4    23 ms    23 ms    25 ms  58.71.243.49
  5    24 ms    23 ms    24 ms  58.71.244.246
  6    28 ms    31 ms    31 ms  58.71.241.21
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9    26 ms    24 ms    24 ms  172.22.144.146

The 58.71.0.0 network is public I suppose, because my public IP which is accessible from the internet has the same range? 58.71.1.1 (just an example)

but 172.22.144.146 is reserved for LAN IP according to wikipedia..

how can I have a public IP, go through 6 IP's within the range of my public IP
and then a local area network IP.. and then going into the internet?

Doesn't that mean something in the routing tables of my ISP is wrong? Because my VPN here is slow as ****!!! and the connection also drops occasionally.

2

Not the first time I have seen that: some ISPs use private IP ranges for part of their networks.

2 Likes
3

Run your trace again at a few different times over a 24 hour period.......

Pay attention to the latency jump ( japan <-> us ) here;

99 ms 99 ms ae-11.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.2.25]
200 ms 199 ms 202 ms ae-4.r23.snjsca04.us.bb.gin.ntt.net [129.250.5.78]

and to the total number of hops....

-try udp vs tcp vpn and vice versa
-check the resource usage on your vpn endpoint
-start looking around for better isp?

1 Like
4

Nope, it is fine for an ISP to do that if they don't have enough IPv4 for all the infrastructure.
You are going from somewhere in Japan to US and then to Netherlands. There are certain hops that add a lot of lag to the trip times, for example 11->12 and 15->16

2 Likes
5

Nope, it's very common for infrastructure routers to silently drop packets that have timed out, rather than respond with the ICMP packet, especially on routers of their "internal" infrastructure.

2 Likes
6

Thank you all for your answers. So basically nothing wrong. Connection is just as it is.

I did try the routing through various times of the day. Also back from Netherlands to Malaysia (my ISP) and from NL back to Malaysia the routing is much more preferable. Goes directly from NL EURORINGS to Singapore (200ms) and from there to me.. total latency 220-230ms

also going from NL to Malaysia faster as from Malaysia to Netherlands.

So I got thinking, because my connection here locally to singapore I hit 100Mbps over the fiber internet, I might try using VyprVPN their singapore server...

to FORCE my ISP to route to Singapore.. and from Singapore they seem to have a good connection to Europe..

that way I would bypass the USA, my thought, that correct?

7

That can work, you can also hire yourself a VPS in Singapore and run your own VPN to it. Like Linode or Digital Ocean

1 Like
8

Meanwhile I tested some more about bypassing ISP routing.

I managed to get a VPN provider in Saudi Arabia. That way I bypass routing from Asia to Europe through the USA.

1 virtual router now builds up a connection to Saudi Arabia and thus using the fast cables from Singapore to Saudi Arabia.

Then cascaded I use a 2nd router through the first router to Europe which thus builds up it's connection to Europe through the VPN in Saudi Arabia.

SO I have a VPN inside a VPN and then inside that my actual VPN..

That way I force the connection the way around the world I want it.

Result: latency less then half compared to ISP
speed in the tunnel more than double as what I achieve with ISP routing.

2 Likes