IPv6 tunnel config, in windows 10 ver 10130.

[zwitterions]

I thank everyone on this issue with Windows 10, but i can not seem to get around it, has anyone come up with a script to make it work?

Any help would be much App!

[ellegi]

doesn't work for me with "Private"   :-\

[ellegi]

I'm investigating for the problem.

After launching the netsh command and opening the driver debug log file c:\windows\inf\setupapi.dev.log

i see this  0x00000005 "Access denied" error. Tell me if someone here have the same problem.

>>>  [Configure Driver Package - c:\windows\system32\driverstore\filerepository\nettun.inf_amd64_73be4b5cbfb3a9a0\nettun.inf]
>>>  Section start 2015/08/04 23:40:28.022
      cmd: netsh  interface ipv6 add v6v4tunnel "Private" 192.168.1.15 1.2.3.4
     sto: Source Filter  = TUNDIRECT.ndi
     sto: Target Filter  = ROOT\*TUNDIRECT\0000
     inf: Class GUID     = {4d36e972-e325-11ce-bfc1-08002be10318}
     inf: Class Options  = Configurable
!!!  idb: Failed to open driver package object 'nettun.inf_amd64_73be4b5cbfb3a9a0'. Error = 0x00000005
<<<  Section end 2015/08/04 23:40:28.038
<<<  [Exit status: FAILURE(0x00000005)]

[LVNeptune]

[Boot Session: 2015/08/16 11:53:03.493]

>>>  [Configure Driver Package - c:\windows\system32\driverstore\filerepository\nettun.inf_amd64_73be4b5cbfb3a9a0\nettun.inf]
>>>  Section start 2015/08/16 11:54:30.082
      cmd: netsh  interface ipv6 add v6v4tunnel "Private" 192.168.2.138 x.x.x.x
     sto: Source Filter  = TUNDIRECT.ndi
     sto: Target Filter  = ROOT\*TUNDIRECT\0000
     inf: Class GUID     = {4d36e972-e325-11ce-bfc1-08002be10318}
     inf: Class Options  = Configurable
!!!  idb: Failed to open driver package object 'nettun.inf_amd64_73be4b5cbfb3a9a0'. Error = 0x00000005
<<<  Section end 2015/08/16 11:54:30.099
<<<  [Exit status: FAILURE(0x00000005)]

[th3cr3a7or]

I used the following defined commands to get it configured correctly
netsh teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface= private localaddress= "Your local address" remoteaddress= "remote address given to you"
netsh interface ipv6 add address interface= private address= 2001:470:1c:211::2
netsh interface ipv6 add route prefix= ::/0 interface= private nexthop= 2001:470:1c:211::1

[abuson]

I used the following defined commands to get it configured correctly
netsh teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface= private localaddress= "Your local address" remoteaddress= "remote address given to you"
netsh interface ipv6 add address interface= private address= 2001:470:1c:211::2
netsh interface ipv6 add route prefix= ::/0 interface= private nexthop= 2001:470:1c:211::1

Thanks, this actually works!!

Small fixes + you don't have to use private, it works with interface name - IP6Tunnel too:
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel localaddress=LocalIPv4 remoteaddress=RemoteIPv4
netsh interface ipv6 add address interface=IP6Tunnel  address=2001:470:1c:211::2
netsh interface ipv6 add route prefix=::/0 interface=IP6Tunnel nexthop=2001:470:1c:211::1

[LVNeptune]

Yea that's a negative. still same errors as before.

[LVNeptune]

So I figured out that every time I ran the add v6v4tunnel command it was adding a subinterface but NOT naming it to what I named.

netsh interface ipv6 show subinterface

this command shows the new "Local Area Connect *X" that was added. If you replace the interface="enter full lan name here" it should work for you.

No clue what's up with stuff not working for everyone though. Really makes little to no sense.

[ellegi]

So I figured out that every time I ran the add v6v4tunnel command it was adding a subinterface but NOT naming it to what I named.

netsh interface ipv6 show subinterface

this command shows the new "Local Area Connect *X" that was added. If you replace the interface="enter full lan name here" it should work for you.

No clue what's up with stuff not working for everyone though. Really makes little to no sense.

same problem here.

[zwitterions]

Hi ALL.

I have tried everything in this post, and the new example in the win 10 example, i can only guess it is because i use a VPN  all the time, it shows that i have bytes out in 6to4 adapter, none in, i am going to get on to Microsoft tech support, and get to the bottom of this. I also can not see why some people are getting it to work, and others like myself are not, i am on full windows 10 now, and nothing makes it work! I thank everyone who has put forward there ideas and configs, if i get a response from Microsoft, i will post it back here today.

[3mook06]

Hey all, im pretty bad with the command line stuff, just gonna post the error i had and see if anyone has any ideas.
---
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

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

C:\Windows\system32>netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel localaddress=192.168.1.101 remoteaddress=216.66.80.90
The function attempted to use a name that is reserved for use by another transaction.
---
^that last line is the error, cant seem to get around it, thanks all



EDIT: ok i think i have fixed it somewhat after much fiddling

1: in device manager, view - show hidden devices
2: uninstall all the "Microsoft Direct Point-to-point Adapter"
3: uninstall all the "Microsoft ISATAP Adapter"
4: Reboot
5: Command Prompt as Admin the following:

netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface="private" localaddress=192.168.1.101 remoteaddress=216.66.80.90
netsh interface ipv6 add address interface="private" address=2001:470:27:19c::2
netsh interface ipv6 add route prefix=::/0 interface="private" nexthop=2001:470:27:19c::1

^so yeah i needed quotes on private, IP6Tunnel would not work for me

6: i had some issues getting anything to use ipv6, so i manually added google ipv6 DNS to my network adapter (2001:4860:4860::8888) and (2001:4860:4860::8844)

seems good enough for now

[zwitterions]

Hi all, i have tried everything possible, and can not get it to work, i see a lot of people saying add private address, however i use a static address, i mean most of us are sages, and i can not see why either one of us sages, or hurricane does not put up a working example. Just a thought, i mean what good are we "Sages" if we can not get this working?

I do thank everyone's input, but were is the Eisenstein out there with us sages?

I am putting off upgrading my other win7 ultimate boxes, for fear of losing my IPv6 i get a lot of IPv6 traffic, and need to keep it there.

PLEASE, some one out there has cracked this..
Regards
Zwitterions

[ellegi]

Me in the same situation. Tried everything: copied old tunnel.sys drivers, changed something in windows registry, but it is a huge problem caused by microsoft and we should complain with them.

At the moment i've temporary solved configuring the oèv6 tunnel on a linux box and routing through vpn.

Hi all, i have tried everything possible, and can not get it to work, i see a lot of people saying add private address, however i use a static address, i mean most of us are sages, and i can not see why either one of us sages, or hurricane does not put up a working example. Just a thought, i mean what good are we "Sages" if we can not get this working?

I do thank everyone's input, but were is the Eisenstein out there with us sages?

I am putting off upgrading my other win7 ultimate boxes, for fear of losing my IPv6 i get a lot of IPv6 traffic, and need to keep it there.

PLEASE, some one out there has cracked this..
Regards
Zwitterions

[Lupo]

Possibly good news for everyone that was experiencing this issue.

After the latest three updates pushed today (KB3081448, KB3081449, KB3081452), I was able to consistently create and delete v6v4tunnel interfaces.
No change in the syntax from what we always used. It seems they fixed whatever problem was preventing it from working correctly.

I tested multiple times, on two computers that were unable to create the interface before, and both instances went through with no issues.

Hopefully this was a global fix, and not just luck on my side.
Regards.


Edit: only one weird thing.. I had to set a dns address in the ipv6 configuration for it to properly work.. Just having ipv6 enabled global dns seems to not work properly for me.

[ellegi]

Great. it works!

I have the same problem with dns. What commands you have used to set dns for the specified interface?

Possibly good news for everyone that was experiencing this issue.

After the latest three updates pushed today (KB3081448, KB3081449, KB3081452), I was able to consistently create and delete v6v4tunnel interfaces.
No change in the syntax from what we always used. It seems they fixed whatever problem was preventing it from working correctly.

I tested multiple times, on two computers that were unable to create the interface before, and both instances went through with no issues.

Hopefully this was a global fix, and not just luck on my side.
Regards.


Edit: only one weird thing.. I had to set a dns address in the ipv6 configuration for it to properly work.. Just having ipv6 enabled global dns seems to not work properly for me.