Ticket ID: SIXXS #9594494 Ticket Status: Resolved PoP: vnhan01 - NetNam Corporation (Hanoi)
ping6 ipv6.google.com ... Destination unreachable: Address unreachable
Shadow Hawkins on Wednesday, 19 June 2013 01:28:05
Cannot connect to the ipv6 network and when ping6 ipv6.google.com, I got the following result:
PING ipv6.google.com(2404:6800:4005:c00::69) 56 data bytes
From vnhan01.sixxs.net icmp_seq=1 Destination unreachable: Address unreachable
From vnhan01.sixxs.net icmp_seq=2 Destination unreachable: Address unreachable
From vnhan01.sixxs.net icmp_seq=3 Destination unreachable: Address unreachable
From vnhan01.sixxs.net icmp_seq=6 Destination unreachable: Address unreachable
^C
--- ipv6.google.com ping statistics ---
8 packets transmitted, 0 received, +4 errors, 100% packet loss, time 7943ms
[sixxs@localhost ~]$ ping6 ipv6.google.com
PING ipv6.google.com(2404:6800:4005:c00::69) 56 data bytes
From vnhan01.sixxs.net icmp_seq=2 Destination unreachable: Address unreachable
From vnhan01.sixxs.net icmp_seq=3 Destination unreachable: Address unreachable
From vnhan01.sixxs.net icmp_seq=5 Destination unreachable: Address unreachable
From vnhan01.sixxs.net icmp_seq=6 Destination unreachable: Address unreachable
^C
--- ipv6.google.com ping statistics ---
6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 5952ms
[sixxs@localhost ~]$ ping6 ipv6.google.com
PING ipv6.google.com(2404:6800:4005:c00::67) 56 data bytes
From vnhan01.sixxs.net icmp_seq=2 Destination unreachable: Address unreachable
From vnhan01.sixxs.net icmp_seq=4 Destination unreachable: Address unreachable
From vnhan01.sixxs.net icmp_seq=5 Destination unreachable: Address unreachable
^C
--- ipv6.google.com ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5513ms
ping6 ipv6.google.com ... Destination unreachable: Address unreachable
Shadow Hawkins on Wednesday, 19 June 2013 06:15:32
i had same problem too. i have installed aiccu. it works fine for a few months, i get both ipv6 and ipv4 connection. but suddenly, on these last 3 days, i can't ping ipv6 sites. my tunnel is T120022. if i try to ping, i got these notification:
mer@mer-1015PW:~$ ping6 google.com
PING google.com(2404:6800:4001:c01::8b) 56 data bytes
From vnhan01.sixxs.net icmp_seq=2 Destination unreachable: Address unreachable
From vnhan01.sixxs.net icmp_seq=4 Destination unreachable: Address unreachable
From vnhan01.sixxs.net icmp_seq=5 Destination unreachable: Address unreachable
help me please. i have to make a presentation about my dual stack network thesis next week.
greets merlie
ping6 ipv6.google.com ... Destination unreachable: Address unreachable
Shadow Hawkins on Wednesday, 19 June 2013 10:27:51
I also had the same problem with this for about 3 days already.
Pinging ipv6.google.com (or any other ipv6 addresses and hostnames) always return:
Destination unreachable: Address unreachable
And, syslog show:
aiccu[2806]: Successfully retrieved tunnel information for T121838
aiccu[2806]: Couldnt set interface name to sixxs: Device or resource busy (16)
aiccu[2806]: Tunnel Setup Failed
When I found the this ticket, ticket#9594494, has been resolved, I was hoping that my issue would also be resolved :( (I just though so)
I restarted the server and thought of being able to ping the ipv6 addresses already.
Now, aiccu wouldn't start anymore.
It's service status is: stop/waiting.
aiccu.log showed (after seeing the stop/waiting status, I attempted to
start it):
============================================================
20131806 15:28:37 Command line: /usr/sbin/aiccu start
20131806 15:28:42 SixXs Automatic IPv6 Connectivity Client Utility started
20131906 16:34:35 Stopping Automatic IPv6 Connectivity Client Utility
20131906 16:34:35 Automatic IPv6 Connectivity Client Utility stopped
20131906 16:36:22 Starting Automatic IPv6 Connectivity Client Utility
20131906 16:36:23 Checking access to tic.sixxs.net:
20131906 16:36:25 OK
20131906 16:36:25 SixXs Automatic IPv6 Connectivity Client Utility started
20131906 16:37:28 Stopping Automatic IPv6 Connectivity Client Utility
============================================================
syslog shows:
============================================================
Couldn't connect to the TIC server tic.sixxs.net
Couldn't retrieve first tunnel for the above reason, aborting.
Also, I found several lines of these logs:
radvd[2885] resetting IPv6-allrouters membership on eth0
radvd[2710] resetting IPv6-allrouters membership on eth0
.
.
radvd[2885] resetting IPv6-allrouters membership on eth0
radvd[2710] resetting IPv6-allrouters membership on eth0
.
.
============================================================
If anyone could enlighten me, I would greatly appreciate it. :)
Have I reached the aiccu stop/start limit and have been blocked from TIC? :(
How long will I be blocked?
By the way, my tunnel Id is: T121838
Thanks.
ping6 ipv6.google.com ... Destination unreachable: Address unreachable
Jeroen Massar on Wednesday, 19 June 2013 11:10:21 Pinging ipv6.google.com (or any other ipv6 addresses and hostnames) always return: Destination unreachable: Address unreachable
Instead of a ping, have you tried a traceroute to the destination to see where it goes wrong?
aiccu[2806]: Successfully retrieved tunnel information for T121838 aiccu[2806]: Couldnt set interface name to sixxs: Device or resource busy (16) aiccu[2806]: Tunnel Setup Failed
That looks like a local issue. Of course when the tunnel is not configured properly you won't be getting anywhere.
I restarted the server and thought of being able to ping the ipv6 addresses already.
What would a 'restart' of exactly what resolve?
Couldn't connect to the TIC server tic.sixxs.net
Various reasons for this:
- broken IPv4 connectivity
- broken DNS setup
- Banned from the TIC server as you have been hammering it with restarts
Have I reached the aiccu stop/start limit and have been blocked from TIC? :(
Likely.
How long will I be blocked?
As long as you keep on hammering on it.
Restarts do not resolve the problem that AICCU has indicated above.
All of this is a problem on your computer though, as such, please per-use the forums for resolving your problem.
ping6 ipv6.google.com ... Destination unreachable: Address unreachable
Shadow Hawkins on Wednesday, 19 June 2013 13:49:41
The problem seems to be at vnhan01.sixxs.net, because "Destination unreachable: Address unreachable" is replied from vnhan01.sixxs.net. I can ping6 vnhan01.sixxs.net and get reply as follows:
ping6 vnhan01.sixxs.net
PING vnhan01.sixxs.net(vnhan01.sixxs.net) 56 data bytes
64 bytes from vnhan01.sixxs.net: icmp_seq=1 ttl=64 time=471 ms
64 bytes from vnhan01.sixxs.net: icmp_seq=2 ttl=64 time=436 ms
64 bytes from vnhan01.sixxs.net: icmp_seq=3 ttl=64 time=474 ms
64 bytes from vnhan01.sixxs.net: icmp_seq=4 ttl=64 time=448 ms
^C
--- vnhan01.sixxs.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3602ms
rtt min/avg/max/mdev = 436.664/457.803/474.514/15.704 ms
[sixxs@localhost ~]$ ping6 ipv6.google.com
PING ipv6.google.com(2404:6800:4005:c00::93) 56 data bytes
From vnhan01.sixxs.net icmp_seq=1 Destination unreachable: Address unreachable
From vnhan01.sixxs.net icmp_seq=2 Destination unreachable: Address unreachable
From vnhan01.sixxs.net icmp_seq=4 Destination unreachable: Address unreachable
From vnhan01.sixxs.net icmp_seq=5 Destination unreachable: Address unreachable
^C
--- ipv6.google.com ping statistics ---
6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 5908ms
ping6 ipv6.google.com ... Destination unreachable: Address unreachable
Jeroen Massar on Wednesday, 19 June 2013 15:14:34
It seems that the routing is broken again indeed, ticket marked reopened and netnam has been informed.
ping6 ipv6.google.com ... Destination unreachable: Address unreachable
Shadow Hawkins on Saturday, 29 June 2013 00:16:50
Hi Jeroen,
The pop has been working for several days so the problem has been resolved.
Thank you very much for your help.
ping6 ipv6.google.com ... Destination unreachable: Address unreachable
Shadow Hawkins on Friday, 21 June 2013 08:01:48
Hi Jeroen,
You're right. Thanks.
Aiccu not starting was a local issue. Our admin blocked/closed udp ports 5072 & 123. But yesterday, they opened it again after our complaint.
I was still not able to ping IPv6 and traceroute gives only:
1 * * *
2 * * *
yesterday.
But this afternoon, I can already ping ipv6 addresses.
So I guess, this has already been resolved.
Thanks a lot :)
Posting is only allowed when you are logged in. |