Forum - Any current issues with facebook ipv6? :: SixXS

Any current issues with facebook ipv6?

Shadow Hawkins on Thursday, 02 April 2015 06:03:18

Hi, Does anyone else experience problems with facebook via your sixxs connection? Without changing my configuration, it seems that there is some issue since some time yesterday at least. Pings do not go through:

root@flowipv6gw-gh36-1:~# ping6 -n www.facebook.com
PING www.facebook.com(2a03:2880:2110:df07:face:b00c:0:1) 56 data bytes
^C
--- www.facebook.com ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6048ms

On the other hand, pings to www.heise.de, for example, work out just fine:

root@flowipv6gw-gh36-1:~# ping6 -n www.heise.de
PING www.heise.de(2a02:2e0:3fe:1001:7777:772e:2:85) 56 data bytes
64 bytes from 2a02:2e0:3fe:1001:7777:772e:2:85: icmp_seq=1 ttl=56 time=53.8 ms
64 bytes from 2a02:2e0:3fe:1001:7777:772e:2:85: icmp_seq=2 ttl=56 time=53.2 ms
64 bytes from 2a02:2e0:3fe:1001:7777:772e:2:85: icmp_seq=3 ttl=56 time=55.9 ms
64 bytes from 2a02:2e0:3fe:1001:7777:772e:2:85: icmp_seq=4 ttl=56 time=53.1 ms
^C
--- www.heise.de ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 53.133/54.048/55.945/1.161 ms

Using an online ipv6 ping utility, facebook seems to be online just fine via v6. So maybe this is not a local issue of my network? Thanks in advance, Florian

Any current issues with facebook ipv6?

Shadow Hawkins on Thursday, 02 April 2015 08:38:25

Hi, I have also problems with the connectivity of my sixxs tunnel since yesterday.

root@gw:~# tracepath6 ipv6.google.com
 1?: [LOCALHOST]                        0.251ms pmtu 1280
 1:  gw-3381.ham-01.de.sixxs.net                          74.149ms 
 1:  gw-3381.ham-01.de.sixxs.net                          72.416ms 
 2:  2001:6f8:862:1::c2e9:c729                            71.823ms asymm  1 
 3:  2001:6f8:862:1::c2e9:c72c                            73.318ms asymm  2 
 4:  no reply
 5:  no reply
 6:  no reply
 7:  no reply
^C

The tracepath6 to www.heise.de is working:

root@gw:~# tracepath6 www.heise.de
 1?: [LOCALHOST]                        0.200ms pmtu 1280
 1:  gw-3381.ham-01.de.sixxs.net                          72.578ms 
 1:  gw-3381.ham-01.de.sixxs.net                          72.776ms 
 2:  2001:6f8:862:1::c2e9:c729                            72.199ms asymm  1 
 3:  2001:6f8:862:1::c2e9:c72c                            73.606ms asymm  2 
 4:  no reply
 5:  te7-2.c101.f.de.plusline.net                         83.880ms asymm  7 
 6:  2a02:2e0:3fe:0:c::1                                  82.506ms !A
     Resume: pmtu 1280

Yesterday a restart of aiccu solves the problem - but only for a few hours. Today a restart of aiccu doesn't help. Maybe it's a good idea to open a ticket.

Any current issues with facebook ipv6?

Jeroen Massar SixXS Staff

on Thursday, 02 April 2015 13:40:52

Yesterday a restart of aiccu solves the problem - but only for a few hours. Today a restart of aiccu doesn't help.

Restarting AICCU does not change anything in the network. Thus if you saw any changes then those where likely very incidental. Can you describe what you think was 'solved', eg what worked and what did not work before/after.

Any current issues with facebook ipv6?

Shadow Hawkins on Thursday, 02 April 2015 16:35:26

As a follow-up to my message from this morning: Still the same experience - facebook.com is unreachable, so it doesn't seem to be temporary. Here's a traceroute from a couple of minutes ago:

root@flowipv6gw-gh36-1:~# traceroute6 www.facebook.com
traceroute to www.facebook.com (2a03:2880:2110:df07:face:b00c:0:1), 30 hops max, 80 byte packets
 1  gw-1171.ham-02.de.sixxs.net (2001:6f8:1c00:492::1)  43.968 ms  46.176 ms  48.452 ms
 2  2001:6f8:891:1::c2e9:c721 (2001:6f8:891:1::c2e9:c721)  51.815 ms  54.965 ms  57.730 ms
 3  2001:6f8:891:1::c2e9:c725 (2001:6f8:891:1::c2e9:c725)  63.422 ms  67.015 ms  66.968 ms
 4  2001:920:0:1::10b (2001:920:0:1::10b)  86.569 ms  90.115 ms  93.039 ms
 5  2001:920:0:1::10a (2001:920:0:1::10a)  94.790 ms  97.814 ms  100.472 ms
 6  te0-0-0-0-pr2.fra.router.colt.net (2001:7f8::201c:0:2)  106.691 ms  64.709 ms  63.710 ms
 7  ae1.br01.fra1.tfbnw.net (2001:7f8::80a6:0:1)  64.017 ms  66.407 ms  68.896 ms
 8  * * *
 9  * * *

(...)

29  * * *
30  * * *

What is suspicious to me: Both Dirk Egert and I are using PoPs in Hamburg, though he uses ham-01 and I am using ham-01 - maybe it is a problem specific to those nodes? By the way, the same with ipv6.google.com for me as well:

traceroute to ipv6.google.com (2a00:1450:4013:c00::65), 30 hops max, 80 byte packets
 1  gw-1171.ham-02.de.sixxs.net (2001:6f8:1c00:492::1)  44.086 ms  46.052 ms  48.953 ms
 2  2001:6f8:891:1::c2e9:c721 (2001:6f8:891:1::c2e9:c721)  51.414 ms  55.262 ms  57.929 ms
 3  2001:6f8:891:1::c2e9:c725 (2001:6f8:891:1::c2e9:c725)  61.344 ms  63.782 ms  66.688 ms
 4  de-cix20.net.google.com (2001:7f8::3b41:0:2)  79.560 ms  82.738 ms  84.955 ms
 5  2001:4860::1:0:4ca2 (2001:4860::1:0:4ca2)  87.878 ms 2001:4860::1:0:70c3 (2001:4860::1:0:70c3)  91.760 ms  94.408 ms
 6  2001:4860::8:0:5038 (2001:4860::8:0:5038)  97.108 ms 2001:4860::8:0:5039 (2001:4860::8:0:5039)  55.594 ms 2001:4860::8:0:5038 (2001:4860::8:0:5038)  57.609 ms
 7  2001:4860::8:0:8f90 (2001:4860::8:0:8f90)  72.137 ms 2001:4860::8:0:8f8e (2001:4860::8:0:8f8e)  59.553 ms 2001:4860::8:0:8f90 (2001:4860::8:0:8f90)  64.980 ms
 8  * * *
 9  * * *

(...)

29  * * *
30  * * *
root@flowipv6gw-gh36-1:~#

What else could I do to solve this?

Any current issues with facebook ipv6?

Jeroen Massar SixXS Staff

on Thursday, 02 April 2015 17:25:59

What is suspicious to me: Both Dirk Egert and I are using PoPs in Hamburg, though he uses ham-01 and I am using ham-01 - maybe it is a problem specific to those nodes?

That can happen if Facebook is unable to route packets back for whatever reason.

What else could I do to solve this?

Nothing much, as it is the big networks that have to resolve such routing issues :(

Any current issues with facebook ipv6?

Shadow Hawkins on Saturday, 04 April 2015 19:54:01

Jeroen Massar wrote:

That can happen if Facebook is unable to route packets back for whatever reason.

Hmm, it's a little bit strange. At the moment www.facebook.com and ipv6.google.com is pingable. But my external server, with a native ipv6 address is not reachable (ping, ssh). With tcpdump I can see the packets arriving and going back to my sixxs tunnel ip. But they never reach the target. When I try to ping my sixxs tunnel ip from my external server, no packets were logged by tcpdump. I've done this check also with two external ipv6 checksites (local firewall is stopped): http://www.ipv6tech.ch/index.shtml?tcpportscan http://www.subnetonline.com/pages/ipv6-network-tools/online-ipv6-port-scanner.php With the Portscanner from www.ipv6tech.ch my mailserver is open with www.subnetonline.com the port is closed. The Ping Test from www.ipv6tech.ch of the ip 2001:6f8:900:d34::1 works. The same from www.subnetonline.com not. So, for me it looks like a problem with the PoP in Hamburg. As of the missing access to the systems between me and my external server, I'm not able to do some more debugging :-(

Nothing much, as it is the big networks that have to resolve such routing issues :(

Maybe somebody of the Easynet PoP in Hamburg can take a quick look at this issue, because it seems that this is not only a problem of "the big network".

Please note Posting is only allowed when you are logged in.