|
Ticket ID: SIXXS #5710762 Ticket Status: User PoP: chzrh02 - Init7 AG (Zurich)
Can't ping tunnel endpoint anymore
![[ch]](/s/countries/ch.gif) Shadow Hawkins on Tuesday, 11 October 2011 08:46:58
Hi
Since yesterday night I'm not able to ping my POPs tunnel endpoint. I'm using a Fritz!Box 7390 to connect to SIXXS. No changes at my infrastructure were made.
Neither using the iPhone 4 (OS 4.3.3) nor Macbook Pro (Mac OS X 10.6.8) I can't connect to IPv6 addresses. Using the heise app on the iPhone - which seems to connect to the IPv6 address if IPv6 is enabled - I realized that the tunnel got a problem.
No firewall and no anti-virus software running.
=== ping6 to PoPs tunnel endpoint ===
mbp:~ thomas$ ping6 2001:1620:f00:90::1
PING6(56=40+8+8 bytes) 2001:1620:f4a::21b:63ff:febf:9fbc --> 2001:1620:f00:90::1
Request timeout for icmp_seq=0
Request timeout for icmp_seq=1
Request timeout for icmp_seq=2
Request timeout for icmp_seq=3
^C
--- 2001:1620:f00:90::1 ping6 statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
=== traceroute6 ===
mbp:~ thomas$ traceroute6 -m 5 2001:1620:f00:90::1
traceroute6 to 2001:1620:f00:90::1 (2001:1620:f00:90::1) from 2001:1620:f4a::21b:63ff:febf:9fbc, 5 hops max, 12 byte packets
1 fritz.box 4.445 ms 4.500 ms 4.117 ms
2 * * *
3 * * *
4 * * *
5 * * *
=== uname -a on MBP ===
mbp:~ thomas$ uname -a
Darwin mbp.fritz.box 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386
=== SIXXS infos ===
NIC Handle : TKF7-SIXXS
Tunnel ID : T38797
Type : Heartbeat
PoP IPv6 : 2001:1620:f00:90::1
Cheers
Thomas
Can't ping tunnel endpoint anymore
Shadow Hawkins on Tuesday, 11 October 2011 08:49:13
What I forgot : Subnet ID -> R16893
IPv6 Them2001:1620:f00:90::2/64 (T38797)
Prefix2001:1620:f4a::/48
StateEnabled
Can't ping tunnel endpoint anymore
Shadow Hawkins on Tuesday, 11 October 2011 09:25:50
Same for here with 2001:1620:f00:80::1
from any location from internet or local lan
They said the pop is up, nice, but the pop doesn't do any routing.
a ping6 nor a traceroute6 from external ipv6 internet hit the endpoint
And I lost -10 points with bot's email alert :-)
Can't ping tunnel endpoint anymore
Shadow Hawkins on Tuesday, 11 October 2011 09:25:33
I have read and followed the "Reporting Problems" section on the Contact page.
I am removing these five pre-filled lines to demonstrate that I really read it.
I am providing the full details as requested on the mentioned Contact page.
If I do not remove this, then please ignore this message as I didn't read it anyway.
------------------------------------------------------------------------------>8
Same here.
Tunnel ID : T73001
Type : AYIYA
PoP IPv6 : 2001:1620:f00:12c::1
State change: user
The state of this ticket has been changed to user
Can't ping tunnel endpoint anymore
Please provide more running configuration details (interfaces, routing tables etc). That you can't reach anything remote primilary just indicates that the tunnel is not working.
Can't ping tunnel endpoint anymore
Shadow Hawkins on Tuesday, 11 October 2011 09:48:07
=== on my MBP ===
Interface en1 (airport) :
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:1b:63:bf:9f:bc
inet6 fe80::21b:63ff:febf:9fbc%en1 prefixlen 64 scopeid 0x5
inet 192.168.178.27 netmask 0xffffff00 broadcast 192.168.178.255
inet6 2001:1620:f4a::21b:63ff:febf:9fbc prefixlen 64 autoconf
media: autoselect
status: active
=== routing tables on MBP ===
mbp:~ thomas$ netstat -rn
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.178.1 UGSc 35 0 en1
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 9 119687 lo0
169.254 link#5 UCS 0 0 en1
172.16.43/24 link#7 UC 3 0 vmnet1
172.16.43.1 0:50:56:c0:0:1 UHLWI 0 55 lo0
172.16.43.255 link#7 UHLWbI 1 14 vmnet1
172.16.192/24 link#8 UC 3 0 vmnet8
172.16.192.1 0:50:56:c0:0:8 UHLWI 0 54 lo0
172.16.192.255 link#8 UHLWbI 1 14 vmnet8
192.168.178 link#5 UCS 2 0 en1
192.168.178.1 bc:5:43:93:fb:15 UHLWI 59 2495 en1 1177
192.168.178.27 127.0.0.1 UHS 1 1417 lo0
192.168.178.255 link#5 UHLWbI 2 94 en1
Internet6:
Destination Gateway Flags Netif Expire
default fe80::be05:43ff:fe93:fb15%en1 UGSc en1
::1 ::1 UH lo0
2001:1620:f4a::/64 link#5 UC en1
2001:1620:f4a::21b:63ff:febf:9fbc 0:1b:63:bf:9f:bc UHL lo0
2001:1620:f4a::be05:43ff:fe93:fb15 bc:5:43:93:fb:15 UHLW en1
fe80::%lo0/64 fe80::1%lo0 Uc lo0
fe80::1%lo0 link#1 UHL lo0
fe80::%en1/64 link#5 UC en1
fe80::21b:63ff:febf:9fbc%en1 0:1b:63:bf:9f:bc UHL lo0
fe80::be05:43ff:fe93:fb15%en1 bc:5:43:93:fb:15 UHL en1
ff01::/32 ::1 Um lo0
ff02::/32 ::1 UmC lo0
ff02::/32 link#5 UmC en1
=== traceroute from an external server (Paris, France) ===
master@supertom:~$ traceroute6 2001:1620:f00:90::1
traceroute to 2001:1620:f00:90::1 (2001:1620:f00:90::1), 30 hops max, 80 byte packets
1 * * *
2 p254-core3-d-ip6.paris.gandi.net (2001:4b98:1f::c3d3:249) 23.425 ms 23.419 ms 23.411 ms
3 p251-core4-d-ip6.paris.gandi.net (2001:4b98:1f::c3c4:254) 6.834 ms * *
4 r1par1.core.init7.net (2001:7f8:43::1:3030:1) 11.377 ms 11.188 ms 11.344 ms
5 r1gva1.core.init7.net (2001:1620:2::9a) 11.129 ms 11.128 ms 11.120 ms
6 r1zug1.core.init7.net (2001:1620:2::8d) 15.802 ms 15.819 ms 15.685 ms
7 r1glb1.core.init7.net (2001:1620:2::d1) 16.155 ms 16.137 ms 16.127 ms
8 r1oer1.core.init7.net (2001:1620:2::c6) 16.392 ms 16.387 ms 16.281 ms
9 r1zur1.core.init7.net (2001:1620:2::c9) 16.793 ms 16.688 ms 16.641 ms
10 r1zlz1.core.init7.net (2001:1620:2::4a) 16.277 ms 16.301 ms 16.376 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Can't ping tunnel endpoint anymore
As that is not the device terminating your tunnel, does that matter when the tunnel is broken?
Can't ping tunnel endpoint anymore
Shadow Hawkins on Tuesday, 11 October 2011 10:41:23
And on the fritx.box (not using DSL anymore - for about two months - but a cable modem connected to LAN1):
# ip -6 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
6: lan: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 1500
inet6 2001:1620:f4a:0:be05:43ff:fe93:fb15/64 scope global
valid_lft forever preferred_lft forever
inet6 fd00::be05:43ff:fe93:fb15/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::be05:43ff:fe93:fb15/64 scope link
valid_lft forever preferred_lft forever
7: guest: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 1500
inet6 2001:1620:f4a:1:be05:43ff:fe93:fb15/64 scope global
valid_lft forever preferred_lft forever
inet6 fd00::1:be05:43ff:fe93:fb15/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::be05:43ff:fe93:fb15/64 scope link
valid_lft forever preferred_lft forever
34: dsl: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP200> mtu 1500 qlen 100
inet6 2001:1620:f00:90::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::be05:43ff:fe93:fb18/64 scope link
valid_lft forever preferred_lft forever
# ipaddr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
3: cpmac0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether bc:05:43:93:fb:15 brd ff:ff:ff:ff:ff:ff
4: wan: <BROADCAST,MULTICAST,UP,LOWER_UP100> mtu 1500 qdisc tbf qlen 32
link/ether bc:05:43:93:fb:15 brd ff:ff:ff:ff:ff:ff
5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 1500 qdisc pfifo_fast qlen 128
link/ether bc:05:43:93:fb:15 brd ff:ff:ff:ff:ff:ff
6: lan: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 1500 qdisc noqueue
link/ether bc:05:43:93:fb:15 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.1/24 brd 192.168.178.255 scope global lan
inet 169.254.1.1/16 brd 169.254.255.255 scope global lan:0
inet6 2001:1620:f4a:0:be05:43ff:fe93:fb15/64 scope global
valid_lft forever preferred_lft forever
inet6 fd00::be05:43ff:fe93:fb15/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::be05:43ff:fe93:fb15/64 scope link
valid_lft forever preferred_lft forever
7: guest: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 1500 qdisc noqueue
link/ether bc:05:43:93:fb:15 brd ff:ff:ff:ff:ff:ff
inet 192.168.179.1/24 brd 192.168.179.255 scope global guest
inet6 2001:1620:f4a:1:be05:43ff:fe93:fb15/64 scope global
valid_lft forever preferred_lft forever
inet6 fd00::1:be05:43ff:fe93:fb15/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::be05:43ff:fe93:fb15/64 scope link
valid_lft forever preferred_lft forever
22: wifi0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether bc:05:43:93:fb:17 brd ff:ff:ff:ff:ff:ff
23: wifi1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether bc:05:43:93:fb:1b brd ff:ff:ff:ff:ff:ff
28: ath0: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 2290 qdisc pfifo_fast qlen 1000
link/ether bc:05:43:93:fb:1b brd ff:ff:ff:ff:ff:ff
29: ath1: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 2290 qdisc pfifo_fast qlen 1000
link/ether bc:05:43:93:fb:17 brd ff:ff:ff:ff:ff:ff
34: dsl: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP200> mtu 1500 qdisc pfifo_fast qlen 100
link/ppp
inet 192.168.178.1/32 scope global dsl
inet6 2001:1620:f00:90::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::be05:43ff:fe93:fb18/64 scope link
valid_lft forever preferred_lft forever
# ifconfig
ath0 Link encap:Ethernet HWaddr BC:05:43:93:FB:1B
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:2290 Metric:1
RX packets:61485 errors:0 dropped:0 overruns:0 frame:0
TX packets:75941 errors:0 dropped:27 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8253427 (7.8 MiB) TX bytes:77985551 (74.3 MiB)
ath1 Link encap:Ethernet HWaddr BC:05:43:93:FB:17
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:2290 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1845 errors:0 dropped:163 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:432112 (421.9 KiB)
cpmac0 Link encap:Ethernet HWaddr BC:05:43:93:FB:15
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:110928 errors:0 dropped:0 overruns:0 frame:0
TX packets:74334 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:90448782 (86.2 MiB) TX bytes:21439340 (20.4 MiB)
Interrupt:14
dsl Link encap:Point-to-Point Protocol
inet addr:192.168.178.1 P-t-P:192.168.178.1 Mask:255.255.255.255
inet6 addr: fe80::be05:43ff:fe93:fb18/64 Scope:Link
inet6 addr: 2001:1620:f00:90::2/64 Scope:Global
UP POINTOPOINT RUNNING NOARP ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:20869 errors:0 dropped:0 overruns:0 frame:0
TX packets:14250 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:7689259 (7.3 MiB) TX bytes:2067772 (1.9 MiB)
eth0 Link encap:Ethernet HWaddr BC:05:43:93:FB:15
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:3442 errors:0 dropped:0 overruns:0 frame:0
TX packets:4471 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:128
RX bytes:277904 (271.3 KiB) TX bytes:1791813 (1.7 MiB)
guest Link encap:Ethernet HWaddr BC:05:43:93:FB:15
inet addr:192.168.179.1 Bcast:192.168.179.255 Mask:255.255.255.0
inet6 addr: 2001:1620:f4a:1:be05:43ff:fe93:fb15/64 Scope:Global
inet6 addr: fd00::1:be05:43ff:fe93:fb15/64 Scope:Global
inet6 addr: fe80::be05:43ff:fe93:fb15/64 Scope:Link
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:9562 (9.3 KiB)
lan Link encap:Ethernet HWaddr BC:05:43:93:FB:15
inet addr:192.168.178.1 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: 2001:1620:f4a:0:be05:43ff:fe93:fb15/64 Scope:Global
inet6 addr: fd00::be05:43ff:fe93:fb15/64 Scope:Global
inet6 addr: fe80::be05:43ff:fe93:fb15/64 Scope:Link
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:64876 errors:0 dropped:0 overruns:0 frame:0
TX packets:23640 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7667429 (7.3 MiB) TX bytes:9050219 (8.6 MiB)
lan:0 Link encap:Ethernet HWaddr BC:05:43:93:FB:15
inet addr:169.254.1.1 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
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:947 errors:0 dropped:0 overruns:0 frame:0
TX packets:947 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:109700 (107.1 KiB) TX bytes:109700 (107.1 KiB)
wan Link encap:Ethernet HWaddr BC:05:43:93:FB:15
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:107234 errors:0 dropped:0 overruns:0 frame:0
TX packets:61232 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:88606294 (84.5 MiB) TX bytes:9341121 (8.9 MiB)
wifi0 Link encap:Ethernet HWaddr BC:05:43:93:FB:17
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:1
TX packets:1883 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:752 (752.0 B) TX bytes:516308 (504.2 KiB)
Interrupt:25 Memory:ba000000-ba010000
wifi1 Link encap:Ethernet HWaddr BC:05:43:93:FB:1B
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:63128 errors:0 dropped:0 overruns:0 frame:37751
TX packets:46841 errors:34 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10897399 (10.3 MiB) TX bytes:39988295 (38.1 MiB)
Interrupt:25 Memory:ba010000-ba020000
Can't ping tunnel endpoint anymore
And on the fritx.box (not using DSL anymore - for about two months - but a cable modem connected to LAN1):
Is that the device terminating the tunnel? As then I really wonder where the tunnel interface is.
34: dsl: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP200> mtu 1500 qlen 100 inet6 2001:1620:f00:90::2/64 scope global valid_lft forever preferred_lft forever [..]
34: dsl: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP200> mtu 1500 qdisc pfifo_fast qlen 100 link/ppp inet 192.168.178.1/32 scope global dsl
That could be it, but it has an MTU of 1500 and further down in your paste it is noted as 'link/ppp'. SixXS does not do PPP, thus that cannot be it.
Also, those are RFC1918 addresses, what devices does your NAT so that this is supposed to work?
It would additionally be useful to see routing tables.
Can't ping tunnel endpoint anymore
Shadow Hawkins on Monday, 03 September 2012 12:02:06
This ticket can be closed, problem solved (long ago)
Can't ping tunnel endpoint anymore
The ticket is closed for SixXS as it is noted to be a problem on the user side that we cannot resolve.
|
on Tuesday, 11 October 2011 09:35:41
Posting is only allowed when you are