Ticket ID: SIXXS #792513 Ticket Status: Resolved PoP: fihel01 - DNA Oy (Helsinki)
Some destinations unreachable, bad routes?
Shadow Hawkins on Monday, 25 August 2008 20:53:28
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:
* Always include clear descriptive information about your problem or inquiry.
Some destinations that were previously reachable are now unreachable. The problem started some time this morning.
* When on a UNIX-alike platform that supports AICCU, please run AICCU and run it using "aiccu test".
* When using AICCU, check that you are using the latest version, and of course please specify where the binary comes from.
The tunnel is up and works. My routes are set up correctly and not changed.
* Always provide your NIC handle and if applicable the Tunnel or Route IDs you wish to discuss.
JK22-SIXXS. This problem applies to other users and tunnels as well so not applicable.
* Use the email address you have provided in your handle as that is what we use as a contact handle.
* Provide details of the setup, type of connections, where NATs are located.
I have a Linux router with a static tunnel to fihel01. No NATs are applicable. The connection is TeliaSonera Laajakaista Extra 24/2 Mbit/s, DHCP, bridged.
* Provide information of your OS type, version and release (ie. uname -a), noting also the distribution name.
joneskoo@hansu:~$ uname -a
Linux hansu.m5.yx.fi 2.6.26 #1 SMP Thu Jul 17 17:25:25 EEST 2008 i686 GNU/Linux
joneskoo@hansu:~$ cat /etc/debian_version
4.0
* Include full interface, routing and firewall tables.
joneskoo@hansu:~$ ip link
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: tunl0: <NOARP> mtu 1480 qdisc noop
link/ipip 0.0.0.0 brd 0.0.0.0
3: gre0: <NOARP> mtu 1476 qdisc noop
link/gre 0.0.0.0 brd 0.0.0.0
4: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
5: ip6tnl0: <NOARP> mtu 1460 qdisc noop
link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
6: ge0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:07:e9:0e:92:ce brd ff:ff:ff:ff:ff:ff
7: fe0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc htb qlen 1000
link/ether 00:13:d3:c8:25:c1 brd ff:ff:ff:ff:ff:ff
8: br0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:07:e9:0e:92:ce brd ff:ff:ff:ff:ff:ff
9: vlan20@br0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:07:e9:0e:92:ce brd ff:ff:ff:ff:ff:ff
10: brwan: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:07:e9:0e:92:ce brd ff:ff:ff:ff:ff:ff
11: vlan10@br0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:07:e9:0e:92:ce brd ff:ff:ff:ff:ff:ff
13: vlan100@br0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:07:e9:0e:92:ce brd ff:ff:ff:ff:ff:ff
14: sixxs@NONE: <POINTOPOINT,NOARP,UP,10000> mtu 1480 qdisc noqueue
link/sit 80.222.132.176 peer 62.78.96.38
20: vlan50@br0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:07:e9:0e:92:ce brd ff:ff:ff:ff:ff:ff
joneskoo@hansu:~$ ip -6 route
2001:14b8:100:202::/64 via :: dev sixxs metric 256 mtu 1480 advmss 1420 hoplimit 4294967295
2001:14b8:182::/64 dev vlan10 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
2001:14b8:182::/64 dev vlan10 metric 1024 mtu 1500 advmss 1440 hoplimit 4294967295
unreachable 2001:14b8:182::/48 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
2002:d58b:a7dc:3::/64 dev vlan50 proto zebra metric 1 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev br0 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev ge0 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev vlan20 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev fe0 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev brwan metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev vlan10 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev vlan100 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 via :: dev sixxs metric 256 mtu 1480 advmss 1420 hoplimit 4294967295
fe80::/64 dev vlan50 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
default dev sixxs metric 1024 mtu 1480 advmss 1420 hoplimit 4294967295
joneskoo@hansu:~$ sudo ip6tables -L -v -n
Chain INPUT (policy ACCEPT 4173K packets, 417M bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 6086K packets, 4775M bytes)
pkts bytes target prot opt in out source destination
* Include a IPv4 and IPv6 traceroute to the PoP in question.
traceroute to fihel01.sixxs.net (62.78.96.38), 30 hops max, 40 byte packets
1 dsl-olubrasgw1-fe40fb00-1.dhcp.inet.fi (84.251.64.1) 41.292 ms 4.777 ms 4.208 ms
2 141.208.151.153 (141.208.151.153) 4.252 ms 4.590 ms 3.910 ms
3 olucore1-e-0-1-0.datanet.tele.fi (141.208.12.145) 4.624 ms 4.668 ms 4.970 ms
4 hkicore1-e-1-1-0.datanet.tele.fi (141.208.8.1) 15.908 ms 15.971 ms 15.695 ms
5 hkiasbr1-s-0-0-0.datanet.tele.fi (141.208.8.10) 15.711 ms * 15.806 ms
6 dna.ficix1-ge.ficix.fi (193.110.226.20) 15.962 ms 16.372 ms 16.224 ms
7 van5r6.k.fv.fi (217.78.198.239) 16.560 ms 16.651 ms 16.739 ms
8 fihel01.sixxs.net (62.78.96.38) 16.495 ms 16.567 ms 16.734 ms
traceroute to fihel01.sixxs.net (2001:14b8:0:3007::6) from 2001:14b8:100:202::2, 30 hops max, 16 byte packets
1 fihel01.sixxs.net (2001:14b8:0:3007::6) 17.198 ms 16.969 ms 16.801 ms
* With heartbeat tunnels, first check clock synchronization or better: use AICCU.
Static tunnel.
* Check with Wireshark or tcpdumps of the interface over which the tunnel runs.
Use -n (numeric) as an option and don't filter returning ICMP which could also come from routers between your endpoint and the PoP and also use -s 1500 so that one gets the full packet.
* The status of the PoP is listed on the PoP Status page, if it is marked down there we are aware of the issue and we will try to resolve it as soon as possible. Additionally other issues are listed in the Ticket Tracker Ticket Tracker.
* We are not your personal helpdesk, thus first read the FAQ and/or use the forum, many cases can already be solved that way, but we do want to have you actually use the tunnel thus do contact us if the problem persists.
I don't think the forum is applicable in this scenario.
----------------------------
So here's the problem after the simple checklist. These worked before:
joneskoo@hansu:~$ curl -v http://stream.ipv6.frequence3.net:19000/frequence3.ogg
* About to connect() to stream.ipv6.frequence3.net port 19000
* Trying 2001:688:0:13::1...
(halts)
joneskoo@hansu:~$ ssh -v xob.kapsi.fi
OpenSSH_4.3p2 Debian-9etch2, OpenSSL 0.9.8c 05 Sep 2006
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to xob.kapsi.fi [2001:670:a0:17::2] port 22.
(halts)
(from xob.kapsi.fi)
traceroute to joneskoo.dy.fi (2001:14b8:100:202::2) from 2001:670:a0:17::3, 30 hops max, 24 byte packets
1 2001:670:a0:17::1 (2001:670:a0:17::1) 0.443 ms 0.779 ms 0.439 ms
2 ge0-1-0-997.bbr1.hel2.fi.v6.eunetip.net (2001:670:3:8::13) 0.813 ms 0.731 ms 0.77 ms
3 ge0-1-0-997.bbr1.hel2.fi.v6.eunetip.net (2001:670:3:8::13) 0.732 ms 0.846 ms 0.724 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
No ping6 response.
This route used to be quite short, over FICIX I think.
joneskoo@lakka:~$ traceroute6 joneskoo.dy.fi
traceroute to joneskoo.dy.fi (2001:14b8:100:202::2) from 2001:1bc8:1004::1, 30 hops max, 24 byte packets
1 ipv6-gw.kapsi.fi (2001:1bc8:1004::fffe) 0.559 ms 0.317 ms 0.324 ms
2 r4-v799.hki.nbl.fi (2001:1bc8:1:2::2) 0.449 ms 0.278 ms 0.286 ms
3 2001:450:2002:35::1 (2001:450:2002:35::1) 7.949 ms 7.952 ms 8.042 ms
4 e0-0-0.6b2.AMS7.Alter.net (2001:7f8:1::a501:2702:1) 30.759 ms 31.733 ms 32.167 ms
5 * * *
6 * * *
7 cl-515.hel-01.fi.sixxs.net (2001:14b8:100:202::2) 54.249 ms 54.716 ms 54.182 ms
In conclusion, I think DNA has some broken routes.
State change: confirmed
Jeroen Massar on Monday, 25 August 2008 21:05:00
The state of this ticket has been changed to confirmed
State change: resolved
Jeroen Massar on Tuesday, 26 August 2008 20:45:39
The state of this ticket has been changed to resolved
Some destinations unreachable, bad routes?
Jeroen Massar on Tuesday, 26 August 2008 20:46:23
Linkup to AS12702 was causing these issues, currently disabled until further investigations complete.
Posting is only allowed when you are logged in. |