| 
 Ticket ID: SIXXS #3615025 Ticket Status: Resolved PoP: dedus01 - SpeedPartner GmbH (Duesseldorf) 
Tunnel T46805 not working 
  Shadow Hawkins on Monday, 07 February 2011 22:03:03
It seems that dedus01 is not working at the moment. I tried with Windows 7 (freshly downloaded aiccu.exe) and Ubuntu 10.10 (provided aiccu). On both systems I cannot ping the POP inner tunnel endpoint (aiccu test 6/8).
Following is the output from "aiccu test":
Tunnel Information for T46805:
POP Id      : dedus01
IPv6 Local  : 2a01:198:200:a41::2/64
IPv6 Remote : 2a01:198:200:a41::1/64
Tunnel Type : ayiya
Adminstate  : enabled
Userstate   : enabled
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.178.29)
### 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 192.168.178.29 (192.168.178.29) 56(84) bytes of data.
64 bytes from 192.168.178.29: icmp_req=1 ttl=64 time=0.017 ms
64 bytes from 192.168.178.29: icmp_req=2 ttl=64 time=0.013 ms
64 bytes from 192.168.178.29: icmp_req=3 ttl=64 time=0.014 ms
--- 192.168.178.29 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.013/0.014/0.017/0.004 ms
######
Did this work? [Y/n] 
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (91.184.37.98)
### 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 91.184.37.98 (91.184.37.98) 56(84) bytes of data.
64 bytes from 91.184.37.98: icmp_req=1 ttl=56 time=53.4 ms
64 bytes from 91.184.37.98: icmp_req=2 ttl=56 time=51.8 ms
64 bytes from 91.184.37.98: icmp_req=3 ttl=56 time=50.9 ms
--- 91.184.37.98 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 50.933/52.061/53.447/1.058 ms
######
Did this work? [Y/n] 
####### [3/8] Traceroute to the PoP (91.184.37.98) 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 91.184.37.98 (91.184.37.98), 30 hops max, 60 byte packets
 1  fritz.box (192.168.178.1)  2.279 ms  3.268 ms  5.640 ms
 2  217.0.116.163 (217.0.116.163)  48.474 ms  49.785 ms  51.500 ms
 3  217.0.67.242 (217.0.67.242)  54.873 ms  57.093 ms  59.162 ms
 4  f-ea5-i.F.DE.NET.DTAG.DE (62.154.16.165)  62.633 ms  64.280 ms  66.117 ms
 5  ffm-b6-link.telia.net (213.248.90.129)  69.127 ms 62.156.138.94 (62.156.138.94)  71.538 ms 80.156.161.118 (80.156.161.118)  72.400 ms
 6  ffm-bb1-link.telia.net (80.91.251.154)  112.683 ms ffm-bb2-link.telia.net (80.91.249.85)  52.172 ms  54.192 ms
 7  ddf-b2-link.telia.net (80.91.247.13)  60.215 ms ddf-b2-link.telia.net (80.91.251.194)  51.199 ms  51.855 ms
 8  speedpartner-106633-ddf-b1.c.telia.net (213.248.68.130)  55.956 ms  56.756 ms  58.575 ms
 9  dedus01.sixxs.net (91.184.37.98)  60.440 ms  63.028 ms  66.903 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: icmp_seq=1 ttl=64 time=0.018 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.022 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.023 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.018/0.021/0.023/0.002 ms
######
Did this work? [Y/n] 
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a01:198:200:a41::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2a01:198:200:a41::2(2a01:198:200:a41::2) 56 data bytes
64 bytes from 2a01:198:200:a41::2: icmp_seq=1 ttl=64 time=0.021 ms
64 bytes from 2a01:198:200:a41::2: icmp_seq=2 ttl=64 time=0.025 ms
64 bytes from 2a01:198:200:a41::2: icmp_seq=3 ttl=64 time=0.025 ms
--- 2a01:198:200:a41::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.021/0.023/0.025/0.005 ms
######
Did this work? [Y/n] 
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2a01:198:200:a41::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 successful then this could be both
### a firewalling and a routing/interface problem
PING 2a01:198:200:a41::1(2a01:198:200:a41::1) 56 data bytes
--- 2a01:198:200:a41::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2009ms
######
Did this work? [Y/n] n
I read a few other tickets about similar problems and I suspect that this is another "hiccup" in the POP software.
Thanks in advance for any help,
Joachim Breitsprecher
 
State change: resolved  
![]()   Shadow Hawkins   on Monday, 07 February 2011 22:10:53
The state of this ticket has been changed to resolved
 
Tunnel T46805 not working 
  Shadow Hawkins   on Monday, 07 February 2011 22:13:55
Problem with the pop-software, which is now under restart. Tunnel should come back up "in a minute". Please let us known when it works for you or if you still see issues.
 
Tunnel T46805 not working 
  Shadow Hawkins on Monday, 07 February 2011 22:29:43
The tunnel is up and working like a charm again. Thank you very much for the quick help!
 
  |