IPv6 Routing Issue
Lobcat
Enthusiast - Level 1

I'm having issue with IPv6 routing. I am not able to make it past the 3rd hop when running a trace route. Sometimes this route switches to another IP address.

Here's the trace routes to ipv6.google.com. I edited out my router's IP.

Tracing route to ipv6.l.google.com [2607:f8b0:4006:817::200e]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  2600:4040:e13a:xxxx::1
  2     4 ms     6 ms     6 ms  2600:4040:e130::1
  3    14 ms    15 ms     7 ms  2600:4000:1:222::e0
  4     *        *        *     Request timed out.

 

Tracing route to ipv6.l.google.com [2607:f8b0:4006:80f::200e]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  2600:4040:e13a:xxxx::1
  2     3 ms     6 ms    20 ms  2600:4040:e130::1
  3    10 ms     7 ms     7 ms  2600:4000:1:222::e2
  4     *        *        *     Request timed out.

 

I'm using a Mikrotik CCR2004-16G-2S+. I receive a /56 prefix. All my devices are assigned an IPv6 address from that prefix. All of the devices have the same routing issue, including the Mikrotik router. I've tried allowing all IPv6 traffic through the firewall but it still has the same issue.

Labels (1)
0 Likes
Reply
1 Solution
Cang_Household
Community Leader
Community Leader

Mikrotik router is compatible with the IPv6 Prefix Delegation used by Verizon Fios.

Mikrotik router should obtain a /56 address on the WAN and choose a /64 block for the LAN. Each LAN device should select an address from that /64 block.

It seems the traffic could go out but is not routable at the 3rd hop. This may suggest a core-routing issue in your region.

View solution in original post

1 Reply
Cang_Household
Community Leader
Community Leader

Mikrotik router is compatible with the IPv6 Prefix Delegation used by Verizon Fios.

Mikrotik router should obtain a /56 address on the WAN and choose a /64 block for the LAN. Each LAN device should select an address from that /64 block.

It seems the traffic could go out but is not routable at the 3rd hop. This may suggest a core-routing issue in your region.