Flipped the switch, now what?

[#1]

I have finally built up the courage and have enabled IPv6 (and switched to the test account). Essentially this was trivial i.e. just a matter of ticking a checkbox and rebooting the router.
The only difference I have noticed so far is that the router now has an allocated IPv6 address. The kit inside my network seems to be working exactly as it did before. On the face of it this is a good thing, but... exactly as before includes NOT being able to see the IPv6 web (from a Windows 7 machine).
Have I done something wrong, or have I missed the point?

[#2]

Hi AxeMurderer,
As IPv6 is a transport protocol (in the generic sense of the term) it is entirely expected that you should indeed not notice any difference when browsing the web. However, it does sound like your IPv6 connectivity might not be working - what are the results of visiting test-ipv6.com? Posting the output of ipconfig /all at the command prompt will also help shed some light on the situation - it may well be that your PC is not obtaining a (publicly routable) IPv6 address.
Mathew

[#3]

Your IPv4 address on the public internet appears to be <censored>
Your IPv6 address on the public internet appears to be <censored>
Your IPv6 service appears to be: Teredo
World IPv6 day is June 8th, 2011. No problems are anticipated for you with this browser, at this location. [more info]
You appear to be able to browse the IPv4 internet only. You will not be able to reach IPv6-only sites.
Your IPv6 connection appears to be using Teredo, a type of IPv4/IPv6 gateway; currently it connects only to direct IP's. Your browser will not be able to go to IPv6 sites by name. This means the current configuration is not useful for browsing IPv6 web sites. [more info]
Your DNS server (possibly run by your ISP) appears to have no access to the IPv6 internet, or is not configured to use it. This may in the future restrict your ability to reach IPv6-only sites. [more info]
Your readiness scores
10/10 for your IPv4 stability and readiness, when publishers offer both IPv4 and IPv6
0/10 for your IPv6 stability and readiness, when publishers are forced to go IPv6 only

and...

Windows IP Configuration
  Host Name . . . . . . . . . . . . : Ian-VAIO
  Primary Dns Suffix  . . . . . . . :
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : home.gateway
Wireless LAN adapter Wireless Network Connection 2:
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
  Physical Address. . . . . . . . . : 58-<censored>
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection:
  Connection-specific DNS Suffix  . : home.gateway
  Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6200 AGN
  Physical Address. . . . . . . . . : 58-94-6B-13-50-0C
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::<censored>%11(Preferred)
  IPv4 Address. . . . . . . . . . . : 192.168.0.12(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Lease Obtained. . . . . . . . . . : 04 June 2011 09:13:12
  Lease Expires . . . . . . . . . . : 05 June 2011 10:16:48
  Default Gateway . . . . . . . . . : 192.168.0.254
  DHCP Server . . . . . . . . . . . : 192.168.0.254
  DHCPv6 IAID . . . . . . . . . . . : 307795051
  DHCPv6 Client DUID. . . . . . . . : 00-01-00-<censored>
  DNS Servers . . . . . . . . . . . : 192.168.0.254
  NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . : home.gateway
  Description . . . . . . . . . . . : Marvell Yukon 88E8057 PCI-E Gigabit Ethernet Controller
  Physical Address. . . . . . . . . : 54-<censored>
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{807B1C00-<censored>}:
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Microsoft ISATAP Adapter
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.home.gateway:
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . : home.gateway
  Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  IPv6 Address. . . . . . . . . . . : 2001:0:<censored>(Preferred)
  Link-local IPv6 Address . . . . . : fe80::<censored>%14(Preferred)
  Default Gateway . . . . . . . . . : ::
  NetBIOS over Tcpip. . . . . . . . : Disabled

[#4]

Were you running ipv6 over a tunnel before taking part in the trial?
PB

[#5]

Until today I had done absolutely nothing to set up/change whatever is done by default.

[#6]

Did you reboot the 7800N & then the Windows 7 PC after enabling ipv6?
I am running a 7800N with 1.06d with, amongst others, a Windows 7 PC.
If I remember correctly there was more than one place I had to enable ipv6 on the router configuration pages.
See http://community.plus.net/forum/index.php/topic,96141.msg810534.html#msg810534
I have carried out a clean install of XP, Vista & W7 on a test PC. Both Vista and W7 used ipv6 & ipv4 with no problems.
I did NOT have to carry out any configuration changes.
I have yet to test a clean install of Linux & will revisit XP at a later date.
PB

[#7]

Yes, I rebooted the router and then the PC.
I checked that forum post before I enabled IPv6 and I've checked post reboot and it matches.
I'm not about to do a clean install onto anything though.

[#8]

You could try booting from a live linux CD, it is one of the things on my list to try, after doing a clean install of Linux on my test PC and before trying XP.
PB

[#9]

Fedora 14 i386 live CD results
Your IPv4 address on the public internet appears to be 81.174.XXX.XXX
Your IPv6 address on the public internet appears to be 2a02:16c8:6000:300:21d:7dff:XXXX:XXXX
World IPv6 day is June 8th, 2011. No problems are anticipated for you with this browser, at this location. [more info]
Congratulations! You appear to have both IPv4 and IPv6 internet working. If a publisher publishes to IPv6, your browser will connect using IPv6. Your browser prefers IPv6 over IPv4 when given the choice (this is the expected outcome).
Your DNS server (possibly run by your ISP) appears to have no access to the IPv6 internet, or is not configured to use it. This may in the future restrict your ability to reach IPv6-only sites.
10/10 for your IPv4 stability and readiness, when publishers offer both IPv4 and IPv6
9/10 for your IPv6 stability and readiness, when publishers are forced to go IPv6 only

[#10]

Update:
Your IPv4 address on the public internet appears to be <removed>
Your IPv6 address on the public internet appears to be <removed>
World IPv6 day is June 8th, 2011. No problems are anticipated for you with this browser, at this location. [more info]
Congratulations! You appear to have both IPv4 and IPv6 internet working. If a publisher publishes to IPv6, your browser will connect using IPv6. Your browser prefers IPv6 over IPv4 when given the choice (this is the expected outcome).
Your DNS server (possibly run by your ISP) appears to have IPv6 internet access.
Your readiness scores
10/10 for your IPv4 stability and readiness, when publishers offer both IPv4 and IPv6
10/10 for your IPv6 stability and readiness, when publishers are forced to go IPv6 only

So what did I do? Rebooted the router again, and rebooted the PC too. I suspect that the Billion, in addition to automatically restarting itself when you enable IPv6, actually requires another reboot immediately afterwards.
Thanks to all for your help; I can do some real testing now!
[Moderator's note by Jim (Oldjim)  Ip addresses removed as I assume you forgot ]
Indeed I did. Ta!

[#11]

Preliminary results:
Assumed to be IPv4:

• Canon MP640 printer/scanner


• Sony BluRay player

IPv4 only:

• iPod Touch 1st Generation


• Wii


• DAP 1522 Access Point/Bridge


• Buffalo Linkstation NAS

IPv4 and v6:

• Windows 7 laptop 64-bit (connects wirelessly)


• iPhone 3GS


• Motorola Defy (if using Firefox browser; system default browser and Dolphin HD are IPv4 only)


• iPod Touch 2nd generation


• Windows XP Professional laptop (once I'd 'installed' i.e. enabled, IPv6)

To be further investigated:

• Windows 7 desktop 32-bit (wired connection to DAP 1522, which acts as a bridge connecting to router wirelessly) - appears to be IPv4 only. Yes, I know Windows 7 is IPv6 internally, but I can't get this one to recognise the IPv6 web. Yet.

And there are several more bits of kit I'm yet to try

Additions in bold

[#12]

Quote from: AxeMurderer

Windows 7 desktop 32-bit (wired connection to DAP 1522, which acts as a bridge connecting to router wirelessly) - appears to be IPv4 only. Yes, I know Windows 7 is IPv6 internally, but I can't get this one to recognise the IPv6 web. Yet.

If you're up for some detective work it would be worth seeing what IPv6 the desktop is seeing using Wireshark, in particular whether it is seeing any Router Advertisments from the gateway or itself attempting any DHCPv6 negotiations (and how far it is getting). Wireshark is pretty good at interpreting the packet types in readable English, however you will likely want to restrict displayed traffic to IPv6 by putting 'ipv6' (lower case) in the filter line (and hitting Apply) - this can be done in realtime.
I would also recommend disabling Teredo tunneling given you've got native IPv6 on offer (potentially!) as it's only going to get in the way otherwise. You can do this with the following at a command prompt:

netsh interface teredo set state disable

Mathew

[#13]

Ta! I'll give that a go if/when I get time. Tonight I tried the Windows 7 laptop that was doing both IPv4 and IPv6 just fine wirelessly, plugged in to the access point with wireless disabled. As expected, it reverted to just IPv4.