|
Browsers do not prefer IPv6
![[ch]](/s/countries/ch.gif) Shadow Hawkins on Sunday, 28 November 2010 22:59:59
I have set up my tunnel on my Windows7 PC and everything works fine with one exception...my browsers will not connect to IPv6 sites using a FQDN.
ping -6 ipv6.google.com / no problem for all sites
tracert -6 ipv6.google.com / no problem for all sites
http://[2001:200:dff:fff1:216:3eff:feb1:44d7] in browser / no problem for all sites
http://ipv6.google.com does not work
http://www.kame.net no dancing turtle :(
(this is the same for IE, Chrome, Firefox and Opera).
Wireshark shows that:
- With Chrome my PC is just requesting A records.
- With Opera it is requesting first A then AAAA, gets responses to both and displays the IPv4 site (kame).
- With IE only A records (www.ipv6.sixxs.net).
When I start my tunnel I get the following error:
c:\aiccu>aiccu-console start
Succesfully retrieved tunnel information for T47241
[warning] Error opening registry key: SYSTEM\CurrentControlSet\Control\Class\{4D
36E972-E325-11CE-BFC1-08002BE10318}\Properties (t1)
[AYIYA-start] : Anything in Anything (draft-02)
[AYIYA-tun->tundev] : (Socket to TUN) started
and the window hangs. CTL-C kills the tunnel. Is this normal?
The interface however is up:
Ethernet adapter tun0:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-ED-4F-3C-A4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:1620:f00:c7::2(Preferred)
Link-local IPv6 Address . . . . . : fe80::172:291b:56d3:dc47%25(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.220.71(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 2001:1620:f00:c7::1
DHCPv6 IAID . . . . . . . . . . . : 721485805
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-41-B4-A0-18-A9-05-29-EC-7B
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Teredo, 6to4, isatap, etc are all disabled.
Any help would be greatly appreciated...
Browsers do not prefer IPv6
Shadow Hawkins on Sunday, 28 November 2010 23:30:27
Just noticed that this problem may be the same as the one in another thread "IPv6 works on CMD, not in browser" (https://www.sixxs.net/forum/?msg=setup-2834721). To date they don't have the answer either.
Browsers do not prefer IPv6
Shadow Hawkins on Monday, 29 November 2010 06:46:26
Problem solved... I added my ULA to the physical interface on my PC. The tunnel is still configured with the global address. The FQDN now works in the browser as well. I assume it has something to do with the browsers not recognizing the tun0 interface as a real IPv6 interface.
Browsers do not prefer IPv6
![[us]](/s/countries/us.gif) Shadow Hawkins on Monday, 29 November 2010 15:01:45
Right.
I think there's something regarding this in the Wiki...if there isn't, there need to be
Browsers do not prefer IPv6
![[de]](/s/countries/de.gif) Shadow Hawkins on Sunday, 26 December 2010 21:02:30
Browsers do not prefer IPv6
You said Problem was solved? How?
I'm just curious what a ULA and a FQND might be?
Greetings
Browsers do not prefer IPv6
Shadow Hawkins on Monday, 27 December 2010 14:54:28
Google will tell you everything you need to know.
Basically you need to assign a public IPv6 address to your network interface.
|
Posting is only allowed when you are