Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  


Welcome to Hurricane Electric's forums!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - tjeske

Pages: [1]
IPv6 on Windows / Windows 10 Spring Creators Update breaks v6v4tunnel
« 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.

IPv6 on Windows / [SOLVED] netsh: Including DNS in RA possible?
« on: May 12, 2016, 01:12:09 PM »

for some time now I am using my Windows 10 machine to establish the tunnel. Since I am using quite a lot of Virtual Machines, I set Windows up to advertise the routed prefix to the local network of the virtual machines.

The problem seems to be that the Router Advertisements from the Windows computer don't include a DNS-server address. So I can ping IPv6 addresses just fine, but I cannot resolve domains/hostnames. I know that AAAA records are also delivered by IPv4-DNS-servers, I can also set the DNS of HE (2001:470:20::2) manually. But I'd prefer automatic.

Is there a configuration for netsh to advertise the DNS? I'd also be fine with a piece of software that does this. Only thing is I want to stick to SLAAC and not start setting up DHCPv6.

IPv6 on Windows / Rejecting routes to cogent
« on: February 12, 2016, 03:26:38 AM »
Ok, so I just learned about the disagreement between HE and cogent. What is bugging me is that HE seems to find a route, but I believe there is no route back, so connections time out before falling back to IPv4.

Here ( somebody found a solution to this on Linux, by rejecting/disabling those routes. Is there a similar way to do this on Windows? I found a way to manually route to my loopback interface, but since this fails it tries to then use the default route - which times out - and then falls back to IPv4. I have not been able to find a way to reject/disable a route on Windows (10 Prof). Is there a solution at all?


I tried reaching using your tunneling service. While online-ping-services show that there's ipv6-connectivity to, I cannot get this done through your tunnel (and I tried different ones from the looking glass). Also, not only pinging is the issue, but also visiting the site.

Now I do not know if this is a routing issue, or if blocks all requests on IPv6 from your endpoints.

Pages: [1]