|
Ticket ID: SIXXS #3310681 Ticket Status: User PoP: plwaw01 - ICM (Warsaw)
Tunnel is not working
![[pl]](/s/countries/pl.gif) Shadow Hawkins on Sunday, 02 January 2011 11:48:00
Hello,
The PoP seems to be up and one of my tunnels is running fine.
However the second one (T49469) is not working. It is marked as enabled, aiccu is tarted up but i have no ipv6 connectivity.
The local IPv6 stack is running:
ping6 ::1 PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.069 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.070 ms
And interface is also up:
sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::4a0:200:22c:2/64 Scope:Link
inet6 addr: 2001:6a0:200:22c::2/64 Scope:Global
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:1416 (1.3 KiB)
ping6 ipv6.google.com PING ipv6.google.com(2a00:1450:8007::68) 56 data bytes
^C
--- ipv6.google.com ping statistics ---
27 packets transmitted, 0 received, 100% packet loss, time 25999ms
The second tunnel i own from this PoP is working fine.
Thanks in advance!
Tunnel is not working
Shadow Hawkins on Sunday, 02 January 2011 11:56:29
Tunnel has just begun to work again... I have changed tunnel type from heartbeat to ayiya in the meantime. Does it makes any difference at all?
Tunnel is not working
If you are behind a NAT or something else that blocks or can't handle protocol 41 then AYIYA versus heartbeat (protocol-41) makes a huge difference.
State change: user
The state of this ticket has been changed to user
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 05 January 2011 12:43:00
Posting is only allowed when you are