Win8 IPv6 success?

[bpier]

Hey all,
I've just started playing with the Windows 8 Consumer Preview release and found that, although Win8 gets a DHCPv6 issued address, it can't even Ping over IPv6 let alone connect anywhere.
Is anyone else having difficulties with this or having success with Win8 and IPv6?

Win8 is running from VirtualBox with Bridged networking set; receives RADVD broadcasts and get's its address from a DHCPv6 server.
I have a similar setup with WinVista, and IPv6 works fine for that system.

FWIW, my host is Ubuntu.

Bill

> ipconfig

Windows IP Configuration

Ethernet adapter Wired Ethernet Connection:

   Connection-specific DNS Suffix  . : 
   IPv6 Address. . . . . . . . . . . : 2001:470:f171:42::44
   Link-local IPv6 Address . . . . . : fe80::803d:4ce6:264d:36ae%12
   IPv4 Address. . . . . . . . . . . : 192.168.1.44
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1

Tunnel adapter isatap.{3A0B46D7-19CA-4AE9-A4A9-44B899ADFFC4}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 

> netsh interface ipv6 show interface

Idx     Met         MTU          State                Name
---  ----------  ----------  ------------  ---------------------------
  1          50  4294967295  connected     Loopback Pseudo-Interface 1
 15          50        1280  disconnected  isatap.{3A0B46D7-19CA-4AE9-A4A9-44B899ADFFC4}
 12          10        1500  connected     Wired Ethernet Connection

> ping -6 2001:470:f171:42::44

Pinging 2001:470:f171:42::44 with 32 bytes of data:
Reply from 2001:470:f171:42::44: time<1ms 
Reply from 2001:470:f171:42::44: time<1ms 
Reply from 2001:470:f171:42::44: time<1ms 
Reply from 2001:470:f171:42::44: time<1ms 

Ping statistics for 2001:470:f171:42::44:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

> ping -6 2001:470:f171:42::1

Pinging 2001:470:f171:42::1 with 32 bytes of data:
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 

Ping statistics for 2001:470:f171:42::1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

> netsh interface ipv6 show dnsservers

Configuration for interface "Wired Ethernet Connection"
    Statically Configured DNS Servers:    2001:470:f171:42::1
                                          2001:4860:4860::8888
                                          2001:470:20::2

> ping -6 2001:4860:4860::8888

Pinging 2001:4860:4860::8888 with 32 bytes of data:
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 

Ping statistics for 2001:4860:4860::8888:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

> ping -6 2001:470:f171:42::1

Pinging 2001:470:f171:42::1 with 32 bytes of data:
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 

Ping statistics for 2001:470:f171:42::1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

[nathana]

What does "route print" show?

-- Nathan

[bpier]

Duh!

There wasn't a default route, so

   

 route -p -6 ADD ::/0  2001:470:f171:42::1 IF 12

Default route in place -- all is well.

Thanks for observing the obvious; I'll now go the corner and stand in shame. :(

[nathana]

Well, that still sounds like a potential bug to me...it's not like you assigned an IP to the computer and forgot to add a default route.  One should have been created for you by the DHCPv6 client in Windows, I'd think...

-- Nathan

[martech]

I know that within Windows 2008R2 There is no option the set the default gateway. You manually need the set this up with this command: "netsh interface ipv6 add route ::/0 "name-of-your-NIC" 2001:234:f34:4ff:c43::2" where 2001:234:f34:4ff:c43::2 is your gateway. You could do this with a loginscript. DNS can be set with option 00023 in server 2008R2.

This is how you should do this on Server 2008R2, but I only have little knowledge about Win8 and Win8 server.

Hope this helps!

---
The other Nathan