SixXS::Sunset 2017-06-06

only replies the endpoint
[es] Carmen Sandiego on Friday, 16 January 2004 21:41:32
hi all: I have a problem with my tunnel, only my endpoint and "myself" seems to reply to ping. I was checking posts in this forum to try to fix the problem but I didn't. I use debian unstable with linux 2.4.24. I'm behind DSL connection. this is the content in /etc/network/interfaces iface sixxs inet6 v4tunnel address 2001:b18:2000:2::2 netmask 64 endpoint 81.92.202.9 ttl 64 up ip link set mtu 1280 dev sixxs up ip route add 2000::/3 via 2001:b18:2000:2::1 dev sixxs [21:33] <manuel@gada> /root/sixxs $ ip link list sixxs 14: sixxs@NONE: <POINTOPOINT,NOARP,PROMISC,UP> mtu 1280 qdisc noqueue link/sit 0.0.0.0 peer 81.92.202.9 [21:33] <manuel@gada> /root/sixxs $ ip address list sixxs 14: sixxs@NONE: <POINTOPOINT,NOARP,PROMISC,UP> mtu 1280 qdisc noqueue link/sit 0.0.0.0 peer 81.92.202.9 inet6 2001:b18:2000:2::2/64 scope global inet6 fe80::c0a8:2/64 scope link [21:33] <manuel@gada> /root/sixxs $ ip -6 route list 2000::/3 via 2001:b18:2000:2::1 dev sixxs metric 1024 mtu 1280 advmss 1220 fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220 fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220 ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220 unreachable default dev lo proto none metric -1 error -101 advmss 1220 and the commands: [21:35] <manuel@gada> /root/sixxs $ ping6 2001:b18:2000:2::1 PING 2001:b18:2000:2::1(2001:b18:2000:2::1) 56 data bytes 64 bytes from 2001:b18:2000:2::1: icmp_seq=1 ttl=64 time=197 ms 64 bytes from 2001:b18:2000:2::1: icmp_seq=2 ttl=64 time=196 ms 64 bytes from 2001:b18:2000:2::1: icmp_seq=3 ttl=64 time=190 ms --- 2001:b18:2000:2::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2022ms rtt min/avg/max/mdev = 190.590/194.822/197.074/2.994 ms [21:37] <manuel@gada> /root/sixxs $ ping6 2001:b18:2000:2::2 PING 2001:b18:2000:2::2(2001:b18:2000:2::2) 56 data bytes 64 bytes from 2001:b18:2000:2::2: icmp_seq=1 ttl=64 time=0.110 ms 64 bytes from 2001:b18:2000:2::2: icmp_seq=2 ttl=64 time=0.095 ms 64 bytes from 2001:b18:2000:2::2: icmp_seq=3 ttl=64 time=0.099 ms --- 2001:b18:2000:2::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 0.095/0.101/0.110/0.010 ms [21:37] <manuel@gada> /root/sixxs $ ping6 www.kame.net PING www.kame.net(orange.kame.net) 56 data bytes --- www.kame.net ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4016ms tcpdump output meanwhile: 21:37:28.884159 2001:b18:2000:2::2 > 2001:b18:2000:2::1: icmp6: echo request 21:37:29.081166 2001:b18:2000:2::1 > 2001:b18:2000:2::2: icmp6: echo reply 21:37:29.896670 2001:b18:2000:2::2 > 2001:b18:2000:2::1: icmp6: echo request 21:37:30.093413 2001:b18:2000:2::1 > 2001:b18:2000:2::2: icmp6: echo reply 21:37:30.906580 2001:b18:2000:2::2 > 2001:b18:2000:2::1: icmp6: echo request 21:37:31.097112 2001:b18:2000:2::1 > 2001:b18:2000:2::2: icmp6: echo reply 21:37:39.669213 2001:b18:2000:2::2 > 2001:200:0:8002:203:47ff:fea5:3085: icmp6: echo request 21:37:40.685657 2001:b18:2000:2::2 > 2001:200:0:8002:203:47ff:fea5:3085: icmp6: echo request 21:37:41.685584 2001:b18:2000:2::2 > 2001:200:0:8002:203:47ff:fea5:3085: icmp6: echo request 21:37:42.685488 2001:b18:2000:2::2 > 2001:200:0:8002:203:47ff:fea5:3085: icmp6: echo request 21:37:43.685450 2001:b18:2000:2::2 > 2001:200:0:8002:203:47ff:fea5:3085: icmp6: echo request any idea? thanks in advance :)
only replies the endpoint
[pt] Shadow Hawkins on Friday, 16 January 2004 23:50:22
I'm seeing precisely the same thing here. I notice we both use the same IPv6 ISP (2001:b18:2000 NFSi, in Portugal) so I guess is something in the routing tables of the ISP... Does anyone know a way to contact the ISP endpoint? Regards, Paulo
only replies the endpoint
[es] Carmen Sandiego on Saturday, 17 January 2004 00:20:20
yes, it's that POP. I also had some problems the day that I enabled the tunnel. it was for several hours that the endpoint itself didn't reply to the ping, much more than those 15mins that the faq talks about. in fact I decided to stop trying for 1 week +-, till yesterday, when I tried to ping again and it worked. I don't know what's the problem, as you can see in the explanations, but it also could be some kind of problem/delay from the POP..? brigadão Paulo! bye all!
only replies the endpoint
[pt] Shadow Hawkins on Saturday, 17 January 2004 00:42:52
I really do believe its something with the POP routing tables (or firewall), since I am able to ping YOU: # ping6 2001:b18:2000:2::2 PING6(56=40+8+8 bytes) 2001:b18:2000:7::2 --> 2001:b18:2000:2::2 16 bytes from 2001:b18:2000:2::2, icmp_seq=0 hlim=63 time=369.055 ms 16 bytes from 2001:b18:2000:2::2, icmp_seq=1 hlim=63 time=306.129 ms 16 bytes from 2001:b18:2000:2::2, icmp_seq=2 hlim=63 time=638.129 ms 16 bytes from 2001:b18:2000:2::2, icmp_seq=3 hlim=63 time=605.647 ms 16 bytes from 2001:b18:2000:2::2, icmp_seq=4 hlim=63 time=407.048 ms 16 bytes from 2001:b18:2000:2::2, icmp_seq=5 hlim=63 time=657.232 ms ^C --- 2001:b18:2000:2::2 ping6 statistics --- 6 packets transmitted, 6 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 306.129/497.207/657.232/140.409 ms However, I cannot, for instance, ping www.sixxs.net: sinfonia# ping6 www.sixxs.net PING6(56=40+8+8 bytes) 2001:b18:2000:7::2 --> 2001:838:1:1:210:dcff:fe20:7c7c ^C --- noc.sixxs.net ping6 statistics --- 6 packets transmitted, 0 packets received, 100.0% packet loss That means either the routing table of the host we connect to is wrong, since we cannot reach outside nodes, or there is some sort of mechanism at work (a firewall?) preventing us to reach out. Regards, Paulo
only replies the endpoint
[es] Carmen Sandiego on Saturday, 17 January 2004 00:51:08
I also can to ping you, and: [00:46] <root@gada> ~/sixxs # tracepath6 2001:b18:2000:7::2 1?: [LOCALHOST] pmtu 1280 1: gw-3.lis-01.pt.sixxs.net 383.429ms 2: cl-8.lis-01.pt.sixxs.net 428.746ms reached Resume: pmtu 1280 hops 2 back 2 so as you say, routes or some other problem are preventing us from seeing the light! :{

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

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