SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #714221
Ticket Status: Resolved

PoP: bebru02 - BELNET, The Belgian Research and Education Network (Brussels)

Can't go further than my PoP
[be] Shadow Hawkins on Tuesday, 22 April 2008 13:10:00
Hello, I can't ping anything further than my PoP.
traceroute6 -n www.sixxs.net traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:6a8:200:19::2, 30 hops max, 16 byte packets 1 2001:6a8:200:19::1 15.044 ms 8.366 ms 8.614 ms 2 * * * 3 * * * 4 * * *
What additional information can I provide ? Thank you. Jehan Bruggeman
State change: confirmed Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 23 April 2008 11:14:31
Message is Locked
The state of this ticket has been changed to confirmed
Can't go further than my PoP
[be] Shadow Hawkins on Sunday, 27 April 2008 22:01:22
Hi, it's been a while now ;-) Do you have any additional information on this problem ? Do you know when it will be fixed ? Do I have an alternative ? Thank you very much !
Can't go further than my PoP
[be] Shadow Hawkins on Wednesday, 13 August 2008 15:57:56
Hi, I have the same problem (already more than 3 months). I will try to give enough information about the problem in order that someone can help us. I have an AICCU tunnel (T11633) with this configuration: PoP Name bebru02 PoP Location Brussels, Belgium Belgium PoP IPv4 193.190.198.32 Your IPv4 AYIYA, currently unknown IPv6 Prefix 2001:6a8:200:15::1/64 PoP IPv6 2001:6a8:200:15::1 Your IPv6 2001:6a8:200:15::2 When I perform an aiccu test, then I get this result: ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (87.67.218.xxx) 3 packets transmitted, 3 received, 0% packet loss, time 1998ms ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (193.190.198.32) 3 packets transmitted, 3 received, 0% packet loss, time 2003ms ####### [3/8] Traceroute to the PoP (193.190.198.32) over IPv4 ### This traceroute should reach the PoP ### In case this traceroute fails then you have no connectivity ### to the PoP and this is most probably the problem traceroute to 193.190.198.32 (193.190.198.32), 30 hops max, 52 byte packets 1 1.218-67-87.adsl-dyn.isp.belgacom.be (87.67.218.1) 8.364 ms 5.951 ms 6.090 ms 2 113.255-240-81.adsl-static.isp.belgacom.be (81.240.255.113) 11.104 ms 14.210 ms 13.847 ms 3 ge0-0.intlmar1.isp.belgacom.be (194.78.0.47) 10.481 ms ge1-0.intlstr1.isp.belgacom.be (194.78.0.146) 10.171 ms ge1-0.intlmar1.isp.belgacom.be (194.78.0.147) 9.983 ms 4 10ge.cr1.brueve.belnet.net (194.53.172.65) 10.128 ms 10.471 ms 10.475 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ###### [4/8] Checking if we can ping IPv6 localhost (::1) 3 packets transmitted, 3 received, 0% packet loss, time 1999ms ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6a8:200:15::2) 3 packets transmitted, 3 received, 0% packet loss, time 2000ms ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6a8:200:15::1) 3 packets transmitted, 3 received, 0% packet loss, time 2003ms ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net) ### This confirms that you can reach the central machine of SixXS ### If that one is reachable you should be able to reach most IPv6 destinations ### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection ### If your browser supports IPv6 and uses it of course. traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:6a8:200:15::2, 30 hops max, 24 byte packets 1 gw-22.bru-02.be.sixxs.net (2001:6a8:200:15::1) 13.595 ms 13.198 ms 13.237 ms 2 gw-22.bru-02.be.sixxs.net (2001:6a8:200:15::1) 3014.91 ms !H 3014.66 ms !H 3020.59 ms !H ###### [8/8] Traceroute6 to (www.kame.net) ### This confirms that you can reach a Japanese IPv6 destination ### If that one is reachable you should be able to reach most IPv6 destinations ### You should also check http://www.kame.net which should display ### a animated kame (turtle), of course only when your browser supports and uses IPv6 traceroute to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:6a8:200:15::2, 30 hops max, 24 byte packets 1 gw-22.bru-02.be.sixxs.net (2001:6a8:200:15::1) 14.728 ms 13.733 ms 13.568 ms 2 gw-22.bru-02.be.sixxs.net (2001:6a8:200:15::1) 3014.32 ms !H 3014.25 ms !H 3014.51 ms !H ###### This is my Debian Etch OS: Linux pluto 2.6.18-6-amd64 #1 SMP Mon Jun 16 22:30:01 UTC 2008 x86_64 GNU/Linux As for me, it seems like the PoP server is isolated from the IPv6 internet. Also this traceroute indicates that something is wrong at the Belnet PoP server: http://www.sixxs.net/tools/traceroute/?pop=noc-6&dpop=bebru02&dest=bebru02.sixxs.net Please is it possible to contact someone of Belnet to check the IPv6 configuration on their PoP server(s) as soon as possible. If you want more information from my side in order to identifying the problem, please ask me. Thanks in advance.
Can't go further than my PoP
[be] Shadow Hawkins on Thursday, 14 August 2008 14:56:09
I contacted the support team of Belnet and they have solved the problem. This ticket can be closed.
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 17 August 2008 00:36:43
Message is Locked
The state of this ticket has been changed to resolved

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

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