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

BGP Feed - Facebook v6 doesnt work without default route

Started by TristramCheer, December 06, 2010, 09:11:55 PM

Previous topic - Next topic


Hi All,

Been scratching my head a little, We have a BGP feed from HE.net for v6 and we've been having trouble access www.v6.facebook.com which we resolve as 2620:0:1cfe:face:b00c::3 but we dont see this in any of the bgp routes. When we add a default route to HE.net it works.

We aren't filtering any incoming routes from HE.net, Does FB announce the routes?


Facebook does announce a /40 range.

It looks like that HE has a peering with Facebook.
I got their prefix 2620:0:1cfe::/40 via HE BGP feed.

But beside that the V6 website is also not reachable from here.
After "facebook.gige-g5-9.core1.sjc2.he.net (2001:470:0:14a::2)" we get only timeouts on a traceroute.


Traceroutes may not work since they're using LISP, AFAIK.  Although I have to admit I don't know a lot about it, having only skimmed some docs on it.  But it didn't seem like something a traceroute would work through.


I'm also experiencing this. Was working earlier sometime in the last week or two but not anymore today. I can ping www.v6.facebook.com but traceroute6 gets as far as:
Quotetraceroute to www.v6.facebook.com (2620:0:1cfe:face:b00c::3), 30 hops max, 80 byte packets
1  ---.tunnel.tserv13.ash1.ipv6.he.net (2001:470:7:---::1)  71.745 ms  78.757 ms  77.020 ms
gige-g4-12.core1.ash1.he.net (2001:470:0:90::1)  79.587 ms  79.510 ms  80.419 ms
10gigabitethernet1-2.core1.atl1.he.net (2001:470:0:1b5::2)  99.962 ms  100.836 ms  100.759 ms
10gigabitethernet3-2.core1.dal1.he.net (2001:470:0:1b6::1)  119.959 ms  122.266 ms  123.169 ms
10gigabitethernet1-2.core1.phx1.he.net (2001:470:0:15a::1)  132.818 ms  134.168 ms  135.005 ms
10gigabitethernet2-2.core1.lax1.he.net (2001:470:0:159::1)  144.328 ms  137.409 ms  136.037 ms
10gigabitethernet2-2.core1.fmt2.he.net (2001:470:0:18d::1)  153.279 ms  154.200 ms  154.124 ms
10gigabitethernet1-1.core1.sjc2.he.net (2001:470:0:31::2)  155.440 ms  160.570 ms  161.486 ms
facebook.gige-g5-9.core1.sjc2.he.net (2001:470:0:14a::2)  150.806 ms  151.680 ms  149.236 ms
10  * * *

I'm using the Anycasted IPv6 Caching Nameserver of 2001:470:20::2 & my ISPs IPv4 DNS servers. Should I also try using the Anycasted IPv4 Caching Nameserver listed in my tunnel details instead or along with the other ones?


traceroute6 www.v6.facebook.com -T -p 80 -f3
traceroute to www.v6.facebook.com (2620:0:1cfe:face:b00c::3), 30 hops max, 80 byte packets
gige-g2-20.core1.ams1.he.net (2001:470:0:7d::1)  140.759 ms  140.698 ms  140.890 ms
10gigabitethernet1-4.core1.lon1.he.net (2001:470:0:3f::1)  141.355 ms  141.331 ms  141.303 ms
10gigabitethernet7-4.core1.nyc4.he.net (2001:470:0:3e::1)  217.966 ms  217.951 ms  217.922 ms
10gigabitethernet5-3.core1.lax1.he.net (2001:470:0:10e::1)  273.302 ms  273.531 ms  270.229 ms
10gigabitethernet2-2.core1.fmt2.he.net (2001:470:0:18d::1)  288.433 ms  288.654 ms  288.630 ms
10gigabitethernet1-1.core1.sjc2.he.net (2001:470:0:31::2)  278.824 ms  278.910 ms  278.811 ms
facebook.gige-g5-9.core1.sjc2.he.net (2001:470:0:14a::2)  278.741 ms  278.987 ms  278.885 ms
10  www.v6.facebook.com (2620:0:1cfe:face:b00c::3)  279.544 ms  279.458 ms  279.335 ms