|
Ticket ID: SIXXS #954984 Ticket Status: User PoP: deham01 - Easynet (Hamburg)
Tunnel T18662 stopped to work
![[de]](/s/countries/de.gif) Shadow Hawkins on Wednesday, 28 January 2009 21:53:09
Tunnel T18662 doesn't work
Hello,
yesterday my tunnel stopped working. Here are some necessary information about the tunnel:
Tunnel: T18662
Tunnel-Typ: ayiya
PoP: deham01
My Handle: HFI2-SIXXS
I run acciu on openwrt kamikaze 8.09 r13118 (Linux router-p 2.6.25.17 #2 Tue Nov 4 01:37:43 UTC 2008 mips unknown), but after it stops working I used my laptop to test the tunnel. It runs debian testing (Linux vitamin-l 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 GNU/Linux)
Also I used a direct dial-up connection, no NAT and no firewall. I restarted aiccu serval times, but that doesnât help. I still canât ping the PoP-Side of the Tunnel (2001:6f8:900:c15::1) and the rest of the IPv6 world like ipv6.google.com, www.kame.net and so on.
Here some logging output:
###############################################
# Following the (verbose) output of aiccu autotest:
###############################################
# aiccu autotest
sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)"
sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/2.6.26-1-686"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1233172056"
sock_printf() : "starttls"
sock_getline() : "400 This service is not SSL enabled (yet)"
TIC Server does not support TLS but TLS is not required, continuing
sock_printf() : "username HFI2-SIXXS"
sock_getline() : "200 Choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 ********************************"
sock_printf() : "authenticate md5 ********************************"
sock_getline() : "200 Succesfully logged in using md5 as HFI2-SIXXS (Hannes Fuchs) from 2001:7b8:3:4f:202:b3ff:fe46:bec"
sock_printf() : "tunnel list"
sock_getline() : "201 Listing tunnels"
sock_getline() : "T18662 2001:6f8:900:c15::2 ayiya deham01"
sock_getline() : "202 <tunnel_id> <ipv6_endpoint> <ipv4_endpoint> <pop_name>"
sock_printf() : "tunnel show T18662"
sock_getline() : "201 Showing tunnel information for T18662"
sock_getline() : "TunnelId: T18662"
sock_getline() : "Type: ayiya"
sock_getline() : "IPv6 Endpoint: 2001:6f8:900:c15::2"
sock_getline() : "IPv6 POP: 2001:6f8:900:c15::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1280"
sock_getline() : "Tunnel Name: tunnel-p"
sock_getline() : "POP Id: deham01"
sock_getline() : "IPv4 Endpoint: ayiya"
sock_getline() : "IPv4 POP: 212.224.0.188"
sock_getline() : "UserState: enabled"
sock_getline() : "AdminState: enabled"
sock_getline() : "Password: ********************************"
sock_getline() : "Heartbeat_Interval: 60"
sock_getline() : "202 Done"
Succesfully retrieved tunnel information for T18662
sock_printf() : "QUIT Illuminaughty"
Tunnel Information for T18662:
POP Id : deham01
IPv6 Local : 2001:6f8:900:c15::2/64
IPv6 Remote : 2001:6f8:900:c15::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
[AYIYA-start] : Anything in Anything (draft-02)
[AYIYA-tun->tundev] : (Socket to TUN) started
heartbeat_socket() - IPv4 : 78.53.155.243
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (78.53.155.243)
### 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 78.53.155.243 (78.53.155.243) 56(84) bytes of data.
64 bytes from 78.53.155.243: icmp_seq=1 ttl=64 time=0.028 ms
64 bytes from 78.53.155.243: icmp_seq=2 ttl=64 time=0.040 ms
64 bytes from 78.53.155.243: icmp_seq=3 ttl=64 time=0.043 ms
--- 78.53.155.243 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.028/0.037/0.043/0.006 ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.224.0.188)
### 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 212.224.0.188 (212.224.0.188) 56(84) bytes of data.
64 bytes from 212.224.0.188: icmp_seq=1 ttl=58 time=37.8 ms
64 bytes from 212.224.0.188: icmp_seq=2 ttl=58 time=37.1 ms
64 bytes from 212.224.0.188: icmp_seq=3 ttl=58 time=37.1 ms
--- 212.224.0.188 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2008ms
rtt min/avg/max/mdev = 37.106/37.361/37.841/0.406 ms
######
####### [3/8] Traceroute to the PoP (212.224.0.188) 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 212.224.0.188 (212.224.0.188), 30 hops max, 40 byte packets
1 lo1.br10.bwe.de.hansenet.net (213.191.64.121) 32.616 ms 34.539 ms 36.518 ms
2 ae1-112.cr02.weham.de.hansenet.net (62.109.109.126) 42.516 ms 44.502 ms 44.515 ms
3 ae0-103.pr05.asham.de.hansenet.net (62.109.118.10) 46.430 ms 56.501 ms 56.505 ms
4 workix.ixhbg.de.easynet.net (80.81.203.26) 50.357 ms 52.398 ms 52.413 ms
5 ge2-0-9.gr10.isham.de.easynet.net (87.86.77.236) 54.334 ms 54.345 ms 56.327 ms
6 ge3-7.br2.isham.de.easynet.net (87.86.71.241) 58.246 ms 37.780 ms 87.891 ms
7 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 37.869 ms 39.865 ms 39.881 ms
8 deham01.sixxs.net (212.224.0.188) 41.805 ms 43.768 ms 45.760 ms
######
###### [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: icmp_seq=1 ttl=64 time=0.043 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.061 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.063 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.043/0.055/0.063/0.012 ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:900:c15::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:6f8:900:c15::2(2001:6f8:900:c15::2) 56 data bytes
64 bytes from 2001:6f8:900:c15::2: icmp_seq=1 ttl=64 time=0.063 ms
64 bytes from 2001:6f8:900:c15::2: icmp_seq=2 ttl=64 time=0.070 ms
64 bytes from 2001:6f8:900:c15::2: icmp_seq=3 ttl=64 time=0.066 ms
--- 2001:6f8:900:c15::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.063/0.066/0.070/0.007 ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:900:c15::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:6f8:900:c15::1(2001:6f8:900:c15::1) 56 data bytes
--- 2001:6f8:900:c15::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2012ms
######
###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
### This confirms that you can reach the central machine of SixXS
### If that one is reachable you should be able to reach most IPv6 destinations
### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection
### If your browser supports IPv6 and uses it of course.
traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
######
###### [8/8] Traceroute6 to (www.kame.net)
### This confirms that you can reach a Japanese IPv6 destination
### If that one is reachable you should be able to reach most IPv6 destinations
### You should also check http://www.kame.net which should display
### a animated kame (turtle), of course only when your browser supports and uses IPv6
traceroute to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
######
###### ACCU Quick Connectivity Test (done)
###############################################
# iptables (IPv4)
###############################################
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
###############################################
# ip6tables
###############################################
# ip6tables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
###############################################
# routing-table
###############################################
# ip -6 ro sh
2001:6f8:900:c15::/64 dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
default via 2001:6f8:900:c15::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
###############################################
# ip -6 ad sh
###############################################
# ip -6 ad sh
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 fe80::217:8ff:fe3a:530b/64 scope link
valid_lft forever preferred_lft forever
15: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qlen 500
inet6 2001:6f8:900:c15::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::4f8:900:c15:2/64 scope link
valid_lft forever preferred_lft forever
###############################################
If more information is needed, just let me know.
Thanks in advance
Hannes Fuchs
State change: user
The state of this ticket has been changed to user
Tunnel T18662 stopped to work
At this moment your host is not sending any valid AYIYA packets, as such the tunnel is down on the PoP.
Tunnel T18662 stopped to work
Shadow Hawkins on Wednesday, 28 January 2009 23:04:21
Tunnel runs! Ping is working!
Did you do something?
I forget to restart aiccu in non verbose mode, after posting this ticket and now it runs again - strange.
I spend about 3 hours yesterdey in reading logs, restarting aiccu serval times, checking the config, but it doesn't helped. Today again, about 1 hour, then i wrote this ticket.
Was there somthing wrong on the server-side? I would like to understand what goes wrong.
Many thanks, what ever you did ;)
Tunnel T18662 stopped to work
If you don't send proper AYIYA packets the PoP disables the tunnel. The moment you start sending proper AYIYA packets, it automatically enables the tunnel again and indeed then it works. That is a fully automatic process, nothing we have to do about it.
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 28 January 2009 22:35:12
Posting is only allowed when you are