Hurricane Electric's IPv6 Tunnel Broker Forums

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: IPv6 routing problem. Who is responsible to fix this?  (Read 469 times)

luizcpj

  • Newbie
  • *
  • Posts: 1
    • View Profile
IPv6 routing problem. Who is responsible to fix this?
« on: July 25, 2016, 04:10:26 PM »

The website https://www.ripe.net/ is IPv6 enabled, but I can only access it by using IPv4 protocol. There seems to be a problem with IPv6 routing. Who is responsible to fix the problem?

From my native IPv6:
Quote
C:\Users\Junior>tracert www.ripe.net

Tracing route to www.ripe.net [2001:67c:2e8:22::c100:68b]
over a maximum of 30 hops:

  1     9 ms     8 ms     8 ms  2804:14c:aa::1
  2     8 ms     9 ms     8 ms  2804:14c:0:b912::1
  3    10 ms    10 ms    11 ms  2804:14c:0:1600:a4b7::1
  4    10 ms    11 ms    11 ms  2804:a8:2:b8::69
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7   125 ms   142 ms   127 ms  2610:18:110::49
  8   247 ms   245 ms   246 ms  2610:18::5b02
  9   238 ms   238 ms   239 ms  2610:18::5303
 10   251 ms   238 ms   236 ms  2610:18::5200
 11   256 ms   241 ms   250 ms  2610:18::5202
 12   236 ms   238 ms   252 ms  cir1.amsterdam2-nh.us.xo.net [2610:18::2044]
 13  Destination net unreachable.

Trace complete.
From Hurricane Electric Looking Glass:
Quote
core1.fmt1.he.net> traceroute ipv6 2001:67c:2e8:22::c100:68b numeric
 
Tracing the route to IPv6 node 2001:67c:2e8:22::c100:68b from 1 to 30 hops

  1    20 ms   17 ms    7 ms 2001:470:0:2f::2
  2    87 ms   86 ms   99 ms 2001:470:0:36d::2
  3   193 ms  141 ms  133 ms 2001:470:0:2cf::1
  4   146 ms  146 ms  151 ms 2001:470:0:2d0::2
  5   149 ms  180 ms  149 ms 2001:7f8:1::a501:2859:2
  6   !H      !H      !H     2001:7f8:1::a500:3333:1
# Entry cached for another 52 seconds.
Logged