SixXS::Sunset 2017-06-06

Tunnels working fine, but BIT <-> Scarlet 'Administratively Prohibited'
[nl] Shadow Hawkins on Monday, 11 September 2006 20:51:42
Hi, I have two tunnels, one from BIT and one from Scarlet. Both work fine: dot$ ping6 irc.ipv6.xs4all.nl --- irc.ipv6.xs4all.nl ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 4.044/4.044/4.044/0.000 ms ns13$ ping6 irc.ipv6.xs4all.nl --- irc.ipv6.xs4all.nl ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 28.887/28.887/28.887/0.000 ms By those tests i am pretty confident that both hosts are able to reach other hosts on the internet by using the IPv6 protocol. Yet, when i ping6 box1 from box2: ns13$ ping6 dot.freshdot.net --- dot.freshdot.net ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms i just have loss, and even weirder, from box1 to box2: dot$ ping6 ns13.freshdot.net From ge-0-5-800.juniper-1.ipv6.network.scarlet.nl icmp_seq=1 Destination unreachable: Administratively prohibited --- ns13.freshdot.net ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms Any ideas what might be wrong?
Tunnels working fine, but BIT <-> Scarlet 'Administratively Prohibited'
[ch] Jeroen Massar SixXS Staff on Monday, 11 September 2006 23:12:29
You could have checked the: Tickets. Scarlet have IPv6 peering issues at AMS-IX it seems.

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

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker