SixXS::Sunset 2017-06-06

No ICMP6 echo reply from PoP
[de] Shadow Hawkins on Thursday, 19 April 2007 18:11:40
Hi there, my tunnel has just been approved. I configured the tunnel with the given information on Debian etch (Sparc): auto sixxs iface sixxs inet6 v4tunnel address 2001:6f8:900:886::2 netmask 64 endpoint 212.224.0.188 ttl 64 up ip link set mtu 1280 dev sixxs up ip route add default via 2001:6f8:900:886::1 dev sixxs ifconfig tells me (sorry, german locale): sixxs Protokoll:IPv6-nach-IPv4 inet6 Adresse: 2001:6f8:900:886::2/64 Gültigkeitsbereich:Global inet6 Adresse: fe80::a00:6464/64 Gültigkeitsbereich:Verbindung inet6 Adresse: fe80::c0a8:6464/64 Gültigkeitsbereich:Verbindung UP PUNKTZUPUNKT RUNNING NOARP MTU:1280 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:266 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:0 (0.0 b) TX bytes:29215 (28.5 KiB) That's the output of "ip addr show": 6: sixxs@NONE: <POINTOPOINT,NOARP,UP,10000> mtu 1280 qdisc noqueue link/sit 0.0.0.0 peer 212.224.0.188 inet6 2001:6f8:900:886::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::a00:6464/64 scope link valid_lft forever preferred_lft forever inet6 fe80::c0a8:6464/64 scope link valid_lft forever preferred_lft forever IMHO this looks quite good. Unfortunately, the PoP doesn't respond to ICMP echo requests (from tcpdump-ni ppp0 proto 41) despite the fact that iptables accepts proto 41 from anywhere: 17:59:51.567623 IP 87.79.236.146 > 212.224.0.188: IP6 2001:6f8:900:886::2 > 2001:6f8:900:886::1: ICMP6, echo request, seq 1, length 64 17:59:52.577068 IP 87.79.236.146 > 212.224.0.188: IP6 2001:6f8:900:886::2 > 2001:6f8:900:886::1: ICMP6, echo request, seq 2, length 64 17:59:53.577135 IP 87.79.236.146 > 212.224.0.188: IP6 2001:6f8:900:886::2 > 2001:6f8:900:886::1: ICMP6, echo request, seq 3, length 64 [...] Am I missing something? The Tunnelrobot wrote: "The SixXS PoP at AS4589 will set up the tunnel automatically in the next hour. Please be patient and do not be alarmed if the tunnel does not ping after you enabled it." That was yesterday at 22:22 UTC. Do I have to wait some more time, or is there something wrong with my setup? regards, Marcel
No ICMP6 echo reply from PoP
[de] Shadow Hawkins on Friday, 20 April 2007 10:46:31
Hi, Problem is solved now. It seems, I was too impatient. After enabling the tunnel it seems it takes some time, for get the thing up and running. regards, Marcel

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker