Forum - IPv6 does not work properly in webbrowser :: SixXS

IPv6 does not work properly in webbrowser

Shadow Hawkins on Friday, 30 April 2010 14:36:04

I have a strange problem with my IPv6 tunnel. The tunnel is working with ping, traceroute, etc., but my webbrowsers (tried Internet Explorer 8 and Opera) does not connect through IPv6 at all. Autotest output (sorry, dutch operating system):

Tunnel Information for T24614: PoP Id : nlede01 IPv6 Local : 2001:7b8:2ff:33e::2/64 IPv6 Remote : 2001:7b8:2ff:33e::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.1.9) ### 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.1.9 met 32 bytes aan gegevens: Antwoord van 192.168.1.9: bytes=32 tijd=1 ms TTL=128 Antwoord van 192.168.1.9: bytes=32 tijd=1 ms TTL=128 Antwoord van 192.168.1.9: bytes=32 tijd=1 ms TTL=128 Ping-statistieken voor 192.168.1.9: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van n bewerking in milliseconden: Minimum = 1ms, Maximum = 1ms, Gemiddelde = 1ms ###### ####### [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=47 ms TTL=59 Antwoord van 193.109.122.244: bytes=32 tijd=46 ms TTL=59 Antwoord van 193.109.122.244: bytes=32 tijd=44 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 = 44ms, Maximum = 47ms, Gemiddelde = 45ms ###### ####### [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 6 ms 4 ms 4 ms 192.168.1.1 2 38 ms 41 ms 37 ms ip1-208-173-82.adsl2.static.versatel.nl [82.173.208.1] 3 42 ms 42 ms 46 ms ge-0-0-0-1116.ncr01ht.versatel.net [217.16.36.145] 4 41 ms 44 ms 41 ms ge-1-0-0-616.br01sara.versatel.net [212.53.18.122] 5 43 ms 45 ms 43 ms amsix-501.xe-0-0-0.jun1.kelvin.network.bit.nl [195.69.144.200] 6 54 ms 44 ms 45 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 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:33e::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:33e::2 met 32 bytes aan gegevens: Antwoord van 2001:7b8:2ff:33e::2: tijd<1 ms Antwoord van 2001:7b8:2ff:33e::2: tijd<1 ms Antwoord van 2001:7b8:2ff:33e::2: tijd<1 ms Ping-statistieken voor 2001:7b8:2ff:33e::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:33e::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:33e::1 met 32 bytes aan gegevens: Antwoord van 2001:7b8:2ff:33e::1: tijd=46 ms Antwoord van 2001:7b8:2ff:33e::1: tijd=44 ms Antwoord van 2001:7b8:2ff:33e::1: tijd=45 ms Ping-statistieken voor 2001:7b8:2ff:33e::1: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van n bewerking in milliseconden: Minimum = 44ms, Maximum = 46ms, Gemiddelde = 45ms ###### ###### [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.

Output from ping to sixxs.net:

C:\>ping -6 sixxs.net Pingen naar sixxs.net [2001:7b8:3:4f:202:b3ff:fe46:bec] met 32 bytes aan gegeven s: Antwoord van 2001:7b8:3:4f:202:b3ff:fe46:bec: tijd=42 ms Antwoord van 2001:7b8:3:4f:202:b3ff:fe46:bec: tijd=43 ms Antwoord van 2001:7b8:3:4f:202:b3ff:fe46:bec: tijd=44 ms Antwoord van 2001:7b8:3:4f:202:b3ff:fe46:bec: tijd=44 ms Ping-statistieken voor 2001:7b8:3:4f:202:b3ff:fe46:bec: Pakketten: verzonden = 4, ontvangen = 4, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van n bewerking in milliseconden: Minimum = 42ms, Maximum = 44ms, Gemiddelde = 43ms

Nslookup sixxs.net:

C:\>nslookup sixxs.net Server: UnKnown Address: 192.168.1.1 Niet-bindend antwoord: Naam: sixxs.net Addresses: 2001:7b8:3:4f:202:b3ff:fe46:bec 2001:1af8:1:f006::6 2001:838:2:1::30:67 2001:960:800::2 94.75.219.73 193.109.122.244 213.204.193.2 213.197.30.67

But when I try to open an IPv6 only site (like ipv6.google.com), it says that it can not find the server. Or when I open www.kame.net (or just www.sixxs.net) it says that I am connected via IPv4. What do I have to change so I can use the tunnel by browser and other applications?

IPv6 does not work properly in webbrowser

Shadow Hawkins on Saturday, 01 May 2010 13:03:02

Have you disabled the IPv6 functionality of the real internet connection (LAN adapter) by giving it a 2002-address? (like suggested in Wiki step 8) http://www.sixxs.net/wiki/Configuring_Windows_Vista#.288.29_Setup_Vista_Specific_IPv6_parameters

Run the following command to work-around the issue with Vista and AICCU IPv6 "AAAA" DNS lookups with a virtual interface:

netsh int ipv6 add address "Local Area Connection" 2002:81a8:102::

If you have not done that, it is possible that the connection does not work through the tunnel, as your PC tries to use the main LAN adapter for it.

IPv6 does not work properly in webbrowser

Shadow Hawkins on Sunday, 02 May 2010 16:46:23

Thanks for your reply. I have added the address to the adapter, but I still can't reach any IPv6 site when entering an domainname in my browser. Here is the output of netsh int ipv6 show address.

C:\Users\Julian Taylor>netsh int ipv6 show address Interface 1: Loopback Pseudo-Interface 1 Adrestype DAD-status Geldig Voorkeur Adres --------- ----------- ---------- ---------- ------------------------ Overig Voorkeur infinite infinite ::1 Interface 11: LAN-verbinding Adrestype DAD-status Geldig Voorkeur Adres --------- ----------- ---------- ---------- ------------------------ Overig Voorkeur infinite infinite fe80::8996:b2a9:d56:d82a%11 Interface 12: aiccu Adrestype DAD-status Geldig Voorkeur Adres --------- ----------- ---------- ---------- ------------------------ Handmatig Voorkeur infinite infinite 2001:7b8:2ff:33e::2 Handmatig Voorkeur infinite infinite 2002:81a8:102:: Overig Voorkeur infinite infinite fe80::d42:58d5:c1b2:1bde%12

And the output netsh int ipv6 show route and ipconfig /all:

C:\Users\Julian Taylor>netsh int ipv6 show route Public. Type Met Voorvoegsel Idx Naam gateway/interface ------- -------- --- ------------------------ --- ------------------------ Ja Handmatig 256 ::/0 12 2001:7b8:2ff:33e::1 Nee Handmatig 256 ::1/128 1 Loopback Pseudo-Interface 1 Nee Handmatig 256 2001:7b8:2ff:33e::/64 12 aiccu Nee Handmatig 256 2001:7b8:2ff:33e::2/128 12 aiccu Nee Handmatig 256 2002:81a8:102::/64 12 aiccu Nee Handmatig 256 2002:81a8:102::/128 12 aiccu Nee Handmatig 256 fe80::/64 12 aiccu Nee Handmatig 256 fe80::/64 11 LAN-verbinding Nee Handmatig 256 fe80::d42:58d5:c1b2:1bde/128 12 aiccu Nee Handmatig 256 fe80::8996:b2a9:d56:d82a/128 11 LAN-verbinding Nee Handmatig 256 ff00::/8 1 Loopback Pseudo-Interface 1 Nee Handmatig 256 ff00::/8 12 aiccu Nee Handmatig 256 ff00::/8 11 LAN-verbinding

C:\Users\Julian Taylor>ipconfig /all Windows IP-configuratie Hostnaam . . . . . . . . . . . . : JT-PC Primair DNS-achtervoegsel . . . . : Knooppunttype . . . . . . . . . . : gemengd IP-routering ingeschakeld . . . . : nee WINS-proxy ingeschakeld . . . . . : nee Ethernet-adapter voor aiccu: Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : TAP-Win32 Adapter V9 Fysiek adres. . . . . . . . . . . : 00-FF-1A-32-9B-B9 DHCP ingeschakeld . . . . . . . . : ja Autom. configuratie ingeschakeld : ja IPv6-adres. . . . . . . . . . . . : 2001:7b8:2ff:33e::2(voorkeur) IPv6-adres. . . . . . . . . . . . : 2002:81a8:102::(voorkeur) Link-local IPv6-adres . . . . . . : fe80::d42:58d5:c1b2:1bde%12(voorkeur) Automatisch geconf.IPv4-adres . . : 169.254.27.222(voorkeur) Subnetmasker. . . . . . . . . . . : 255.255.0.0 Standaardgateway. . . . . . . . . : 2001:7b8:2ff:33e::1 DHCPv6 IAID . . . . . . . . . . . : 335609626 DHCPv6-client DUID. . . . . . . . : 00-01-00-01-13-66-54-12-E0-CB-4E-BA-D8-7B 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 voor LAN-verbinding: Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : Realtek PCIe GBE Family Controller Fysiek adres. . . . . . . . . . . : E0-CB-4E-BA-D8-7B DHCP ingeschakeld . . . . . . . . : ja Autom. configuratie ingeschakeld : ja Link-local IPv6-adres . . . . . . : fe80::8996:b2a9:d56:d82a%11(voorkeur) IPv4-adres. . . . . . . . . . . . : 192.168.1.9(voorkeur) Subnetmasker. . . . . . . . . . . : 255.255.255.0 Lease verkregen . . . . . . . . . : zondag 2 mei 2010 9:32:55 Lease verlopen. . . . . . . . . . : maandag 3 mei 2010 16:23:03 Standaardgateway. . . . . . . . . : 192.168.1.1 DHCP-server . . . . . . . . . . . : 192.168.1.1 DHCPv6 IAID . . . . . . . . . . . : 249613134 DHCPv6-client DUID. . . . . . . . : 00-01-00-01-13-66-54-12-E0-CB-4E-BA-D8-7B DNS-servers . . . . . . . . . . . : 192.168.1.1 NetBIOS via TCPIP . . . . . . . . : ingeschakeld

When I just ping (not ping -6!) it says that the hostname is known, but when I use the ping -6, it's working. I can also visit IPv6 sites by using the direct IP, like www.kame.net on http://[2001:200:0:8002:203:47ff:fea5:3085]/. That is working great. So it looks like the resolve of IPv6 hosts is not working correctly. I tried already to use OpenDNS and Google DNS, but that does not work either. I have also reset all the settings, and set up all thing again, but I still get the same results.

IPv6 does not work properly in webbrowser

Shadow Hawkins on Sunday, 02 May 2010 16:53:06

My apologies, I made a mistake in the sentence "When I just ping (not ping -6!) it says that the hostname is known". This had to be "When I just ping (not ping -6!) it says that the hostname is not known". This guy describes exactly my problem: http://ipv6-or-no-ipv6.blogspot.com/2009/02/teredo-ipv6-on-vista-no-aaaa-resolving.html, with the only difference that I do not use teredo of course (as you can see in the output of ipconfig /all).

IPv6 does not work properly in webbrowser

Shadow Hawkins on Sunday, 02 May 2010 21:22:55

You should add that 2002: address to the REAL internet connection = "LAN-verbinding", not to Aiccu... Interface 11: LAN-verbinding Adrestype DAD-status Geldig Voorkeur Adres --------- ----------- ---------- ---------- ------------------------ Overig Voorkeur infinite infinite fe80::8996:b2a9:d56:d82a%11 Interface 12: aiccu Adrestype DAD-status Geldig Voorkeur Adres --------- ----------- ---------- ---------- ------------------------ Handmatig Voorkeur infinite infinite 2001:7b8:2ff:33e::2 Handmatig Voorkeur infinite infinite 2002:81a8:102:: Overig Voorkeur infinite infinite fe80::d42:58d5:c1b2:1bde%12 The idea is to prevent real internet connection to be used, so that traffic gets directed to Aiccu and then through the tunnel.

IPv6 does not work properly in webbrowser

Shadow Hawkins on Monday, 03 May 2010 21:45:58

Thanks! It works great now!

IPv6 does not work properly in webbrowser

Shadow Hawkins on Monday, 02 August 2010 22:02:10

Hi. I just had the same problem. So thanks for the answer. But this solution does not make any sense. Why should I add a randomly generated IPv6 address to the active IPv4 internet connection to have IPv6 connections via the tunnel interface? Did Microsoft do something really stupid again? BTW: You should not use an IPv6 address from 2002::/16 as this is reserved for 6-to-4 tunneling. I'd use an IP address from the documentation network 2001:db8::/32 as there are no valid targets for these IP addresses on the internet and it works as well. If you have a SixXS subnet at hand I guess the best solution is to use an IP address from this network. Regards K. Zumbusch

IPv6 does not work properly in webbrowser

Jeroen Massar SixXS Staff

on Monday, 02 August 2010 23:24:02

Did Microsoft do something really stupid again?

The "stupid" thing is people not understanding the background reason...

Why should I add a randomly generated IPv6 address to the active IPv4

internet connection to have IPv6 connections via the tunnel interface?

Because the IETF has defined that the order of connections is: IPv6 native, IPv4 native, IPv6 tunneled, IPv4 tunneled. Microsoft implemented this standard. Then to make Windows think that you have native connectivity you add an IPv6 address (any, as long as you don't have proper routing for it) and voila, your tunneled connectivity is suddenly ordered high enough and suddenly tunneled IPv6 is preferred over IPv4. See RFC3484 for more details.

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