Hi,
thank you for the detailed information! Btw. the usual way to post screenshots is to use some image hoster (e.g.
http://postimage.org/) to upload a screenshot and then use the "Insert Image" button to specify its URL. As a result the screenshot is implicitly downloaded and shown embedded into your posting. You can use a freeware like
XnView to generate screenshots.
To summarize, this is your configuration reduced to the essential parts for IPv6:
WAN side:
---------
Remote IPv4 Address : 209.51.161.58
Remote IPv6 Address : 2001:470:4:571::1
Local IPv4 Address : x.x.x.x (my WAN addr here and its correct)
Local IPv6 Address : 2001:470:4:571::2
Primary IPv6 DNS Server : 2001:470:20::2
Secondary IPv6 DNS Server : -
LAN side:
---------
LAN IPv6 Address : 2001:470:5:571::1/64
LAN IPv6 Link-Local Address : FE80::218:E7FF:FEDE:E915/64
Client (wireless):
------------------
IPv6 Address: 2001:470:5:571:f158:c63e:cae3:6930
Temporary IPv6 Address: 2001:470:5:571:<changing Interface ID>
Link-local IPv6 Address: fe80::f158:c63e:cae3:6930%10
Default Gateway: fe80::218:e7ff:fede:e915%10
DNS Servers: 192.168.0.1
According to your router's setting "Autoconfiguration Type : SLAAC + Stateless DHCPv6" it should deploy the configured IPv6 DNS server address (2001:470:20::2) via stateless DHCPv6 to your client, but it doesn't. But this is only a minor problem and doesn't matter because you can also resolve names to IPv6 addresses by asking a DNS server via IPv4 (192.168.0.1 acting as a DNS relay).
Nothing looks wrong and your client's ipv6 routing table shows the routing entries as expected, especially the default route ::/0 pointing to the link local address of your router (fe80::218:e7ff:fede:e915). And this address is also shown in the IPv6 neighbor cache together with its resolved MAC address 00-18-e7-de-e9-15 (your router's LAN side MAC address). (Btw. the OUI "00-18-e7" contained in your router's MAC address belongs to 'Cameo Communications, INC.' and not to D-Link, as one would expect. You can see it, if you search for 00-18-e7 on
this website)
It's only its reachability state "Stale" that may be a problem if it never reaches the state "Reachable". Hence, please check if you can provoke state "Reachable" by entering the following commands inside a command prompt:
ping fe80::218:e7ff:fede:e915%10netsh int ipv6 show neighborFirst you should see ping replies coming back from your router's link local address fe80::218:e7ff:fede:e915.
Second the neighbor cache entry for your router's link local address fe80::218:e7ff:fede:e915 should now show state=Reachable.
Do these things happen as predicted?
Looking at
C:\Users\Christian>tracert -d -6 2001:4860:4860::8888
Tracing route to 2001:4860:4860::8888 over a maximum of 30 hops
1 * * * Request timed out.
2 * * * Request timed out.
...
this result is surprising because even if something is wrong on the WAN side your router should at least react correctly to the first step of traceroute resulting in the following expected output:
C:\Users\Christian>tracert -d -6 2001:4860:4860::8888
Tracing route to 2001:4860:4860::8888 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 2001:470:5:571::1
2 * * * Request timed out.
...
This is consistent with the results I get when doing a traceroute to your router's IPv6 WAN address:
While traceroute to your remote tunnel address 2001:470:4:571::1 works fine
C:\>tracert -d 2001:470:4:571::1
Routenverfolgung zu 2001:470:4:571::1 über maximal 30 Abschnitte
1 1 ms <1 ms <1 ms 2001:4dd0:????:????:9ec7:a6ff:fe??:????
2 21 ms 22 ms 22 ms 2001:4dd0:????:????::1
3 21 ms 21 ms 21 ms 2001:4dd0:1234:3::42
4 21 ms 21 ms 21 ms 2001:4dd0:1234:3:dc40::a
5 21 ms 21 ms 21 ms 2001:4dd0:a2b:37:dc40::c
6 25 ms 26 ms 25 ms 2001:4dd0:a2b:a8:30::b
7 34 ms 25 ms 26 ms 2001:7f8:1::a500:6939:1
8 32 ms 40 ms 32 ms 2001:470:0:2d0::1
9 111 ms 103 ms 102 ms 2001:470:0:2cf::2
10 103 ms 103 ms 103 ms 2001:470:0:299::1
11 120 ms 121 ms 123 ms 2001:470:0:1b5::2
12 * 133 ms 139 ms 2001:470:0:a6::1
13 131 ms 131 ms 131 ms 2001:470:4:571::1
Ablaufverfolgung beendet.
I get the following result when doing a traceroute to your local tunnel address 2001:470:4:571::2:
C:\>tracert -d 2001:470:4:571::2
Routenverfolgung zu 2001:470:4:571::2 über maximal 30 Abschnitte
1 <1 ms <1 ms <1 ms 2001:4dd0:????:????:9ec7:a6ff:fe??:????
2 22 ms 20 ms 21 ms 2001:4dd0:????:????::1
3 22 ms 21 ms 21 ms 2001:4dd0:1234:3::42
4 21 ms 21 ms 21 ms 2001:4dd0:1234:3:dc40::a
5 21 ms 21 ms 21 ms 2001:4dd0:a2b:37:dc40::c
6 25 ms 32 ms 25 ms 2001:4dd0:a2b:a8:30::b
7 25 ms 26 ms 26 ms 2001:7f8:1::a500:6939:1
8 43 ms 33 ms 41 ms 2001:470:0:2d0::1
9 105 ms 103 ms 103 ms 2001:470:0:2cf::2
10 105 ms 103 ms 103 ms 2001:470:0:299::1
11 120 ms 120 ms 122 ms 2001:470:0:1b5::2
12 * 134 ms 139 ms 2001:470:0:a6::1
13 141 ms 141 ms 141 ms 2001:470:0:8c::2
14 Zielhost nicht erreichbar.
Ablaufverfolgung beendet.
As you can see, both traceroutes differ from each other starting at step 13, where I interpret 2001:470:0:8c::2 being the Internet side and 2001:470:4:571::1 being the tunnel side address of the last IPv6 router on the path to your DIR-825. Consequently step 14 "Zielhost nicht erreichbar." is your router not reacting on the traceroute (via sending an ICMPv6 error message type 3 "Time Exceeded") as it does not on its LAN interface as shown above.
<EDIT>The last statement is wrong because the observed behaviour can be explained by the results I reported in my next posting, see
below. Performing a "tracert -d 2001:470:4:571::2" again while tracing it with wireshark reveals the same result as reported below, namely that it ends with an ICMPv6 error "Destination Unreachable" (Type 1) and Code 3 (Address unreachable) - which is reflected in the last line of the tracert above "Zielhost nicht erreichbar" (=Destination host not reachable)
</EDIT>Taking together these results gives us a strong hint that it is your DIR-825 not acting like an IPv6 router.
<EDIT>This conclusion must possibly be revised, because it was based on an assumption that turned out to be wrong, see my last EDIT above and my next posting
below.
</EDIT>On the other hand there are no other configuration options left inside your DIR-825 that you could change to solve the problem.
You could reset your router and repeat a complete configuration from scratch. In the worst case IPv6 routing function is broken in your firmware version, so the last option left is to try another one. I don't know if there is a newer version than 2.09NA (does this version fit your region?), the latest official version I can see on D-Link's US FTP download side is 2.07NA for Rev B - perhaps you should use that former version.
PT