Tickets - Airport + Gblon02 = no luck beyond first hop :: SixXS

Ticket ID: SIXXS #6379578
Ticket Status: Invalid

PoP: gblon02 - Goscomb Technologies (London)

Airport + Gblon02 = no luck beyond first hop

Shadow Hawkins on Wednesday, 01 February 2012 14:52:15

TR3-SIXXS My traffic is not being routed beyond the first hop to ipv6.google.com and other IPv6-only websites:

traceroute6 ipv6.google.com traceroute6 to ipv6.l.google.com (2a00:1450:400c:c01::68) from 2a01:348:6:590:c818:ba81:2f99:6a1f, 64 hops max, 12 byte packets 1 2a01:348:6:590:7aca:39ff:fefd:b795 11.655 ms 13.073 ms 4.523 ms 2 * * * 3 * * * 4 * * * 5 * * * 6 * * *

I am using a 6-to-4 tunnel through an Apple Airport device (latest firmware) that works perfectly well with HE Tunnelbroker. I'm aware that a number of people have reported issues on your forum, but have not been able to find a fix that works for me. Both Macs on the network are running OS X 10.7.2. For HE Tunnelbroker, I did not need to change firewall settings or my router's configuration. ------- Tunnel Id : T87182 PoP Name : gblon02 (uk.goscomb [AS39326]) SixXS IPv6 : 2a01:348:6:590::1/64 Your IPv6 : 2a01:348:6:590::2/64 SixXS IPv4 : 77.75.104.126 Tunnel Type : Static (Proto-41) Your IPv4 : 87.194.132.246 ------- I have followed your Airport guide to the letter and have had no such luck.

Airport + Gblon02 = no luck beyond first hop

Jeroen Massar SixXS Staff

on Wednesday, 01 February 2012 15:14:23

Your first hop is:

1 2a01:348:6:590:7aca:39ff:fefd:b795 11.655 ms 13.073 ms 4.523 ms

That is an address in the tunnel /64. In that prefix you only have <tunnel>::1 which is the PoP and <tunnel>::2 which is your side of the tunnel. You need a subnet routed toward your tunnel endpoint for the ability to give other hosts connectivity. As this obviously is a configuration issue on your side, please per-use the forums to resolve your problem. As I can ping your endpoint from a variety of places: 64 bytes from 2a01:348:6:590::2: icmp_seq=1 ttl=56 time=23.8 ms I would state that the tunnel itself works.

I am using a 6-to-4 tunnel

Please note the big naming issue here. 6to4 is RFC3056 and uses address space out of 2002::/16. If you are using 6to4 then it does not go through SixXS as we do not support 6to4. SixXS has proto-41 tunnels with optionally a heartbeat, or AYIYA tunnels. Please see FAQ: IPv6 Transition Mechanism / Tunneling Comparison for more details.

State change: invalid Locked

Jeroen Massar SixXS Staff

on Wednesday, 01 February 2012 15:14:28

The state of this ticket has been changed to invalid

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