dear readers
I wanted to know how to configure the ipv6 tunnel with windows 7 32 bit
my configuration is this
open ms dos administrator:
set state disabled netsh interface teredo
netsh interface ipv6 add v6v4tunnel IP6Tunnel 184 104 229 221 216.66.80.30
netsh interface ipv6 add address 2001:470:1 IP6Tunnel f0a: 1A00:: 2
netsh interface ipv6 add route:: / 0 IP6Tunnel f0a 2001:470:1: 1A00:: 1
I set up the tunnel as an illustration with windows 7 but then it does not work
these are my tunnel data
IPv6 Tunnel Endpoints
Server IPv4 address: 216.66.80.30
Server IPv6 address: 2001:470:1 f0a: 1A00:: 1 / 64
Client IPv4 address: 184104229221
Client IPv6 address: 2001:470:1 f0a: 1A00:: 2 / 64
Available DNS Resolvers
Anycasted IPv6 Caching Nameserver: 2001:470:20:: 2
Anycasted caching nameserver IPv4: 74.82.42.42
can someone help me thanks
perhaps we are missing some command
Ascolta
Trascrizione fonetica
Dizionario - Visualizza dizionario dettagliato
are you behind a nat? If so, you need to substitute that address for your public ip. is your firewall passing protocol 41?
BastardOperHell
I want you to post the contents of a file I would have you create. Please enter the following commands.
ipconfig /all > ipv6log.txt
netsh interface ipv6 show interface IP6Tunnel >> ipv6log.txt
This should help determine what is wrong.
I see this is your configuration:
QuoteI set up the tunnel as an illustration with windows 7 but then it does not work
these are my tunnel data
IPv6 Tunnel Endpoints
Server IPv4 address: 216.66.80.30
Server IPv6 address: 2001:470:1 f0a: 1A00:: 1 / 64
Client IPv4 address: 184104229221
Client IPv6 address: 2001:470:1 f0a: 1A00:: 2 / 64
You do have some strange "spaces" in this configuration...however looks like HE is also your v4 provider and
>ping 216.66.80.30
Pinging 216.66.80.30 with 32 bytes of data:
Reply from 216.66.80.30: bytes=32 time=74ms TTL=54
Ping statistics for 216.66.80.30:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 74ms, Average = 73ms
>ping 184.104.229.221
Pinging 184.104.229.221 with 32 bytes of data:
Reply from 184.104.229.221: bytes=32 time=72ms TTL=54
Ping statistics for 184.104.229.221:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 77ms, Average = 75ms
>ping 2001:470:1f0a:1A00::1
Pinging 2001:470:1f0a:1a00::1 from 2001:470:9313:0:3c54:b17b:2626:7bd3 with 32 bytes of data:
Reply from 2001:470:1f0a:1a00::1: time=78ms
Ping statistics for 2001:470:1f0a:1a00::1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 78ms, Average = 75ms
>ping 2001:470:1f0a:1A00::2
Pinging 2001:470:1f0a:1a00::2 from 2001:470:9313:0:3c54:b17b:2626:7bd3 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2001:470:1f0a:1a00::2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Your public ip both client and server addresses respond to ICMP v4
The HE end of your v6 tunnel responds to ICMP v6
Try recreating the tunnel without the extraneous spaces and ensure firewalling is permitting protocol 41
Regards
lukec