Hurricane Electric's IPv6 Tunnel Broker Forums
General IPv6 Topics => IPv6 on Windows => Topic started by: ilpappa on February 11, 2018, 11:57:42 AM
-
Hi guys,
I'm sorry to bother you, but i am facing some difficulties getting my IPV6 working here in Italy. In Italy the only ISP who provides a kind of ipv6 is FASTWEB. FASTWEB does not provide native ipv6, but offers a 6rd tunnel (IPV6 6RD prefix
2001:b07:d448:f3b6::/64). The problem here is that, even after getting an IPV6 address, i cant reach or ping any ipv6 site. Here are my details:
C:\Users\miche>ipconfig /all
Configurazione IP di Windows
Nome host . . . . . . . . . . . . . . : Lenovo-ideapad500S
Suffisso DNS primario . . . . . . . . :
Tipo nodo . . . . . . . . . . . . . . : Ibrido
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No
Scheda Ethernet Ethernet:
Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Indirizzo fisico. . . . . . . . . . . : 1C-39-47-38-74-5C
DHCP abilitato. . . . . . . . . . . . : Sė
Configurazione automatica abilitata : Sė
Scheda LAN wireless Connessione alla rete locale (LAN)* 2:
Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Indirizzo fisico. . . . . . . . . . . : 32-52-CB-75-67-6D
DHCP abilitato. . . . . . . . . . . . : Sė
Configurazione automatica abilitata : Sė
Scheda LAN wireless Wi-Fi:
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Qualcomm Atheros QCA9377 Wireless Network Adapter
Indirizzo fisico. . . . . . . . . . . : 30-52-CB-75-67-6D
DHCP abilitato. . . . . . . . . . . . : Sė
Configurazione automatica abilitata : Sė
Indirizzo IPv6 . . . . . . . . . . . . . . . . . : 2001:b07:d448:f3b6:9195:f971:c637:ec2d(Preferenziale)
Indirizzo IPv6 locale rispetto al collegamento . : fe80::9195:f971:c637:ec2d%9(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.1.115(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Lease ottenuto. . . . . . . . . . . . : domenica 11 febbraio 2018 19:10:15
Scadenza lease . . . . . . . . . . . : lunedė 12 febbraio 2018 20:23:00
Gateway predefinito . . . . . . . . . : fe80::ead1:1bff:fe86:6939%9
192.168.1.1
Server DHCP . . . . . . . . . . . . . : 192.168.1.1
IAID DHCPv6 . . . . . . . . . . . : 120607435
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-1E-0B-F4-74-1C-39-47-38-74-5C
Server DNS . . . . . . . . . . . . . : 2001:4860:4860::8888
2001:4860:4860::8844
8.8.8.8
8.8.4.4
Server WINS primario . . . . . . . . : 192.168.1.1
NetBIOS su TCP/IP . . . . . . . . . . : Attivato
My bet would be that having a FE80 gateway does not allow me to reach the outside world. So i tried setting a manual ipv6 and putting the above mentioned ipv6 prefix (2001:b07:d448:f3b6::/64) as my gateway, but still no luck:
Scheda LAN wireless Wi-Fi:
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Qualcomm Atheros QCA9377 Wireless Network Adapter
Indirizzo fisico. . . . . . . . . . . : 30-52-CB-75-67-6D
DHCP abilitato. . . . . . . . . . . . : Sė
Configurazione automatica abilitata : Sė
Indirizzo IPv6 . . . . . . . . . . . . . . . . . : 2001:b07:d448:f3b6:9195:f971:c637:ec2d(Preferenziale)
Indirizzo IPv6 locale rispetto al collegamento . : fe80::9195:f971:c637:ec2d%9(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.1.115(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Lease ottenuto. . . . . . . . . . . . : domenica 11 febbraio 2018 19:10:15
Scadenza lease . . . . . . . . . . . : lunedė 12 febbraio 2018 20:23:00
Gateway predefinito . . . . . . . . . : fe80::ead1:1bff:fe86:6939%9
2001:b07:d448:f3b6::1
192.168.1.1
Server DHCP . . . . . . . . . . . . . : 192.168.1.1
IAID DHCPv6 . . . . . . . . . . . : 120607435
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-1E-0B-F4-74-1C-39-47-38-74-5C
Server DNS . . . . . . . . . . . . . : 2001:4860:4860::8888
2001:4860:4860::8844
8.8.8.8
8.8.4.4
Server WINS primario . . . . . . . . : 192.168.1.1
NetBIOS su TCP/IP . . . . . . . . . . : Attivato
C:\Users\miche>ping ipv6.google.com
Esecuzione di Ping ipv6.l.google.com [2a00:1450:4002:808::200e] con 32 byte di dati:
Rete di destinazione non raggiungibile.
Rete di destinazione non raggiungibile.
Rete di destinazione non raggiungibile.
Rete di destinazione non raggiungibile.
Statistiche Ping per 2a00:1450:4002:808::200e:
Pacchetti: Trasmessi = 4, Ricevuti = 0,
Persi = 4 (100% persi),
I deactivated all MS ipv6 privacy settings, but nothing changed. Could you please help me?
Thanks a lot,
Michele
-
The FE80 address is expected; it should be the local address of your gateway. How are you handing out addresses? SLACC? DHCPv6?
-
DHCPv6 with mac addresses filtered. Tried also with no mac address filtering.
-
Are you able to ping the gateway? Can you get on the gateway and try to ping external?
-
I couldn't ping the gateway:
C:\Users\miche>ping fe80::ead1:1bff:fe86:6939%9
Esecuzione di Ping fe80::ead1:1bff:fe86:6939%9 con 32 byte di dati:
Host di destinazione non raggiungibile.
Host di destinazione non raggiungibile.
Host di destinazione non raggiungibile.
Host di destinazione non raggiungibile.
Statistiche Ping per fe80::ead1:1bff:fe86:6939%9:
Pacchetti: Trasmessi = 4, Ricevuti = 0,
Persi = 4 (100% persi),
But if I remove the % sign the ping works:
C:\Users\miche>ping fe80::ead1:1bff:fe86:6939
Esecuzione di Ping fe80::ead1:1bff:fe86:6939 con 32 byte di dati:
Risposta da fe80::ead1:1bff:fe86:6939: durata=2ms
Risposta da fe80::ead1:1bff:fe86:6939: durata=2ms
Risposta da fe80::ead1:1bff:fe86:6939: durata=1ms
Risposta da fe80::ead1:1bff:fe86:6939: durata=5ms
Statistiche Ping per fe80::ead1:1bff:fe86:6939:
Pacchetti: Trasmessi = 4, Ricevuti = 4,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 1ms, Massimo = 5ms, Medio = 2ms
I am not able to reach the gateway. I really don't know what to do. I just found a workaround creating a tunnel, but I think that is not the right way to fix the situation as my Ipv6 has to work normally. Here is what i did to fix the problem:
1) covert IPv4 (public) to IPv6 from https://www.ipaddressguide.com/ipv4-to-ipv6
2) create tunnel address starting from 2001:b07 (ISP prefix) and adding the previous conversion with ::1 at the end
3) cmd with admin rights
4) following commandsi:
netsh
interface
ipv6
add v6v4tunnel interface= private localaddress= 192.168.1.115 remoteaddress= 81.208.50.214
add address interface= private address= 2001:b07......::1
add route ::/0 private
I really think that this tunnel is a big resource consuming one.
Any other idea?
Thanks a lot,
Michele
-
You need the % because that identifies the interface.
Why are you converting the IPv4 to IPv6?
If you're not able to reach the gateway, I think you've found your issue
-
How can i fix that and reach the gateway? Thanks
-
What addresses ranges do you have?
-
external static ip: 93.42.79.X
internal lan 192.168.1.100-149 but they are outside dhcp range and assigned by mac address; dhcp range is 200-249
-
Is this an IPv4 forum or IPv6 forum?
8)