Changing tunnel server - Would there be any benefits?

[Quill]

My tunnel server is currently  Quill-1.tunnel.tserv6.fra1.ipv6.he.net, which I believe is Frankfurt. However, I currently reside in East Asia and physically, the nearest server would be Tokyo, followed by Hong kong. As such, would there be any significant benefit in changing to a physically closer server?

If I pursue this change, I assume I just delete the existing tunnel and create a new one? Also, Will this affect the certification?

Thank you for your time.

[kcochran]

As all your IPv6 traffic goes via the tserv, the distance between you and the tserv factors directly into the average latency you have.  Closer is better.

Tunnel status doesn't have any direct relationship with the certification process.  You can get Sage just as easily with native v6, a tunnel with another broker, etc.

[Quill]

Thanks for the reply. I changed the server to the Tokyo and the latency increased significantly, so I tried the Hong Kong server, the results were the same. I then tried Stockholm, as that appears to be the next nearest and the latency came down to a level similar to that when I was using Frankfurt:

Code Select Expand

C:\Windows\System32>ping -6 ipv6.google.com
Pinging ipv6.l.google.com [2a00:1450:4008:c00::68] with 32 bytes of data:
Reply from 2a00:1450:4008:c00::68: time=805ms
Reply from 2a00:1450:4008:c00::68: time=804ms
Reply from 2a00:1450:4008:c00::68: time=805ms
Reply from 2a00:1450:4008:c00::68: time=809ms

Ping statistics for 2a00:1450:4008:c00::68:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 804ms, Maximum = 809ms, Average = 805ms

C:\Windows\System32>tracert -6 ipv6.google.com

Tracing route to ipv6.l.google.com [2a00:1450:4008:c00::68]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  *** [2001:470:24:60::1]
  2   528 ms   527 ms   527 ms  2001:470:23:60::1
  3   526 ms   526 ms   526 ms  gige-g2-3.core1.tyo1.he.net [2001:470:0:118::1]
  4   527 ms   527 ms   527 ms  15169.tyo.equinix.com [2001:de8:5::1:5169:1]
  5   648 ms   528 ms   527 ms  2001:4860::1:0:298
  6   531 ms   530 ms   529 ms  2001:4860::1:0:75
  7   646 ms   646 ms   646 ms  2001:4860::1:0:610
  8   646 ms   646 ms   647 ms  2001:4860::8:0:252d
  9   688 ms   688 ms   688 ms  2001:4860::1:0:92e
10   713 ms   793 ms   713 ms  2001:4860::1:0:3be
11   780 ms   780 ms   780 ms  2001:4860::1:0:15f
12   788 ms   788 ms   845 ms  2001:4860::1:0:4b3
13   800 ms   800 ms   799 ms  2001:4860::1:0:fdd
14   805 ms   807 ms   805 ms  2001:4860::1:0:60d
15   807 ms   810 ms   808 ms  2001:4860:0:1::217
16   805 ms   804 ms   804 ms  2a00:1450:4008:c00::68

Trace complete.

C:\Windows\System32>ping -6 ipv6.google.com

Pinging ipv6.l.google.com [2a00:1450:4008:c00::63] with 32 bytes of data:
Reply from 2a00:1450:4008:c00::63: time=824ms
Reply from 2a00:1450:4008:c00::63: time=828ms
Reply from 2a00:1450:4008:c00::63: time=824ms
Reply from 2a00:1450:4008:c00::63: time=824ms

Ping statistics for 2a00:1450:4008:c00::63:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 824ms, Maximum = 828ms, Average = 825ms

C:\Windows\System32>tracert -6 ipv6.google.com

Tracing route to ipv6.l.google.com [2a00:1450:4008:c00::63]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  *** [2001:470:19:97d::1]
  2   512 ms   517 ms   511 ms  2001:470:18:97d::1
  3   509 ms   509 ms   509 ms  gige-g3-13.core1.hkg1.he.net [2001:470:0:ba::1]
  4   512 ms   511 ms   511 ms  google3-10G.hkix.net [2001:7fa:0:1::ca28:a10a]
  5   513 ms   512 ms   535 ms  2001:4860::1:0:1063
  6   563 ms   563 ms   563 ms  2001:4860::1:0:47
  7   673 ms   682 ms   673 ms  2001:4860::1:0:795
  8   674 ms   697 ms   673 ms  2001:4860::8:0:252d
  9   710 ms   709 ms   709 ms  2001:4860::1:0:92e
10   732 ms   732 ms   737 ms  2001:4860::1:0:3be
11   802 ms   800 ms   800 ms  2001:4860::1:0:15f
12   809 ms   807 ms   807 ms  2001:4860::1:0:4b3
13   829 ms   820 ms   822 ms  2001:4860::1:0:fdd
14   826 ms   830 ms   833 ms  2001:4860::1:0:60d
15   826 ms   827 ms   849 ms  2001:4860:0:1::217
16   830 ms   824 ms   825 ms  2a00:1450:4008:c00::63

Trace complete.


C:\Windows\System32>ping -6 ipv6.google.com

Pinging ipv6.l.google.com [2a00:1450:4008:c00::68] with 32 bytes of data:
Reply from 2a00:1450:4008:c00::68: time=293ms
Reply from 2a00:1450:4008:c00::68: time=291ms
Reply from 2a00:1450:4008:c00::68: time=292ms
Reply from 2a00:1450:4008:c00::68: time=292ms

Ping statistics for 2a00:1450:4008:c00::68:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 291ms, Maximum = 293ms, Average = 292ms

C:\Windows\System32>tracert -6 ipv6.google.com

Tracing route to ipv6.l.google.com [2a00:1450:4008:c00::68]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  *** [2001:470:28:***::1]
  2   252 ms   251 ms   252 ms  2001:470:27:***::1
  3   251 ms   250 ms   250 ms  gige-g2-20.core1.sto1.he.net [2001:470:0:11e::1]
  4   275 ms   274 ms   279 ms  10gigabitethernet3-3.core1.fra1.he.net [2001:470:0:110::1]
  5   276 ms   275 ms   275 ms  de-cix10.net.google.com [2001:7f8::3b41:0:1]
  6   277 ms   276 ms   277 ms  2001:4860::1:0:11
  7   287 ms   289 ms   287 ms  2001:4860::1:0:fdd
  8   341 ms   292 ms   292 ms  2001:4860::1:0:60d
  9   299 ms   292 ms   301 ms  2001:4860:0:1::215
10   292 ms   292 ms   291 ms  2a00:1450:4008:c00::68

Trace complete.

   

[sttun]

Well, I'm no expert put this looks strange longer rtt fom East asia to Hk and  Tokyo than to Sweeden, well japan may have issues (maybe fiber splicing is not the first priority after å triple catastrophe) and that again can make others usually on the Tokyo server to move tunnels to hk (can anyone fom HE pleace say if I'm missing the target here)?
It might also be a case ofpoor ipv4 peering between you and the tunnel servers, Wold you mind providibg ipv4 traceroutes from you to the 3 tunnel servers?

[Quill]

Not sure if this helps, but here are the results of the ipv4 traceroutes:

Code Select Expand

C:\Windows\System32>tracert 216.218.221.6 (Hong Kong)

Tracing route to tserv20.hkg1.ipv6.he.net [216.218.221.6]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Ozzy [192.168.1.1]
  2     1 ms     1 ms     1 ms  lo1.asr1000-l2tp-bras3.core.vladlink.net [109.126.1.132]
  3     1 ms     1 ms     1 ms  GE-7-48.c6509-100l.core.vladlink.net [109.126.0.213]
  4     1 ms     1 ms     1 ms  TenGigabitEthernet0-1-0.50.asr1002-border.core.vladlink.net [109.126.1.158]
  5     2 ms     1 ms     1 ms  vvk15.vvk.25.f05.transtelecom.net [217.150.54.10]
  6   215 ms   175 ms   179 ms  lnn11-ge500.501.transtelecom.net [195.66.224.212]
  7   168 ms   168 ms   168 ms  10gigabitethernet1-1.core1.lon1.he.net [195.66.224.21]
  8   253 ms   249 ms   249 ms  10gigabitethernet7-4.core1.nyc4.he.net [72.52.92.77]
  9   307 ms   307 ms   313 ms  10gigabitethernet5-3.core1.lax1.he.net [72.52.92.226]
10   429 ms   428 ms   428 ms  gige-g3-18.core1.hkg1.he.net [72.52.92.98]
11   429 ms   428 ms   429 ms  tserv20.hkg1.ipv6.he.net [216.218.221.6]

Trace complete.

C:\Windows\System32>tracert 74.82.46.6 (Tokyo)

Tracing route to tserv22.tyo1.ipv6.he.net [74.82.46.6]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Ozzy [192.168.1.1]
  2     1 ms     1 ms     1 ms  lo1.asr1000-l2tp-bras3.core.vladlink.net [109.126.1.132]
  3     1 ms     1 ms     1 ms  GE-7-48.c6509-100l.core.vladlink.net [109.126.0.213]
  4     1 ms     1 ms     1 ms  TenGigabitEthernet0-1-0.50.asr1002-border.core.vladlink.net [109.126.1.158]
  5     1 ms     1 ms     1 ms  vvk15.vvk.25.f05.transtelecom.net [217.150.54.10]
  6   178 ms   178 ms   230 ms  lnn11-ge500.501.transtelecom.net [195.66.224.212]
  7   180 ms   166 ms   174 ms  10gigabitethernet1-1.core1.lon1.he.net [195.66.224.21]
  8   246 ms   247 ms   249 ms  10gigabitethernet7-4.core1.nyc4.he.net [72.52.92.77]
  9   317 ms   324 ms   324 ms  10gigabitethernet3-1.core1.sjc2.he.net [72.52.92.25]
10   443 ms   443 ms   443 ms  10gigabitethernet1-2.core1.tyo1.he.net [72.52.92.238]
11   443 ms   443 ms   443 ms  tserv22.tyo1.ipv6.he.net [74.82.46.6]

Trace complete.


C:\Windows\System32>tracert 216.66.80.90 (Stockholm)

Tracing route to tserv24.sto1.ipv6.he.net [216.66.80.90]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Ozzy [192.168.1.1]
  2     1 ms     1 ms     1 ms  lo1.asr1000-l2tp-bras3.core.vladlink.net [109.126.1.132]
  3     1 ms     1 ms     1 ms  GE-7-48.c6509-100l.core.vladlink.net [109.126.0.213]
  4     1 ms     1 ms     1 ms  TenGigabitEthernet0-1-0.50.asr1002-border.core.vladlink.net [109.126.1.158]
  5     1 ms     1 ms     1 ms  vvk15.vvk.25.f05.transtelecom.net [217.150.54.10]
  6   226 ms   199 ms   199 ms  lnn11-ge500.501.transtelecom.net [195.66.224.212]
  7   199 ms   199 ms   200 ms  10gigabitethernet1-1.core1.lon1.he.net [195.66.224.21]
  8   206 ms   201 ms   201 ms  10gigabitethernet4-2.core1.fra1.he.net [184.105.213.146]
  9   218 ms   218 ms   218 ms  10gigabitethernet1-1.core1.sto1.he.net [72.52.92.234]
10   228 ms   228 ms   228 ms  tserv24.sto1.ipv6.he.net [216.66.80.90]

Trace complete.