Tickets - AYIYA not working :: SixXS - IPv6 Deployment & Tunnel Broker

Ticket ID: SIXXS #1086965
Ticket Status: Resolved

PoP: deham01 - Easynet (Hamburg)

AYIYA not working

Shadow Hawkins on Friday, 15 May 2009 10:51:37

retrieved tunnel information is working fine, but the tunnel it self does not work. my second tunnel (6in4-static ip) is working fine at deham01. AICCU output with verbose=true sock_getline() : "201 Showing tunnel information for T9969" sock_getline() : "TunnelId: T9969" sock_getline() : "Type: ayiya" sock_getline() : "IPv6 Endpoint: 2001:6f8:900:76f::2" sock_getline() : "IPv6 POP: 2001:6f8:900:76f::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "Tunnel Name: work" 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 T9969 sock_printf() : "QUIT Zij die gaan, groeten u" Tunnel Information for T9969: POP Id : deham01 IPv6 Local : 2001:6f8:900:76f::2/64 IPv6 Remote : 2001:6f8:900:76f::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Connection refused (111) [AYIYA-start] : Anything in Anything (draft-02) [AYIYA-tun->tundev] : (Socket to TUN) started

ipv6 does not work with deham01

Carmen Sandiego on Friday, 15 May 2009 10:19:47

Since today i can not use ipv6 with deham01. I used "aiccu test", result is the test 6/8 fails

###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:900:be4::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:be4::1(2001:6f8:900:be4::1) 56 data bytes --- 2001:6f8:900:be4::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2008ms

using external tools link -> same result

ipv6 does not work with deham01

Carmen Sandiego on Friday, 15 May 2009 10:19:41

ping6

State change: user Locked

Jeroen Massar SixXS Staff

on Friday, 15 May 2009 10:19:55

The state of this ticket has been changed to user

ipv6 does not work with deham01

Jeroen Massar SixXS Staff

on Friday, 15 May 2009 10:21:44

You really need to send AYIYA packets for an AYIYA tunnel to be up. When there have not been any packets for 120 seconds AYIYA tunnels are marked down, and then, indeed both ends of the tunnel will be unreachable.

ipv6 does not work with deham01

Carmen Sandiego on Friday, 15 May 2009 10:29:25

but i have the same problem with tunnel T13824.

###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:900:a9a::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:a9a::1(2001:6f8:900:a9a::1) 56 data bytes --- 2001:6f8:900:a9a::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2008ms

and this tunnel works for about 30 weeks. I restarted aiccu

ipv6 does not work with deham01

Jeroen Massar SixXS Staff

on Friday, 15 May 2009 10:33:33

For which also no valid AYIYA packets are coming in. There are a few people with a wrongly-set clock for which packets are not being accepted for that reason, but you are not one of those.

ipv6 does not work with deham01