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

Connection problems to facebook

Started by bjo, November 19, 2013, 08:07:41 AM

Previous topic - Next topic

bjo

Hi,

since several days using Facebook via IPv6 is no fun any more. The routing goes some strange ways: Tunnelserver in Frankfurt -> Amsterdam (HE -> Telia) -> Frankfurt (Telia -> Facebook). AFAIR the traffic went via HE to Washington before and then into the Facebook-network.

  1.|-- macoma.ipv6.nord-west.net  0.0%    10    0.6   0.7   0.5   1.0   0.0
  2.|-- bjo-1.tunnel.tserv6.fra1.  0.0%    10   39.3  40.1  38.9  42.6   0.9
  3.|-- v320.core1.fra1.he.net     0.0%    10   38.4  40.7  33.7  66.8   9.9
  4.|-- 10gigabitethernet10-7.cor  0.0%    10   50.8  46.7  41.1  52.5   4.2
  5.|-- 2001:7f8:1::a500:9121:1   60.0%    10  6721. 7045. 6721. 7313. 295.4
  6.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
  7.|-- win-b4-link.telia.net      0.0%    10   87.3  87.8  87.3  88.9   0.0
  8.|-- ffm-b12-v6.telia.net       0.0%    10   82.0  85.5  81.9  99.5   5.6
  9.|-- facebook-ic-155645-ffm-b1  0.0%    10   82.3  84.3  81.6 100.6   5.7
10.|-- ae2.bb02.fra2.tfbnw.net    0.0%    10   82.3  83.9  81.7  90.1   2.8
11.|-- ae8.bb01.cdg1.tfbnw.net    0.0%    10   91.5  94.7  91.5 102.3   3.7
12.|-- ae6.bb01.lga1.tfbnw.net    0.0%    10  162.9 165.7 162.4 183.8   6.6
13.|-- ae9.bb02.iad1.tfbnw.net    0.0%    10  169.1 171.5 169.0 179.4   3.1
14.|-- ae8.bb04.frc1.tfbnw.net    0.0%    10  184.9 190.6 184.7 209.1   8.0
15.|-- ae4.dr03.frc1.tfbnw.net    0.0%    10  183.4 182.8 180.0 186.2   2.3
16.|-- po1020.csw13d.frc1.tfbnw. 10.0%    10  184.9 181.9 180.2 185.6   1.9
17.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
18.|-- edge-star6-shv-13-frc1.fa 10.0%    10  184.9 185.2 184.0 187.0   0.8

kasperd

Before you try to understand the routing, you need to understand which IP addresses you are communicating with. Facebook is using multiple domain names, and the majority of traffic might not go to the one, you expected. You should look at the network traffic to see which DNS lookups are being performed, and in particular which IP addresses you are pointed at.

If the IP addresses themselves are not local, then it could be that you are using a DNS server, which is far from you. Once you have ensured that your DNS settings are such that the IP addresses you get are local, then you can start looking at traceroute to each of those IPs. Keep in mind that you only see the forward path and not the return path.

The traceroute you posted suggests most of the latency is within the facebook network, possibly you are communicating with an IP, which is simply far from the peering point where your packets enter the facebook network. From your traceroute output I cannot figure out which IP was the destination of your traceroute.