Hurricane Electric's IPv6 Tunnel Broker Forums

Tunnelbroker.net Specific Topics => Questions & Answers => Topic started by: scottnelson on June 01, 2008, 08:41:52 PM

Title: Problem with 209.51.161.14
Post by: scottnelson on June 01, 2008, 08:41:52 PM
Tunnel connected to 209.51.161.14 ( tserv4.nyc4.ipv6.he.net ) server.
I can ping the IPv4 address but can't ping the IPv6 address.
Rebuilt the tunnel but still no luck.

Server OK?

Scott
Title: Re: Problem with 209.51.161.14
Post by: broquea on June 02, 2008, 03:57:50 PM
Sorry for the delay, this should be resolved now. I can ping6 your side.
Title: Re: Problem with 209.51.161.14
Post by: scottnelson on June 02, 2008, 06:59:14 PM
Yep, looks good.

Thanks.  :-)

Scott
Title: Re: Problem with 209.51.161.14
Post by: bdonlan on June 05, 2008, 03:42:42 PM
There seem to be problems with this server again. I can ping6 the remote end:
PING 2001:470:1f06:61f::1(2001:470:1f06:61f::1) 56 data bytes
64 bytes from 2001:470:1f06:61f::1: icmp_seq=1 ttl=64 time=2.08 ms
64 bytes from 2001:470:1f06:61f::1: icmp_seq=2 ttl=64 time=2.17 ms
64 bytes from 2001:470:1f06:61f::1: icmp_seq=3 ttl=64 time=2.16 ms
64 bytes from 2001:470:1f06:61f::1: icmp_seq=4 ttl=64 time=2.03 ms

but I can't reach remote sites:
PING www.kame.net(orange.kame.net) 56 data bytes
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=1 Destination unreachable: No route
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=2 Destination unreachable: No route
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=3 Destination unreachable: No route
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=4 Destination unreachable: No route

PING ipv6.google.com(2001:4860:0:1001::68) 56 data bytes
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=1 Destination unreachable: No route
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=2 Destination unreachable: No route
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=3 Destination unreachable: No route
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=4 Destination unreachable: No route

My IPv4 address is 207.192.69.114
Title: Re: Problem with 209.51.161.14
Post by: broquea on June 05, 2008, 04:17:56 PM
We're looking at it right now. For faster responses, please email issues like this to ipv6@he.net

Quote from: bdonlan on June 05, 2008, 03:42:42 PM
There seem to be problems with this server again. I can ping6 the remote end:
PING 2001:470:1f06:61f::1(2001:470:1f06:61f::1) 56 data bytes
64 bytes from 2001:470:1f06:61f::1: icmp_seq=1 ttl=64 time=2.08 ms
64 bytes from 2001:470:1f06:61f::1: icmp_seq=2 ttl=64 time=2.17 ms
64 bytes from 2001:470:1f06:61f::1: icmp_seq=3 ttl=64 time=2.16 ms
64 bytes from 2001:470:1f06:61f::1: icmp_seq=4 ttl=64 time=2.03 ms

but I can't reach remote sites:
PING www.kame.net(orange.kame.net) 56 data bytes
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=1 Destination unreachable: No route
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=2 Destination unreachable: No route
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=3 Destination unreachable: No route
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=4 Destination unreachable: No route

PING ipv6.google.com(2001:4860:0:1001::68) 56 data bytes
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=1 Destination unreachable: No route
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=2 Destination unreachable: No route
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=3 Destination unreachable: No route
From bdonlan.tunnel.tserv4.nyc4.ipv6.he.net icmp_seq=4 Destination unreachable: No route

My IPv4 address is 207.192.69.114
Title: Re: Problem with 209.51.161.14
Post by: scott on June 05, 2008, 04:21:27 PM
Same problem with same server...  Server maintenance?

Thanks,
Scott
Title: Re: Problem with 209.51.161.14
Post by: scott on June 05, 2008, 04:33:46 PM
Back!  ;D

Thanks,
Scott