Windows 7 tunnel goes down unexpectedly
Shadow Hawkins on Tuesday, 08 December 2009 10:03:31
Dear all,
I have installed aiccu-console on Windows 7 and have done all the steps in the wiki for Vista configuration. In fact, the tunnel is running, but closed unexpectedly after different time. I have started the tunnel and it was still up after 5 minutes (heartbeat) but closed after 9 minutes. Stopped the tunnel and started it again it was up for 12 minutes. When trieing to ping I receive
C:\>ping -6 ipv6.google.com
Ping wird ausgefhrt fr ipv6.l.google.com [2001:4860:a003::68] mit 32 Bytes Dat
en:
Zielport nicht erreichbar.
Zielport nicht erreichbar.
Zielport nicht erreichbar.
Zielport nicht erreichbar.
Ping-Statistik fr 2001:4860:a003::68:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4
(100% Verlust),
when the tunnel is down.
Can anybody help me please? I have no idea what to do. Do you need further information?
Thanks in advance
Sebastian
Windows 7 tunnel goes down unexpectedly
Jeroen Massar on Tuesday, 08 December 2009 10:08:54
* Check the clock on your computer (NTP sync it with a local NTP server)
* Check your firewall, NAT box etc
=> Provide a LOT more information about your network.
Windows 7 tunnel goes down unexpectedly
Shadow Hawkins on Tuesday, 08 December 2009 10:20:00
Thanks for your reply!
Time is synced with 0.de.pool.ntp.org.
For testing reasons, I have switched off the firewall for the internal and external network in 7, but that does not help. I have a Mac within my network, and there are no problems running the tunnel over days. Thats why I think I have no problem with my fritzbox.
I have just this small aicco.conf:
username ****-SIXXS
password ********
tunnel_id T*****
verbose true
automatic false
What information do you need regarding my network? The 7 computer has a fixed ipv4 address (192.168.1.200) with fixed gateway and fixed DNS (the gatweway).
Installed is a Tun/Tap V9 as provided in the Wiki.
Is it normal that the Tun/Tap Network adapter semms not to be "cabled" after establishing the tunnel. It's still in state "Media disconnected".
The tunnel should be a 6in4 tunnel with is perfectly working on my Mac.
Any ideas?
Windows 7 tunnel goes down unexpectedly
Jeroen Massar on Tuesday, 08 December 2009 10:33:59 Thats why I think I have no problem with my fritzbox.
Fritzboxes are effectively Linux boxes and they also do connection tracking, see the FAQ. But a better question is, why not terminate the tunnel on your fritzbox, quite a few models support IPv6 directly.
Is it normal that the Tun/Tap Network adapter semms not to be "cabled" after establishing the tunnel. It's still in state "Media disconnected". The tunnel should be a 6in4 tunnel with is perfectly working on my Mac.
Tun/TAP is used for AYIYA tunnels, not for proto-41/6in4/heartbeat tunnels.
Windows 7 tunnel goes down unexpectedly
Shadow Hawkins on Tuesday, 08 December 2009 10:41:55 quite a few models support IPv6 directly
But not mine :-( (Fritzbox 7141)
Tun/TAP is used for AYIYA tunnels, not for proto-41/6in4/heartbeat tunnels.
Ok, i have just recognized that.
In fact the Fritzbox is also located in front of my Mac and my Mac is working properly. I'm really thinking that the problem is located in Win 7.
Is there anything I can check again?
Thank you very much!
Windows 7 tunnel goes down unexpectedly
Shadow Hawkins on Tuesday, 08 December 2009 11:02:18
Here is my output when starting the tunnel:
sock_getline() : "POP Id: dedus01"
sock_getline() : "IPv4 Endpoint: heartbeat"
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 T******
sock_printf() : "QUIT Insomnia"
Tunnel Information for T*:
PoP Id : dedus01
IPv6 Local : *
IPv6 Remote : *
Tunnel Type : 6in4-heartbeat
Adminstate : enabled
Userstate : enabled
Name : My First Tunnel
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
heartbeat_socket() - IPv4 : 192.168.1.200
[HB] HEARTBEAT TUNNEL 2a01:198:200:614::2 sender 1260266378 add1ff6143a0037a969d
dee153f056a4
This is what is confusing me
heartbeat_socket() - IPv4 : 192.168.1.200
Is this correct?
Windows 7 tunnel goes down unexpectedly
Jeroen Massar on Tuesday, 08 December 2009 11:32:22
Of course that is correct, as that is your local tunnel endpoint.
One of the many things that can go wrong here is that your fritzbox sends return traffic (pop to you) to the wrong box, especially as you seem to have used both the mac and the windows box.
Hard to debug though. Wireshark might be one of the few things that can give you more information.
Posting is only allowed when you are logged in. |