Ticket ID: SIXXS #1702381 Ticket Status: User PoP: nlhaa01 - Leaseweb B.V. (Haarlem)
cannot ping PoP, no connection through tunnel
Shadow Hawkins on Monday, 17 May 2010 19:12:16
Aiccu is making a tunnel, but I cannot ping the remote end of the tunnel.
handle :pbl3-sixxs
tunnel: T19462
State change: user
Jeroen Massar on Monday, 17 May 2010 19:26:55
The state of this ticket has been changed to user
cannot ping PoP, no connection through tunnel
Jeroen Massar on Monday, 17 May 2010 19:27:23
Please provide a *lot* more details. "It is broken" is effectively all you wrote now.
cannot ping PoP, no connection through tunnel
Shadow Hawkins on Monday, 17 May 2010 21:28:18
Hello,
to be more specific:
I use aiccu on my openwrt router.
aiccu starts fine. a tunnel is created, an ipv6 address is assigned, a default route is created (same setup has worked fine for some weeks before).
#ifconfig
...
sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
-00
inet6 addr: 2001:1af8:fe00:5f::2/64 Scope:Global
inet6 addr: fe80::18f8:fe00:5f:2/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:312 (312.0 B)
# ip -6 route show
2001:1af8:fe00:5f::/64 dev sixxs metric 256 expires 21334361sec mtu 1280 advms
s 1220 hoplimit 4294967295
2001:1af8:fe97::/64 dev br-lan metric 256 expires 21325812sec mtu 1500 advmss
1440 hoplimit 4294967295
fe80::/64 dev eth0 metric 256 expires 21325802sec mtu 1500 advmss 1440 hoplimi
t 4294967295
fe80::/64 dev eth0.0 metric 256 expires 21325805sec mtu 1500 advmss 1440 hopli
mit 4294967295
fe80::/64 dev br-lan metric 256 expires 21325805sec mtu 1500 advmss 1440 hopli
mit 4294967295
fe80::/64 dev eth0.1 metric 256 expires 21325808sec mtu 1500 advmss 1440 hopli
mit 4294967295
fe80::/64 dev sixxs metric 256 expires 21334361sec mtu 1280 advmss 1220 hoplim
it 4294967295
default via 2001:1af8:fe00:5f::1 dev sixxs metric 1024 expires 21334361sec mtu
1280 advmss 1220 hoplimit 4294967295
however:
# ping6 www.sixxs.net
PING www.sixxs.net (2001:838:2:1::30:67): 56 data bytes
^C
--- www.sixxs.net ping statistics ---
9 packets transmitted, 0 packets received, 100% packet loss
and:
# ping6 2001:1af8:fe00:5f::1
PING 2001:1af8:fe00:5f::1 (2001:1af8:fe00:5f::1): 56 data bytes
^C
--- 2001:1af8:fe00:5f::1 ping statistics ---
19 packets transmitted, 0 packets received, 100% packet loss
it appears that the other end of the line isn't working properly.
kind regards,
Pieter Brouwer
(sorry about the initial post, it was not complete when I posted it)
cannot ping PoP, no connection through tunnel
Shadow Hawkins on Monday, 17 May 2010 23:01:03
ipv4 ping to the tunnel endpoint (nlhaa01.sixxs.net) doesn't work either
cannot ping PoP, no connection through tunnel
Shadow Hawkins on Tuesday, 18 May 2010 10:12:57
some more info:
traceroute ends somewhere at leaseweb.
traceroute to nlhaa01.sixxs.net (94.75.219.73), 30 hops max, 38 byte packets
1 10.210.184.1 (10.210.184.1) 7.284 ms 6.191 ms 6.257 ms
2 csw1-vlan201.assen1.dr.home.nl (213.51.132.193) 8.097 ms 7.102 ms 6.226 m
s
3 zl-rc0001-cr102-ae17-0.core.as9143.net (213.51.157.42) 7.050 ms 6.811 ms
24.256 ms
4 asd-tr0409-cr101-ae3-0.core.as9143.net (213.51.158.146) 12.933 ms 12.427 m
s 12.078 ms
5 crs-tc2.leaseweb.net (195.69.144.215) 13.928 ms 12.954 ms 13.846 ms
6 po80.hv5.evo.leaseweb.net (62.212.80.78) 13.197 ms 13.668 ms 13.334 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
cannot ping PoP, no connection through tunnel
Shadow Hawkins on Tuesday, 18 May 2010 20:10:41
All is well again.
Posting is only allowed when you are logged in. |