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.

Messages - tjeske

Pages: [1] 2 3
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.

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.

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).

Probably it's not DMZ, but exposed host. Maybe your router doesn't forward IP-protocol 41 (protocol, not port!). What's your router model?

Maybe if you're using IPv6 privacy extensions, you'll get lots of different addresses for your device(s), and all seem to need an entry in those geolocation databases.

I have the same problem with domain. How was your friend able to help you out?

It seems this problem still exists. HE doesn't "activate" delegation on their NS before they are marked as authorative. However, e.g. doesn't give authority before the delegation isn't active. Thus, deadlock still exists.

Questions & Answers / Re: tunnel down (endpoint Prague)
« on: March 18, 2017, 02:26:08 PM »
Down again, though endpoint still pingable. I guess just maintenance?

Edit: Never mind. Working again fine. Just a minor hickup. Status page shows all green again as well.

CU? You mean Creator's Update? So that means you're on the Windows Insider program? So it's not fixed on the stable/mainstream channel?

Questions & Answers / Re: Testing protocol 41
« on: February 22, 2017, 09:35:31 AM »
I don't think proto 41 works like that. It's not like you open a connection, and this connection stays open and all data flows through it and the switches at your end will know where to send the data. No. Proto 41 needs end-to-end connectivity. How should the gateway know it is you that wants this package? You can monitor your interface with Wireshark to check for incoming proto 41 packages, but I think most 4G gateways will only work for TCP and - if you're lucky - UDP and ICMP.

Questions & Answers / Re: Carrier grade NAT on 4G
« on: February 22, 2017, 09:12:05 AM »
I know it's a lot of work, but there's also the option to take your server elsewhere, to a service, that offers a whole subnet. I wouldn't even think of IPv6-nat as well. Many devices probably won't even be able to work that way. At least you'd be the one controlling the port forwardings, so you wouldn't have to worry that much about your monitoring equipment.

And no, SixXS is/was the only service with ayiya.

Questions & Answers / Re: Using TunnelBroker for several routers
« on: February 22, 2017, 06:51:56 AM »
Which should be as follows:
LAN Prefix Length: 64 (if you didn't apply for 48 prefix)
LAN IPv6 Prefix: 2001:470:28:15c:: (check in your account settings whether the "28"-part is actually correct).

IPv6 settings of your access points shouldn't need any configurations. Just make sure that the LAN-device on those other units has IPv6 turned on (or not disabled). Also, your tp-link repeater might still pass the IPv6-RA to other devices, even if it doesn't assign itself an IPv6 (I'm using a TP-Link WR841ND unit as AP in my network, and even though it's a pre-IPv6 version, it passes the RA requests to all clients, as it happens at a different level of the OSI layers).

Questions & Answers / Re: Using TunnelBroker for several routers
« on: February 22, 2017, 06:09:41 AM »
Ok, AP mode is the way to go. But how do you connect to the HE tunnel? Which device does this and how?

Questions & Answers / Re: Using TunnelBroker for several routers
« on: February 22, 2017, 04:29:46 AM »
Does every router span its own subnet? Then you would need to configure prefix delegation and setting up the correct routes on each device. Much easier than running those router cascades is to run them in one single subnet, only the first unit working as a router, and the others working in switch mode.

Care to share your setup?

Questions & Answers / Re: tunnel down (endpoint Prague)
« on: February 22, 2017, 02:13:40 AM »
Berlin is working again. Now let's hope Prague comes back soon as well.

Thanks so much people at HE! You're the best!

Pages: [1] 2 3