IPv6 on new Vista machine
Shadow Hawkins on Wednesday, 12 November 2008 21:20:38
Untill now I used a XP machine with Aiccu, without any problem. I just bought a Vista machine and I have some difficulties getting IPv6 working.
With test Isget this result. Can anyone help me a bit further ?
Microsoft Windows [versie 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. Alle rechten voorbehouden.
C:\Windows\system32>aiccu.exe
aiccu.exe wordt niet herkend als een interne
of externe opdracht, programma of batchbestand.
C:\Windows\system32>cd..
C:\Windows>cd
C:\Windows
C:\Windows>cd..
C:\>cd users
C:\Users>cd arno
C:\Users\Arno>cd desktop
C:\Users\Arno\Desktop>aiccu.exe autotest
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
001-SP1"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1226520460"
sock_printf() : "username AVS1-6BONE"
sock_getline() : "200 Choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 0a12eacb202436292d810348e598da8b"
sock_printf() : "authenticate md5 028707f0cb0222f213d429a299513797"
sock_getline() : "200 Succesfully logged in using md5 as AVS1-6BONE (Arno van St
appershoef) from 2001:7b8:3:4f:202:b3ff:fe46:bec"
sock_printf() : "tunnel show T17955"
sock_getline() : "201 Showing tunnel information for T17955"
sock_getline() : "TunnelId: T17955"
sock_getline() : "Type: ayiya"
sock_getline() : "IPv6 Endpoint: 2001:7b8:2ff:27d::2"
sock_getline() : "IPv6 POP: 2001:7b8:2ff:27d::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1280"
sock_getline() : "Tunnel Name: My First Tunnel"
sock_getline() : "POP Id: nlede01"
sock_getline() : "IPv4 Endpoint: ayiya"
sock_getline() : "IPv4 POP: 193.109.122.244"
sock_getline() : "UserState: enabled"
sock_getline() : "AdminState: enabled"
sock_getline() : "Password: 27f6d9510f07b0fb54a533f6f54efe0c"
sock_getline() : "Heartbeat_Interval: 60"
sock_getline() : "202 Done"
Succesfully retrieved tunnel information for T17955
sock_printf() : "QUIT Die With You"
Tunnel Information for T17955:
PoP Id : nlede01
IPv6 Local : 2001:7b8:2ff:27d::2/64
IPv6 Remote : 2001:7b8:2ff:27d::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 {656DF4B0-C540-47E4-8D49-18E550D1CB9B},
using it
[tun-start] Trying \\.\Global\{656DF4B0-C540-47E4-8D49-18E550D1CB9B}.tap
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[AYIYA-start] : Anything in Anything (draft-02)
heartbeat_socket() - IPv4 : 80.56.177.145
#######
[AYIYA-tun->tundev] : (Socket to TUN) started
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (80.56.177.145)
### 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 80.56.177.145 met 32 bytes aan gegevens:
Antwoord van 80.56.177.145: bytes=32 tijd<1 ms TTL=128
Antwoord van 80.56.177.145: bytes=32 tijd<1 ms TTL=128
Antwoord van 80.56.177.145: bytes=32 tijd<1 ms TTL=128
Ping-statistieken voor 80.56.177.145:
Pakketten: verzonden = 3, ontvangen = 3, verloren = 0
(0% verlies).
De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (193.109.122.244)
### 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 193.109.122.244 met 32 bytes aan gegevens:
Antwoord van 193.109.122.244: bytes=32 tijd=12 ms TTL=59
Antwoord van 193.109.122.244: bytes=32 tijd=9 ms TTL=59
Antwoord van 193.109.122.244: bytes=32 tijd=11 ms TTL=59
Ping-statistieken voor 193.109.122.244:
Pakketten: verzonden = 3, ontvangen = 3, verloren = 0
(0% verlies).
De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 9ms, Maximum = 12ms, Gemiddelde = 10ms
######
####### [3/8] Traceroute to the PoP (193.109.122.244) 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
Traceren van de route naar nlede01.sixxs.net [193.109.122.244]
via maximaal 30 hops:
1 4 ms 5 ms 3 ms 10.15.44.1
2 6 ms 4 ms 5 ms p50097.net.upc.nl [212.142.50.97]
3 8 ms 7 ms 8 ms p14232073.net.upc.nl [212.142.32.73]
4 9 ms 8 ms 7 ms p14232129.net.upc.nl [212.142.32.129]
5 7 ms 8 ms 9 ms 213.46.183.65
6 9 ms 9 ms 10 ms amsix-501.xe-0-0-0.jun1.kelvin.network.bit.nl [1
95.69.144.200]
7 12 ms 10 ms 13 ms nlede01.sixxs.net [193.109.122.244]
De trace is voltooid.
######
###### [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 van ::1 met 32 bytes aan 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 milliseconden:
Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:7b8:2ff:27d::2
)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
Pingen naar 2001:7b8:2ff:27d::2 van 2001:7b8:2ff:27d::2 met 32 bytes aan gegeven
s:
Antwoord van 2001:7b8:2ff:27d::2: tijd<1 ms
Antwoord van 2001:7b8:2ff:27d::2: tijd<1 ms
Antwoord van 2001:7b8:2ff:27d::2: tijd<1 ms
Ping-statistieken voor 2001:7b8:2ff:27d::2:
Pakketten: verzonden = 3, ontvangen = 3, verloren = 0
(0% verlies).
De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:7b8:2ff:27d::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:7b8:2ff:27d::1 van 2001:7b8:2ff:27d::2 met 32 bytes aan gegeven
s:
Antwoord van 2001:7b8:2ff:27d::1: tijd=12 ms
Antwoord van 2001:7b8:2ff:27d::1: tijd=14 ms
Antwoord van 2001:7b8:2ff:27d::1: tijd=11 ms
Ping-statistieken voor 2001:7b8:2ff:27d::1:
Pakketten: verzonden = 3, ontvangen = 3, verloren = 0
(0% verlies).
De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 11ms, Maximum = 14ms, Gemiddelde = 12ms
######
###### [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.
tracert6 wordt niet herkend als een interne
of externe opdracht, programma of batchbestand.
######
###### [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
tracert6 wordt niet herkend als een interne
of externe opdracht, programma of batchbestand.
######
###### 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.
C:\Users\Arno\Desktop>
IPv6 on new Vista machine
Jeroen Massar on Thursday, 13 November 2008 00:04:51 Antwoord van 2001:7b8:2ff:27d::1: tijd=12 ms
Looks like it works to me.
For actual usage though it seems Vista is a bit odd, see this forum entry for a possible solution.
Posting is only allowed when you are logged in. |