SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #5127653
Ticket Status: Resolved

PoP: ittrn01 - ITgate (Torino)

Tunnel broken
[it] Shadow Hawkins on Monday, 04 July 2011 09:17:23
As of July 1st, the tunnel is broken. Aiccu starts with no problem on my Debian machine: Tunnel Information for T70017: POP Id : ittrn01 IPv6 Local : 2001:1418:100:43e::2/64 IPv6 Remote : 2001:1418:100:43e::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled but I receive no packets from the tunnel nor I am able to ping the tunnel's end or ipv6.google.com (0 received, 100% packet loss) Here is my interface status: sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 addr: 2001:1418:100:43e::2/64 Scope:Global inet6 addr: fe80::1418:100:43e: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:271 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 B) TX bytes:27536 (26.8 KiB) I didn't find any information on the log file even if aiccu is set to verbose, the only logged lines are: AICCU running as PID 3388 [AYIYA-start] : Anything in Anything (draft-02) [AYIYA-tun->tundev] : (Socket to TUN) started Thanks for your help!
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Monday, 04 July 2011 10:56:09
Message is Locked
The state of this ticket has been changed to resolved
Tunnel broken
[it] Shadow Hawkins on Wednesday, 13 July 2011 17:19:19
Same problem here as first days of July with tunnel T24344, aiccu starts but I am not able to ping tunnel's endpoint nor ipv6.google.com. Tunnel Information for T24344: POP Id : ittrn01 IPv6 Local : 2001:1418:100:315::2/64 IPv6 Remote : 2001:1418:100:315::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 priority: 0 groups: tun egress status: active inet6 fe80::215:e9ff:fe7c:a128%tun0 -> prefixlen 64 scopeid 0x9 inet6 fe80::1418:100:315:2%tun0 -> prefixlen 64 scopeid 0x9 inet6 2001:1418:100:315::2 -> 2001:1418:100:315::1 prefixlen 128
Tunnel broken
[ch] Jeroen Massar SixXS Staff on Wednesday, 13 July 2011 17:22:20
Resolved (this issue is one of the major reasons we'll be moving to sixxsd v4 btw)
Tunnel broken
[it] Shadow Hawkins on Friday, 02 September 2011 18:20:47
Same problem again since midday. I can't reach any IP6 sites. Pinging ipv6.google.com has 100% packet loss. Thanks.
Tunnel broken again
[it] Shadow Hawkins on Saturday, 03 September 2011 13:00:27
Since yesterday afternoon, the tunnel is down again. Aiccu starts with no problem on my Debian machine: Tunnel Information for T70017: POP Id : ittrn01 IPv6 Local : 2001:1418:100:43e::2/64 IPv6 Remote : 2001:1418:100:43e::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled but I receive no packets from the tunnel nor I am able to ping the tunnel's end or ipv6.google.com (0 received, 100% packet loss) Here is my interface status: Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 addr: 2001:1418:100:43e::2/64 Scope:Global inet6 addr: fe80::1418:100:43e: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:4914 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 B) TX bytes:401848 (392.4 KiB) Thanks for your help!

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker