First, I'm limited to using a teredo tunnel due to our corporate (nearly broken) LAN. I use a 6to4 tunnel at home, but I see teredo routes through he.net anyways so I thought here is the right place to post.
C:\>tracert6 he.net
Tracing route to he.net [2001:470:0:76::2]
from 2001:0:4137:9e76:0:fab7:27fd:dd61 over a maximum of 30 hops:
1 58 ms 29 ms 14 ms 6to4.fmt2.he.net [2001:470:0:108::2]
2 30 ms 13 ms 40 ms gige-g5-20.core1.fmt2.he.net [2001:470:0:108::1]
3 21 ms 35 ms 25 ms gige-g4-18.core1.fmt1.he.net [2001:470:0:2d::1]
4 13 ms 22 ms 83 ms he.net [2001:470:0:76::2]
Trace complete.
Ok, no problem there..
C:\>tracert6 www.v6.facebook.com
Tracing route to www.v6.facebook.com [2620:0:1cfe:face:b00c::3]
from 2001:0:4137:9e76:0:fab7:27fd:dd61 over a maximum of 30 hops:
1 2001:470:0:1e1::2 reports: No route to destination.
Trace complete.
C:\tracert6 ipv6.google.com
Tracing route to ipv6.l.google.com [2001:4860:4001:803::1012]
from 2001:0:4137:9e76:0:fab7:27fd:dd61 over a maximum of 30 hops:
1 2001:470:0:1e1::2 reports: No route to destination.
Trace complete.
I recognize 2001:470:0:* as being under he.net, so what's the problem? I can ping the tunnel side of my home machine, too.
C:\>tracert6 davygrvy-1.tunnel.tserv3.fmt2.ipv6.he.net
Tracing route to davygrvy-1.tunnel.tserv3.fmt2.ipv6.he.net [2001:470:1f04:ed::1]
from 2001:0:4137:9e76:0:fab7:27fd:dd61 over a maximum of 30 hops:
1 71 ms 18 ms 16 ms 6to4.fmt2.he.net [2001:470:0:108::2]
2 13 ms 11 ms 21 ms gige-g5-20.core1.fmt2.he.net [2001:470:0:108:
:1]
3 14 ms 12 ms 26 ms davygrvy-1.tunnel.tserv3.fmt2.ipv6.he.net [20
01:470:1f04:ed::1]
Trace complete.
Here's my 'ipconfig /all' and 'netsh interface ipv6 show teredo'
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : PRODUCTMG
Primary Dns Suffix . . . . . . . : Nady.lan
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Nady.lan
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-13-20-02-09-A7
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.139
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::213:20ff:fe02:9a7%5
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.20
DNS Servers . . . . . . . . . . . : 192.168.1.20
192.168.1.1
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Primary WINS Server . . . . . . . : 192.168.1.20
Secondary WINS Server . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Wednesday, May 25, 2011 12:50:40 AM
Lease Expires . . . . . . . . . . : Thursday, May 26, 2011 12:50:40 AM
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-FA-B7-27-FD-DD-61
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 2001:0:4137:9e76:0:fab7:27fd:dd61
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%4
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : C0-A8-01-8B
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.139%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled
C:\>netsh interface ipv6 show teredo
Teredo Parameters
---------------------------------------------
Type : enterpriseclient
Server Name : teredo.ipv6.microsoft.com
Client Refresh Interval : default
Client Port : default
State : qualified
Type : teredo client
Network : managed
NAT : restricted
??? ???
Well, this is interesting.. I can't ping my computer at work.
davygrvy@bigmoma:~$ ping6 2001:0:4137:9e76:0:fab7:27fd:dd61
PING 2001:0:4137:9e76:0:fab7:27fd:dd61(2001:0:4137:9e76:0:fab7:27fd:dd61) 56 data bytes
From 2001:470:0:108::2 icmp_seq=11 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=13 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=14 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=20 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=22 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=23 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=24 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=25 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=27 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=28 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=29 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=30 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=31 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=32 Destination unreachable: Address unreachable
^C
--- 2001:0:4137:9e76:0:fab7:27fd:dd61 ping statistics ---
32 packets transmitted, 0 received, +14 errors, 100% packet loss, time 31081ms
davygrvy@bigmoma:~$
Quote from: davygrvy on May 25, 2011, 07:38:00 PM
Well, this is interesting.. I can't ping my computer at work.
davygrvy@bigmoma:~$ ping6 2001:0:4137:9e76:0:fab7:27fd:dd61
PING 2001:0:4137:9e76:0:fab7:27fd:dd61(2001:0:4137:9e76:0:fab7:27fd:dd61) 56 data bytes
From 2001:470:0:108::2 icmp_seq=11 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=13 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=14 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=20 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=22 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=23 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=24 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=25 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=27 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=28 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=29 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=30 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=31 Destination unreachable: Address unreachable
From 2001:470:0:108::2 icmp_seq=32 Destination unreachable: Address unreachable
^C
--- 2001:0:4137:9e76:0:fab7:27fd:dd61 ping statistics ---
32 packets transmitted, 0 received, +14 errors, 100% packet loss, time 31081ms
davygrvy@bigmoma:~$
Neither can I
[carl@mars ~]$ ping6 2001:0:4137:9e76:0:fab7:27fd:dd61
PING6(56=40+8+8 bytes) 2001:470:c27d:e000:20c:29ff:fe8a:1618 --> 2001:0:4137:9e76:0:fab7:27fd:dd61
^C
--- 2001:0:4137:9e76:0:fab7:27fd:dd61 ping6 statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
where's it die? show a trace.
I can ping you, though.
C:\>ping6 2001:470:c27d:e000:20c:29ff:fe8a:1618
Pinging 2001:470:c27d:e000:20c:29ff:fe8a:1618
from 2001:0:4137:9e76:0:f22f:27fd:dd61 with 32 bytes of data:
Reply from 2001:470:c27d:e000:20c:29ff:fe8a:1618: bytes=32 time=313ms
Reply from 2001:470:c27d:e000:20c:29ff:fe8a:1618: bytes=32 time=88ms
Reply from 2001:470:c27d:e000:20c:29ff:fe8a:1618: bytes=32 time=83ms
Ping statistics for 2001:470:c27d:e000:20c:29ff:fe8a:1618:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 313ms, Average = 161ms
Here's my trace trying to get out from the troubled work computer:
C:\>tracert6 he.net
Tracing route to he.net [2001:470:0:76::2]
from 2001:0:4137:9e76:0:f22f:27fd:dd61 over a maximum of 30 hops:
1 92 ms 19 ms 16 ms 6to4.fmt2.he.net [2001:470:0:108::2]
2 35 ms 25 ms 48 ms gige-g5-20.core1.fmt2.he.net [2001:470:0:108::1]
3 34 ms 38 ms 32 ms gige-g4-18.core1.fmt1.he.net [2001:470:0:2d::1]
4 21 ms 28 ms 17 ms he.net [2001:470:0:76::2]
Trace complete.
It sees he.net fine, but not the world.
C:\>tracert6 www.v6.facebook.com
Tracing route to www.v6.facebook.com [2620:0:1cfe:face:b00c::3]
from 2001:0:4137:9e76:0:f22f:27fd:dd61 over a maximum of 30 hops:
1 2001:470:0:1e1::2 reports: No route to destination.
Trace complete.
Is 2001:470:0:1e1::2 having problems?
Totally bizarre! ??? Only some sites are routeable through 2001:470:0:1e1::2
C:\>ping6 ipv6.net
Pinging ipv6.net [2a00:1188:5:2::8]
from 2001:0:4137:9e76:0:f22f:27fd:dd61 with 32 bytes of data:
Reply from 2a00:1188:5:2::8: bytes=32 time=603ms
Reply from 2a00:1188:5:2::8: bytes=32 time=227ms
Reply from 2a00:1188:5:2::8: bytes=32 time=232ms
Reply from 2a00:1188:5:2::8: bytes=32 time=215ms
Ping statistics for 2a00:1188:5:2::8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 215ms, Maximum = 603ms, Average = 319ms
*bump*
Anyone know what's broken? It's been broken going on 4 weeks now.
Happy World IPv6 day, everyone.