Hurricane Electric's IPv6 Tunnel Broker Forums

General IPv6 Topics => IPv6 on Windows => Topic started by: tjeske on April 20, 2018, 06:16:24 AM

Title: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: tjeske on April 20, 2018, 06:16:24 AM
It seems there's a serious problem. After updating to Spring Creators Update, my tunnel is not working anymore. I cannot setup the tunnel device (adding v6v4tunnel fails). I fear this will not be resolved in the final build of the newly named April 2018 update. For now, I strongly advise against updating.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: cholzhauer on April 20, 2018, 06:32:04 AM
You must be on the insiders fast ring?  What build number?
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: tjeske on April 22, 2018, 06:37:39 AM
Not really. I am not even registered for the insiders program. I was just quick to download ISO file before Microsoft found some problem and decided to withdraw the final status again, and to delay the update until further adjustments have been made. I am currently on build 17133.1. Well, of course it could be possible that "some problems" also include the v6v4tunnel, but I have doubts about that.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: tjeske on April 26, 2018, 09:55:11 AM
I set a test machine to Windows Insider on the Release Preview ring. Build 17134.1. Problem still existing. I'll now try Slow Ring, and if that fails Fast Ring. From what I've found out, this issue exists at least since insider preview build 17046.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: tjeske on April 26, 2018, 12:39:12 PM
Seems like this problem slipped by unnoticed. Just "skipped ahead to the next Windows release" Insider 1803 build 17655.1000, and it's still broken.

I strongly advise anyone not to upgrade past Windows 1709 at the moment, if you need to start the tunnel from Windows. Maybe this bug will cause more noise once the April 2018 update goes live, and hopefully will result in a quicker fix then.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: RDWells on April 30, 2018, 04:59:55 PM
I am getting these errors when attempting to install the IPv6 Tunnel following the Win10 Pro x64 Spring Creators Update, v1803 (OS Build 17134.1):


C:\WINDOWS\system32>netsh interface teredo set state disabled
Ok.

C:\WINDOWS\system32>netsh interface ipv6 add v6v4tunnel interface=IPv6Tunnel localaddress=192.168.0.x remoteaddress=184.105.xxx.xx
There is no driver selected for the device information set or element.


C:\WINDOWS\system32>netsh interface ipv6 add address interface=IPv6Tunnel address=2001:470:1f10:111f::2
The filename, directory name, or volume label syntax is incorrect.


C:\WINDOWS\system32>netsh interface ipv6 add route prefix=::/0 interface=IPv6Tunnel nexthop=2001:470:1f10:111f::1
The filename, directory name, or volume label syntax is incorrect.

Those commands worked in the previous build but will not work now.  What is concerning is the line "There is no driver selected for the device information set or element."

Is it possible that the Spring Creators Update changed the netsh commands without telling us?
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: tjeske on May 02, 2018, 04:09:16 AM
Those commands worked in the previous build but will not work now.  What is concerning is the line "There is no driver selected for the device information set or element."

For some reason, the v6v4tunnel-driver/binding/whatever-its-called is not correctly installed anymore. It's actually part of netip6.inf, which is for IPv6 in general, but it doesn't seem to work anymore. No idea if this can be manually fixed. I don't know the commands. Tried reinstalling the inf-file with no success.

netcfg -v -m (optionally use  "netcfg -v -m | clip" which will copy to clipboard so you can paste output to notepad)

This shows at least one line "Binding entry ignored since it is Type:5 Name:ms_tcpip6_tunnel". So, Windows somehow is aware that this tunnel exists in theory. Maybe they even disabled it intentionally, since MS says they don't want to actively support IPv6-transition mechanisms anymore and instead push people towards using native IPv6. See for yourself:

https://docs.microsoft.com/en-us/windows/deployment/planning/windows-10-1803-removed-features

"6to4 has been disabled by default since Windows 10, version 1607 (the Anniversary Update), ISATAP has been disabled by default since Windows 10, version 1703 (the Creators Update), and Direct Tunnels has always been disabled by default. Please use native IPv6 support instead."

However, this doesn't mention "6in4". Or is that what "Direct Tunnels" are? In that case, it should be possible to enable it somehow.

Edit: if you need v6v4tunnel to work, DON'T update to 1803!!! Just stay on 1709.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: RDWells on May 02, 2018, 09:47:49 AM
Well, harrumph, they don't exactly say how to implement native IPv6, do they?  My ISP (RCN) doesn't support it yet.

Guess we're stuck for now, huh?
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: cholzhauer on May 02, 2018, 10:12:27 AM
Let's clarify some things here.

*You* can't implement native IPv6; you have to wait for your ISP to do that.

And as far as the "Direct Tunnels", I suspect they're talking about Teredo.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: RDWells on May 02, 2018, 10:18:49 AM
Let's clarify some things here.

*You* can't implement native IPv6; you have to wait for your ISP to do that.

Right, got that, and as far as I could discern, they aren't exactly hopping to it yet.

And as far as the "Direct Tunnels", I suspect they're talking about Teredo.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: cholzhauer on May 02, 2018, 10:20:23 AM
Nah, very few seem to be.  Until you have IPv6-only content, it'll be hard to convince the small ISP's to make the infrastructure investment.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: tjeske on May 03, 2018, 04:04:50 AM
Is there maybe a 3rd party client software for 6in4 tunnels? I couldn't find anything. All the results are just saying about v6v4tunnel and how to do it from Windows.

I am really pissed. The one time that I directly deleted the previous Windows version after upgrading seeing it booted fine. And now this shit. And I don't have the time to reinstall Windows 10 at the moment.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: broquea on May 04, 2018, 11:25:58 AM
Do you not have a device upstream of the Windows machine to configure the tunnel on? I mean, you could probably even run a linux VM on the Windows machine if it needs to be running on it.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: tjeske on May 06, 2018, 02:56:31 PM
No, cause I need this machine to be directly connected to the network.

I thought about the VM stuff, but I'd need a VM that forwards proto 41 from host to guest. And VirtualBox doesn't seem to be doing that.

I also posted in Windows forums, they seem to be aware of this issue now, and are also considering it an issue, and not a "feature for removal". But at least in insider build 17661 it's not fixed. To be honest, I don't know exactly how it works with the build numbers and possible intermediate patches. So, I am still just gonna sit it out.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: tjeske on May 09, 2018, 01:38:27 AM
Update: no news!

Still broken in final 1803 build 17134.48

Also still broken in
-RS5 insider build 17661.1001
-RS5 insider build 17666.1000
-RS5 insider build 17672
-RS5 insider build 17677.1000
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: RDWells on May 17, 2018, 04:05:49 PM
I just spent a LOT of time with four, count 'em, four "techs" through MS' Virtual Assistant thingie, all of whom wanted to remote control my computer and do stuff completely irrelevant to the problem (I'll spare y'all the gory details), but I FINALLY convinced the fourth one who pretty much summed the issue as a bug which, he wanly suggested, would be looked at by MS engineers who'll send out a fix whenever they dang well feel like it.

So there we have it.  MS "fixed" what ain't broken;  i.e., the netsh command to install a v6v4tunnel doesn't work due to a "bug" and now the geniuses who broke it are gonna fix it. 

So they say.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: tjeske on May 18, 2018, 09:00:26 AM
So did someone actually login to your machine? What did they try?

Anyway, there's also this thread on TechNet:
https://social.technet.microsoft.com/Forums/windows/en-US/af68159a-87fc-4e39-92a9-c5f209aa4058/will-v6v4tunnel-be-fixed-in-final-version-of-april-2018?forum=win10itpronetworking

It appears as if Microsoft acknowledges this issue. However, I am not sure how serious they treat this issue and how fast it might get resolved. The statement doesn't sound too promising, to hopefully fix it with the next release. And I hope by "release" they mean cumulative update, not Redstone 5. Maybe if more people post over there it'll spark more interest to tackle this bug.

All in all it's probably really only a handful of people affected, since most will have a non-Windows upstream device serving as the local tunnel endpoint.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: RDWells on May 18, 2018, 01:12:29 PM
So did someone actually login to your machine? What did they try?

Yes, and one wanted to do a System Restore (NO!), another wanted to update the network driver (duh, not the problem), the third did a network reset (which served to do absolutely nothing) and the fourth had me try to use the lengthy version of the netsh command:

netsh interface ipv6 add v6v4tunnel interface=private localaddress= "Your local address" remoteaddress= "remote address given to you" (with the proper numbers put where they belong.)

...which did bupkis.  Same answer:  "no driver selected...."

He (the fourth guy) also wanted to be sure that the mobo drivers were up-to-date.  This is what I meant by irrelevant, and my drivers are ALL up-to-date.  I'm OCD that way.

Anyway, there's also this thread on TechNet:
https://social.technet.microsoft.com/Forums/windows/en-US/af68159a-87fc-4e39-92a9-c5f209aa4058/will-v6v4tunnel-be-fixed-in-final-version-of-april-2018?forum=win10itpronetworking

It appears as if Microsoft acknowledges this issue. However, I am not sure how serious they treat this issue and how fast it might get resolved. The statement doesn't sound too promising, to hopefully fix it with the next release. And I hope by "release" they mean cumulative update, not Redstone 5. Maybe if more people post over there it'll spark more interest to tackle this bug.

All in all it's probably really only a handful of people affected, since most will have a non-Windows upstream device serving as the local tunnel endpoint.

At least I know that it's not just me (or you) having this issue, but for FOUR techs not really having the first clue as to what I talking about is troubling at the least, annoying (and more) at most.  So, looks like we'll just have to twiddle our collective thumbs until MS gets it into gear (without too much grinding?).  The fourth tech said maybe a week or two.  Maybe....

In the meantime, the fourth tech also suggested that as many people as possible submit feedback through their feedback hub so the engineers can spot it.  Yes, that's what he said, so hop to it, readers of this forum.  Light a fire under their bums and let's get this fixed, ASAP.  Here's the link:  https://aka.ms/AA1dxur

P.S. I am not a Windows Insider, I have Window 10 Pro x64 v1803(OS build 17134.48), the April 2018 Spring Update with subsequent quality update of KB4103721 (5/10/18).
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: tjeske on May 19, 2018, 09:27:12 AM
Okay, so I tried to investigate a bit more. At least I found something that was different from 1803 to 1709. If you run this command:

Code: [Select]
netcfg -s n
you will get a list of network adapters, network protocols, and network services. If you scroll through the list you'll find an item called "ms_tcpip6_tunnel - Microsoft TCP/IP version 6 - Tunnels". On 1709 this is listed under "Network Protocols", together with "ms_tcpip6", while on 1803 "ms_tcpip6_tunnel" is listed under "Network Services", while "ms_tcpip6" is still in the "Network Protocols" group.

I was able to delete ms_tcpip6_tunnel and afterwards add it again as a protocol, instead of a service. While on 1709 this was possible with simple administrative privileges, on 1803 I had to run it as "TrustedInstaller". Even though it is listed now in the correct category, it still doesn't work. This is also understandable from the output of "nvspbind.exe", which is a separate tool by Microsoft. The output shows all services or protocols bound to specific network adapters. While on 1709 I can find both "ms_tcpip6" and "ms_tcpip6_tunnel", I can't find the latter on the affected 1803. I haven't found a way yet if it is possible to somehow manually add a protocol. The nvspbind-utility doesn't have an option for this, only to enable or disable already bound protocols.

EDIT:
I think it's because nettun.inf is missing from 1803. I find it on 1709 under HKEY_LOCAL_MACHINE\DRIVERS\DriverDatabase\DriverPackages\ but it's missing completely on 1803. Maybe possible to transfer the INF over and do a manual install.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: tjeske on May 21, 2018, 04:53:05 AM
Okay, after a little more digging I wanna share my new insight:

It seems to be indeed nettun.inf and the associated driver tunnel.sys which is used to set up the 6in4 tunnel. If you start a tunnel, it will appear as "Microsoft Direct Point-to-Point Tunnel Adapter" in the device manager. The inf-file also holds all the driver information for Teredo, ISATAP, 6to4, and some more. The bad news about this is that 6in4 is therefor indeed the "Direct Tunnels" which where marked deprecated as of 1803 along with all the other IPv6 transition technologies. So I fear that even if it should be able to enable it somehow, Microsoft will not honor this bug and leave it unfixed.

So, I've tried to fix it myself by copying over the driver from a healthy 1709 installation. First pitfall, I can't find to copy the signed driver (inf file misses signture?), and therefor installation is only possible with driver signature enforcement turned off during boot. After that, it installs without error. When I try to set up the tunnel, it still doesn't work, but the error message changed to a simple "Element not found". Checking device manager, I get the Direct Tunnel adapter with a yellow sign and error code 56, manually adding the driver fails with a time out.

What seems still different is that the driver is listed in the registry under some oemxx.inf-key, whereas on an original installation it's simply called nettun.inf. I'll try to copy over some registry keys and see if that helps.

Fingers crossed.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: Hoser13 on May 23, 2018, 07:43:01 PM
Found this after months of researching on an MS site:

https://docs.microsoft.com/en-us/windows/deployment/planning/windows-10-1803-removed-features

IPv4/6 Transition Technologies (6to4, ISATAP, and Direct Tunnels)   6to4 has been disabled by default since Windows 10, version 1607 (the Anniversary Update), ISATAP has been disabled by default since Windows 10, version 1703 (the Creators Update), and Direct Tunnels has always been disabled by default. Please use native IPv6 support instead.

So does this mean there is no way to use a Tunnelbroker tunnel going forward?  Or can someone more technical than me offer a suggestion?

Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: cholzhauer on May 24, 2018, 05:06:42 AM
You don't use any of these technologies with HE, HE is 6in4
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: tjeske on May 24, 2018, 11:19:50 AM
But I am pretty certain now that "Direct Tunnels" is 6in4. Why? If I create an IPv6-tunnel with the "add v6v4tunnel", a "Microsoft Direct Point-to-Point Tunnel Adapter" gets added to "Device Manager". Furthermore, after fiddling with the driver for "Direct Tunnels", I was able to change the error message given by netsh.
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: tjeske on May 25, 2018, 11:07:17 AM
Still broken in:

-RS5 insider build 17677.1000
Title: Re: Windows 10 Spring Creators Update breaks v6v4tunnel
Post by: RDWells on May 25, 2018, 12:32:42 PM
Following an OOB Quality Update KB4100403 for Win10 to v1803 (17134.81), it's still broken.

Dangit.