Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: 1 2 [3] 4 5 ... 10
 21 
 on: May 02, 2018, 10:20:23 AM 
Started by tjeske - Last post by cholzhauer
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.

 22 
 on: May 02, 2018, 10:18:49 AM 
Started by tjeske - Last post by RDWells
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.

 23 
 on: May 02, 2018, 10:12:27 AM 
Started by tjeske - Last post by cholzhauer
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.

 24 
 on: May 02, 2018, 09:47:49 AM 
Started by tjeske - Last post by RDWells
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?

 25 
 on: May 02, 2018, 04:09:16 AM 
Started by tjeske - Last post by tjeske
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.

 26 
 on: May 01, 2018, 09:41:09 PM 
Started by seboi - Last post by seboi
Hi...
My Account Name:seboi
 
i would like to inform that i've complete the Sage level of free Ipv6 certification, i wanted to apply my tunnel to be giving full access into irc so i can connected right away.
 
nb. already send email to ipv6@he.net
but dont get autoemail from ipv6@he.net

ty for help me

 27 
 on: April 30, 2018, 04:59:55 PM 
Started by tjeske - Last post by RDWells
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?

 28 
 on: April 30, 2018, 01:59:02 PM 
Started by vimerate - Last post by vimerate
Just to make sure we're on the same page, you mean you can ping the HE side of the tunnel, right?

What happens if you disable your firewall for testing, do things work then?

Is your MTU value correct?
Yes, I meant to say that. I temporarily disabled FirewallD and everything works! Which means that something with FirewallD must be causing the problem. I also set my MTU to 1480.

 29 
 on: April 30, 2018, 10:22:34 AM 
Started by peterbjornx - Last post by snarked
After that, you have to log in and actually push the button.

 30 
 on: April 30, 2018, 09:19:38 AM 
Started by peterbjornx - Last post by broquea
You have to email ipv6@he.net with your account info if you are a Sage, to get access enabled to the filter removal buttons.

Pages: 1 2 [3] 4 5 ... 10