|
Ticket ID: SIXXS #3691325 Ticket Status: User PoP:
AICCU blocks all network connections after few hours
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Wednesday, 16 February 2011 22:23:42
Hello,
I'm using an AYIYA tunnel on my home server running Windows XP SP3. I've configured the console version of AICCU, and the tunnel actually works well. But after 2-3 hours, all network connections stop on the machine. The running usenet download using an ipv6-server stops, but also all ipv4 connections don't work anymore. I even can't ping the box.
When I walk to the box, all appears normal. AICCU still says the the tunnel is up, there are no errors. After I stop AICCU, all connections start to work immediately. If I then restart AICCU, all is still ok. The usenet downloads start again. But after 2-3 hours the whole story restarts.
So I made a little vbscript that kills and restarts AICCU every 2 hours, which has worked well for a few days. But this isn't a proper solution off course.
What could solve my problem? Why does it always occur after 2-3 hours? What happens at that moment?
Thanks in advance for any help.
AICCU blocks all network connections after few hours
Shadow Hawkins on Wednesday, 16 February 2011 22:25:51
Oh I forgot to mention a few infos:
Tunnel ID: T32565
Type: AYIYA
State change: user
The state of this ticket has been changed to user
AICCU blocks all network connections after few hours
Note also that automatically restarting AICCU causes TIC connections, that might just lead you into automatically getting blocked from the TIC server.
As for what happens on your machine, no idea, missing a lot of details about your setup and what goes wrong. Please read the "Reporting Problems Checklist" on the contact page for more details.
AICCU blocks all network connections after few hours
Shadow Hawkins on Thursday, 17 February 2011 11:49:56
Sorry for not providing details.
When running AICCU, this is the output:
Succesfully retrieved tunnel information for T32565
[warning] Couln't open registery key: SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000\ComponentId (t2/2 vs 0/384 vs 1)
[AYIYA-start] : Anything in Anything (draft-02)
[AYIYA-tun->tundev] : (Socket to TUN) started
this is the output for running AICCU test:
C:\Documents and Settings\Koen>C:\aiccu\aiccu-2008-03-15-windows-console.exe tes
t aiccu.conf
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/5.1.2
600-SP3"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1297899056"
sock_printf() : "username KVB4-SIXXS"
sock_getline() : "200 KVB4-SIXXS choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 1436b0332a8fe4df71df5ed569fba423"
sock_printf() : "authenticate md5 eef39263aaa43dd18ba581fa5ab1ec5d"
sock_getline() : "200 Successfully logged in using md5 as KVB4-SIXXS (Koen van B
eek)"
sock_printf() : "tunnel show T32565"
sock_getline() : "201 Showing tunnel information for T32565"
sock_getline() : "TunnelId: T32565"
sock_getline() : "Type: ayiya"
sock_getline() : "IPv6 Endpoint: 2001:838:300:38f::2"
sock_getline() : "IPv6 POP: 2001:838:300:38f::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1280"
sock_getline() : "Tunnel Name: My First Tunnel"
sock_getline() : "POP Id: nlams01"
sock_getline() : "IPv4 Endpoint: ayiya"
sock_getline() : "IPv4 POP: 213.197.27.252"
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 T32565
sock_printf() : "QUIT Something I can never have"
Tunnel Information for T32565:
PoP Id : nlams01
IPv6 Local : 2001:838:300:38f::2/64
IPv6 Remote : 2001:838:300:38f::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
Name : My First Tunnel
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[warning] Couldn't open registry key: SYSTEM\CurrentControlSet\Control\Class\{4D
36E972-E325-11CE-BFC1-08002BE10318}\0000\ComponentId (t2/2 vs 0/1668 vs 1)
Found interface named 'aiccu', with guid {C1631505-4B77-4C9F-909B-EF3D9B926612},
using it
[tun-start] Trying \\.\Global\{C1631505-4B77-4C9F-909B-EF3D9B926612}.tap
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[AYIYA-start] : Anything in Anything (draft-02)
heartbeat_socket() - IPv4 : 192.168.2.111
#######
####### AICCU Quick Connectivity Test
[AYIYA-tun->tundev] : (Socket to TUN) started
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.2.111)
### 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
Pingen naar 192.168.2.111 met 32 byte gegevens:
Antwoord van 192.168.2.111: bytes=32 tijd<1 ms TTL=128
Antwoord van 192.168.2.111: bytes=32 tijd<1 ms TTL=128
Antwoord van 192.168.2.111: bytes=32 tijd<1 ms TTL=128
Ping-statistieken voor 192.168.2.111:
Pakketten: verzonden = 3, ontvangen = 3, verloren = 0
(0% verlies).De gemiddelde tijd voor het uitvoeren van n bewerking in mill
iseconden:
Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms
######
Did this work? [Y/n] y
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (213.197.27.252)
### 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
Pingen naar 213.197.27.252 met 32 byte gegevens:
Antwoord van 213.197.27.252: bytes=32 tijd=10 ms TTL=57
Antwoord van 213.197.27.252: bytes=32 tijd=14 ms TTL=57
Antwoord van 213.197.27.252: bytes=32 tijd=14 ms TTL=57
Ping-statistieken voor 213.197.27.252:
Pakketten: verzonden = 3, ontvangen = 3, verloren = 0
(0% verlies).De gemiddelde tijd voor het uitvoeren van n bewerking in mill
iseconden:
Minimum = 10ms, Maximum = 14ms, Gemiddelde = 12ms
######
Did this work? [Y/n] y
####### [3/8] Traceroute to the PoP (213.197.27.252) 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
Bezig met het traceren van de route naar tunnelserver.concepts-ict.net [213.197.
27.252]
via maximaal 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 6 ms 8 ms 7 ms 53524801.cm-6-3b.dynamic.ziggo.nl [83.82.72.1]
3 6 ms 8 ms 9 ms bd-rc0002-cr102-irb-202.core.as9143.net [213.51.
149.33]
4 14 ms 11 ms 12 ms asd-tr0409-cr101-ae9-0.core.as9143.net [213.51.1
58.76]
5 11 ms 9 ms 11 ms TenGigabitEthernet-1-3.br0.ams-glob.concepts-ict
.net [195.69.144.32]
6 10 ms 11 ms 11 ms TenGigabitEthernet-1-2.br0.ams-nik.concepts-ict.
net [213.197.18.10]
7 12 ms 11 ms 11 ms GigabitEthernet-0-3-0.br1.brd-cp.concepts-ict.ne
t [213.197.18.50]
8 13 ms 11 ms 11 ms tunnelserver.concepts-ict.net [213.197.27.252]
De trace is voltooid.
######
Did this work? [Y/n] y
###### [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
Pingen naar ::1 met 32 byte gegevens:
Antwoord van ::1: tijd<1 ms
Antwoord van ::1: tijd<1 ms
Antwoord van ::1: tijd<1 ms
Ping-statistieken voor ::1:
Pakketten: verzonden = 3, ontvangen = 3, verloren = 0
(0% verlies).De gemiddelde tijd voor het uitvoeren van n bewerking in mill
iseconden:
Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms
######
Did this work? [Y/n] y
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:838:300:38f::2
)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
Pingen naar 2001:838:300:38f::2 met 32 byte gegevens:
Antwoord van 2001:838:300:38f::2: tijd<1 ms
Antwoord van 2001:838:300:38f::2: tijd<1 ms
Antwoord van 2001:838:300:38f::2: tijd<1 ms
Ping-statistieken voor 2001:838:300:38f::2:
Pakketten: verzonden = 3, ontvangen = 3, verloren = 0
(0% verlies).De gemiddelde tijd voor het uitvoeren van n bewerking in mill
iseconden:
Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms
######
Did this work? [Y/n] y
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:838:300:38f::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
Pingen naar 2001:838:300:38f::1 met 32 byte gegevens:
Antwoord van 2001:838:300:38f::1: tijd=11 ms
Antwoord van 2001:838:300:38f::1: tijd=13 ms
Antwoord van 2001:838:300:38f::1: tijd=13 ms
Ping-statistieken voor 2001:838:300:38f::1:
Pakketten: verzonden = 3, ontvangen = 3, verloren = 0
(0% verlies).De gemiddelde tijd voor het uitvoeren van n bewerking in mill
iseconden:
Minimum = 11ms, Maximum = 13ms, Gemiddelde = 12ms
######
Did this work? [Y/n] y
###### [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 connecti
on
### If your browser supports IPv6 and uses it of course.
Route traceren tot: noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c]
vanaf: 2001:838:300:38f::2 via maximaal 30 hops:
1 10 ms 10 ms 11 ms gw-912.ams-01.nl.sixxs.net [2001:838:300:38f:
:1]
2 10 ms 10 ms 10 ms teredo-relay.concepts-ict.net [2001:838:2:1::
30:87]
3 10 ms 14 ms 14 ms ge-1-3-0-2.brd.ipv6.concepts-ict.net [2001:83
8:2:1::1]
4 14 ms 10 ms 26 ms noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7
c]
De trace is voltooid.
######
Did this work? [Y/n] y
###### [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
Route traceren tot: orange.kame.net [2001:200:dff:fff1:216:3eff:feb1:44d7]
vanaf: 2001:838:300:38f::2 via maximaal 30 hops:
1 13 ms 12 ms 12 ms gw-912.ams-01.nl.sixxs.net [2001:838:300:38f:
:1]
2 12 ms 12 ms 13 ms teredo-relay.concepts-ict.net [2001:838:2:1::
30:87]
3 12 ms 13 ms 12 ms ge-1-3-0-2.brd.ipv6.concepts-ict.net [2001:83
8:2:1::1]
4 14 ms 14 ms 14 ms gi2-11.nikhef.ipv6.concepts-ict.net [2001:838
:5:a::1]
5 15 ms 16 ms 15 ms ge-0.ams-ix.amstnl02.nl.bb.gin.ntt.net [2001:
7f8:1::a500:2914:1]
6 297 ms 299 ms 299 ms as-0.r25.tokyjp01.jp.bb.gin.ntt.net [2001:418
:0:2000::16]
7 292 ms 289 ms 289 ms ae-9.r20.tokyjp01.jp.bb.gin.ntt.net [2001:218
:0:2000::1c5]
8 296 ms 296 ms 309 ms po-1.a15.tokyjp01.jp.ra.gin.ntt.net [2001:218
:0:6000::10e]
9 287 ms 410 ms 298 ms ge-8-2.a15.tokyjp01.jp.ra.gin.ntt.net [2001:2
18:2000:5000::82]
10 285 ms 285 ms 285 ms ve44.foundry6.otemachi.wide.ad.jp [2001:200:0
:10::141]
11 285 ms 285 ms 285 ms ve42.foundry4.nezu.wide.ad.jp [2001:200:0:11:
:66]
12 290 ms 293 ms 289 ms cloud-net1.wide.ad.jp [2001:200:0:1c0a:218:8b
ff:fe43:d1d0]
13 287 ms 288 ms 289 ms 2001:200:dff:fff1:216:3eff:feb1:44d7
De trace is voltooid.
######
Did this work? [Y/n] y
###### 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.
*** press a key to continue ***
C:\Documents and Settings\Koen>
The 'Reporting Problems' checklist mentioned this:
"Always provide your NIC handle and if applicable the Tunnel or Route IDs you wish to discuss."
I don't realy understand what a NIC handle is, although I've looked it up on Google.
The setup:
Internet --> Cable modem --> DD-WRT router (gets Internet IP via DHCP from modem) --> All clients have IP 192.168.2.xxx.
The router is 192.168.2.1
The server is 192.168.2.111.
Server: Windows XP Pro SP3 NL. Fully up-to-date, including the optional updates.
I use the standard XP Firewall and Avast Home Edition as antivirus software.
Traceroute POP via ipv4:
Microsoft Windows XP [versie 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Koen>tracert 213.197.27.252
Bezig met het traceren van de route naar tunnelserver.concepts-ict.net [213.197.
27.252]
via maximaal 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 8 ms 8 ms 7 ms 53524801.cm-6-3b.dynamic.ziggo.nl [83.82.72.1]
3 8 ms 7 ms 7 ms bd-rc0002-cr102-irb-202.core.as9143.net [213.51.
149.33]
4 12 ms 11 ms 12 ms asd-tr0409-cr101-ae9-0.core.as9143.net [213.51.1
58.76]
5 13 ms 9 ms 11 ms TenGigabitEthernet-1-3.br0.ams-glob.concepts-ict
.net [195.69.144.32]
6 8 ms 11 ms 7 ms TenGigabitEthernet-1-2.br0.ams-nik.concepts-ict.
net [213.197.18.10]
7 9 ms 11 ms 15 ms GigabitEthernet-0-3-0.br1.brd-cp.concepts-ict.ne
t [213.197.18.50]
8 11 ms 11 ms 11 ms tunnelserver.concepts-ict.net [213.197.27.252]
De trace is voltooid.
via ipv6:
C:\Documents and Settings\Koen>tracert 2001:838:300:38f::1
Bezig met het traceren van de route naar gw-912.ams-01.nl.sixxs.net [2001:838:30
0:38f::1]
via maximaal 30 hops:
1 88 ms 60 ms 79 ms gw-912.ams-01.nl.sixxs.net [2001:838:300:38f::1]
De trace is voltooid.
I hope this is the information you need. Thanks for the fast response.
AICCU blocks all network connections after few hours
Everything shows as working, thus what is there to resolve?
Please for debugging problems on your side peruse the forums.
AICCU blocks all network connections after few hours
Shadow Hawkins on Thursday, 17 February 2011 15:02:46
Well, my problem is that everything seems to be OK, until all connections are blocked after 2-3 hours. It's caused by AICCU, because everything works again after restarting it.
I already have read along the forums, but have yet to discover the same problem I'm having.
AICCU blocks all network connections after few hours
Shadow Hawkins on Friday, 02 December 2011 18:50:29
I think he has having problems with the Aiccu client like more people do. There was a ticket before about it but it has not been solved yet. It's this thread/ticket:
http://www.sixxs.net/forum/?msg=apps-686074
Currently Aiccu is using a lot of system resources resulting in slowing down Windows and/or other applications. Aiccu is using system handles and not making them free after usage. See this Wiki about Handle Leaks. http://en.wikipedia.org/wiki/Handle_leak
Some more information wich is showing that Aiccu is using that much handles.
Process Explorer: Performance
Task ManagerProcess List
Handles: ~16.7 Million...
If I combine the Wikipedia page, my problems and the problems others are having, I am thinking this is a bug in the Aiccu windows software. I made a process dump with Process Explorer, wich I can make available on request for debugging purpose.
Maybe the Windows concole version source code can be made public so that the SixXS community can try to solve the issue? Willing to help to make SixXs/Aiccu better.
Windows version: Windows 7 Pro (64bit, Dutch, up-to-date)
Aiccu version: Aiccu 2008-03-15 (console)
(Aiccu test is not relevant to this issue, the connection is working but with performance issues)
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 16 February 2011 23:08:19
Posting is only allowed when you are 
