|
Can't connect to the noc.sixxs.net
![[de]](/s/countries/de.gif) Shadow Hawkins on Thursday, 27 December 2012 16:44:12
Hi, I get my Tunnel today.
I use Ubuntu Linux 12.4/ kernel version 3.2.0.
the aiccu setup was successful, but I have trouble connecting to ipv6 websites like ipv6.google.com ....
it has to be said that my computer is also not ping-able from outside:
traceroute to 2001:4dd0:ff00:1124::2 (2001:4dd0:ff00:1124::2), 30 hops max, 40 byte packets
1 2001:2e8:635:0:2:2:0:2 (2001:2e8:635:0:2:2:0:2) 0.112 ms 0.022 ms 0.014 ms
2 2001:2e8:22:204::2 (2001:2e8:22:204::2) 0.479 ms 0.605 ms 0.725 ms
3 2001:2e8:20::22:11 (2001:2e8:20::22:11) 9.430 ms 9.536 ms 9.614 ms
4 gigabitethernet2-8.core1.tyo1.he.net (2001:7fa:7:1::6939:1) 8.101 ms 8.155 ms 8.206 ms
5 10gigabitethernet3-3.core1.sjc2.he.net (2001:470:0:119::1) 132.328 ms 132.404 ms 132.426 ms
6 10gigabitethernet3-3.core1.den1.he.net (2001:470:0:1b4::2) 160.044 ms 160.285 ms 153.987 ms
7 10gigabitethernet8-2.core1.chi1.he.net (2001:470:0:1af::1) 177.522 ms 177.034 ms 186.028 ms
8 10gigabitethernet7-2.core1.nyc4.he.net (2001:470:0:1c6::1) 195.823 ms 195.447 ms 195.481 ms
9 10gigabitethernet1-2.core1.lon1.he.net (2001:470:0:128::2) 263.027 ms 272.585 ms 265.482 ms
10 2001:7f8:4::20e6:1 (2001:7f8:4::20e6:1) 263.144 ms 263.427 ms 263.763 ms
11 core-pg1-vl46.netcologne.de (2001:4dd0:a2b:18:dc10::c1) 276.496 ms 275.966 ms 275.477 ms
12 core-eup2-te4-1.netcologne.de (2001:4dd0:a2b:1d:dc40::1) 275.169 ms 275.502 ms 275.732 ms
13 2001:4dd0:1234:3::42 (2001:4dd0:1234:3::42) 273.975 ms 274.437 ms 274.124 ms
14 gw-4389.cgn-01.de.sixxs.net (2001:4dd0:ff00:1124::1) 275.353 ms 275.144 ms 275.653 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
it is what aiccu test say:
pouyan@Voyoger:~$ sudo aiccu test
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (172.20.169.139)
### This should return so called 'echo replies'
### If it doesn't then check your firewall settings
### Your local endpoint should always be pingable
### It could also indicate problems with your IPv4 stack
PING 172.20.169.139 (172.20.169.139) 56(84) bytes of data.
64 bytes from 172.20.169.139: icmp_req=1 ttl=64 time=0.037 ms
64 bytes from 172.20.169.139: icmp_req=2 ttl=64 time=0.029 ms
64 bytes from 172.20.169.139: icmp_req=3 ttl=64 time=0.034 ms
--- 172.20.169.139 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.029/0.033/0.037/0.005 ms
######
Did this work? [Y/n] y
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (78.35.24.124)
### These pings should reach the PoP and come back to you
### In case there are problems along the route between your
### host and the PoP this could not return replies
### Check your firewall settings if problems occur
PING 78.35.24.124 (78.35.24.124) 56(84) bytes of data.
64 bytes from 78.35.24.124: icmp_req=1 ttl=55 time=14.5 ms
64 bytes from 78.35.24.124: icmp_req=2 ttl=55 time=14.4 ms
64 bytes from 78.35.24.124: icmp_req=3 ttl=55 time=14.5 ms
--- 78.35.24.124 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 14.489/14.553/14.586/0.108 ms
######
Did this work? [Y/n] y
####### [3/8] Traceroute to the PoP (78.35.24.124) 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 78.35.24.124 (78.35.24.124), 30 hops max, 60 byte packets
1 kha-2nd-gateway.kha.uni-karlsruhe.de (172.20.169.129) 0.165 ms 0.141 ms 0.130 ms
2 r-wh-kha.rz.uni-karlsruhe.de (172.20.2.17) 1.077 ms 1.277 ms 1.272 ms
3 Karlsruhe1.belwue.de (129.143.166.9) 7.523 ms 7.742 ms 7.723 ms
4 Karlsruhe10.belwue.de (129.143.166.230) 7.987 ms 7.920 ms 8.146 ms
5 Mannheim-RZ-1-10GE-0-1-0-3.belwue.net (129.143.57.158) 8.920 ms 8.921 ms 8.913 ms
6 Frankfurt-DECIX-1-10GE-0-0-0-0.belwue.net (129.143.1.22) 10.605 ms 10.286 ms 10.492 ms
7 rtdecix-g00.netcologne.de (80.81.192.212) 10.976 ms 10.604 ms 10.588 ms
8 core-sto2-t71.netcologne.de (89.1.16.5) 16.553 ms 15.668 ms 15.267 ms
9 core-eup2-t32.netcologne.de (87.79.17.29) 15.000 ms 15.001 ms 14.995 ms
10 sixxs-pop1.netcologne.net (78.35.24.124) 14.692 ms 14.542 ms 14.518 ms
######
Did this work? [Y/n] y
###### [4/8] Checking if we can ping IPv6 localhost (::1)
### This confirms if your IPv6 is working
### If ::1 doesn't reply then something is wrong with your IPv6 stack
PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.037 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.037 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.037 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.037/0.037/0.037/0.000 ms
######
Did this work? [Y/n] y
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4dd0:ff00:1124::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:4dd0:ff00:1124::2(2001:4dd0:ff00:1124::2) 56 data bytes
64 bytes from 2001:4dd0:ff00:1124::2: icmp_seq=1 ttl=64 time=0.036 ms
64 bytes from 2001:4dd0:ff00:1124::2: icmp_seq=2 ttl=64 time=0.036 ms
64 bytes from 2001:4dd0:ff00:1124::2: icmp_seq=3 ttl=64 time=0.040 ms
--- 2001:4dd0:ff00:1124::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.036/0.037/0.040/0.005 ms
######
Did this work? [Y/n] y
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4dd0:ff00:1124::1)
### This confirms the reachability of the other side of the tunnel
### If it doesn't reply then check your interface and routing tables
### Don't forget to check your firewall of course
### If the previous test was successful then this could be both
### a firewalling and a routing/interface problem
PING 2001:4dd0:ff00:1124::1(2001:4dd0:ff00:1124::1) 56 data bytes
64 bytes from 2001:4dd0:ff00:1124::1: icmp_seq=1 ttl=64 time=11.9 ms
64 bytes from 2001:4dd0:ff00:1124::1: icmp_seq=2 ttl=64 time=11.8 ms
64 bytes from 2001:4dd0:ff00:1124::1: icmp_seq=3 ttl=64 time=14.5 ms
--- 2001:4dd0:ff00:1124::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 11.802/12.763/14.515/1.247 ms
######
Did this work? [Y/n] y
###### [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:4dd0:ff00:1124::2, 30 hops max, 24 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
######
Did this work? [Y/n] n
the syslog says something like this:
Dec 27 17:40:50 Voyoger aiccu[31937]: Successfully retrieved tunnel information for T112534
Dec 27 17:40:50 Voyoger aiccu[31942]: AICCU running as PID 31942
Dec 27 17:40:50 Voyoger aiccu[31942]: [AYIYA-start] : Anything in Anything (draft-02)
Dec 27 17:40:50 Voyoger aiccu[31942]: [AYIYA-tun->tundev] : (Socket to TUN) started
aicu tunnels output:
pouyan@Voyoger:~$ sudo aiccu tunnels
T112534 2001:4dd0:ff00:1124::2 ayiya decgn01
Can't connect to the noc.sixxs.net
![[cy]](/s/countries/cy.gif) Shadow Hawkins on Friday, 28 December 2012 11:26:27
i have the same problem as well , i can't access ipv6 sites since yesterday for some reason
Can't connect to the noc.sixxs.net
Instead of 'it does not work' you might want to provide actual details so that people can help you determine what might be wrong. See the big yellow/orange box which links to the Contact page's "Reporting Problems" link for a long list of details that one should provide.
Can't connect to the noc.sixxs.net
it has to be said that my computer is also not ping-able from outside:
That traceroute indicates that the tunnel is marked up (and as you are using AYIYA that AYIYA packets are being received by the PoP). But if your host is filtering the ping packets or sending them out through a wrong path or with a wrong source etc, then that ping won't work.
There are many many reasons why this can't work. You'll have to provide a lot more details, as requested by that big orange/yellow box while posting.
Can't connect to the noc.sixxs.net
Shadow Hawkins on Friday, 28 December 2012 20:27:59
So can it be a problem with my NAT? I have to say, I am behind a NAT and and my IPV4 is not accessible from outside world. It is valid but not accessible.
One more thing:
gogo6 client works well, I know they use other technology but maybe it can help.
I also don't have nay rules in iptables and my selinux is also off.
Can't connect to the noc.sixxs.net
Shadow Hawkins on Wednesday, 02 January 2013 17:40:51
Hi, wanted to say that is working now after changing my Ipv4 ISP.
|
![[ch]](/s/countries/ch.gif)
on Friday, 28 December 2012 18:52:50
Posting is only allowed when you are