Okay, great! Microsoft really did it in insider build 17711 and brought back native 6in4 tunneling!

However, nettun.inf isn't there anymore, tunnel.sys is though. But I am not sure if it is still being used, because there's no device visible in device manager anymore. The tunnel works, it's device is listed using netsh. But I have no idea which driver is being used now. It just works™. Probably I'll have a look in the registry, but for now I am satisfied.

Let's hope they keep it running! Again: it's probably not going to be backported to RS4 aka 1803. Everyone who wants to use it needs to update to become a Windows insider and update to the current build. Fortunately, insider builds seem already quite progressed and I'd even use it in a mild production environment. But that's for everyone to decide on his/her own.

So, insider build 17711 is out. It seems fixed. But it looks like it's not nettun.inf anymore. However, I am not 100% sure, as I just updated the previous 17704 insider build where I applied the manual fix. Will do a fresh install now and report back. Also note that this hasn't been mentioned in the changelog.

Just looked, still no received followups to that ticket. Go ahead and fax in the LOA PDF on company letterhead to the number in the email.

I resent a LOA file by fax.
9/7/2018 6:57 HKT time

Just looked, still no received followups to that ticket. Go ahead and fax in the LOA PDF on company letterhead to the number in the email.

Can an engineer have a look at it? It has been 4 days.

Not seeing any replies to either BGP tunnel ticket. Please try again, make certain you are replying to the automatically opened ticket. Also might need to try from a different email address.

I have resent it, I sent the fax the day before yesterday but no one has responded to me.

You can check it in the ticketing system.
mail title: Re: [HE#3845288] IPv6 BGP Tunnel Request From AS137940

The minimum MTU size for IPv6 is 1,280 bytes.  Try setting your MTU to that value and see if it works then.  If not, then the problem might not be your configuration.  I have also noted that sometimes there is a routing problem over IPv6 which isn't there via IPv4 - especially where the two paths are distinctly different.

What can i do with the mtu size?

Hi,

I have a question regarding DDNS: My tunnel ends on a router running edgeos, and I want to use the DDNS feature to avoid a broken tunnel after getting a new v4 address.
My config:

Code: [Select]

service {
    dns {
        dynamic {
            interface eth0 {
                service dyndns {
                    host-name <redacted>.tunnel.tserv26.ber1.ipv6.he.net
                    login rsokoll
                    password <tunnelbrokerupdatekey>
                    server ipv4.tunnelbroker.net
                }
            }
        }
But this results in:

Code: [Select]

FAILED:   updating <redacted>.tunnel.tserv26.ber1.ipv6.he.net: nohost: The hostname specified does not exist in the database
WARNING:  file /var/cache/ddclient/ddclient_eth0.cache, line 3: Invalid Value for keyword 'ip' = ''
WARNING:  skipping update of <redacted>.tunnel.tserv26.ber1.ipv6.he.net from <nothing> to <myipv4>.
WARNING:   last updated <never> but last attempt on Thu Jul  5 12:44:08 2018 failed.
WARNING:   Wait at least 5 minutes between update attempts.
Maybe I am missing an API key? It does not work with an empty string and also not with the update key


What am I missing?

Thanks,
Rainer

Can an engineer have a look at it? It has been 4 days.

Not seeing any replies to either BGP tunnel ticket. Please try again, make certain you are replying to the automatically opened ticket. Also might need to try from a different email address.

I'm not sure what you're referring to?