SixXS::Sunset 2017-06-06

Some problems
[pt] Shadow Hawkins on Saturday, 20 March 2004 20:02:44
I'm trying to configure linux to act as a router behind NAT. NAT box is forwarding protocol 41 to linux box. I'm using kernel 2.6.2, and this is what I'm doing:
ip tunnel add sixxs mode sit local 192.168.0.3 remote 81.92.202.9 ip link set sixxs up ip link set mtu 1280 dev sixxs ip tunnel change sixxs ttl 64 ip -6 addr add 2001:b18:2000:b::2/64 dev sixxs ip -6 route add default via 2001:b18:2000:b::1 dev sixxs
Heartbeat configuration:
os "linux" ipv4_interface "eth0" ipv4_pop "ptlis01.sixxs.net" hb_behindnat 1 ipv6_interface "sixxs" ipv6_pop "2001:b18:2000:b::1" ipv6_local "2001:b18:2000:b::2" ipv6_prefixlen 64 hb_password "*******" hb_sendinterval 60 hb_timeout 300 daemonize 0
Tunnel information:
POP Description: NFSi - Soluções Internet, Lda. POP Location: Lisboa, Portugal POP IPv4: 81.92.202.9 Your Location: Almada, Portugal Your IPv4: heartbeat IPv6 Prefix: 2001:b18:2000:b::1/64 POP IPv6: 2001:b18:2000:b::1 Your IPv6: 2001:b18:2000:b::2 Last Alive: 2004-03-20 19:04:50 Last Dead: 2004-03-03 01:19:31 State: Heartbeat Heartbeat Password: "*******"
Pinging pop:
wizepc linux # ping6 2001:b18:2000:b::1 PING 2001:b18:2000:b::1(2001:b18:2000:b::1) 56 data bytes 64 bytes from 2001:b18:2000:b::1: icmp_seq=1 ttl=64 time=79.2 ms 64 bytes from 2001:b18:2000:b::1: icmp_seq=2 ttl=64 time=76.8 ms --- 2001:b18:2000:b::1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 76.860/78.063/79.266/1.203 ms
Pinging other ipv6 host using the same pop:
wizepc linux # 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=63 time=736 ms 64 bytes from 2001:b18:2000:2::2: icmp_seq=2 ttl=63 time=574 ms 64 bytes from 2001:b18:2000:2::2: icmp_seq=3 ttl=63 time=738 ms --- 2001:b18:2000:2::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 574.694/683.312/738.305/76.812 ms
Pinging any other ipv6 host:
wizepc linux # ping6 www.ipv6.sixxs.net PING www.ipv6.sixxs.net(2001:838:1:1:210:dcff:fe20:7c7c) 56 data bytes From 2001:b18:0:1000::1 icmp_seq=1 Destination unreachable: No route From 2001:b18:0:1000::1 icmp_seq=2 Destination unreachable: No route From 2001:b18:0:1000::1 icmp_seq=3 Destination unreachable: No route --- www.ipv6.sixxs.net ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3001ms
Traceroute:
wizepc linux # traceroute6 www.ipv6.sixxs.net traceroute to noc.ipv6.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:b18:2000:b::2, 30 hops max, 16 byte packets 1 gw-12.lis-01.pt.sixxs.net (2001:b18:2000:b::1) 87.342 ms 81.506 ms 72.041 ms 2 2001:b18:0:1000::1 (2001:b18:0:1000::1) 121.447 ms !N 94.993 ms !N 60.271 ms !N
(notice the !N) tcpdump while pinging www.ipv6.sixxs.net:
18:47:22.062552 192.168.0.3 > 81.92.202.9: 2001:b18:2000:b::2 > 2001:838:1:1:210:dcff:fe20:7c7c: icmp6: echo request (DF) 18:47:22.139619 81.92.202.9 > 192.168.0.3: 2001:b18:0:1000::1 > 2001:b18:2000:b::2: [|icmp6] 18:47:23.220792 192.168.0.3 > 81.92.202.9: 2001:b18:2000:b::2 > 2001:838:1:1:210:dcff:fe20:7c7c: icmp6: echo request (DF) 18:47:23.327516 81.92.202.9 > 192.168.0.3: 2001:b18:0:1000::1 > 2001:b18:2000:b::2: [|icmp6] 18:47:25.104432 192.168.0.3 > 81.92.202.9: 2001:b18:2000:b::2 > 2001:838:1:1:210:dcff:fe20:7c7c: icmp6: echo request (DF) 18:47:25.259108 81.92.202.9 > 192.168.0.3: 2001:b18:0:1000::1 > 2001:b18:2000:b::2: [|icmp6]
Why isn't it working?
Route not available
[ch] Jeroen Massar SixXS Staff on Saturday, 20 March 2004 20:19:06
This simply means that at the moment of your testing there was no route available to that destination.
Route not available
[pt] Shadow Hawkins on Saturday, 20 March 2004 20:34:27
So when should I expect it to be fixed?
Route not available
[pt] Shadow Hawkins on Monday, 22 March 2004 15:07:28
Still no luck... :'(
Route not available
[pt] Shadow Hawkins on Thursday, 25 March 2004 16:02:37
I believe its the same routing problem that the NFSi POP sported before the crash. I am also on this POP, and haven't got IPv6 external connection through it from over a week. I can however ping others inside this POP, like yourself: ping6 2001:b18:2000:b::2 PING 2001:b18:2000:b::2(2001:b18:2000:b::2) 56 data bytes 64 bytes from 2001:b18:2000:b::2: icmp_seq=2 ttl=62 time=1448 ms 64 bytes from 2001:b18:2000:b::2: icmp_seq=3 ttl=62 time=1469 ms 64 bytes from 2001:b18:2000:b::2: icmp_seq=4 ttl=62 time=1224 ms 64 bytes from 2001:b18:2000:b::2: icmp_seq=5 ttl=62 time=1076 ms 64 bytes from 2001:b18:2000:b::2: icmp_seq=6 ttl=62 time=1008 ms 64 bytes from 2001:b18:2000:b::2: icmp_seq=7 ttl=62 time=827 ms 64 bytes from 2001:b18:2000:b::2: icmp_seq=8 ttl=62 time=965 ms 64 bytes from 2001:b18:2000:b::2: icmp_seq=9 ttl=62 time=1115 ms 64 bytes from 2001:b18:2000:b::2: icmp_seq=10 ttl=62 time=1049 ms 64 bytes from 2001:b18:2000:b::2: icmp_seq=11 ttl=62 time=1440 ms 64 bytes from 2001:b18:2000:b::2: icmp_seq=12 ttl=62 time=1339 ms 64 bytes from 2001:b18:2000:b::2: icmp_seq=13 ttl=62 time=1262 ms 64 bytes from 2001:b18:2000:b::2: icmp_seq=14 ttl=62 time=1381 ms traceroute6 -n 2001:b18:2000:b::2 traceroute6 to 2001:b18:2000:b::2 (2001:b18:2000:b::2) from 2001:b18:2000:7::2, 64 hops max, 12 byte packets 1 2001:b18:2000:7::1 28.934 ms 29.113 ms 23.197 ms 2 2001:b18:2000:b::2 1277.080 ms 1343.466 ms 1114.215 ms Also, as it can be supposed from the Stats on the latency page (https://noc.sixxs.net/misc/latency/) and my own tests with the traceroute tool (https://noc.sixxs.net/tools/traceroute/), it seems clear that although the NFSi POP sports IPv4 connection to the world (and to the Sixxs hosts) it hasn't IPv6 world connectivity, and hasn't had it for quite some time. IPv4 traceroute to ptlis01.sixxs.net (81.92.202.9), 64 hops max, 40 byte packets 1 fe0.breda.concepts-ict.net (213.197.29.1) [AS12871] 0 ms 0 ms 0 ms 2 e3-0-1-1.nikhef.concepts-ict.net (213.197.27.5) [AS12871] 4 ms 4 ms 3 ms 3 AMS-IX.AMS-1-eth110.nl.lambdanet.net (195.69.144.212) [AS1200] 3 ms 4 ms 3 ms 4 NFSI.nl.lambdanet.net (217.71.99.14) [AS13237] 59 ms 64 ms 64 ms 5 s-2-1.cisco1.leiria.nfsi.pt (81.92.201.77) [AS25137] 62 ms 64 ms 62 ms 6 ge-0.Colo.Leiria.NFSi.pt (81.92.201.2) [AS25137] 62 ms 62 ms 61 ms 7 ptlis01.sixxs.net (81.92.202.9) [AS25137] 61 ms 61 ms 63 ms IPv6 traceroute to ptlis01.sixxs.net (2001:b18:0:1000::2) from 2001:838:1:1:210:dcff:fe20:7c7c, 30 hops max, 16 byte packets 1 fe0.breda.ipv6.concepts-ict.net (2001:838:1:1::1) 0.277 ms 0.299 ms 0.264 ms 2 se2.ams-ix.ipv6.concepts-ict.net (2001:838:0:10::1) 3.507 ms 3.402 ms 4.236 ms 3 nikhef.ams-ix.ipv6.intouch.net (2001:7f8:1::a500:8954:1) 31.862 ms 26.329 ms 32.075 ms 4 2001:7f8:1::a502:5137:1 (2001:7f8:1::a502:5137:1) 80.759 ms 72.385 ms 85.996 ms 5 2001:7f8:1::a502:5137:1 (2001:7f8:1::a502:5137:1) 67.308 ms !H 60.23 ms !H 63.553 ms !H I suppose it would be better that a POP would only appear as UP on the status page if it was reachable by both IPv4 and IPv6.
Route not available
[pt] Shadow Hawkins on Sunday, 28 March 2004 23:42:52
It seems it's working now (finally)... 8-)

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

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