Hurricane Electric's IPv6 Tunnel Broker Forums

Tunnelbroker.net Specific Topics => Questions & Answers => Topic started by: edoardocolombo99 on April 07, 2017, 08:20:55 AM

Title: Windows 10
Post by: edoardocolombo99 on April 07, 2017, 08:20:55 AM
Hello, how i can set up a tunnel in windows 10? i used pre-made config from my tunnelbroker.net dashboard but it didnt work, i get an ipv6 address but its local: https://gyazo.com/4a3c6dea811bfa0fca1d06f5a8453abf

First i had windows 7 and it was working, but now with windows 10 no :( can someone help me?

Title: Re: Windows 10
Post by: cholzhauer on April 07, 2017, 08:22:46 AM
I see a 2001: address on that screenshot, what makes you think it's local?
Title: Re: Windows 10
Post by: edoardocolombo99 on April 07, 2017, 12:43:21 PM
I cant load anything in ipv6, also if i ping ipv6.google.com or my vps ipv6 i get error
https://gyazo.com/989e9da5b0af934b1bf9fda0a681a9c5
Title: Re: Windows 10
Post by: cholzhauer on April 08, 2017, 12:03:51 PM
Please post the output of ipconfig /all and the commands you used to create the tunnel
Title: Re: Windows 10
Post by: edoardocolombo99 on April 09, 2017, 09:43:58 AM
Quote from: cholzhauer on April 08, 2017, 12:03:51 PM
Please post the output of ipconfig /all and the commands you used to create the tunnel
These are commands :
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel localaddress=82.54.134.250 remoteaddress=216.66.84.46
netsh interface ipv6 add address interface=IP6Tunnel address=2001:470:1f14:925::2
netsh interface ipv6 add route prefix=::/0 interface=IP6Tunnel nexthop=2001:470:1f14:925::1

Output: https://gyazo.com/a088f369eafda73220347e06dd4dcdb3


I have a lot of tunnels but no one is working (Sorry but my pc is in italian)

Configurazione IP di Windows

   Nome host . . . . . . . . . . . . . . : EdoardoColomboPC212
   Suffisso DNS primario . . . . . . . . :
   Tipo nodo . . . . . . . . . . . . . . : Ibrido
   Routing IP abilitato. . . . . . . . . : No
   Proxy WINS abilitato . . . . . . . .  : No
   Elenco di ricerca suffissi DNS. . . . : homenetwork

Scheda Ethernet Ethernet:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione: homenetwork
   Descrizione . . . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Indirizzo fisico. . . . . . . . . . . : AC-22-0B-4D-B4-A0
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì

Scheda LAN wireless Local Area Connection* 2:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Indirizzo fisico. . . . . . . . . . . : 16-E9-84-8D-E4-9E
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì

Scheda Ethernet Ethernet 4:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : TAP-Windows Adapter V9
   Indirizzo fisico. . . . . . . . . . . : 00-FF-19-1A-47-1B
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì

Scheda Ethernet Ethernet 5:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : gogo6 Virtual Multi-Tunnel Adapter
   Indirizzo fisico. . . . . . . . . . . : 02-50-F2-00-00-01
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì

Scheda Tunnel IP6Tunnel99:

   Suffisso DNS specifico per connessione: homenetwork
   Descrizione . . . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
   Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP abilitato. . . . . . . . . . . . : No
   Configurazione automatica abilitata   : Sì
   Indirizzo IPv6 locale rispetto al collegamento . : fe80::7136:b029:d6a7:8470%15(Preferenziale)
   Gateway predefinito . . . . . . . . . :
   IAID DHCPv6 . . . . . . . . . . . : 838860800
   DUID Client DHCPv6. . . . . . . . : 00-01-00-01-1F-AB-02-24-AC-22-0B-4D-B4-A0
   Server DNS . . . . . . . . . . . . .  : 192.168.1.1
   NetBIOS su TCP/IP . . . . . . . . . . : Disattivato

Scheda LAN wireless Wi-Fi:

   Suffisso DNS specifico per connessione: homenetwork
   Descrizione . . . . . . . . . . . . . : Qualcomm Atheros AR9287 Wireless Network Adapter
   Indirizzo fisico. . . . . . . . . . . : C4-E9-84-8D-E4-9E
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì
   Indirizzo IPv6 locale rispetto al collegamento . : fe80::c8ab:abb7:cf66:3fa2%20(Preferenziale)
   Indirizzo IPv4. . . . . . . . . . . . : 192.168.1.5(Preferenziale)
   Subnet mask . . . . . . . . . . . . . : 255.255.255.0
   Lease ottenuto. . . . . . . . . . . . : domenica 9 aprile 2017 18:39:37
   Scadenza lease . . . . . . . . . . .  : lunedì 10 aprile 2017 18:39:36
   Gateway predefinito . . . . . . . . . : fe80::928d:78ff:fe77:11b4%20
                                           192.168.1.1
   Server DHCP . . . . . . . . . . . . . : 192.168.1.1
   IAID DHCPv6 . . . . . . . . . . . : 80013700
   DUID Client DHCPv6. . . . . . . . : 00-01-00-01-1F-AB-02-24-AC-22-0B-4D-B4-A0
   Server DNS . . . . . . . . . . . . .  : 192.168.1.1
   NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet Ethernet 2:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : Anchorfree HSS VPN Adapter
   Indirizzo fisico. . . . . . . . . . . : 00-FF-65-42-BD-DB
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì

Scheda Tunnel isatap.homenetwork:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione: homenetwork
   Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP abilitato. . . . . . . . . . . . : No
   Configurazione automatica abilitata   : Sì

Scheda Tunnel IP6Tunnel:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
   Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP abilitato. . . . . . . . . . . . : No
   Configurazione automatica abilitata   : Sì

Scheda Tunnel Local Area Connection* 13:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : Microsoft 6to4 Adapter
   Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP abilitato. . . . . . . . . . . . : No
   Configurazione automatica abilitata   : Sì

Scheda Tunnel IP6Tunnel2:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
   Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP abilitato. . . . . . . . . . . . : No
   Configurazione automatica abilitata   : Sì

Scheda Tunnel IP6Tunneldio:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
   Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP abilitato. . . . . . . . . . . . : No
   Configurazione automatica abilitata   : Sì
Title: Re: Windows 10
Post by: cholzhauer on April 10, 2017, 05:50:08 AM
Posting multiple threads won't get you help any faster.

You need to substitute your NAT address for your public IP address
Title: Re: Windows 10
Post by: edoardocolombo99 on April 10, 2017, 09:15:29 AM
Im sorry... i just delete the other post.
I used my local (192.168.1.3) address but ipv6 still not working :(

Ipconfig:
Scheda Tunnel IP6Tunnel:

   Suffisso DNS specifico per connessione: homenetwork
   Descrizione . . . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
   Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP abilitato. . . . . . . . . . . . : No
   Configurazione automatica abilitata   : Sì
   Indirizzo IPv6 . . . . . . . . . . . . . . . . . : 2001:470:25:64d::2(Preferenziale)
   Indirizzo IPv6 locale rispetto al collegamento . : fe80::5015:4fb:7a17:1d1%58(Preferenziale)
   Gateway predefinito . . . . . . . . . : 2001:470:25:64d::1
   IAID DHCPv6 . . . . . . . . . . . : 973078528
   DUID Client DHCPv6. . . . . . . . : 00-01-00-01-1F-AB-02-24-AC-22-0B-4D-B4-A0
   Server DNS . . . . . . . . . . . . .  : 2a00:6d40:60:6a7f::1
                                           94.177.171.127
   NetBIOS su TCP/IP . . . . . . . . . . : Disattivato
Title: Re: Windows 10
Post by: cholzhauer on April 10, 2017, 09:44:51 AM
Let's see ipconfig /all and the commands you used to create the tunnel.

Is your ISP blocking protocol 41?
Title: Re: Windows 10
Post by: edoardocolombo99 on April 12, 2017, 11:21:59 AM
Ipconfig:
Configurazione IP di Windows

   Nome host . . . . . . . . . . . . . . : EdoardoColomboPC212
   Suffisso DNS primario . . . . . . . . :
   Tipo nodo . . . . . . . . . . . . . . : Ibrido
   Routing IP abilitato. . . . . . . . . : No
   Proxy WINS abilitato . . . . . . . .  : No
   Elenco di ricerca suffissi DNS. . . . : homenetwork

Scheda Ethernet Ethernet:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione: homenetwork
   Descrizione . . . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Indirizzo fisico. . . . . . . . . . . : AC-22-0B-4D-B4-A0
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì

Scheda LAN wireless Local Area Connection* 2:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Indirizzo fisico. . . . . . . . . . . : 16-E9-84-8D-E4-9E
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì

Scheda Ethernet Ethernet 4:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : TAP-Windows Adapter V9
   Indirizzo fisico. . . . . . . . . . . : 00-FF-19-1A-47-1B
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì

Scheda Ethernet Ethernet 5:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : gogo6 Virtual Multi-Tunnel Adapter
   Indirizzo fisico. . . . . . . . . . . : 02-50-F2-00-00-01
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì

Scheda Tunnel IP6Tunnel:

   Suffisso DNS specifico per connessione: homenetwork
   Descrizione . . . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
   Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP abilitato. . . . . . . . . . . . : No
   Configurazione automatica abilitata   : Sì
   Indirizzo IPv6 . . . . . . . . . . . . . . . . . : 2001:470:25:64d::2(Preferenziale)
   Indirizzo IPv6 locale rispetto al collegamento . : fe80::5015:4fb:7a17:1d1%13(Preferenziale)
   Gateway predefinito . . . . . . . . . : 2001:470:25:64d::1
   IAID DHCPv6 . . . . . . . . . . . : 973078528
   DUID Client DHCPv6. . . . . . . . : 00-01-00-01-1F-AB-02-24-AC-22-0B-4D-B4-A0
   Server DNS . . . . . . . . . . . . .  : 2a00:6d40:60:6a7f::1
                                           94.177.171.127
   NetBIOS su TCP/IP . . . . . . . . . . : Disattivato

Scheda LAN wireless Wi-Fi:

   Suffisso DNS specifico per connessione: homenetwork
   Descrizione . . . . . . . . . . . . . : Qualcomm Atheros AR9287 Wireless Network Adapter
   Indirizzo fisico. . . . . . . . . . . : C4-E9-84-8D-E4-9E
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì
   Indirizzo IPv6 locale rispetto al collegamento . : fe80::c8ab:abb7:cf66:3fa2%19(Preferenziale)
   Indirizzo IPv4. . . . . . . . . . . . : 192.168.1.3(Preferenziale)
   Subnet mask . . . . . . . . . . . . . : 255.255.255.0
   Lease ottenuto. . . . . . . . . . . . : martedì 11 aprile 2017 18:01:15
   Scadenza lease . . . . . . . . . . .  : giovedì 13 aprile 2017 18:49:08
   Gateway predefinito . . . . . . . . . : 192.168.1.1
   Server DHCP . . . . . . . . . . . . . : 192.168.1.1
   IAID DHCPv6 . . . . . . . . . . . : 80013700
   DUID Client DHCPv6. . . . . . . . : 00-01-00-01-1F-AB-02-24-AC-22-0B-4D-B4-A0
   Server DNS . . . . . . . . . . . . .  : 2a00:6d40:60:6a7f::1
                                           94.177.171.127
   NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet Ethernet 2:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : Anchorfree HSS VPN Adapter
   Indirizzo fisico. . . . . . . . . . . : 00-FF-65-42-BD-DB
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì

Scheda Tunnel isatap.homenetwork:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione: homenetwork
   Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #5
   Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP abilitato. . . . . . . . . . . . : No
   Configurazione automatica abilitata   : Sì

Scheda Tunnel Local Area Connection* 13:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : Microsoft 6to4 Adapter
   Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP abilitato. . . . . . . . . . . . : No
   Configurazione automatica abilitata   : Sì

Scheda Tunnel Local Area Connection* 14:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
   Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP abilitato. . . . . . . . . . . . : No
   Configurazione automatica abilitata   : Sì

Commands:
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel localaddress=192.168.1.3 remoteaddress=216.66.80.98
netsh interface ipv6 add address interface=IP6Tunnel address=2001:470:25:64d::2
netsh interface ipv6 add route prefix=::/0 interface=IP6Tunnel nexthop=2001:470:25:64d::1

my router have a NAT section, i need to modify some options? https://gyazo.com/6025fd6a592d25d169de825c2224b5bf
PS. my static local address is 192.168.1.3 and my SO is win 10 64 bit!
I also try to forward the port 41 to my pc from roter but the tunnel didnt work :(
Thx for the help
Title: Re: Windows 10
Post by: edoardocolombo99 on April 12, 2017, 11:37:43 AM
Idk if my isp block port 41... but i think no, the only port that they restrict is 25 https://gyazo.com/3a727a64a8f517eb1942501e8da563c7
Title: Re: Windows 10
Post by: cholzhauer on April 12, 2017, 12:05:11 PM
Couple things

First, keep in mind that protocol 41 != port 41

Second, I would ask your ISP straight up if they block protocol41  (protocol, not port)
Title: Re: Windows 10
Post by: edoardocolombo99 on April 13, 2017, 10:13:02 AM
My isp is not blocking NAT, i just called. i try to add my PC local address to DMZ and now i can ping ipv6 addreses but i cant open any ipv6 site from any browser ( i try with google chrome, chrome canary firefix and firefox Developer edition)
https://gyazo.com/60f61c6b4cbb5d16f76dae505ac609e6
https://gyazo.com/789d7d1d3a015545856bed8430f24b45

:(((((((((((
Title: Re: Windows 10
Post by: cholzhauer on April 13, 2017, 10:24:40 AM
Not NAT, protocol41

Ping works but web doesn't?  Check your MTU
Title: Re: Windows 10
Post by: edoardocolombo99 on April 14, 2017, 02:17:06 AM
Quote from: cholzhauer on April 13, 2017, 10:24:40 AM
Not NAT, protocol41

Ping works but web doesn't?  Check your MTU

MTU value is 1492: https://gyazo.com/80876765bc446a178de57b58da6cb2dd
Yes, i cant open websites but ping works
Title: Re: Windows 10
Post by: cholzhauer on April 14, 2017, 05:09:17 AM
Again, check your MTU value, it could be less than 1492
Title: Re: Windows 10
Post by: edoardocolombo99 on April 14, 2017, 10:32:26 AM
Quote from: cholzhauer on April 14, 2017, 05:09:17 AM
Again, check your MTU value, it could be less than 1492

i run the test: https://gyazo.com/d929dac7e8414ff9688596ed57b09cd1
Title: Re: Windows 10
Post by: edoardocolombo99 on April 14, 2017, 10:42:57 AM
Quote from: cholzhauer on April 14, 2017, 05:09:17 AM
Again, check your MTU value, it could be less than 1492

Now its 1492 https://gyazo.com/0faaf22036d87400f6b34b2365c9f964
But i cant visit any ipv6 site https://gyazo.com/e41a6f1254f24329a832db420f3e842b


No ipv6 for me :( :O
Title: Re: Windows 10
Post by: xiecong520 on April 16, 2017, 11:43:50 PM
netsh interface ipv6 add dnsservers "Wi-Fi" 2001:470:20::2 index=1

Try the above command, such as not not. Please try the following command

netsh interface isatap set state disabled
netsh interface 6to4 set state disabled
netsh interface teredo set state disabled
netsh interface ipv6 delete interface "IP6Tunnel*"
route -f
netsh interface ipv6 reset

After input the above command, restart the computer.

netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel localaddress=192.168.1.3 remoteaddress=216.66.80.98
netsh interface ipv6 add address interface=IP6Tunnel address=2001:470:25:64d::2
netsh interface ipv6 add route prefix=::/0 interface=IP6Tunnel nexthop=2001:470:25:64d::1


Once again, restart the computer.  OK
Title: Re: Windows 10
Post by: edoardocolombo99 on April 18, 2017, 10:05:45 AM
Thanks for the reply, but still not working :(

https://gyazo.com/33c7c0921497d62000de3427d806f447
Title: Re: Windows 10
Post by: xiecong520 on May 06, 2017, 01:31:08 AM
ipconfig /flushdns
netsh int ipv6 delete neighbors
netsh int ipv6 delete destinationcache
netsh int ipv4 delete neighbors
netsh int ipv4 delete destinationcache
netsh int ipv6 reset
netsh int ipv4 reset
netsh winsock reset

restart the computer

ipconfig /registerdns
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel localaddress=192.168.1.3 remoteaddress=216.66.80.98
netsh interface ipv6 add address interface=IP6Tunnel address=2001:470:25:64d::2
netsh interface ipv6 add route prefix=::/0 interface=IP6Tunnel nexthop=2001:470:25:64d::1
netsh interface ipv6 add dnsservers "Wi-Fi" 2001:4860:4860::8888  index=1
netsh interface ipv6 delete route ::/0 ""Wi-Fi"" fe80::1

If you can't. 
  ping 216.66.80.98   or    tracert -d 216.66.80.98
  ping -6 2001:470:25:64d::1    or   tracert -d 2001:470:25:64d::1
  [ing -6 2001:4860:4860::8888    or    tracert -d 2001:4860:4860::8888
Look at the problem in where