|
Ticket ID: SIXXS #587048 Ticket Status: User PoP: sesto01 - Availo (Stockholm)
Tunnel endpoint 2001:16d8:ff00:cd::2 didn't ping for 17 days
![[no]](/s/countries/no.gif) Shadow Hawkins on Thursday, 04 October 2007 16:15:24
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
Im loosing points because of no ping when i got the tunnel up running.
Result using your tracerout.
IPv6 traceroute from noc.sixxs.net @ SixXS NOC, AS12871 to 2001:16d8:ff00:cd::2 :
Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation
1. 2001:838:1:1::1 0.0% 5 0.4 0.4 0.4 0.5 0.0 [.nl] Netherlands, The 12871 Concepts ICT
ge-1-3-0.breda.ipv6.concepts-ict.net.
2. 2001:838:0:10::1 0.0% 5 2.5 2.4 2.3 2.5 0.1 [.nl] Netherlands, The 12871 Concepts ICT
3. 2001:7f8:1::a500:3549:1 0.0% 5 3.1 3.6 2.9 5.2 0.9
eth10-0-0.xr1.ams1.gblx.net.
4. 2001:450:2001:1000:0:670:170 0.0% 5 28.4 30.3 28.4 37.6 4.1 [.us] United States Global Crossing
5. 2001:450:2002:17::2 0.0% 5 28.9 29.9 28.0 36.2 3.5 [.us] United States Global Crossing
6. 2001:16d8:2::a 0.0% 5 28.7 28.8 28.7 28.9 0.1 [.se] Sweden 16150 Port80 AB
7. 2001:16d8:ff00:cd::2 0.0% 5 56.7 56.7 56.4 56.9 0.2 [.no] Norway 16150 Port80 AB
cl-206.sto-01.se.sixxs.net.
State change: user
The state of this ticket has been changed to user
Tunnel endpoint 2001:16d8:ff00:cd::2 didn't ping for 17 days
You clearly did not read and followed the "Reporting Problems" section on the Contact page and are not providing the requested details.
Please do so as a traceroute doesn't say a thing. Also check the FAQ, most very likely the one about Connection Tracking applies to you.
Tunnel endpoint 2001:16d8:ff00:cd::2 didn't ping for 17 days
Shadow Hawkins on Friday, 05 October 2007 17:52:28
Description
Tracing from all other then my PoP as source using https://noc.sixxs.net/tools/traceroute/ is giving result but with sesto01 it want give any thing on IPv6, but it will give trace for IPv4.
On IPv4 i got firewall but have opened all subnet from PortAB and nothing have been changed for the past year there. And tracing over IPv4 looks fine from PoP.
No firewall for IPv6
Checked "Connection Tracking" and other topics in FAQ and cant find any problem on my side of the tunnel.
Other requested info:
NIC Handle: egb2-6bone
Mail: espen^AT^borgso^DOT^net
Tunnel: T8445
Subnet: R3316
PoP: sesto01 - Port80 AB
Setup: No NAT, direct to internet with IPv4 endpoint
ip tunnel add sixxs mode sit local $END remote 82.96.56.14
ip link set sixxs up
ip link set mtu 1280 dev sixxs
ip tunnel change sixxs ttl 64
ip -6 addr add 2001:16d8:ff00:cd::/64 dev sixxs
ip -6 addr add 2001:16d8:ff00:cd::1/64 dev sixxs
ip -6 addr add 2001:16d8:ff00:cd::2/64 dev sixxs
ip addr add 2001:16d8:ff89::/48 dev sixxs
ip -6 route add default dev sixxs
route -A inet6 add ::/0 gw fe80::c171:3a50 dev sixxs
route -A inet6 add 2000::/3 gw fe80::c171:3a50 dev sixxs
Firewall, only IPv4. No change since it was going like it is now. Just added this lines to test:
iptables -t raw -A PREROUTING --proto 41 -j NOTRACK
iptables -A INPUT -s 82.96.56.0/24 -j ACCEPT
iptables -A INPUT -s 82.96.0.0/18 -j ACCEPT
iptables -A INPUT -s 82.96.48.0/20 -j ACCEPT
iptables -A INPUT -s 82.96.32.0/19 -j ACCEPT
Interfaces:
sixxs Link encap:UNSPEC HWaddr 54-34-FF-7B-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: 2001:16d8:ff89::1001/48 Scope:Global
inet6 addr: 2001:16d8:ff89::/48 Scope:Global
inet6 addr: 2001:16d8:ff00:cd::/64 Scope:Global
inet6 addr: 2001:16d8:ff89::1/48 Scope:Global
inet6 addr: 2001:16d8:ff00:cd::1/64 Scope:Global
inet6 addr: 2001:16d8:ff00:cd::2/64 Scope:Global
inet6 addr: 2001:16d8:ff89::2007/48 Scope:Global
inet6 addr: fe80::5434:ff7b/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:67 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6968 (6.8 KiB) TX bytes:1488 (1.4 KiB)
eth0 Link encap:Ethernet HWaddr 00:00:E8:99:93:84
inet addr:84.52.255.123 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::200:e8ff:fe99:9384/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18349992 errors:7 dropped:0 overruns:0 frame:9
TX packets:21813612 errors:0 dropped:0 overruns:7 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3925510816 (3.6 GiB) TX bytes:20433325 (19.4 MiB)
Interrupt:10 Base address:0xac00
Source: https://noc.sixxs.net/archive/sixxs/aiccu/unix/aiccu_current.tar.gz
Using: "./aiccu test" all test passes OK
OS: Slackware-12 Linux HOSTNAME 2.6.22.9 #1 SMP Tue Oct 2 14:39:39 CEST 2007 i686 AMD Athlon(tm) processor AuthenticAMD GNU/Linux
####### AICCU Quick Connectivity Test
Tunnel Information for T8445:
POP Id : sesto01
IPv6 Local : 2001:16d8:ff00:cd::2/64
IPv6 Remote : 2001:16d8:ff00:cd::1/64
Tunnel Type : 6in4-static
Adminstate : enabled
Userstate : enabled
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (84.52.255.123)
PING 84.52.255.123 (84.52.255.123) 56(84) bytes of data.
64 bytes from 84.52.255.123: icmp_seq=1 ttl=64 time=0.185 ms
64 bytes from 84.52.255.123: icmp_seq=2 ttl=64 time=0.142 ms
64 bytes from 84.52.255.123: icmp_seq=3 ttl=64 time=0.142 ms
--- 84.52.255.123 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.142/0.156/0.185/0.022 ms
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (82.96.56.14)
PING 82.96.56.14 (82.96.56.14) 56(84) bytes of data.
64 bytes from 82.96.56.14: icmp_seq=1 ttl=56 time=28.1 ms
64 bytes from 82.96.56.14: icmp_seq=2 ttl=56 time=28.1 ms
64 bytes from 82.96.56.14: icmp_seq=3 ttl=56 time=28.2 ms
--- 82.96.56.14 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 28.175/28.191/28.210/0.137 ms
####### [3/8] Traceroute to the PoP (82.96.56.14) over IPv4
traceroute to 82.96.56.14 (82.96.56.14), 30 hops max, 38 byte packets
1 84.52.255.1 (84.52.255.1) 7.943 ms 12.025 ms 4.063 ms
2 84.52.198.41.3p.ntebb.no (84.52.198.41) 0.450 ms 0.562 ms 0.404 ms
3 121.213-167-114.customer.lyse.net (213.167.114.121) 174.400 ms 199.240 ms 1.693 ms
4 17.213-167-114.customer.lyse.net (213.167.114.17) 9.436 ms 9.388 ms 9.315 ms
5 * * *
6 port80.ge-2-0-0.407ar1.ARN1.gblx.net (207.138.144.102) 27.370 ms 27.607 ms 27.272 ms
7 hy-cr1-r87.sto.se.p80.net (217.75.100.87) 27.673 ms 27.643 ms 27.856 ms
8 sixxs.port80.se (82.96.56.14) 28.166 ms 28.072 ms 27.895 ms
###### [4/8] Checking if we can ping IPv6 localhost (::1)
PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.112 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.097 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.082 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.082/0.097/0.112/0.012 ms
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:16d8:ff00:cd::2)
PING 2001:16d8:ff00:cd::2(2001:16d8:ff00:cd::2) 56 data bytes
64 bytes from 2001:16d8:ff00:cd::2: icmp_seq=1 ttl=64 time=0.114 ms
64 bytes from 2001:16d8:ff00:cd::2: icmp_seq=2 ttl=64 time=0.097 ms
64 bytes from 2001:16d8:ff00:cd::2: icmp_seq=3 ttl=64 time=0.155 ms
--- 2001:16d8:ff00:cd::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.097/0.122/0.155/0.024 ms
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:16d8:ff00:cd::1)
PING 2001:16d8:ff00:cd::1(2001:16d8:ff00:cd::1) 56 data bytes
64 bytes from 2001:16d8:ff00:cd::1: icmp_seq=1 ttl=64 time=28.2 ms
64 bytes from 2001:16d8:ff00:cd::1: icmp_seq=2 ttl=64 time=28.2 ms
64 bytes from 2001:16d8:ff00:cd::1: icmp_seq=3 ttl=64 time=28.4 ms
--- 2001:16d8:ff00:cd::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 28.258/28.321/28.446/0.213 ms
###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:16d8:ff00:cd::2, 30 hops max, 16 byte packets
1 gw-206.sto-01.se.sixxs.net (2001:16d8:ff00:cd::1) 28.42 ms 28.385 ms 28.273 ms
2 ge1-sto.cr1.hy-sto.se.p80.net (2001:16d8:2::81) 28.46 ms 28.563 ms 28.503 ms
3 2001:16d8:2::86 (2001:16d8:2::86) 28.645 ms 250.605 ms 37.515 ms
4 2001:450:2002:17::1 (2001:450:2002:17::1) 38.746 ms 28.882 ms 28.755 ms
5 eth10-0-0.xr1.ams1.gblx.net (2001:7f8:1::a500:3549:1) 54.494 ms 57.024 ms 54.98 ms
6 ams-ix.ipv6.concepts.nl (2001:7f8:1::a501:2871:1) 54.645 ms 54.983 ms 54.805 ms
7 2001:838:0:10::2 (2001:838:0:10::2) 56.986 ms 84.199 ms 56.84 ms
8 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 56.612 ms 56.687 ms 56.497 ms
###### [8/8] Traceroute6 to (www.kame.net)
traceroute to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:16d8:ff00:cd::2, 30 hops max, 16 byte packets
1 gw-206.sto-01.se.sixxs.net (2001:16d8:ff00:cd::1) 28.561 ms 28.19 ms 28.101 ms
2 ge1-sto.cr1.hy-sto.se.p80.net (2001:16d8:2::81) 28.579 ms 28.629 ms 28.64 ms
3 2001:16d8:2::86 (2001:16d8:2::86) 28.562 ms 28.726 ms 29.448 ms
4 2001:450:2002:17::1 (2001:450:2002:17::1) 28.953 ms 29.004 ms 28.983 ms
5 2001:cc8:102:5::2 (2001:cc8:102:5::2) 215.248 ms 207.393 ms 207.227 ms
6 2001:cc8:102:5::2 (2001:cc8:102:5::2) 371.258 ms 399.342 ms 224.357 ms
7 2001:cc8:102:5::1 (2001:cc8:102:5::1) 532.23 ms 403.941 ms 451.141 ms
8 hitachi1.otemachi.wide.ad.jp (2001:200:0:1800::9c4:2) 409.8 ms 427.084 ms 428.404 ms
9 2001:200:0:1802:20c:dbff:fe1f:7200 (2001:200:0:1802:20c:dbff:fe1f:7200) 396.321 ms * 321.872 ms
10 ve44.foundry4.nezu.wide.ad.jp (2001:200:0:3::102) 326.884 ms 328.027 ms 328.89 ms
11 pc3.nezu.wide.ad.jp (2001:200:0:1c04:250:4ff:febc:7cd6) 328.956 ms 328.613 ms 328.118 ms
12 ve-4.nec2.yagami.wide.ad.jp (2001:200:0:1c04:230:13ff:feae:5b) 412.364 ms 324.434 ms 324.789 ms
13 lo0.alaxala1.k2.wide.ad.jp (2001:200:0:4800::7800:1) 324.409 ms 325.258 ms 325.853 ms
14 orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) 328.54 ms 329.082 ms 326.936 ms
###### ACCU Quick Connectivity Test (done)
Tunnel endpoint 2001:16d8:ff00:cd::2 didn't ping for 17 days
Shadow Hawkins on Saturday, 13 October 2007 12:47:38
The tunnel is disabled at the moment, but see your tunnel information page it clearly showed no response for the time that your tunnel was enabled and also a week later.
ip tunnel add sixxs mode sit local $END remote 82.96.56.14 ip link set sixxs up ip link set mtu 1280 dev sixxs ip tunnel change sixxs ttl 64
So far so good, now comes a lot of junk that doesn't make sense
ip -6 addr add 2001:16d8:ff00:cd::/64 dev sixxs
That is the subnet anycast address, you really don't need to add that locally, IPv6 does that automatically.
ip -6 addr add 2001:16d8:ff00:cd::1/64 dev sixxs
That is the PoP side of the tunnel. This is why the PoP can't ping you back as when you respond the packets arrive locally.
ip -6 addr add 2001:16d8:ff00:cd::2/64 dev sixxs
That is your end, and also the only IP address that should be assigned on this tunnel.
ip addr add 2001:16d8:ff89::/48 dev sixxs
/48 prefixed IP addresses don't make sense. Also in effect you are routing the full /48 back up the internet. Did you follow the "1 step to create routing loops" FAQ of some strange site?
ip -6 route add default dev sixxs
That should be 'ip -6 ro add default via 2001:16d8:ff00:cd::1', thus via the PoP. The above causes the packets simply to be dumped on the tunnel interface. The PoP will never see them
route -A inet6 add ::/0 gw fe80::c171:3a50 dev sixxs route -A inet6 add 2000::/3 gw fe80::c171:3a50 dev sixxs
These two don't make sense at all. They might work sometimes, as the PoP might assign those addresses on it's interface (due to autoconfig), but as we didn't define them they might just as well change.
Clean up and fix your configuration, as that is the problem.
|
![[ch]](/s/countries/ch.gif)
on Thursday, 04 October 2007 16:37:16
Posting is only allowed when you are