IPv6: Two Questions

So I decided to mess around with IPv6 yesterday and see what it was all about. After some time, It's finally "working", though I was wondering if anybody could help me iron out two kinks I seem to be having...

1) While my IPv6 connection works fine (I can ping6, tracert6, listen to audio streams, etc), Firefox and IE don't seem to make use of it. If I go to a site with IPv6 content, both Firefox and IE bring up the IPv4 page instead of the IPv6 page. Trying to force them to use IPv6 by using the IPv6 IP results in IE returning a server not found error and Firefox just sitting there saying it's connecting. However, like I said before, I can ping6 the IP fine, as well as even use telnet to view the IPv6 version

2) With IPv6 on, I seem to be having a hard time accessing Google. While I can access any OTHER IPv4 site, Google refuses to load under any circumstances. Strangely, using Google's IP address I can access it, but not with it's URL... My hosts file is clean too from what I can tell (is there more than one?)
Hmmmm.... Seems Google magically started working in the middle of this post... Wonder what's up with that!

Any thoughts?
JigPu

I havn't used IPv6 myself yet, but I can tell you this:

Running a IPv6 network in your house is good, but it doesn't mean that the Internet runs IPv4. In order to connect to the internet, you need an IPv6 to IPv4 gateway, unless you have an IPv6 internet connection.

When you do a DNS lookup, on Google, for example, your computer sees that you are running IPv6, and looks up the IPv6 IP. Your computer then tries to contact the IPv6 IP, and fails because you don't have an IPv6 route to it.. your Internet connection is IPv4. So after a timeout it falls back and tries the IPv4 address in Google's DNS, which works. This will happen with any site that publishes IPv6 IPs, and this is the same reason that Firefox and IE won't make use of it.

If you set up a local webserver with an IPv6 address, then it will contact it using IPv6.

The only thing to do now is to get an IPv6 Internet connection (or tunnel to an IPv6 network), where your IPv6 traffic can be routed across IPv6. However, a lot of the Internet is still running on IPv4.

I'm able to look at ipv6 websites fine in Firefox, and I tried it once on IE6 from Win2k3 and it was ok.

My ipv6 is all set up and talking to the internet correctly though.

My IPv6 connection is fine as far as I can tell. I've got a tunnel set up from Hurricane Electric and can access IPv6 stuff without problem so long as I'm not using my browser Like I said, even though Firefox/IE won't show me the IPv6 content, using telnet to connect to port 80 will... Mabey firefox needs reinstalling to realize that I have IPv6?

JigPu

If you go to www.kame.net, do you see an animated turtle?

Nope, no animated turtle.

BTW: Reinstalling firefox didn't seem to help, so I'm out of ideas of my own...
JigPu

Can you ping6 or traceroute6 to www.kame.org from a command prompt?

If your ipv6 was set up right, and you had a version of IE supporting ipv6 (like the one in Win2003), then when you go to www.kame.org you should be hitting the ipv6 version of the site and get an animating turtle.

I have an idea... are you cool with giving me your ip?

I'll give you some of mine, see if you can ping them:
My desktop: 3ffe:2900:110f:7:2e0:81ff:fe03:ee04
My fileserver: 3ffe:2900:110f:7::1
My test server: 3ffe:2900:110f:7::90
My Xbox: 3ffe:2900:110f:7:250:f2ff:fe2d:f9c3
My website: 3ffe:2900:110f:1:240:c7ff:fe2d:b0a6

Ping6 results:

Pinging www.kame.net [2001:200:0:8002:203:47ff:fea5:3085]
from 2001:470:1f01:ffff::55 with 32 bytes of data:

Reply from 2001:200:0:8002:203:47ff:fea5:3085: bytes=32 time=258ms
Reply from 2001:200:0:8002:203:47ff:fea5:3085: bytes=32 time=260ms
Reply from 2001:200:0:8002:203:47ff:fea5:3085: bytes=32 time=289ms
Reply from 2001:200:0:8002:203:47ff:fea5:3085: bytes=32 time=257ms

Click to expand...

Pinging 3ffe:2900:110f:7:2e0:81ff:fe03:ee04
from 2001:470:1f01:ffff::55 with 32 bytes of data:

Reply from 3ffe:2900:110f:7:2e0:81ff:fe03:ee04: bytes=32 time=242ms
Reply from 3ffe:2900:110f:7:2e0:81ff:fe03:ee04: bytes=32 time=239ms
Reply from 3ffe:2900:110f:7:2e0:81ff:fe03:ee04: bytes=32 time=237ms
Reply from 3ffe:2900:110f:7:2e0:81ff:fe03:ee04: bytes=32 time=239ms

Click to expand...

Pinging 3ffe:2900:110f:7::1
from 2001:470:1f01:ffff::55 with 32 bytes of data:

Reply from 3ffe:2900:110f:7::1: bytes=32 time=278ms
Reply from 3ffe:2900:110f:7::1: bytes=32 time=240ms
Reply from 3ffe:2900:110f:7::1: bytes=32 time=366ms
Reply from 3ffe:2900:110f:7::1: bytes=32 time=268ms

Click to expand...

Pinging 3ffe:2900:110f:7::90
from 2001:470:1f01:ffff::55 with 32 bytes of data:

Reply from 3ffe:2900:110f:7::90: bytes=32 time=751ms
Reply from 3ffe:2900:110f:7::90: bytes=32 time=378ms
Reply from 3ffe:2900:110f:7::90: bytes=32 time=361ms
Reply from 3ffe:2900:110f:7::90: bytes=32 time=867ms

Click to expand...

Pinging 3ffe:2900:110f:7:250:f2ff:fe2d:f9c3
from 2001:470:1f01:ffff::55 with 32 bytes of data:

Reply from 3ffe:2900:110f:7:250:f2ff:fe2d:f9c3: bytes=32 time=949ms
Reply from 3ffe:2900:110f:7:250:f2ff:fe2d:f9c3: bytes=32 time=1208ms
Reply from 3ffe:2900:110f:7:250:f2ff:fe2d:f9c3: bytes=32 time=1179ms
Reply from 3ffe:2900:110f:7:250:f2ff:fe2d:f9c3: bytes=32 time=1365ms

Click to expand...

Pinging 3ffe:2900:110f:1:240:c7ff:fe2d:b0a6
from 2001:470:1f01:ffff::55 with 32 bytes of data:

Reply from 3ffe:2900:110f:1:240:c7ff:fe2d:b0a6: bytes=32 time=218ms
Reply from 3ffe:2900:110f:1:240:c7ff:fe2d:b0a6: bytes=32 time=218ms
Reply from 3ffe:2900:110f:1:240:c7ff:fe2d:b0a6: bytes=32 time=218ms
Reply from 3ffe:2900:110f:1:240:c7ff:fe2d:b0a6: bytes=32 time=219ms

Click to expand...

My IP (should be) 2001:470:1f01:ffff::55 from what I can tell.
JigPu

I can't ping your ip. Can't seem to get past 2001:470:1fff:4:210:79ff:feea:e400