Tickets - Routing issue :: SixXS - IPv6 Deployment & Tunnel Broker

Ticket ID: SIXXS #12039469
Ticket Status: User

PoP: nlhaa01 - Leaseweb B.V. (Haarlem)

Routing issue

Shadow Hawkins on Friday, 25 July 2014 08:56:04

My tunnel (T150997) is up, and the rubnet behind it is routed correctly (could ping internal lan ip when firewall allowed it). But I cannot reach any sites via http, using ipv6 only. See below the tracepath6 & traceroute6 results.

tracepath6 ipv6.google.com
 1?: [LOCALHOST]                        0.110ms pmtu 1280
 1:  2001:1af8:fe00:8497:ee43:f6ff:fefc:e174               2.531ms 
 1:  2001:1af8:fe00:8497:ee43:f6ff:fefc:e174               2.263ms 
 2:  fe80::ee43:f6ff:fefc:e174                             2.365ms !P
     Resume: pmtu 1280

traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2a00:1450:4013:c00::8b) from 2001:1af8:fe00:8497:f400:ce1b:12a6:5aca, 30 hops max, 24 byte packets
 1  2001:1af8:fe00:8497:ee43:f6ff:fefc:e174 (2001:1af8:fe00:8497:ee43:f6ff:fefc:e174)  7.239 ms  2.148 ms  4.849 ms
 2  2001:1af8:fe00:8497:ee43:f6ff:fefc:e174 (2001:1af8:fe00:8497:ee43:f6ff:fefc:e174)  3009.22 ms !H  3043.3 ms !H  3010.46 ms !H

State change: user Locked

Jeroen Massar SixXS Staff

on Friday, 25 July 2014 08:58:28

The state of this ticket has been changed to user

Routing issue

Jeroen Massar SixXS Staff

on Friday, 25 July 2014 08:59:09

tracepath6 ipv6.google.com
 1?: [LOCALHOST]                        0.110ms pmtu 1280
 1:  2001:1af8:fe00:8497:ee43:f6ff:fefc:e174               2.531ms 
 1:  2001:1af8:fe00:8497:ee43:f6ff:fefc:e174               2.263ms 
 2:  fe80::ee43:f6ff:fefc:e174                             2.365ms !P
     Resume: pmtu 1280

That is all in your local network, you never reach the PoP. Note the !P typically indicates a fire-walling issue.

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