Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Double routing detour on Prague tserver? (answered)  (Read 578 times)

hradil

  • Newbie
  • *
  • Posts: 1
    • View Profile
Double routing detour on Prague tserver? (answered)
« on: January 01, 2017, 02:22:13 PM »

Hello
I'm using HE tunnel since 2012 and everything was fine. Yesterday, I tried to do something and the latency seemed unusually high. I did some pings and tracerts and have found this:
(My tunnel is on server in Prague and I live in Prague)

Tracert from me to the tunnel server over IPv4
Code: [Select]
Tracing route to tserv1.prg1.he.net [216.66.86.122]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.2.3
  2     2 ms     2 ms     2 ms  125.56.192.213.dymamic.bdtel.cz [213.192.56.125]
  3     3 ms     3 ms     3 ms  30.12.99.93.dymamic.bdtel.cz [93.99.12.30]
  4     7 ms     7 ms     4 ms  te0-6-0-8-s162.cz-pra-pop1-rb1.net.upc.cz [62.240.162.37]
  5     4 ms     4 ms     4 ms  cz-prg02a-ra2-vla110.net.upc.cz [84.116.222.109]
  6     4 ms     4 ms     4 ms  pl-waw05a-ri1-ae-5-0.aorta.net [84.116.135.234]
  7     8 ms    19 ms     3 ms  20ge1-3.core1.prg1.he.net [91.210.16.201]
  8    31 ms    30 ms    36 ms  100ge5-1.core1.waw1.he.net [184.105.80.146]
  9    39 ms    47 ms    48 ms  10ge3-1.core1.ber1.he.net [184.105.213.226]
 10    37 ms    46 ms    37 ms  tserv1.prg1.he.net [216.66.86.122]

Trace complete.
From the moment the packets reach HE network in Prague, they take a scenic route thru Warsaw and Berlin, before reaching tunnel server, again, in Prague.

Now, doing traceroute on site in Prague over IPv6:
Code: [Select]
Tracing route to nix.cz [2a02:38::1001]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  xxx:xx:xxxx::x
  2    44 ms    44 ms    43 ms  xxxxxxxx.tunnel.tserv27.prg1.ipv6.he.net [xxxx:xxx:xx:xxx::x]
  3    41 ms    48 ms    38 ms  ge2-20.core1.ber1.he.net [2001:470:0:220::1]
  4    48 ms    49 ms    48 ms  10ge3-3.core1.muc1.he.net [2001:470:0:310::1]
  5    58 ms    66 ms    55 ms  10ge1-7.core1.vie1.he.net [2001:470:0:2f9::1]
  6    60 ms    65 ms    61 ms  100ge14-2.core1.prg1.he.net [2001:470:0:1b4::1]
  7    61 ms    63 ms    61 ms  gw2-ipv6.nix.cz [2001:7f8:14::2]
  8    61 ms    61 ms    60 ms  info.nix.cz [2a02:38::1001]

Trace complete.
After doing the round in previous traceroute, and coming into IPv6 network in Prague, the packets take another detour over Berlin, Munich and Vien, before coming to Prague.

Assuming that I am right :-) is there any reason for this? I know that non-existing peering between two ISPs may take packets to different country, but this thing, twice, inside HE network?

I am thinking about creating tunnel in Frankfurt, just because it's 9 hops and 14ms, instead of 10 hops and ~40ms to my own city, but the Frankfurt tunnel server have almost twice as many active tunnels.

What should I do?
« Last Edit: January 08, 2017, 10:24:01 AM by hradil »
Logged

HECZ

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: Double routing detour?
« Reply #1 on: January 08, 2017, 01:41:18 AM »

Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1671
    • View Profile
    • Another IPv6 Blog...
Re: Double routing detour?
« Reply #2 on: January 08, 2017, 10:12:53 AM »

Prague tserv had a hardware failure. Instead of leaving tunnels down, we put them temporarily on some gear in Berlin. Once the Prague tserv hardware is replaced, the tunnels will be brought up there again.

NO ETA.
Logged