• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

Can connect to many sites, but not tunnelbroker.net

Started by blackbear, May 28, 2010, 07:44:25 PM

Previous topic - Next topic

blackbear

I've set up my tunnel via my DLINK-615, and it works fine.  Except that some sites don't work, most annoyingly tunnelbroker.net. 

Here's my router setup:
IPv6 Connection Type :     IPv6 in IPv4 Tunnel
Network Status :     connect
WAN IPv6 Address :     2001:470:1f06:c59::2/64
IPv6 Default Gateway :     2001:470:1f06:c59::1
LAN IPv6 Address :     2001:470:1f07:c59::1/64
LAN IPv6 Link-Local Address :     fe80::222:b0ff:feb2:e822/64
Primary DNS Address :     2001:470:20::2
Seccondary DNS Address :     none

Here's my Mac Pro setup:

en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
   ether 00:1f:5b:3c:bf:d5
   inet 10.0.2.1 netmask 0xff000000 broadcast 10.255.255.255
   inet6 fe80::21f:5bff:fe3c:bfd5%en1 prefixlen 64 scopeid 0x5
   inet6 2001:470:1f07:c59::10 prefixlen 64
   media: autoselect (100baseTX <full-duplex,flow-control>)
   status: active

I can route to ipv6.google.com just fine:
traceroute6: Warning: ipv6.l.google.com has multiple addresses; using 2001:4860:800f::67
traceroute6 to ipv6.l.google.com (2001:4860:800f::67) from 2001:470:1f07:c59::10, 64 hops max, 12 byte packets
1  2001:470:1f07:c59::1  0.318 ms  0.445 ms  0.237 ms
2  blackbear-1.tunnel.tserv4.nyc4.ipv6.he.net  24.976 ms  24.412 ms  25.209 ms
3  gige-g3-8.core1.nyc4.ipv6.he.net  22.474 ms  21.640 ms  22.481 ms
4  core1-0-0-8.lga.net.google.com  22.470 ms  22.984 ms  27.215 ms
5  2001:4860::1:0:3be  22.715 ms  22.994 ms  22.449 ms
6  2001:4860::1:0:9ff  29.952 ms  30.501 ms  27.452 ms
7  2001:4860:0:1::149  39.967 ms
    2001:4860:0:1::14b  33.059 ms
    2001:4860:0:1::149  30.493 ms
8  iad04s01-in-x67.1e100.net  29.219 ms  30.514 ms  27.450 ms

But trying to connect to tunnelbroker.net fails

traceroute6 to tunnelbroker.net (2001:470:0:63::2) from 2001:470:1f07:c59::10, 64 hops max, 12 byte packets
1  2001:470:1f07:c59::1  0.395 ms  0.398 ms  0.475 ms
2  blackbear-1.tunnel.tserv4.nyc4.ipv6.he.net  25.171 ms  24.512 ms  24.946 ms
3  gige-g3-8.core1.nyc4.ipv6.he.net  22.501 ms  21.758 ms  22.473 ms
4  10gigabitethernet5-3.core1.lax1.he.net  82.446 ms  81.761 ms  92.687 ms
5  10gigabitethernet1-3.core1.pao1.ipv6.he.net  97.667 ms  98.885 ms  99.957 ms
6  10gigabitethernet1-2.core1.fmt1.ipv6.he.net  92.424 ms  96.915 ms  102.421 ms
7  * * *

Any ideas what's wrong?
James

jimb

Is it just traceroutes failing, or ping, web browser, etc?  If the latter, most likely it's a prob on the HE side.  Email the ipv6@he.net addy.