|
Unable to ping my PoP IPv6
![[be]](/s/countries/be.gif) Shadow Hawkins on Friday, 27 April 2012 17:34:21
Hello All
I've problems setting up my IPv6 tunnel on my Debian router (2.6.32).
My Debian router is connected to the internet via a D-LINK router. I've put the Debian router in the DMZ zone so all trafic should be allowed on the D-LINK router
As I wasn't sure of my previous configuration, I build a new Debian machine. So right after installing, y network configuration on the Debian router looks like this:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
After installing the debian machine, I did installed aiccu via the command apt-get install aiccu
After installing Aiccu, my network status (ifconfig) looks like this:
eth0 Link encap:Ethernet HWaddr 00:0c:29:4a:29:a9
inet addr:192.168.100.199 Bcast:192.168.100.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe4a:29a9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14533 errors:0 dropped:0 overruns:0 frame:0
TX packets:5996 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21266536 (20.2 MiB) TX bytes:401317 (391.9 KiB)
Interrupt:19 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:117 errors:0 dropped:0 overruns:0 frame:0
TX packets:117 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13864 (13.5 KiB) TX bytes:13864 (13.5 KiB)
sixxs Link encap:IPv6-in-IPv4
inet6 addr: fe80::5ee2:341/128 Scope:Link
inet6 addr: 2001:6f8:202:2f7::2/64 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
When running the Aiccu test commando I get the following result
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (94.226.3.65)
### 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 94.226.3.65 (94.226.3.65) 56(84) bytes of data.
64 bytes from 94.226.3.65: icmp_req=1 ttl=64 time=1.42 ms
64 bytes from 94.226.3.65: icmp_req=2 ttl=64 time=3.69 ms
64 bytes from 94.226.3.65: icmp_req=3 ttl=64 time=2.17 ms
--- 94.226.3.65 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 1.429/2.433/3.695/0.942 ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.100.184.146)
### 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 212.100.184.146 (212.100.184.146) 56(84) bytes of data.
64 bytes from 212.100.184.146: icmp_req=1 ttl=54 time=29.0 ms
64 bytes from 212.100.184.146: icmp_req=2 ttl=54 time=22.1 ms
64 bytes from 212.100.184.146: icmp_req=3 ttl=54 time=21.1 ms
--- 212.100.184.146 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 21.123/24.079/29.004/3.509 ms
######
####### [3/8] Traceroute to the PoP (212.100.184.146) 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 212.100.184.146 (212.100.184.146), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 11.031 ms 10.818 ms 10.413 ms
2 94-226-0-1.access.telenet.be (94.226.0.1) 14.781 ms 18.396 ms 18.648 ms
3 dD5E0C521.access.telenet.be (213.224.197.33) 21.154 ms 20.919 ms 21.075 ms
4 dD5E0F86A.access.telenet.be (213.224.248.106) 19.207 ms 18.817 ms 18.419 ms
5 te-3-3.car2.Brussels1.Level3.net (212.3.237.53) 16.491 ms te-3-1.car2.Brussels1.Level3.net (212.3.237.17) 18.761 ms te-3-3.car2.Brussels1.Level3.net (212.3.237.53) 17.327 ms
6 ae-6-6.ebr1.Amsterdam1.Level3.net (4.69.148.174) 24.807 ms 14.570 ms 15.368 ms
7 ae-56-111.csw1.Amsterdam1.Level3.net (4.69.153.186) 20.024 ms ae-58-113.csw1.Amsterdam1.Level3.net (4.69.153.194) 19.838 ms ae-59-114.csw1.Amsterdam1.Level3.net (4.69.153.198) 18.553 ms
8 ae-1-51.edge3.Amsterdam1.Level3.net (4.69.139.137) 18.293 ms 16.955 ms 18.097 ms
9 unknown.Level3.net (212.72.33.106) 23.923 ms 24.769 ms 24.501 ms
10 ge2-0-3.gr11.ixbru.be.easynet.net (87.86.77.28) 23.998 ms 27.053 ms 27.695 ms
11 ge0-2-0-324.br1.ixbru.easynet.net (87.86.71.189) 27.432 ms 21.106 ms 24.483 ms
12 ge5-2.cr11.gdbru.be.easynet.net (212.100.161.69) 20.741 ms 25.553 ms 24.388 ms
13 212.100.184.146 (212.100.184.146) 24.656 ms 23.057 ms 23.790 ms
######
###### [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.050 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.079 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.088 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.050/0.072/0.088/0.017 ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:202:2f7::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:6f8:202:2f7::2(2001:6f8:202:2f7::2) 56 data bytes
64 bytes from 2001:6f8:202:2f7::2: icmp_seq=1 ttl=64 time=0.062 ms
64 bytes from 2001:6f8:202:2f7::2: icmp_seq=2 ttl=64 time=0.086 ms
64 bytes from 2001:6f8:202:2f7::2: icmp_seq=3 ttl=64 time=0.085 ms
--- 2001:6f8:202:2f7::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.062/0.077/0.086/0.015 ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:202:2f7::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:6f8:202:2f7::1(2001:6f8:202:2f7::1) 56 data bytes
From 2001:6f8:202:2f7::2 icmp_seq=1 Destination unreachable: Address unreachable
From 2001:6f8:202:2f7::2 icmp_seq=2 Destination unreachable: Address unreachable
From 2001:6f8:202:2f7::2 icmp_seq=3 Destination unreachable: Address unreachable
--- 2001:6f8:202:2f7::1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 1999ms
######
###### [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), 30 hops max, 80 byte packets
1 cl-760.bru-01.be.sixxs.net (2001:6f8:202:2f7::2) 0.080 ms !H 0.032 ms !H 0.025 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:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets
1 cl-760.bru-01.be.sixxs.net (2001:6f8:202:2f7::2) 0.092 ms !H 0.018 ms !H 0.017 ms !H
######
###### ACCU Quick Connectivity Test (done)
### Either the above all works and gives no problems
### or it shows you where what goes wrong
### Check the SixXS FAQ (http://www.sixxs.net/faq/
### for more information and possible solutions or hints
### Don't forget to check the Forums (http://www.sixxs.net/forum/)
### for a helping hand.
### Passing the output of 'aiccu autotest >aiccu.log' is a good idea.
So when pinging to my PoP IPv6 (2001:6f8:202:2f7::1) I get the result that the Destination is unreachable.
Anybody an idea?
Thanks for your help
Unable to ping my PoP IPv6
My Debian router is connected to the internet via a D-LINK router. I've put the Debian router in the DMZ zone so all trafic should be allowed on the D-LINK router
As various D-link models support IPv6 themselves, are you sure this really works and that it properly forwards proto-41 inbound and outbound?
sixxs Link encap:IPv6-in-IPv4 inet6 addr: fe80::5ee2:341/128 Scope:Link inet6 addr: 2001:6f8:202:2f7::2/64 Scope:Global ... RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Nothing sent or received? That is odd.
Also, what does the output of 'ip tunnel show' show?
When running the Aiccu test commando I get the following result
Did you now configure your tunnel statically using /etc/network/interfaces or are you using AICCU?
1 cl-760.bru-01.be.sixxs.net (2001:6f8:202:2f7::2) 0.080 ms !H 0.032 ms !H 0.025 ms !H
That shows that your local host already decides that it can't send the packet. That indicates a local misconfiguration. If packets are getting lost routing works and the first hop would just time out.
Do also check all the other items on the contact page's "Reporting Problems" list. The AICCU "test" command merely establish that it works or does not work, not much else.
Unable to ping my PoP IPv6
Shadow Hawkins on Saturday, 28 April 2012 12:14:23As various D-link models support IPv6 themselves, are you sure this really works and that it properly forwards proto-41 inbound and outbound?
I've a D-Link DIR-655 which doesn't support IPv6 out of the box (as far as I can see).
Did you now configure your tunnel statically using /etc/network/interfaces or are you using AICCU?
I tried both. With the manual configuration, it didn't worked so now I did set up a new machine, installed aiccu and did again the test.
But I now also found something strange. If I run the command ip tunnel show before I run aiccu test then I get the following result
sit0: ipv6/ip remote any local any ttl 64 nopmtudisc
sixxs: ipv6/ip remote 212.100.184.146 local 94.226.3.65 ttl 64
If I run the same command after aiccu test, I only see the tunnel sit0. Also when I then check ifconfig, the adapter sixxs is gone. When I then check the routing table, I only see 1 active route
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
When I run aiccu stop and aiccu start, it is all back.
Unable to ping my PoP IPv6
I've a D-Link DIR-655 which doesn't support IPv6 out of the box (as far as I can see).
According to http://www.dlink.com/ipv6 it does
sixxs: ipv6/ip remote 212.100.184.146 local 94.226.3.65 ttl 64
As you are behind a NAT, that will not work, you need to have local set to your local IP not the external one.
Unable to ping my PoP IPv6
Shadow Hawkins on Sunday, 29 April 2012 14:05:35
Hello
I've change the aiccu.conf settings. Now the ip 6 tunnel shows the following
sixxs: ipv6/ip remote 212.100.184.146 local 192.168.100.199 ttl 64
Still no luck ;'(
Unable to ping my PoP IPv6
Likely because your DLINK is not passing the protocol 41 packets properly.
Check if you cannot terminate the tunnel on the DLINK, it should be more than capable of doing it.
Unable to ping my PoP IPv6
Shadow Hawkins on Wednesday, 02 May 2012 17:40:49
I wasn't able to terminate the tunnel on my DLINK. I searched all options but I couldn't find it.
Today I had the opportunity to test my tunnel on another location. Here, I was connected to the internet via a FRITZ!Box.
In this location, I have no problems at all to setup the tunnel. Even without change-ing anyting on the router, I was able to ping to ipv6.google.com.
So the problem is not with my Debian configuration but with my DLINK. Is their perhaps a way to solve this issue with port-forwarding?
Thanks for your help!!!
Unable to ping my PoP IPv6
Is their perhaps a way to solve this issue with port-forwarding?
No, as you have currently a static tunnel which uses protocol 41 ("protocol" thus not "port").
Your easiest solution is to change the tunnel type to AYIYA and terminate it that way.
Another option is to check if you can get a firmware upgrade for your DLINK so that it supports IPv6.
Unable to ping my PoP IPv6
Shadow Hawkins on Friday, 04 May 2012 18:05:35
Super, I changed it to AYIYA and now it works whitout any problem.
Thanks for your help!
|
![[ch]](/s/countries/ch.gif)
on Friday, 27 April 2012 18:30:37
Posting is only allowed when you are