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

Cannot ping from Dlink 636L

Started by btarantina, June 23, 2015, 10:51:22 AM

Previous topic - Next topic


Hello everybody!

I have AT&T U-Verse and a DLink 636L router. I've placed the DLink into DMZ-plus mode on the U-Verse gateway and it is listed as being wide open. I set up my tunnel config on my dlink and even followed this tutorial: http://srijit.com/how-to-configure-ipv6-connectivity-with-tunnel-broker-service-on-dlink-dir-615-router/

My windows machine is getting an IPv6 address and when I try to ping ipv6.google.com, it finds the address from DNS but cannot ping. I also cannot ping the Google IPv6 DNS from my router directly. When I try to go to test-ipv6.com it only recognizes that I have an IPv4 address.

What am I missing?


U-verse released updated firmwares a year or so ago which wound up breaking 6in4 tunnels.  That said, in theory, they've deployed and enabled 6rd to many of their locations, so you might actually have v6 direct from AT&T available at this time.  Settings / LAN / IPv6 would be the place to check.


I've called UVerse and they confirmed that I have the latest firmware... that said, I don't have v6 on the AT&T gateway. Settings / LAN / IPv6 doesn't exist.


I have a PACE 5031 NV UVerse gateway if that makes a difference.



If I go to a third-party site: 4or6.com both the ping and the traceroute (both UDP and ICMP) show that the client tunnel endpoint (listed on my tunnelbroker specs) is unreachable:

#ping6 -c 3 2001:470:7:35c::2
PING 2001:470:7:35c::2(2001:470:7:35c::2) 56 data bytes
From 2001:470:0:8c::2 icmp_seq=1 Destination unreachable: Address unreachable
From 2001:470:0:8c::2 icmp_seq=2 Destination unreachable: Address unreachable
From 2001:470:0:8c::2 icmp_seq=3 Destination unreachable: Address unreachable

--- 2001:470:7:35c::2 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2003ms

#traceroute -6  -I 2001:470:7:35c::2
traceroute to 2001:470:7:35c::2 (2001:470:7:35c::2), 30 hops max, 80 byte packets
1  2607:f2f8:1600::1 (2607:f2f8:1600::1)  3.119 ms  3.091 ms  3.088 ms
2  2001:504:13::1a (2001:504:13::1a)  109.272 ms  109.278 ms  109.340 ms
10ge14-1.core1.den1.he.net (2001:470:0:15d::1)  29.988 ms  29.994 ms  29.993 ms
10ge5-5.core1.mci3.he.net (2001:470:0:240::2)  50.782 ms  51.187 ms  51.190 ms
10ge1-4.core1.ash1.he.net (2001:470:0:30b::1)  67.340 ms  67.345 ms  67.344 ms
tserv1.mia1.he.net (2001:470:0:8c::2)  72.895 ms  99.842 ms  99.843 ms
tserv1.mia1.he.net (2001:470:0:8c::2)  117.901 ms !H  108.974 ms !H  112.502 ms !H


I've tried 6to4 and 6in4 and 6rd... Uverse is blocking all IPv6 outgoing traffic. I'm going to wait a few months for my service contract to expire and then consider switching to a different provider.