|
Ticket ID: SIXXS #3402205 Ticket Status: Resolved PoP: dedus01 - SpeedPartner GmbH (Duesseldorf)
tunnel non-working
![[de]](/s/countries/de.gif) Shadow Hawkins on Sunday, 16 January 2011 21:13:24
Hello,
my situation is similar to
https://www.sixxs.net/tickets/?msg=tickets-3366193
traceroute to PoP (ipv4) "internal" works fine:
traceroute to 91.184.37.98 (91.184.37.98), 30 hops max, 60 byte packets
1 192.168.1.1 0.611 ms 1.079 ms 1.370 ms
2 192.168.178.1 8.979 ms 9.979 ms 10.391 ms
3 88.64.176.1 21.841 ms 22.254 ms 25.634 ms
4 145.254.15.113 26.020 ms 27.775 ms 28.827 ms
5 145.254.18.206 33.993 ms 35.864 ms 38.039 ms
6 145.253.33.134 41.504 ms 43.220 ms 44.129 ms
7 217.239.37.146 46.098 ms 39.547 ms 62.154.43.130 42.053 ms
8 194.54.95.218 338.670 ms 327.689 ms 327.278 ms
9 91.184.37.98 29.683 ms 31.740 ms 31.419 ms
traceroute to Pop (ipv6) from external (my other tunnel) fails with "network unreachable:
traceroute to 2a01:198:200:291::1 (2a01:198:200:291::1) from 2001:6f8:1c00:2aa::2, 30 hops max, 16 byte packets
1 2001:6f8:1c00:2aa::1 57.563 ms 51.805 ms 64.868 ms
2 2001:6f8:800:1003::209:55 57.308 ms 68.43 ms 83.451 ms
3 2001:6f8:1:0:87:86:71:240 239.966 ms 192.303 ms 174.044 ms
4 2001:6f8:1:0:87:86:77:67 79.348 ms 54.628 ms 50.412 ms
5 2001:6f8:1:0:86:87:77:81 57.835 ms 56.858 ms 79.897 ms
6 2001:6f8:1:0:87:86:77:83 130.389 ms 210.251 ms 85.52 ms
7 2001:6f8:1:0:86:87:77:95 64.506 ms 71.372 ms 60.059 ms
8 * 2001:6f8:1:0:87:86:77:247 63.885 ms *
9 2001:7f8::a2dc:0:1 62.741 ms 61.2 ms 60.741 ms
10 * 2001:7f8:3a:e102::2 68.117 ms 80.583 ms
11 2a01:198:200::2 68.408 ms !N 68.362 ms !N 71.821 ms !N
so I guess ipv6 network connectivity of my pop isn't available.
a ping from my router to the pop' tunnel endpoint fails.
a user in #sixxs.net that uses dedus1, too, has the same problems.
Thanks
Uwe
tunnel non-working
Shadow Hawkins  on Sunday, 16 January 2011 21:20:46
Problem with pop-software. Should be resolved now. Thank you for reporting.
tunnel non-working again
Shadow Hawkins on Tuesday, 25 January 2011 17:43:00
Hello Michael,
I have that problem again. Router cannot ping pop tunnel endpoint (ipv6) and traceroute6 2a01:198:200:291::1 from a different net ends in "network unreachable".
Best regards
Uwe
tunnel non-working again
Works for me:
64 bytes from 2a01:198:200:291::1: icmp_seq=1 ttl=57 time=11.4 ms
Also your side of the tunnel:
64 bytes from 2a01:198:200:291::2: icmp_seq=1 ttl=56 time=45.5 ms
You might want to supply a lot more details as requested by that big orange box.
tunnel non-working again
Shadow Hawkins on Friday, 28 January 2011 21:42:09
Yeah, usually works after some time again. Just now it's borken again.
(from a different ipv6 enabled network)
ukl@octopus:~$ traceroute6 -n 2a01:198:200:291::1
traceroute to 2a01:198:200:291::1 (2a01:198:200:291::1), 30 hops max, 40 byte packets
1 2001:6f8:1178:2::1 0.152 ms 0.175 ms 0.183 ms
2 2001:6f8:900:a6e::1 30.025 ms 32.058 ms 34.040 ms
3 2001:6f8:800:1003::209:55 36.133 ms 36.116 ms 38.167 ms
4 2001:6f8:1:0:87:86:71:240 36.024 ms * *
5 2001:6f8:1:0:87:86:77:67 38.064 ms * *
6 2001:6f8:1:0:86:87:77:81 38.055 ms * *
7 2001:6f8:1:0:87:86:77:83 37.922 ms * *
8 2001:6f8:1:0:86:87:77:95 42.168 ms * *
9 2001:6f8:1:0:87:86:77:247 40.016 ms 37.835 ms 39.732 ms
10 2001:7f8::a2dc:0:1 196.268 ms 196.252 ms 158.375 ms
11 2001:7f8:3a:e102::2 43.991 ms 43.981 ms 42.181 ms
12 2a01:198:200::2 43.885 ms !N * *
(from my router)
root@phineas:~# ping6 -c6 2a01:198:200:291::1
PING 2a01:198:200:291::1 (2a01:198:200:291::1): 56 data bytes
--- 2a01:198:200:291::1 ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.178.2)
### 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.2 (192.168.178.2): 56 data bytes
64 bytes from 192.168.178.2: seq=0 ttl=64 time=0.950 ms
64 bytes from 192.168.178.2: seq=1 ttl=64 time=0.656 ms
64 bytes from 192.168.178.2: seq=2 ttl=64 time=0.652 ms
--- 192.168.178.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.652/0.752/0.950 ms
######
####### [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 data bytes
64 bytes from 91.184.37.98: seq=0 ttl=56 time=19.071 ms
64 bytes from 91.184.37.98: seq=1 ttl=56 time=23.779 ms
64 bytes from 91.184.37.98: seq=2 ttl=56 time=18.512 ms
--- 91.184.37.98 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 18.512/20.454/23.779 ms
######
####### [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, 38 byte packets
1 192.168.178.1 (192.168.178.1) 4.287 ms 4.086 ms 3.863 ms
2 dslb-088-064-176-001.pools.arcor-ip.net (88.64.176.1) 10.460 ms 9.706 ms 9.949 ms
3 145.254.15.117 (145.254.15.117) 11.951 ms 10.350 ms 9.944 ms
4 dus-145-254-18-202.arcor-ip.net (145.254.18.202) 16.491 ms 16.655 ms 17.717 ms
5 145.253.33.130 (145.253.33.130) 19.418 ms 18.065 ms 17.856 ms
6 217.239.37.150 (217.239.37.150) 16.606 ms d-ec1-i.D.DE.NET.DTAG.DE (62.154.43.134) 16.404 ms 217.239.37.150 (217.239.37.150) 17.848 ms
7 oc-fra.speedpartner.de (194.54.95.218) 18.517 ms 17.082 ms 17.085 ms
8 dedus01.sixxs.net (91.184.37.98) 17.156 ms 18.323 ms 18.848 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: seq=0 ttl=64 time=0.906 ms
64 bytes from ::1: seq=1 ttl=64 time=0.822 ms
64 bytes from ::1: seq=2 ttl=64 time=0.817 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.817/0.848/0.906 ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a01:198:200:291::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2a01:198:200:291::2 (2a01:198:200:291::2): 56 data bytes
64 bytes from 2a01:198:200:291::2: seq=0 ttl=64 time=0.977 ms
64 bytes from 2a01:198:200:291::2: seq=1 ttl=64 time=1.052 ms
64 bytes from 2a01:198:200:291::2: seq=2 ttl=64 time=0.892 ms
--- 2a01:198:200:291::2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.892/0.973/1.052 ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2a01:198:200:291::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 2a01:198:200:291::1 (2a01:198:200:291::1): 56 data bytes
--- 2a01:198:200:291::1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
######
root@phineas:/tmp/run# cat aiccu-cfg021b7e.conf.bak | grep -v password
username UKD1-SIXXS
protocol tic
tunnel_id T18221
behindnat true
makebeats false
daemonize true
pidfile /var/run/aiccu-cfg021b7e.pid
tunnel non-working again
Shadow Hawkins on Thursday, 10 February 2011 10:36:37
and again it's borken in the same way. The config is unchanged since before the first report.
I saw different behaviors of traceroute6 on the pop inner tunnel endpoint (2a01:198:200:291::1) from external during the current breakage.
First it ended in:
11 oc-fra.dus.speedpartner.de (2001:7f8:3a:e102::2) 43.545 ms 45.327 ms 43.525 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 oc-fra.dus.speedpartner.de (2001:7f8:3a:e102::2) 41.847 ms !H * *
then
11 2001:7f8:3a:e102::2 41.880 ms 41.882 ms 44.043 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
and then
11 2001:7f8:3a:e102::2 41.930 ms 41.873 ms 43.947 ms
12 2a01:198:200::2 44.028 ms * 42.012 ms
13 2001:7f8:3a:e102::2 41.949 ms 42.061 ms 42.054 ms
14 * * 2a01:198:200::2 41.980 ms
15 * * 2001:7f8:3a:e102::2 43.995 ms
16 2a01:198:200::2 44.090 ms * 149.844 ms !N
tunnel working again
Shadow Hawkins on Thursday, 10 February 2011 10:38:15
I don't know if it self-repairs? At least it works again now.
Best regards from a frustrated user
Uwe
State change: resolved
 Shadow Hawkins on Sunday, 16 January 2011 21:20:50
The state of this ticket has been changed to resolved
|
![[ch]](/s/countries/ch.gif)
Posting is only allowed when you are