Adding Windows 7 IPv6 machine to local network

[drydog]

I have IPv6 setup with a D-Link DIR-825 router with a HE IPv6 to IPv4 tunnel.  I have two machines behind it running Solaris that can ping ipv6.google.com, and I can ping ipv6.google.com from the DIR-825 router.

Now I want to add a Windows 7 machine.  I can ping the IPv6 link-local address fe80::28:e7ff:fef7:3a73, but I can't ping the LAN IPv6 address 2001:470:d:2ed::1.  I think I'm missing some configuration steps, as no 2001:* address shows up on the netsh output (below).  What additional steps do I need to do to add a 2001:* address.  Isn't this supposed to be automatic?  I don't want another tunnel on the Windows 7 machine--I already have one on the D-Link router.

- Dan

Here's my HE tunnel configuration:
    http://dan.drydog.com/images/he-ipv6-settings.png
Here's my D-Link DIR-825 IPv6 config:
    http://dan.drydog.com/images/dlink-ipv6-settings.png

Here's my Windows 7 configuration:

C:\Windows\System32>netsh interface ipv6 show interfaces
Idx     Met         MTU          State                Name
---  ----------  ----------  ------------  ---------------------------
 1          50  4294967295  connected     Loopback Pseudo-Interface 1
12          50        1280  disconnected  6TO4 Adapter
11          10        1500  connected     Local Area Connection
C:\Windows\System32>netsh interface ipv6 show addresses
Interface 1: Loopback Pseudo-Interface 1
Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Other      Preferred     infinite   infinite ::1
Interface 11: Local Area Connection
Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Other      Preferred     infinite   infinite fe80::2d82:4d0b:b84c:f5ec%11
C:\Windows\System32>netsh interface ipv6 show route
Publish  Type      Met  Prefix                    Idx  Gateway/Interface Name
-------  --------  ---  ------------------------  ---  ------------------------
No       Manual    256  ::1/128                     1  Loopback Pseudo-Interface 1
No       Manual    1000  2002::/16                  12  6TO4 Adapter
No       Manual    256  fe80::/64                  11  Local Area Connection
No       Manual    256  fe80::2d82:4d0b:b84c:f5ec/128   11  Local Area Connection
No       Manual    256  ff00::/8                    1  Loopback Pseudo-Interface 1
No       Manual    256  ff00::/8                   11  Local Area Connection

C:\Windows\System32>ping fe80::218:e7ff:fef7:3a73
Pinging fe80::218:e7ff:fef7:3a73 with 32 bytes of data:
Reply from fe80::218:e7ff:fef7:3a73: time=6ms
Reply from fe80::218:e7ff:fef7:3a73: time<1ms
Ping statistics for fe80::218:e7ff:fef7:3a73:
   Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 0ms, Maximum = 6ms, Average = 3ms
Control-C
C:\Windows\System32>ping 2001:470:d:2ed::1
Pinging 2001:470:d:2ed::1 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 2001:470:d:2ed::1:
   Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C

[drydog]

SOLVED: To answer my own question, here's how I manually added an address and a route to the D-Link router (see below for the netsh commands I used).

QUESTION: It still leaves the question, how come the interfaces weren't added automatically by Windows 7?  Is some autoconfiguration missing from the D-Link DIR-825 router? Looking around on Google, it may be because router advertisement is broken in D-Link routers:

C:\Windows\system32>netsh interface ipv6 add address 11 2001:470:d:2ed::13
C:\Windows\system32>netsh interface ipv6 add route ::/0 11 fe80::218:e7ff:fef7:3a73
Ok.
C:\Windows\system32>ping ipv6.google.com
Pinging ipv6.l.google.com [2001:4860:8011::68] with 32 bytes of data:
Reply from 2001:4860:8011::68: time=41ms
Reply from 2001:4860:8011::68: time=35ms
Reply from 2001:4860:8011::68: time=35ms
Reply from 2001:4860:8011::68: time=35ms
Ping statistics for 2001:4860:8011::68:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 35ms, Maximum = 41ms, Average = 36ms
C:\Windows\system32>netsh int ipv6 show route
Publish  Type      Met  Prefix                    Idx  Gateway/Interface Name
-------  --------  ---  ------------------------  ---  ------------------------
No       Manual    256  ::/0                       11  fe80::218:e7ff:fef7:3a73
No       Manual    256  ::1/128                     1  Loopback Pseudo-Interface 1
No       Manual    256  2001:470:d:2ed::/64        11  Local Area Connection
No       Manual    256  2001:470:d:2ed::13/128     11  Local Area Connection
No       Manual    1000  2002::/16                  12  6TO4 Adapter
No       Manual    256  fe80::/64                  11  Local Area Connection
No       Manual    256  fe80::2d82:4d0b:b84c:f5ec/128   11  Local Area Connection
No       Manual    256  ff00::/8                    1  Loopback Pseudo-Interface 1
No       Manual    256  ff00::/8                   11  Local Area Connection
C:\Windows\system32>netsh int ipv6 show interfaces
Idx     Met         MTU          State                Name
---  ----------  ----------  ------------  ---------------------------
 1          50  4294967295  connected     Loopback Pseudo-Interface 1
12          50        1280  disconnected  6TO4 Adapter
11          10        1500  connected     Local Area Connection
C:\Windows\system32>netsh int ipv6 show addresses
Interface 1: Loopback Pseudo-Interface 1
Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Other      Preferred     infinite   infinite ::1
Interface 11: Local Area Connection
Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Manual     Preferred     infinite   infinite 2001:470:d:2ed::13
Other      Preferred     infinite   infinite fe80::2d82:4d0b:b84c:f5ec%11

[cholzhauer]

is your router doing RA?  what is the RA flag set to on you win 7 machine?

[drydog]

is your router doing RA?  what is the RA flag set to on you win 7 machine?

I don't think so--how can I be sure?.  I ran snoop on a third machine, and I see Solicit messages from the Win7 machine, but no Router Advertisement (ICMPv6 type 134) messages. I see neighbor advertisement (ICMPv6 type 136) messages from a non-Windows (Solaris) machine (below).

Code Select Expand


DHCPv6: ----- Dynamic Host Configuration Protocol Version 6 -----
DHCPv6:
DHCPv6: Message type (msg-type) = 1 (Solicit)
DHCPv6: Transaction ID = bbc019
DHCPv6:
DHCPv6: Option Code = 8 (Elapsed Time)
DHCPv6:   Elapsed Time = 65.00 seconds
DHCPv6: Option Code = 1 (Client Identifier)
DHCPv6:   DUID Type = 1 (Link-layer Address Plus Time)
DHCPv6:   Hardware Type = 1 (Ethernet (10Mb))
DHCPv6:   Time = 339677451 (Wed Oct  6 03:50:51 2010)
DHCPv6:   Link Layer Address = 00:0e:0c:68:9d:d7
DHCPv6: Option Code = 3 (Identity Association for Non-temporary Addresses)
DHCPv6:   IAID = 234884620
DHCPv6:   T1 (renew) = 0 seconds
DHCPv6:   T2 (rebind) = 0 seconds
DHCPv6: Option Code = 39 (Client FQDN)
DHCPv6:   Flags = 00
DHCPv6:         .... ...0 = No AAAA RR updates
DHCPv6:         .... ..0. = No server override updates
DHCPv6:         .... .0.. = Server performs updates
DHCPv6:   FQDN = 0x00 0x06 0x6C 0x61 0x73 0x73 0x65 0x6E
DHCPv6: Option Code = 16 (Vendor Class)
DHCPv6:   Enterprise Number = 311 (Unknown)
DHCPv6:   Class = 4d 53 46 54 20 35 2e 30
DHCPv6: Option Code = 6 (Option Request)
DHCPv6:   Requested Option Code = 24 (Domain Search List)
DHCPv6:   Requested Option Code = 23 (DNS Recursive Name Server)
DHCPv6:   Requested Option Code = 17 (Vendor-specific Information)

ICMPv6:  ----- ICMPv6 Header -----
ICMPv6:
ICMPv6:  Type = 136 (Neighbor advertisement)
ICMPv6:  Code = 0
ICMPv6:  Checksum = dd9b
ICMPv6:  Target node = 2001:470:d:2ed::2, 2001:470:d:2ed::2
ICMPv6:  Router flag: NOT SET, Solicited flag: NOT SET, Override flag: SET
ICMPv6:
ICMPv6:  +++ ICMPv6 Target LL Addr option +++
ICMPv6:  Link Layer address: 0:15:17:f4:12:21
ICMPv6:
DHCPv6:   Requested Option Code = 39 (Client FQDN)
DHCPv6:


[cholzhauer]

How are you assigning addresses to your Solaris machines?

I just saw your other post ("D Link native support..." and it looks like you have the RA box checked on the router.  Thirty minutes does seem like a long time though.

To check your windows RA settings, see reply #5 here  http://www.tunnelbroker.net/forums/index.php?topic=1209.0  (you'd obviously want to enable instead of disable)

[drydog]

I have router discovery enabled on Windows 7 (see below).  IPv6 autoconfiguration on Win7 used to work when I had the HE 6over4 tunnel on Solaris and IPv6 was setup automatically on Win7 (and WinXP before that).  Now that I moved the tunnel from Solarris to the D-Link DIR-825 router , there appears to be no Router Advertising and autoconfiguration from the D-Link router.

I also now have to setup IPv6 manually on Solaris. Before (except for the Solaris box that had the tunnel), all I needed was an empty /etc/hostname6.e1000g0 file.  Now I need this to manually setup a IPv6 address and persistent route (both last through reboots):

Code Select Expand


# cat /etc/hostname6.e1000g0
addif 2001:470:d:2ed::2/128 up
# route -p add -inet6 default fe80::218:e7ff:fef7:3a73

Windows 7 configuration:

Code Select Expand

C:\Windows\System32>netsh int ipv6 show interfaces
Idx     Met         MTU          State                Name
---  ----------  ----------  ------------  ---------------------------
 1          50  4294967295  connected     Loopback Pseudo-Interface 1
12          50        1280  disconnected  6TO4 Adapter
11          10        1500  connected     Local Area Connection
C:\Windows\System32>netsh int ipv6 sh int 11
Interface Local Area Connection Parameters
----------------------------------------------
IfLuid                             : ethernet_6
IfIndex                            : 11
State                              : connected
Metric                             : 10
Link MTU                           : 1500 bytes
Reachable Time                     : 18000 ms
Base Reachable Time                : 30000 ms
Retransmission Interval            : 1000 ms
DAD Transmits                      : 1
Site Prefix Length                 : 64
Site Id                            : 1
Forwarding                         : disabled
Advertising                        : disabled
Neighbor Discovery                 : enabled
Neighbor Unreachability Detection  : enabled
Router Discovery                   : enabled
Managed Address Configuration      : enabled
Other Stateful Configuration       : enabled
Weak Host Sends                    : disabled
Weak Host Receives                 : disabled
Use Automatic Metric               : enabled
Ignore Default Routes              : disabled
Advertised Router Lifetime         : 1800 seconds
Advertise Default Route            : disabled
Current Hop Limit                  : 0
Force ARPND Wake up patterns       : disabled
Directed MAC Wake up patterns      : disabled

[cholzhauer]

Sounds like a bug in the dlink (or the advertisement interval is set too high)

You could always assign by hand (same way you would an IPv4 address, just pick the v6 adapter instead.