Print

[Hoser13]

Idx     Met         MTU          State                Name
---  ----------  ----------  ------------  ---------------------------
  1          75  4294967295  connected     Loopback Pseudo-Interface 1
 10          30        1500  connected     Wi-Fi
 11          25        1500  disconnected  Local Area Connection* 1
  6          25        1280  connected     IP6Tunnel

[cholzhauer]

You've told me your tunnel works, so I'm not sure what I would be looking for.

We need details, without them, we can't help.

[Hoser13]

I just know that none of the IPv6 tests show that I have 6 capability.  What details can I provide?

[cholzhauer]

Well, that's more than I knew before

Can you ping an ipv6 site and get a reply?  If not, your tunnel isn't up

Make sure your isp isn't blocking protocol41, make sure your router isn't blocking it, and make sure that if you have an rfc1918 address that you followed the instructions and altered the commands you used to create the tunnel

[Hoser13]

Changes made:

- Changed router to an AP (as I have the ISP router as well, where I turned off at least the 2G wireless.

- Added a DMZ for my new laptop address from the main router.  I no longer need (or can) change most settings on the AP as they are no longer relevant.  As a result, I get 20/20 on http://ipv6-test.com/, I am recognized as IPv6 on the NE site, and I can get a response from a ping -6 on google.

I thank you for you patience and assistance.  You have been awesome with your guidance.

[tjeske]

Apparently, Windows Spring Creators Update aka Redstone 4 aka 1803 breaks IPv6-tunneling. Even in the final build. Let's hope 1804 will fix it. I'll sit it out for now, as I have no time to do a full reinstall (and I deleted the rollback version already).