Tickets - PoP not routing traffic :: SixXS - IPv6 Deployment & Tunnel Broker

Ticket ID: SIXXS #15557685
Ticket Status: User

PoP: dkcph01 - Availo (Copenhagen)

PoP not routing traffic

Carmen Sandiego on Wednesday, 07 September 2016 09:29:12

I can ping my tunnel gateway at 2001:16d8:dd00:1a5::1 without problem, from both firewall and client computer. But I cannot ping ipv6.google.com (by IP6 or hostname), or any other ipv6 host i know of. I conclude that my subnet, R199466, is not being routed properly.

ping -6 ipv6.google.com -t

Pinging ipv6.l.google.com [2a00:1450:4005:803::200e] with 32 bytes of data:
Destination net unreachable.
Destination net unreachable.

Ping statistics for 2a00:1450:4005:803::200e:
    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),

tracert -6 ipv6.google.com

Tracing route to ipv6.l.google.com [2a00:1450:4005:803::200e]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  2001:16d8:dd00:81a5:b::1
  2  Destination net unreachable.

Trace complete.

ping 2001:16d8:dd00:1a5::1

Pinging 2001:16d8:dd00:1a5::1 with 32 bytes of data:
Reply from 2001:16d8:dd00:1a5::1: time=31ms
Reply from 2001:16d8:dd00:1a5::1: time=30ms

Ping statistics for 2001:16d8:dd00:1a5::1:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 31ms, Average = 30ms

State change: user Locked

Jeroen Massar SixXS Staff

on Wednesday, 07 September 2016 09:32:58

The state of this ticket has been changed to user

PoP not routing traffic

Jeroen Massar SixXS Staff

on Wednesday, 07 September 2016 09:33:45

Please actually read the big yellow boxes while posting and provide the information requested. Also, you did read our news page articles and have Called Your ISP for Native IPv6 by now we hope?

PoP not routing traffic

Carmen Sandiego on Wednesday, 07 September 2016 11:02:09

Yes. I have read the yellow boxes. I fail to see what relevant information I have excluded? Apart from my issue apparently being similar #10039206, although that ticket is resolved, and is regarding the outside of the PoP - and not the PoPs routing. Here is another traceroute from another host:

traceroute6 ipv6.google.com
traceroute to ipv6.google.com (2a00:1450:4005:80a::200e), 30 hops max, 80 byte packets
 1  2001:16d8:dd00:81a5:a::1 (2001:16d8:dd00:81a5:a::1)  0.413 ms  0.573 ms  0.641 ms
 2  2001:16d8:dd00:81a5:a::1 (2001:16d8:dd00:81a5:a::1)  0.686 ms !N  0.738 ms !N  0.784 ms !N

I am using PfSense, and the tunnel has been working without problems thus far. A GIF tunnel is being used. In case you are missing the routing table, here is the relevant part:

DestinationGatewayFlagsUseMtuNetifExpire
2001:16d8:dd00:1a5::1link#11UH209741280gif0
2001:16d8:dd00:1a5::2link#11UHS016384lo0
2001:16d8:dd00:81a5:a::/80link#3U50541500em2
2001:16d8:dd00:81a5:a::1link#3UHS016384lo0
2001:16d8:dd00:81a5:b::/80link#1U11481500em0
2001:16d8:dd00:81a5:b::1link#1UHS016384lo0

I have contacted my ISP serveral times in the past regarding ipv6 - and they are due for another reminder. If you feel confident there is something wrong with my setup, please reply "It's your own fault", and I will get on with rebuilding my config :)

PoP not routing traffic

Jeroen Massar SixXS Staff

on Wednesday, 07 September 2016 11:10:45

I fail to see what relevant information I have excluded?

All the steps that are listed.

2 2001:16d8:dd00:81a5:a::1 (2001:16d8:dd00:81a5:a::1) 0.686 ms !N 0.738 ms !N 0.784 ms !N

That is an address in your network. Nothing we can do about.

In case you are missing the routing table, here is the relevant part:

[..]

Ever thought of a default route?

If you feel confident there is something wrong with my setup, please reply "It's your own fault", and I will get on with rebuilding my config :)

If you would read through the "Reporting Problems Checklist" you would have found the problem already...

Please note Posting is only allowed when you are logged in.