Hi.
I'm having problems with my tunnel. I created it usingnetsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel 192.168.1.2 216.66.84.46
netsh interface ipv6 add address interface=IP6Tunnel 2001:470:1f14:1a6e::2
netsh interface ipv6 add route ::/0 interface=IP6Tunnel 2001:470:1f14:1a6e::1
and it appears it is upC:\Users\Radu>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Radu-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros L1 Gigabit Ethernet 10/100/1000Base-T Controller
Physical Address. . . . . . . . . : 00-1E-8C-26-C9-97
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR5005GS Wireless Network Adapter
Physical Address. . . . . . . . . : 00-18-E7-1B-9D-07
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1cc5:9ba8:2f3b:a51b%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 11 iunie 2011 17:02:47
Lease Expires . . . . . . . . . . : 12 iunie 2011 19:15:19
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 184555751
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-51-27-34-00-1E-8C-26-C9-97
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{4992B96F-CF66-40B6-9D38-A237723A4246}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter IP6Tunnel:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:470:1f14:1a6e::2(Preferred)
Link-local IPv6 Address . . . . . : fe80::9049:e0ae:8f4f:f501%19(Preferred)
Default Gateway . . . . . . . . . : 2001:470:1f14:1a6e::1
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Disabled
C:\Users\Radu>route print
===========================================================================
Interface List
12...00 1e 8c 26 c9 97 ......Atheros L1 Gigabit Ethernet 10/100/1000Base-T Controller
11...00 18 e7 1b 9d 07 ......Atheros AR5005GS Wireless Network Adapter
1...........................Software Loopback Interface 1
18...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
19...00 00 00 00 00 00 00 e0 Microsoft Direct Point-to-point Adapater
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.2 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.1.0 255.255.255.0 On-link 192.168.1.2 281
192.168.1.2 255.255.255.255 On-link 192.168.1.2 281
192.168.1.255 255.255.255.255 On-link 192.168.1.2 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.2 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.2 281
===========================================================================
Persistent Routes:
None
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
19 286 ::/0 2001:470:1f14:1a6e::1
1 306 ::1/128 On-link
19 286 2001:470:1f14:1a6e::/64 On-link
19 286 2001:470:1f14:1a6e::2/128
On-link
19 286 fe80::/64 On-link
11 281 fe80::/64 On-link
11 281 fe80::1cc5:9ba8:2f3b:a51b/128
On-link
19 286 fe80::9049:e0ae:8f4f:f501/128
On-link
1 306 ff00::/8 On-link
19 286 ff00::/8 On-link
11 281 ff00::/8 On-link
===========================================================================
Persistent Routes:
If Metric Network Destination Gateway
0 4294967295 ::/0 2001:470:1f14:1a6e::1
===========================================================================
C:\Users\Radu>
But if I ping the gateway, it failsC:\Users\Radu>ping -6 2001:470:1f14:1a6e::1
Pinging 2001:470:1f14:1a6e::1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2001:470:1f14:1a6e::1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Radu>
Can anyone provide any suggestions?
OS: Windows 7 64bit (Version 6.1 - Build 7601: Service Pack 1)
Behind Router: Yes
DMZ: No, but I tried with it activated and it's the same.
Thank you in advance.
Tunnel isn't up if you can't ping the ::1 gateway ;)
You have NAT, so I suspect it's a protocol41 issue. You said you put your host in the DMZ, but this still doesn't work on some routers...what router are you using?
Huawei EchoLife HG520b
DMZ works for opened ports, and I don't see why it would care if ip.proto == 41 and not 6 or 17...
Meanwhile I tried with a FreeBSD virtual pc setup as dmz, with my windows tunnel config... and still nothing.
Also Wireshark shows some packets "289918 273.170729 2001:470:1f14:1a6e::2 2001:470:0:63::2 TCP 12720 > http [SYN] Seq=0 Win=8192 Len=0 MSS=1220 WS=8 SACK_PERM=1" that seem to be exchanged or at least sent.
Keep in mind that protocol != port
I assume that packet is headed out...do you see any packets coming back in?
The way to test this is to put your host in front of your firewall and try the tunnel again.
Sorry I did not mean that port = protocol, I meant that DMZ works as far as ports are concerned.
As for putting the computer in front of the firewall I don't know any other way besides DMZ. And the router is an ADSL modem, so I can't connect the computer directly. :(
Regarding the packet trace, I ran it for 10 mins and I did not notice any incoming packets or replies.