SixXS::Sunset 2017-06-06

IPv6 on Vista
[nl] Shadow Hawkins on Tuesday, 04 November 2008 08:23:07
Hallo I have tried to set up a IPv6 connection but it never worked!¦ I really don't know what I do wrong. I have windows vista, and use a Linksys wag325n. My tunnel is an ayiya . Can't ping anything with ping -6, only thing works is IPv4. Hope there is someone that can help me. Tnx Joey
IPv6 on Vista
[ch] Jeroen Massar SixXS Staff on Tuesday, 04 November 2008 08:24:33
You did use the console version of AICCU and installed the tap901 driver I hope? :) If you did, then it should be quite easy to get the debug output from it by disabling daemonize mode and setting verbose to true. Pass that debug output here and it should help a lot already. Of course if it doesn't work, do a 'netsh int ipv6 reset' before running aiccu as that will clear out any left-over settings from other attempts.
IPv6 on Vista
[nl] Shadow Hawkins on Tuesday, 04 November 2008 17:06:32
Yes,and know I can ping -6 to ipv6.google.com via the cmd. But I can't visit ipv6.google.com with a webrouwser(IE7, FF3.0)
IPv6 on Vista
[nl] Shadow Hawkins on Tuesday, 04 November 2008 18:01:31
I see know in my graphs on sixxs.net that my tunnel is working, can use it with utorrent, but stil not with my webrouwser. Tnx
IPv6 on Vista
[ch] Jeroen Massar SixXS Staff on Tuesday, 04 November 2008 20:59:30
Which source/destination address? Please provide a lot more details about your configuration. Do note also that Vista apparently has some strange rules on selecting if an IPv6 address can be used for actual connects or not. http://www.ipv6.sixxs.net which is an IPv6 only URL should btw always work, even with those rules in place.
IPv6 on Vista
[nl] Shadow Hawkins on Tuesday, 04 November 2008 21:04:31
Not even http://www.ipv6.sixxs.net works. I can ping -6 to kame.net, but when i put it in the browser won't work, the same with all other sites that are ipv6. I don't know witch source/destination address you mean? hope you can help! tnx
IPv6 on Vista
[ch] Jeroen Massar SixXS Staff on Tuesday, 04 November 2008 21:08:44
start -> run, then type "cmd" and in there type "ipconfig /all", then do a right mouse and from the menu "select all", then hit enter, and paste that in the forum between a [ code ] block as indicated on the right of the textbox, thus without the spaces.
IPv6 on Vista
[nl] Shadow Hawkins on Tuesday, 04 November 2008 21:12:41
Windows IP-configuratie Hostnaam . . . . . . . . . . . . : PC_van_joey Primair DNS-achtervoegsel . . . . : Knooppunttype . . . . . . . . . . : gemengd IP-routering ingeschakeld . . . . : nee WINS-proxy ingeschakeld . . . . . : nee DNS-achtervoegselzoeklijst. . . . : WAG325N Ethernet-adapter sixxs: Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : TAP-Win32 Adapter V9 Fysiek adres. . . . . . . . . . . : 00-FF-D2-C8-D3-0F DHCP ingeschakeld . . . . . . . . : ja Autom. configuratie ingeschakeld : ja IPv6-adres. . . . . . . . . . . . : 2001:960:2:5d9::2(voorkeur) Link-local IPv6-adres . . . . . . : fe80::dd38:a0dd:d3f1:3217%30(voorkeur) Automatisch geconf.IPv4-adres . . : 169.254.50.23(voorkeur) Subnetmasker. . . . . . . . . . . : 255.255.0.0 Standaardgateway. . . . . . . . . : 2001:960:2:5d9::1 DNS-servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS via TCPIP . . . . . . . . : ingeschakeld Ethernet-adapter Bluetooth-netwerkverbinding 4: Mediumstatus. . . . . . . . . . . : medium ontkoppeld Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : Bluetooth-apparaat (Personal Area Network ) #4 Fysiek adres. . . . . . . . . . . : 00-10-60-D0-23-F9 DHCP ingeschakeld . . . . . . . . : ja Autom. configuratie ingeschakeld : ja Adapter voor draadloos LAN Draadloze netwerkverbinding 2: Verbindingsspec. DNS-achtervoegsel: WAG325N Beschrijving. . . . . . . . . . . : Fujitsu Siemens Computers WLAN 802.11b/g (SiS163u) Fysiek adres. . . . . . . . . . . : 00-19-99-10-A4-C7 DHCP ingeschakeld . . . . . . . . : ja Autom. configuratie ingeschakeld : ja Link-local IPv6-adres . . . . . . : fe80::b065:832:d4eb:7609%20(voorkeur) IPv4-adres. . . . . . . . . . . . : 192.168.1.102(voorkeur) Subnetmasker. . . . . . . . . . . : 255.255.255.0 Lease verkregen . . . . . . . . . : dinsdag 4 november 2008 19:46:48 Lease verlopen. . . . . . . . . . : woensdag 5 november 2008 19:46:48 Standaardgateway. . . . . . . . . : 192.168.1.1 DHCP-server . . . . . . . . . . . : 192.168.1.1 DNS-servers . . . . . . . . . . . : 195.121.1.34 195.121.1.66 NetBIOS via TCPIP . . . . . . . . : ingeschakeld Ethernet-adapter LAN-verbinding: Mediumstatus. . . . . . . . . . . : medium ontkoppeld Verbindingsspec. DNS-achtervoegsel: WAG325N Beschrijving. . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet Fysiek adres. . . . . . . . . . . : 00-14-0B-32-B3-B3 DHCP ingeschakeld . . . . . . . . : ja Autom. configuratie ingeschakeld : ja Ethernet-adapter LAN-verbinding 2: Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet 1 Fysiek adres. . . . . . . . . . . : 00-50-56-C0-00-01 DHCP ingeschakeld . . . . . . . . : nee Autom. configuratie ingeschakeld : ja Link-local IPv6-adres . . . . . . : fe80::1d2:8aea:14c:abb8%16(voorkeur) IPv4-adres. . . . . . . . . . . . : 192.168.65.1(voorkeur) Subnetmasker. . . . . . . . . . . : 255.255.255.0 Standaardgateway. . . . . . . . . : DNS-servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS via TCPIP . . . . . . . . : ingeschakeld Ethernet-adapter LAN-verbinding 3: Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet 8 Fysiek adres. . . . . . . . . . . : 00-50-56-C0-00-08 DHCP ingeschakeld . . . . . . . . : nee Autom. configuratie ingeschakeld : ja Link-local IPv6-adres . . . . . . : fe80::a5fc:2ded:2b68:f045%18(voorkeur) IPv4-adres. . . . . . . . . . . . : 192.168.40.1(voorkeur) Subnetmasker. . . . . . . . . . . : 255.255.255.0 Standaardgateway. . . . . . . . . : DNS-servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS via TCPIP . . . . . . . . : ingeschakeld Tunnel-adapter LAN-verbinding* 2: Mediumstatus. . . . . . . . . . . : medium ontkoppeld Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Fysiek adres. . . . . . . . . . . : 02-00-54-55-4E-01 DHCP ingeschakeld . . . . . . . . : nee Autom. configuratie ingeschakeld : ja Tunnel-adapter LAN-verbinding* 4: Mediumstatus. . . . . . . . . . . : medium ontkoppeld Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : isatap.{F4E04011-72F4-41CB-B8C5-A4FA9676C F03} Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP ingeschakeld . . . . . . . . : nee Autom. configuratie ingeschakeld : ja Tunnel-adapter LAN-verbinding* 9: Mediumstatus. . . . . . . . . . . : medium ontkoppeld Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : isatap.{59D01450-1A14-4DC0-83AF-8E70E94AE E18} Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP ingeschakeld . . . . . . . . : nee Autom. configuratie ingeschakeld : ja Tunnel-adapter LAN-verbinding* 11: Mediumstatus. . . . . . . . . . . : medium ontkoppeld Verbindingsspec. DNS-achtervoegsel: WAG325N Beschrijving. . . . . . . . . . . : isatap.WAG325N Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP ingeschakeld . . . . . . . . : nee Autom. configuratie ingeschakeld : ja Tunnel-adapter LAN-verbinding* 16: Mediumstatus. . . . . . . . . . . : medium ontkoppeld Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : isatap.{7CF53084-EDDF-4CCB-B350-375137818 96A} Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP ingeschakeld . . . . . . . . : nee Autom. configuratie ingeschakeld : ja Tunnel-adapter LAN-verbinding* 12: Mediumstatus. . . . . . . . . . . : medium ontkoppeld Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : Microsoft ISATAP Adapter #5 Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP ingeschakeld . . . . . . . . : nee Autom. configuratie ingeschakeld : ja
IPv6 on Vista
[us] Shadow Hawkins on Wednesday, 05 November 2008 06:45:46
Joey -- Test to see if you are being bitten by the Vista IPv6 Virtual Adapter DNS design flaw/bug. Since you state that you can ping an IPv6 host successfully, I am assuming that your dns server, tunnel configuration, aiccu, and tap/tun driver is working properly. If this is not the case, try running the "autotest" parameter with the command line version of aiccu. If you can access Google IPv6 via the following url in IE/Firefox: http://[2001:4860:0:2001::68]/ but not via: http://ipv6.google.com Then you need to "fake out" Vista into thinking IPv6 DNS should be enabled. (Test BOTH IE and Firefox) If both work with the first url, but fail with the second, then try the following from an administrative command prompt: In order to get an administrative command prompt in Vista, you either (A) need to disable UAC, or (B) Create a custom shortcut for "cmd.exe" with the advanced properties setup for "Run as Administrator"
netsh int ipv6 add address "WAG325N" 2002:81a8:102::
or you can just go into the IPv6 settings GUI for your WAG325N network interface, and setup a non-routed static ip address (2002:81a8:102:: will work as long as you do not setup a default router) 2002:81a8:102:: is the equiv of 192.168.1.2 in the 6to4 address range if my memory is correct. If this does NOT solve the issue for you, then you should get a wireshark capture to see in more detail what is happening. The issue is that Microsoft has some pretty strange "by design" parameters (which I see as a bug ) on when to use AAAA DNS requests: http://technet.microsoft.com/en-us/library/bb727035.aspx Good Luck. -_Dave Horn
IPv6 on Vista
[nl] Shadow Hawkins on Wednesday, 05 November 2008 13:43:39
You're right, http://[2001:4860:0:2001::68]/ works but not via: http://ipv6.google.com netsh int ipv6 add address "WAG325N" 2002:81a8:102:: doesn't work, it say's can't find a syntaxis. this is what I get with the autotest parameter:
C:\aiccu>aiccu 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 1225887063" sock_printf() : "username JMY4-SIXXS" sock_getline() : "200 Choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 6f7a58008860403b2383d3f0decc82e3" sock_printf() : "authenticate md5 8a3162b138d983b6423315fd144cdc4e" sock_getline() : "200 Succesfully logged in using md5 as JMY4-SIXXS (joey mitite lu) from 2001:7b8:3:4f:202:b3ff:fe46:bec" sock_printf() : "tunnel show T15678" sock_getline() : "201 Showing tunnel information for T15678" sock_getline() : "TunnelId: T15678" sock_getline() : "Type: ayiya" sock_getline() : "IPv6 Endpoint: 2001:960:2:5d9::2" sock_getline() : "IPv6 POP: 2001:960:2:5d9::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "Tunnel Name: My First Tunnel" sock_getline() : "POP Id: nlams04" sock_getline() : "IPv4 Endpoint: ayiya" sock_getline() : "IPv4 POP: 213.204.193.2" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: 530360aab0b328efc0337bb376ac61a3" sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T15678 sock_printf() : "QUIT I'll be back. Ha, you didn't know I was going to say that !" Tunnel Information for T15678: PoP Id : nlams04 IPv6 Local : 2001:960:2:5d9::2/64 IPv6 Remote : 2001:960:2:5d9::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 {D2C8D30F-E112-41E2-96AB-A93755D4AF3A}, using it [tun-start] Trying \\.\Global\{D2C8D30F-E112-41E2-96AB-A93755D4AF3A}.tap [error] [tun-start] Problem while enumerating key SYSTEM\CurrentControlSet\Contr ol\Network\{4D36E972-E325-11CE-BFC1-08002BE10318} [error] [tun-start] No working Tap device found! [error] Tunnel Setup Failed
I see my tap tunnel has an APIPA addres for de IPv4, don't know if that is right. Also my WAG325N has no IPv6 settings, so I can't setup a non-routed static ip address. tnx
IPv6 on Vista
[us] Shadow Hawkins on Wednesday, 05 November 2008 17:33:19
Joey - Sorry, the Dutch through me for a loop ;) It should have been:
netsh int ipv6 add address "LAN-verbinding" 2002:81a8:102::
Where "LAN-verbinding" is the name of your network connection (interface name) in Vista. (I mistakenly thought you had named the adapter WAG325N) I always rename mine to make them less generic, but that is cosmetic only. I believe "LAN-verbinding" in Dutch is equiv to "Local Area Connection" in English for Vista's auto-naming network interfaces. If your physical network interface is named something different, substitute that name. When I said IPv6 settings GUI, I meant for "Lan-verbinding" Vista interface, not your router configuration. Sorry about the confusion. Let me know how it goes. -_Dave Horn
IPv6 on Vista
[nl] Shadow Hawkins on Wednesday, 05 November 2008 17:59:59
Yes man, it works:D tnx
IPv6 on Vista
[us] Shadow Hawkins on Wednesday, 05 November 2008 18:23:22
Glad to hear it worked. In case anyone is curious, I have contacted Microsoft about this Vista issue again, and hopefully we can get some traction this time. There is either (A) something that needs to change in the tap/tun driver, or (B) something that needs to change in the OS. I *hate* having to assign a dummy address to an interface to work around this issue. -_Dave Horn
IPv6 on Vista
[de] Shadow Hawkins on Tuesday, 04 November 2008 21:23:03
Maybe this is stupid, but did you check you're not using a proxy in your browsers?
IPv6 on Vista
[nl] Shadow Hawkins on Tuesday, 04 November 2008 21:25:10
No I use a proxy only at school, at home a set it always back to use no proxy, in FF and IE.
IPv6 on Vista
[nl] Shadow Hawkins on Saturday, 08 November 2008 13:02:36
Hallo I have a new problem I think.. I get this error when I want to start aiccu, because looks like it doesn's start by it self enymore.
C:\aiccu>aiccu start [error] Couldn't retrieve first tunnel for the above reason, aborting
After 3 times (every time 3 times trying) aiccu starts, and I have IPv6 connectivity, but when I close the command line, cant't ping or visit any ipv6 website. So I think there is something in the registry.. Oh and I have the same on other 2 computers, the error from above, so it could be also my tunnel. tnx
IPv6 on Vista
[ch] Jeroen Massar SixXS Staff on Monday, 10 November 2008 09:49:11
When you close the console of the console version, it indeed quits. When you start/stop AICCU too often, the TIC server doesn't serve you anymore for some time.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker