|
Ticket ID: SIXXS #2959001 Ticket Status: Resolved PoP: fihel01 - DNA Oy (Helsinki)
Connection to PoP lost
![[fi]](/s/countries/fi.gif) Shadow Hawkins on Friday, 05 November 2010 08:12:09
Hi,
First time reporting a ticket, but here goes nothing:
It seems that my connection to my PoP is cut. For example when I try to connect to some other IPv6 server for any reason, the connection times out.
"From fihel01.sixxs.net icmp_seq=2 Destination unreachable: No route"
The problem occured yesterday, I think. It started as connection going on and off every couple of minutes, but now there's no connection at all. PoP is up and running according to the PoPs-page.
AICCU stop and AICCU start didn't resolve the problem, neither did the reboot of my server.
NIC handle: MLO3-SIXXS
Tunnel NameMy First Tunnel
PoP Namefihel01
PoP LocationHelsinki, Finland Finland
PoP IPv462.78.96.38
TIC Servertic.sixxs.net (default in AICCU)
Your LocationHelsinki, Finland Finland
Your IPv4AYIYA
IPv6 Prefix2001:14b8:100:282::1/64
PoP IPv62001:14b8:100:282::1
Your IPv62001:14b8:100:282::2
Created2009-10-28 16:31:05 CET
Last Alive2010-11-04 08:53:02 CET
StateAYIYA (automatically enabled on the fly)
Oh and about my setup: I'm sure everything is set-up just fine, since everything has been okay for a long time. If it helps, I'm running an Ubuntu server (lucid) where AICCU resides.
Everything works just fine before this in aiccu test:
[6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:14b8:100:282::1)
--- 2001:14b8:100:282::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2016ms
#######
[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:14b8:100:282::2, 30 hops max, 16 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
#######
[8/8] Traceroute6 to (www.kame.net)
traceroute to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2001:14b8:100:282::2, 30 hops max, 16 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
...
#######
Here's the rest of the stuff, as response to:
iptables -nvL ; ip6tables -nvL ip -4 route ; ip -6 route ;ifconfig
Chain INPUT (policy ACCEPT 16803 packets, 2557K bytes)
pkts bytes target prot opt in out source destination
13190 1001K fail2ban-ssh-ddos tcp -- * * 0.0.0.0/0 0.0.0.0/0 multiport dports 22
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 16098 packets, 2837K bytes)
pkts bytes target prot opt in out source destination
Chain fail2ban-ssh-ddos (1 references)
pkts bytes target prot opt in out source destination
13190 1001K RETURN all -- * * 0.0.0.0/0 0.0.0.0/0
ip6tables v1.4.4: option `-4' requires an argument
Try `ip6tables -h' or 'ip6tables --help' for more information.
2001:14b8:100:282::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev br0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
default via 2001:14b8:100:282::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 0
br0 Link encap:Ethernet HWaddr 00:09:6b:9d:65:2c
inet addr:192.168.100.200 Bcast:192.168.100.255 Mask:255.255.255.0
inet6 addr: fe80::209:6bff:fe9d:652c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26546 errors:0 dropped:0 overruns:0 frame:0
TX packets:16396 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4028742 (4.0 MB) TX bytes:3082100 (3.0 MB)
eth0 Link encap:Ethernet HWaddr 00:09:6b:9d:65:2c
inet6 addr: fe80::209:6bff:fe9d:652c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26582 errors:0 dropped:0 overruns:0 frame:0
TX packets:16390 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4427012 (4.4 MB) TX bytes:3081232 (3.0 MB)
eth1 Link encap:Ethernet HWaddr 00:0e:2e:3b:8b:aa
UP BROADCAST PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:20 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:66 errors:0 dropped:0 overruns:0 frame:0
TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6309 (6.3 KB) TX bytes:6309 (6.3 KB)
sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: 2001:14b8:100:282::2/64 Scope:Global
inet6 addr: fe80::14b8:100:282:2/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:144 (144.0 B)
T38209 on fihel01 doesn't work
Shadow Hawkins on Friday, 05 November 2010 08:20:00
Maybe two days ago my tunnel T38209 on fihel01 stopped working. I'm running openwrt backfire 10.03 and haven't changed anything in the router, so I'm suspecting this is an issue in the PoP.
When I try to ping the PoP's end of tunnel (2001:14b8:100:2a6::1), I see this on the router's interface connected to the adsl modem:
8:56:00.693292 IP a85-156-250-252.elisa-laajakaista.fi > fihel01.sixxs.net: IP6 cl-679.hel-01.fi.sixxs.net > gw-679.hel-01.fi.sixxs.net: ICMP6, echo request, seq 2, length 64
08:56:00.704656 IP fihel01.sixxs.net > a85-156-250-252.elisa-laajakaista.fi: ICMP fihel01.sixxs.net protocol 41 port 0 unreachable, length 132
08:56:01.693571 IP a85-156-250-252.elisa-laajakaista.fi > fihel01.sixxs.net: IP6 cl-679.hel-01.fi.sixxs.net > gw-679.hel-01.fi.sixxs.net: ICMP6, echo request, seq 3, length 64
08:56:01.705154 IP fihel01.sixxs.net > a85-156-250-252.elisa-laajakaista.fi: ICMP fihel01.sixxs.net protocol 41 port 0 unreachable, length 132
08:56:02.693850 IP a85-156-250-252.elisa-laajakaista.fi > fihel01.sixxs.net: IP6 cl-679.hel-01.fi.sixxs.net > gw-679.hel-01.fi.sixxs.net: ICMP6, echo request, seq 4, length 64
08:56:02.705940 IP fihel01.sixxs.net > a85-156-250-252.elisa-laajakaista.fi: ICMP fihel01.sixxs.net protocol 41 port 0 unreachable, length 132
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (85.156.250.252)
### This should return so called 'echo replies'
### If it doesn't then check your firewall settings
### Your local endpoint should always be pingable
### It could also indicate problems with your IPv4 stack
PING 85.156.250.252 (85.156.250.252): 56 data bytes
64 bytes from 85.156.250.252: seq=0 ttl=64 time=0.268 ms
64 bytes from 85.156.250.252: seq=1 ttl=64 time=0.181 ms
64 bytes from 85.156.250.252: seq=2 ttl=64 time=0.181 ms
--- 85.156.250.252 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.181/0.210/0.268 ms
######
Did this work? [Y/n]
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (62.78.96.38)
### These pings should reach the PoP and come back to you
### In case there are problems along the route between your
### host and the PoP this could not return replies
### Check your firewall settings if problems occur
PING 62.78.96.38 (62.78.96.38): 56 data bytes
64 bytes from 62.78.96.38: seq=0 ttl=60 time=12.142 ms
64 bytes from 62.78.96.38: seq=1 ttl=60 time=11.206 ms
64 bytes from 62.78.96.38: seq=2 ttl=60 time=10.830 ms
--- 62.78.96.38 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 10.830/11.392/12.142 ms
######
Did this work? [Y/n]
####### [3/8] Traceroute to the PoP (62.78.96.38) over IPv4
### This traceroute should reach the PoP
### In case this traceroute fails then you have no connectivity
### to the PoP and this is most probably the problem
traceroute to 62.78.96.38 (62.78.96.38), 30 hops max, 38 byte packets
1 lemlem1.fi.elisa.net (85.156.248.1) 7.421 ms 12.059 ms 8.035 ms
2 ge1-0-0.tamhra-p1.fi.elisa.net (139.97.49.5) 7.854 ms 6.649 ms 9.144 ms
3 as0.esptnl-p1.fi.elisa.net (139.97.28.145) 12.575 ms 10.007 ms 13.006 ms
4 ae3.heltli-gw1.fi.elisa.net (139.97.21.161) 12.642 ms 10.156 ms 11.492 ms
5 dna.ficix1-ge.ficix.fi (193.110.226.20) 12.310 ms 10.091 ms 11.795 ms
6 esp2-tr1.dnaip.fi (62.78.107.44) 12.703 ms 11.301 ms 14.226 ms
7 van1-er2.dnaip.fi (62.78.111.13) 14.463 ms 11.248 ms 12.270 ms
8 fihel01.sixxs.net (62.78.96.38) 12.264 ms 10.830 ms 12.521 ms
######
Did this work? [Y/n]
###### [4/8] Checking if we can ping IPv6 localhost (::1)
### This confirms if your IPv6 is working
### If ::1 doesn't reply then something is wrong with your IPv6 stack
PING ::1 (::1): 56 data bytes
64 bytes from ::1: seq=0 ttl=64 time=0.266 ms
64 bytes from ::1: seq=1 ttl=64 time=0.231 ms
64 bytes from ::1: seq=2 ttl=64 time=0.231 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.231/0.242/0.266 ms
######
Did this work? [Y/n]
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:14b8:100:2a6::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:14b8:100:2a6::2 (2001:14b8:100:2a6::2): 56 data bytes
64 bytes from 2001:14b8:100:2a6::2: seq=0 ttl=64 time=0.322 ms
64 bytes from 2001:14b8:100:2a6::2: seq=1 ttl=64 time=0.263 ms
64 bytes from 2001:14b8:100:2a6::2: seq=2 ttl=64 time=0.265 ms
--- 2001:14b8:100:2a6::2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.263/0.283/0.322 ms
######
Did this work? [Y/n]
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:14b8:100:2a6::1)
### This confirms the reachability of the other side of the tunnel
### If it doesn't reply then check your interface and routing tables
### Don't forget to check your firewall of course
### If the previous test was succesful then this could be both
### a firewalling and a routing/interface problem
PING 2001:14b8:100:2a6::1 (2001:14b8:100:2a6::1): 56 data bytes
--- 2001:14b8:100:2a6::1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
######
Did this work? [Y/n] n
T38209 on fihel01 doesn't work
Shadow Hawkins on Friday, 05 November 2010 08:28:17
Mikael filed a similar ticket eight minutes before me :)
https://www.sixxs.net/tickets/?msg=tickets-2959001
Please mark this as duplicate (if the ticket system supports that).
Connection to PoP lost
Shadow Hawkins on Friday, 05 November 2010 08:30:29
I have a similar problem with fihel01. I filed a ticket just after Mikael:
https://www.sixxs.net/tickets/?msg=tickets-2959025
State change: resolved
The state of this ticket has been changed to resolved
|
![[ch]](/s/countries/ch.gif)
on Friday, 05 November 2010 14:14:24
Posting is only allowed when you are