|
Ticket ID: SIXXS #2844797 Ticket Status: Resolved PoP: dedus01 - SpeedPartner GmbH (Duesseldorf)
Aiccu connection can be made, but no connectivity
![[de]](/s/countries/de.gif) Shadow Hawkins on Saturday, 23 October 2010 22:18:05
Seems to be a problem similar to this one: I can establish an aiccu connection, but cannot reach other IPv6 hosts, not even the next hop.
AICCU output with verbose=true:
sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)"
sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/2.6.25.17"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1287864834"
sock_printf() : "username JAS3-SIXXS"
sock_getline() : "200 JAS3-SIXXS choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 ***"
sock_printf() : "authenticate md5 ***"
sock_getline() : "200 Successfully logged in using md5 as JAS3-SIXXS (Jannis Andrija Schnitzer)"
sock_printf() : "tunnel show T17728"
sock_getline() : "201 Showing tunnel information for T17728"
sock_getline() : "TunnelId: T17728"
sock_getline() : "Type: ayiya"
sock_getline() : "IPv6 Endpoint: 2a01:198:200:23d::2"
sock_getline() : "IPv6 POP: 2a01:198:200:23d::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1280"
sock_getline() : "Tunnel Name: A minor"
sock_getline() : "POP Id: dedus01"
sock_getline() : "IPv4 Endpoint: ayiya"
sock_getline() : "IPv4 POP: 91.184.37.98"
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 T17728
sock_printf() : "QUIT Tschau!"
Tunnel Information for T17728:
POP Id : dedus01
IPv6 Local : 2a01:198:200:23d::2/64
IPv6 Remote : 2a01:198:200:23d::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
[AYIYA-start] : Anything in Anything (draft-02)
[AYIYA-tun->tundev] : (Socket to TUN) started
"aiccu test" obviously fails at step 6/8, can't ping 2a01:198:200:23d::1. It worked some hours ago, and I didn't change any firewall configuration or whatsoever.
I also tried with the other tunnel I have, T21144, but the same problem occurs.
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Saturday, 23 October 2010 22:40:22
Right now an error message turned up in that aiccu-running shell, which I had earlier, but hadn't reproduced until now:
[AYIYA-tundev->tun] : Error (-1) while sending 138 bytes to network: Connection refused (146)
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Saturday, 23 October 2010 23:29:36
i have the same problem on dedus01, i used ayiya first and now changed to heartbeat, the pop answers
ICMP: protocol 41 port 0 unreachable
aiccu testing results in the same as with the user who opend the ticket
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Sunday, 24 October 2010 00:03:37
Working again, for me :)
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Sunday, 24 October 2010 01:49:20
Yep, resolved for me, too.
State change: user
The state of this ticket has been changed to user
Aiccu connection can be made, but no connectivity
Where is the rest of you local configuration? Please see those big orange boxes when posting a message which refer to the contact page's "Reporting Problems" section.
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Thursday, 28 October 2010 22:12:45
I thought it was enough to state that it had worked with the very same configuration before. But if you like...
Aiccu running on a LinkSys WRT54GL with OpenWRT "Kamikaze". Connected to a AVM wifi access point (NAT) which connects to 1&1 IPv4 DSL.
By the way, it's not working again right now.
uname -a
Linux Rukrym 2.6.25.17 #16 Sun Feb 15 00:19:46 CET 2009 mips unknown
aiccu.conf
username JAS3-SIXXS
password ***
tunnel_id T17728
daemonize false
verbose true
pidfile /var/run/aiccu-cfg02e934.pid
output of "ifconfig"
aiccu Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: 2a01:198:200:23d::2/64 Scope:Global
inet6 addr: fe80::98:200:23d: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:1123 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:91440 (89.2 KiB)
eth0 Link encap:Ethernet HWaddr 00:18:F8:DB:0D:43
inet6 addr: fe80::218:f8ff:fedb:d43/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:110274 errors:0 dropped:0 overruns:0 frame:0
TX packets:260858 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15222125 (14.5 MiB) TX bytes:74898480 (71.4 MiB)
Interrupt:4
eth0.0 Link encap:Ethernet HWaddr 00:18:F8:DB:0D:43
inet addr:192.168.176.1 Bcast:192.168.176.255 Mask:255.255.255.0
inet6 addr: 2a01:198:300::1/64 Scope:Global
inet6 addr: fe80::218:f8ff:fedb:d43/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:109942 errors:0 dropped:0 overruns:0 frame:0
TX packets:117693 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13176574 (12.5 MiB) TX bytes:15691508 (14.9 MiB)
eth0.1 Link encap:Ethernet HWaddr 00:18:F8:DB:0D:43
inet6 addr: fe80::218:f8ff:fedb:d43/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:143157 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:58118902 (55.4 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:114 errors:0 dropped:0 overruns:0 frame:0
TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10688 (10.4 KiB) TX bytes:10688 (10.4 KiB)
wlan0 Link encap:Ethernet HWaddr 00:90:4C:5F:00:2A
inet addr:192.168.182.2 Bcast:192.168.182.255 Mask:255.255.255.0
inet6 addr: fe80::290:4cff:fe5f:2a/64 Scope:Link
inet6 addr: 2a01:198:300:fade::1/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1091102 errors:0 dropped:0 overruns:0 frame:0
TX packets:1026555 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:415319241 (396.0 MiB) TX bytes:421782242 (402.2 MiB)
wmaster0 Link encap:UNSPEC HWaddr 00-90-4C-5F-00-2A-01-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
ip route
192.168.176.0/24 dev eth0.0 proto kernel scope link src 192.168.176.1
192.168.182.0/24 dev wlan0 proto kernel scope link src 192.168.182.2
default via 192.168.182.1 dev wlan0
ip -6 route
2a01:198:200:23d::/64 dev aiccu metric 256 expires 21333707sec mtu 1280 advmss 1220 hoplimit 4294967295
2a01:198:300::/64 dev eth0.0 metric 256 expires 20901445sec mtu 1500 advmss 1440 hoplimit 4294967295
2a01:198:300::/64 dev eth0.0 metric 1024 expires 20901446sec mtu 1500 advmss 1440 hoplimit 4294967295
2a01:198:300:deaf::/64 dev wlan0 metric 1024 expires 20901446sec mtu 1500 advmss 1440 hoplimit 4294967295
2a01:198:300:fade::/64 dev wlan0 metric 256 expires 20901446sec mtu 1500 advmss 1440 hoplimit 4294967295
2a01:198:300:fade::/64 dev wlan0 metric 1024 expires 20901446sec mtu 1500 advmss 1440 hoplimit 4294967295
2a01:198:300:ffff::/64 dev eth0.0 metric 1024 expires 20901446sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth0 metric 256 expires 20901414sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth0.0 metric 256 expires 20901414sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth0.1 metric 256 expires 20901415sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev wlan0 metric 256 expires 20901429sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev aiccu metric 256 expires 21333707sec mtu 1280 advmss 1220 hoplimit 4294967295
default via 2a01:198:200:23d::1 dev aiccu metric 1024 expires 21333707sec mtu 1280 advmss 1220 hoplimit 4294967295
iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP all -- anywhere anywhere state INVALID
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT all -- anywhere anywhere
syn_flood tcp -- anywhere anywhere tcp flags:FIN,SYN,RST,ACK/SYN
input_rule all -- anywhere anywhere
input all -- anywhere anywhere
Chain FORWARD (policy DROP)
target prot opt source destination
DROP all -- anywhere anywhere state INVALID
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
forwarding_rule all -- anywhere anywhere
forward all -- anywhere anywhere
reject all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
DROP all -- anywhere anywhere state INVALID
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT all -- anywhere anywhere
output_rule all -- anywhere anywhere
output all -- anywhere anywhere
Chain forward (1 references)
target prot opt source destination
zone_lan_forward all -- anywhere anywhere
zone_lan_forward all -- anywhere anywhere
Chain forwarding_lan (1 references)
target prot opt source destination
Chain forwarding_rule (1 references)
target prot opt source destination
Chain forwarding_wan (1 references)
target prot opt source destination
Chain input (1 references)
target prot opt source destination
zone_lan all -- anywhere anywhere
zone_lan all -- anywhere anywhere
Chain input_lan (1 references)
target prot opt source destination
Chain input_rule (1 references)
target prot opt source destination
Chain input_wan (1 references)
target prot opt source destination
Chain output (1 references)
target prot opt source destination
zone_lan_ACCEPT all -- anywhere anywhere
zone_wan_ACCEPT all -- anywhere anywhere
Chain output_rule (1 references)
target prot opt source destination
Chain reject (5 references)
target prot opt source destination
REJECT tcp -- anywhere anywhere reject-with tcp-reset
REJECT all -- anywhere anywhere reject-with icmp-port-unreachable
Chain syn_flood (1 references)
target prot opt source destination
RETURN tcp -- anywhere anywhere tcp flags:FIN,SYN,RST,ACK/SYN limit: avg 25/sec burst 50
DROP all -- anywhere anywhere
Chain zone_lan (2 references)
target prot opt source destination
input_lan all -- anywhere anywhere
zone_lan_ACCEPT all -- anywhere anywhere
Chain zone_lan_ACCEPT (3 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
Chain zone_lan_DROP (0 references)
target prot opt source destination
DROP all -- anywhere anywhere
DROP all -- anywhere anywhere
DROP all -- anywhere anywhere
DROP all -- anywhere anywhere
Chain zone_lan_MSSFIX (0 references)
target prot opt source destination
TCPMSS tcp -- anywhere anywhere tcp flags:SYN,RST/SYN TCPMSS clamp to PMTU
TCPMSS tcp -- anywhere anywhere tcp flags:SYN,RST/SYN TCPMSS clamp to PMTU
Chain zone_lan_REJECT (0 references)
target prot opt source destination
reject all -- anywhere anywhere
reject all -- anywhere anywhere
reject all -- anywhere anywhere
reject all -- anywhere anywhere
Chain zone_lan_forward (2 references)
target prot opt source destination
zone_wan_MSSFIX all -- anywhere anywhere
zone_wan_ACCEPT all -- anywhere anywhere
forwarding_lan all -- anywhere anywhere
zone_lan_ACCEPT all -- anywhere anywhere
Chain zone_wan (0 references)
target prot opt source destination
input_wan all -- anywhere anywhere
zone_wan_REJECT all -- anywhere anywhere
Chain zone_wan_ACCEPT (2 references)
target prot opt source destination
Chain zone_wan_DROP (0 references)
target prot opt source destination
Chain zone_wan_MSSFIX (1 references)
target prot opt source destination
Chain zone_wan_REJECT (2 references)
target prot opt source destination
Chain zone_wan_forward (0 references)
target prot opt source destination
forwarding_wan all -- anywhere anywhere
zone_wan_REJECT all -- anywhere anywhere
traceroute dedus01.sixxs.net
traceroute to dedus01.sixxs.net (91.184.37.98), 64 hops max, 52 byte packets
1 192.168.182.1 (192.168.182.1) 3.520 ms 1.579 ms 1.908 ms
2 rdsl-mnhm-de02.nw.mediaways.net (213.20.56.10) 29.585 ms 24.439 ms 25.394 ms
3 xmws-mnhm-de02-chan-19.nw.mediaways.net (195.71.159.214) 24.933 ms 24.931 ms 26.536 ms
4 rmws-mnhm-de01-gigaet-0-1-0.nw.mediaways.net (213.20.250.113) 26.169 ms 25.825 ms 24.933 ms
5 rmwc-frnk-de01-xe-1-0-3-0.nw.mediaways.net (195.71.159.153) 26.651 ms 27.404 ms 27.145 ms
6 rmwc-dsdf-de01-chan-2-0.nw.mediaways.net (195.71.254.146) 31.331 ms 49.311 ms 30.334 ms
7 xmwc-dsdf-de01-vlan-2.nw.mediaways.net (195.71.243.34) 30.583 ms 31.259 ms 30.862 ms
8 xmws-dsdf-de01-gigaet-1-1.nw.mediaways.net (195.71.243.230) 30.246 ms 33.567 ms 31.443 ms
9 speedpartner.dus.ecix.net (194.146.118.13) 32.024 ms 31.556 ms 30.481 ms
10 dedus01.sixxs.net (91.184.37.98) 31.126 ms * *
traceroute6 dedus01.sixxs.net
traceroute to dedus01.sixxs.net (2a01:198:200::2) from 2a01:198:200:23d::2, 30 hops max, 16 byte packets
1 * * *
2 * * *
(etc.)
Aiccu connection can be made, but no connectivity
Pings for me...
64 bytes from 2a01:198:200:23d::2: icmp_seq=1 ttl=56 time=49.4 ms
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Friday, 29 October 2010 19:18:59
Obviously connection always returns again after some time. However, dedus01's status didn't change to "Down" in the meantime, and the fact that the issue occured twice already made me think there could be a problem. Maybe it's just usual business, though. I'll post again if I notice another dropout.
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Saturday, 30 October 2010 16:42:23
It's happening again.
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Saturday, 30 October 2010 19:59:50
i can confirm that its happening again... i cannot ping the pop over ipv6
Aiccu connection can be made, but no connectivity
Shadow Hawkins  on Saturday, 30 October 2010 20:20:26
hmmm ...
no problem for my tunnel@dedus01
$ traceroute6 www.heise.de
traceroute to www.heise.de (2a02:2e0:3fe:100::7), 30 hops max, 80 byte packets
1 fritz.box (XX) 0.737 ms 0.715 ms 0.815 ms
2 gw-3.dus-01.de.sixxs.net (2a01:198:200:2::1) 17.502 ms 18.594 ms 20.710 ms
3 2a01:198:10::1 (2a01:198:10::1) 22.498 ms 24.573 ms 25.418 ms
4 gi1-15.c1.d.de.plusline.net (2001:7f8:8::3012:0:1) 36.628 ms 38.212 ms 39.344 ms
5 ge1-16.c302.f.de.plusline.net (2a02:2e0:1::45) 210.531 ms 210.526 ms 210.831 ms
6 te2-4.c102.f.de.plusline.net (2a02:2e0:1::5) 41.536 ms 36.060 ms 37.282 ms
7 te6-2.c13.f.de.plusline.net (2a02:2e0:1::22) 39.475 ms 21.194 ms 21.122 ms
8 www.heise.de (2a02:2e0:3fe:100::7) 22.489 ms 24.437 ms 25.687 ms
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Sunday, 31 October 2010 05:03:29
its strange somehow, the connectivity is restored now, and i know it does not happen to all users of dedus01 but it happens sometimes and as it seems to quite some users.
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Monday, 01 November 2010 16:30:57
Having the same problem here. I can ping the pop via IPv4 but with IPv6 I can't. Connection (AYIYA) is established, but no chance to connect to a IPv6 host.
Aiccu connection can be made, but no connectivity
I would say it is broken, but as you are unable to provide any information as requested, nothing we can do about it.
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Monday, 01 November 2010 18:08:12
Don't know exactly what you need but here is the output of aiccu start:
sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs
.net)"
sock_printf() : "client TIC/draft-00 AICCU/2008.03.15-console-win32 WinNT/6.0.6
000"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1288631019"
sock_printf() : "username DRE2-SIXXS"
sock_getline() : "200 DRE2-SIXXS choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 1e8e909c8a7ab824010c9d225e758749"
sock_printf() : "authenticate md5 0dadbd0cccd58aee2e2275def6dbad19"
sock_getline() : "200 Successfully logged in using md5 as DRE2-SIXXS (Daniel Reu
tter)"
sock_printf() : "tunnel show T43801"
sock_getline() : "201 Showing tunnel information for T43801"
sock_getline() : "TunnelId: T43801"
sock_getline() : "Type: ayiya"
sock_getline() : "IPv6 Endpoint: 2a01:198:200:9f9::2"
sock_getline() : "IPv6 POP: 2a01:198:200:9f9::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1428"
sock_getline() : "Tunnel Name: My First Tunnel"
sock_getline() : "POP Id: dedus01"
sock_getline() : "IPv4 Endpoint: ayiya"
sock_getline() : "IPv4 POP: 91.184.37.98"
sock_getline() : "UserState: enabled"
sock_getline() : "AdminState: enabled"
sock_getline() : "Password: 8c34083eccf6c28f015c7403cca93919"
sock_getline() : "Heartbeat_Interval: 60"
sock_getline() : "202 Done"
Succesfully retrieved tunnel information for T43801
sock_printf() : "QUIT Stranded"
Tunnel Information for T43801:
PoP Id : dedus01
IPv6 Local : 2a01:198:200:9f9::2/64
IPv6 Remote : 2a01:198:200:9f9::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
Name : My First Tunnel
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[warning] Error opening registry key: SYSTEM\CurrentControlSet\Control\Class\{4D
36E972-E325-11CE-BFC1-08002BE10318}\Properties (t1)
Found interface named 'SixXS', with guid {322A0EBD-05E9-4D0E-AD5C-37D0B44E6174},
using it
[tun-start] Trying \\.\Global\{322A0EBD-05E9-4D0E-AD5C-37D0B44E6174}.tap
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[AYIYA-start] : Anything in Anything (draft-02)
[AYIYA-tun->tundev] : (Socket to TUN) started
Here the output of aiccu autotest:
Tunnel Information for T43801:
PoP Id : dedus01
IPv6 Local : 2a01:198:200:9f9::2/64
IPv6 Remote : 2a01:198:200:9f9::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
Name : My First Tunnel
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.0.103)
### 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 wird ausgefhrt fr 192.168.0.103 mit 32 Bytes Daten:
Antwort von 192.168.0.103: Bytes=32 Zeit<1ms TTL=128
Antwort von 192.168.0.103: Bytes=32 Zeit<1ms TTL=128
Antwort von 192.168.0.103: Bytes=32 Zeit<1ms TTL=128
Ping-Statistik fr 192.168.0.103:
Pakete: Gesendet = 3, Empfangen = 3, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms
######
####### [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 wird ausgefhrt fr 91.184.37.98 mit 32 Bytes Daten:
Antwort von 91.184.37.98: Bytes=32 Zeit=16ms TTL=56
Antwort von 91.184.37.98: Bytes=32 Zeit=26ms TTL=56
Antwort von 91.184.37.98: Bytes=32 Zeit=19ms TTL=56
Ping-Statistik fr 91.184.37.98:
Pakete: Gesendet = 3, Empfangen = 3, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 16ms, Maximum = 26ms, Mittelwert = 20ms
######
####### [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
Routenverfolgung zu dedus01.sixxs.net [91.184.37.98] ber maximal 30 Abschnitte:
1 * * * Zeitberschreitung der Anforderung.
2 9 ms 8 ms 10 ms 172.30.25.53
3 8 ms 9 ms 9 ms HSI-KBW-078-042-040-049.hsi3.kabel-badenwuerttemberg.de [78.42.40.49]
4 12 ms 11 ms 12 ms ae1.FRA-M1.ip-bb.kabel-badenwuerttemberg.de [78.42.40.17]
5 16 ms 19 ms 16 ms oc-fra.speedpartner.de [194.54.95.218]
6 16 ms 17 ms 16 ms dedus01.sixxs.net [91.184.37.98]
Ablaufverfolgung beendet.
######
###### [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 wird ausgefhrt fr ::1 mit 32 Bytes Daten:
Antwort von ::1: Zeit<1ms
Antwort von ::1: Zeit<1ms
Antwort von ::1: Zeit<1ms
Ping-Statistik fr ::1:
Pakete: Gesendet = 3, Empfangen = 3, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a01:198:200:9f9::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
Ping wird ausgefhrt fr 2a01:198:200:9f9::2 mit 32 Bytes Daten:
Antwort von 2a01:198:200:9f9::2: Zeit<1ms
Antwort von 2a01:198:200:9f9::2: Zeit<1ms
Antwort von 2a01:198:200:9f9::2: Zeit<1ms
Ping-Statistik fr 2a01:198:200:9f9::2:
Pakete: Gesendet = 3, Empfangen = 3, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2a01:198:200:9f9::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 (both IPv4 and IPv6) of course
### If the previous test was succesful then this could be both
### a firewalling and a routing/interface problem
Ping wird ausgefhrt fr 2a01:198:200:9f9::1 mit 32 Bytes Daten:
Zeitberschreitung der Anforderung.
Zeitberschreitung der Anforderung.
Zeitberschreitung der Anforderung.
Ping-Statistik fr 2a01:198:200:9f9::1:
Pakete: Gesendet = 3, Empfangen = 0, Verloren = 3
(100% Verlust),
######
###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
### This confirms that you can reach the central machine of SixXS
### If that one is reachable you should be able to reach most IPv6 destinations
### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection
### If your browser supports IPv6 and uses it of course.
######
###### [8/8] Traceroute6 to (www.kame.net)
### This confirms that you can reach a Japanese IPv6 destination
### If that one is reachable you should be able to reach most IPv6 destinations
### You should also check http://www.kame.net which should display
### a animated kame (turtle), of course only when your browser supports and uses IPv6
######
###### ACCU Quick Connectivity Test (done)
### Either the above all works and gives no problems
### or it shows you where what goes wrong
### Check the SixXS FAQ (http://www.sixxs.net/faq/
### for more information and possible solutions or hints
### Don't forget to check the Forums (http://www.sixxs.net/forum/)
### for a helping hand.
### Passing the output of 'aiccu autotest >aiccu.log' is a good idea.
And my config file:
# Login information
username ...
password ...
protocol tic
server tic.sixxs.net
# Interface names to use
ipv6_interface SixXS
# The tunnel_id to use
# (only required when there are multiple tunnels in the list)
tunnel_id T43801
# Try to automatically login and setup the tunnel?
automatic true
# Script to run after setting up the interfaces
#setupscript <path>
# No configuration, only beat?
noconfigure false
# TLS Required?
requiretls false
# Be verbose?
verbose true
# Daemonize?
daemonize false
# Behind a NAT?
behindnat true
# Make heartbeats when the protocol needs it?
makebeats true
Hope this helps.
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Wednesday, 03 November 2010 17:44:15
Is anybody on it? I'm still unable to get a connection via PoP...
Aiccu connection can be made, but no connectivity
See that big orange box and provide proper details. We do not have access to your host and thus you'll need to provide details. (Oh and no, we do not want access to your host either, as we are not a helpdesk).
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Friday, 05 November 2010 20:24:51
Hi there,
I'm trying to describe the problem as detailed as possible.
First I have to say that I allready was able to connect with this configuration to a IPv6 host. I'm using almost the same setting on two computers. Both run with Windows 7 Professional x64. Software firewall is Windows firewall, hardware firewall is my router D-Link DIR-300. With aiccu and ayiya tunnel I had no problems with firewalls when I set up the software first. My antivirus software is Avast! Free Antivirus 5. My desktop pc is connected via LAN with the router. I had to set my IPv6-Address of the LAN interface to 2002:81a8:102:: so that I could load websites. When I start the tunnel (aiccu.exe start) in cmd the ethernet capturing with wireshark looks like this:
capture.zip
My internal IPv4 addresses beginn with 10.10.xx.xx
I also did a screenshot of the status pages from my LAN interface (left) and the tunnel adapter (right). Any other interface is disabled or not connected.
Screenshot
In the windows networkcenter my lan interface is connected to the internet, the IPv6 tunnel is not connected to the internet.
Traceroutes to the PoP are in my previous post. The PoP is not pingable via IPv6.
Hope this information helps you to help me ;)
Aiccu connection can be made, but no connectivity
Please try to actually read that big orange box, there is a nice checklist, those items are what we need, that is if there really is a PoP issue; the PoP is looking fine, thus I can only recommend that you see the wiki for information on setting up a tunnel on Vista/Seven, and use the forums for any further help.
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Thursday, 11 November 2010 20:55:40
And again. Sorry to bother you with this problem once more. The symptoms are exactly the same as above, including the IPv4 traceroute to dedus01.sixxs.net that shows one latency value and two timeout stars again (see below).
(with -n this time, because my DNS works over the SixXS IPv6 servers and I don't want to change it now)
jannis@Antarctica ~ $ traceroute -n dedus01.sixxs.net
traceroute to dedus01.sixxs.net (91.184.37.98), 64 hops max, 52 byte packets
1 192.168.182.1 2.485 ms 0.974 ms 1.076 ms
2 213.20.56.10 24.521 ms 25.578 ms 25.174 ms
3 195.71.159.214 24.484 ms 24.958 ms 24.644 ms
4 213.20.250.114 24.644 ms 24.429 ms 25.762 ms
5 62.53.239.97 27.550 ms 26.899 ms 28.326 ms
6 195.71.158.17 26.708 ms
195.71.212.221 27.177 ms
195.71.158.21 27.093 ms
7 195.71.254.146 45.800 ms 30.049 ms 30.236 ms
8 195.71.243.34 30.506 ms 30.199 ms 32.307 ms
9 195.71.243.230 31.208 ms 31.757 ms 29.988 ms
10 194.146.118.13 31.453 ms 29.779 ms 30.947 ms
11 91.184.37.98 29.916 ms * *
I don't include all the other outputs now since they show exactly the same as the ones in my above post.
I guess the issue will be gone again in a few hours, but since it's occuring over and over again I'd like to know what's happening here.
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Thursday, 11 November 2010 21:05:44
dedus01 crashed a few minutes ago but should be available by now - please try again.
Sorry for any inconvenience.
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Thursday, 11 November 2010 21:06:10
Indeed. Thanks.
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Saturday, 18 December 2010 19:43:09
This seems to happen repeatedly, the issue is occuring again right now and yet
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Saturday, 18 December 2010 19:45:21
This is an interesting one, I didn't include a desc tag in a link in my post, so the post obviously got replaced by an error message.
Anyway, what I wrote was that the issue is occuring again without https://www.sixxs.net/pops/speedpartner/ denoting "Down". So it seems to me that the down-ness detection mechanism is somewhat broken for dedus01.
State change: resolved
Shadow Hawkins on Thursday, 11 November 2010 21:08:11
The state of this ticket has been changed to resolved
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Saturday, 18 December 2010 22:33:26
I am sorry to report that dedus01 seems to be down again. local setup unchanged, and here is the output of aiccu autotest:
root@one:~# aiccu autotest
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (10.0.0.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 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.018 ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.042 ms
64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.026 ms
--- 10.0.0.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.018/0.028/0.042/0.011 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(84) bytes of data.
64 bytes from 91.184.37.98: icmp_seq=1 ttl=59 time=8.70 ms
64 bytes from 91.184.37.98: icmp_seq=2 ttl=59 time=9.10 ms
64 bytes from 91.184.37.98: icmp_seq=3 ttl=59 time=9.89 ms
--- 91.184.37.98 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 8.706/9.233/9.894/0.506 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, 60 byte packets
1 gateway.home.knupe.de (10.0.0.1) 0.552 ms 1.009 ms 1.116 ms
2 10.80.0.1 (10.80.0.1) 12.520 ms 12.470 ms 12.591 ms
3 1211F-MX960-01-xe-9-1-0.dortmund.unity-media.net (80.69.103.113) 12.804 ms 15.506 ms 15.613 ms
4 1411G-MX960-01-ae8.neuss.unity-media.net (80.69.107.9) 17.160 ms 17.226 ms 17.415 ms
5 speedpartner.dus.ecix.net (194.146.118.13) 17.635 ms 19.641 ms 19.974 ms
6 dedus01.sixxs.net (91.184.37.98) 19.322 ms 22.752 ms 22.942 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: icmp_seq=1 ttl=64 time=0.017 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.034 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.034 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.017/0.028/0.034/0.009 ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a01:198:200:96e::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2a01:198:200:96e::2(2a01:198:200:96e::2) 56 data bytes
64 bytes from 2a01:198:200:96e::2: icmp_seq=1 ttl=64 time=0.010 ms
64 bytes from 2a01:198:200:96e::2: icmp_seq=2 ttl=64 time=0.035 ms
64 bytes from 2a01:198:200:96e::2: icmp_seq=3 ttl=64 time=0.051 ms
--- 2a01:198:200:96e::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.010/0.032/0.051/0.016 ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2a01:198:200:96e::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:96e::1(2a01:198:200:96e::1) 56 data bytes
--- 2a01:198:200:96e::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2016ms
######
###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
### This confirms that you can reach the central machine of SixXS
### If that one is reachable you should be able to reach most IPv6 destinations
### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection
### If your browser supports IPv6 and uses it of course.
traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c), 30 hops max, 80 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
######
###### [8/8] Traceroute6 to (www.kame.net)
### This confirms that you can reach a Japanese IPv6 destination
### If that one is reachable you should be able to reach most IPv6 destinations
### You should also check http://www.kame.net which should display
### a animated kame (turtle), of course only when your browser supports and uses IPv6
traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
######
###### ACCU Quick Connectivity Test (done)
### Either the above all works and gives no problems
### or it shows you where what goes wrong
### Check the SixXS FAQ (http://www.sixxs.net/faq/
### for more information and possible solutions or hints
### Don't forget to check the Forums (http://www.sixxs.net/forum/)
### for a helping hand.
### Passing the output of 'aiccu autotest >aiccu.log' is a good idea.
root@one:~#
Aiccu connection can be made, but no connectivity
Shadow Hawkins on Saturday, 18 December 2010 23:32:43
Thank you, it works now.
|
![[ch]](/s/countries/ch.gif)
Posting is only allowed when you are 