SixXS::Sunset 2017-06-06

Problem reaching www.facebook.com
[se] Shadow Hawkins on Wednesday, 05 June 2013 14:33:15
Hi, since a few days back I've got a lot of trouble trying to reach www.facebook.com over ipv6. I have two separate tunnels at two different locations, and both have the same issue. Just stuck trying to load the page. I can "ping -6" the host without problem, and also enter via www.v6.facebook.com. But the regular page just don't work. Any ideas? Anyone with same issue? Regards Zebastian
Problem reaching www.facebook.com
[de] Shadow Hawkins on Wednesday, 05 June 2013 15:18:53
Same here. I'm connected via deham02 and a trace does reveal some packet-loss to the main facebook page:
mtr -6 -n www.facebook.com
Host Loss% Snt Last Avg Best Wrst StDev 1. 2001:6f8:1ddb::1 0.0% 237 0.6 0.6 0.4 0.8 0.1 2. 2001:6f8:1c00:394::1 0.0% 236 40.8 41.3 40.1 62.7 1.9 3. 2001:6f8:891:1::c2e9:c721 0.0% 236 40.9 41.3 40.1 57.8 1.5 4. 2001:6f8:891:1::c2e9:c725 0.0% 236 41.3 47.1 40.6 247.5 26.0 5. 2001:6f8:1:0:87:86:69:214 20.3% 236 44.9 44.5 42.3 62.4 2.1 6. 2001:6f8:1:0:87:86:77:83 0.0% 236 45.3 44.8 42.7 65.3 2.2 7. 2003:0:1401:8001::1 15.7% 236 44.3 44.6 41.9 57.8 1.7 8. 2003:0:1308:4000::1 0.0% 236 90.3 53.8 49.1 103.3 9.9 9. 2003:0:1308:4009::2 0.0% 236 50.6 51.4 49.0 93.8 5.8 10. 2620:0:1cff:dead:beef::1343 0.0% 236 49.5 51.3 49.3 80.1 4.0 11. 2620:0:1cff:dead:beef::144d 0.0% 236 61.1 67.6 59.7 118.3 13.1 12. 2620:0:1cff:dead:beef::207 0.0% 236 149.1 151.3 148.2 198.4 7.4 13. 2620:0:1cff:dead:beef::475 0.0% 236 198.1 150.2 147.8 198.1 4.7 14. 2620:0:1cff:dead:beef::d2 0.0% 236 164.3 165.0 162.7 199.4 4.3 15. 2620:0:1cff:dead:beef::1d6 0.0% 236 158.8 159.6 157.7 183.5 3.5 16. 2620:0:1cff:dead:beef::161f 0.0% 236 160.6 161.4 159.0 189.6 3.9 17. ??? 18. 2a03:2880:2110:3f07:face:b00c:0: 0.0% 236 159.2 159.2 157.8 174.7 1.4
Problem reaching www.facebook.com
[de] Shadow Hawkins on Wednesday, 05 June 2013 15:24:42
Although I can reach facebook via www.v6.facebook.com too, the package-loss seems to be the same:
Host Loss% Snt Last Avg Best Wrst StDev 1. 2001:6f8:1ddb::1 0.0% 202 0.6 0.6 0.5 0.7 0.0 2. gw-917.ham-02.de.sixxs.net 0.0% 201 41.1 41.3 40.1 51.4 1.2 3. 2001:6f8:891:1::c2e9:c721 0.0% 201 41.4 41.4 40.1 60.9 2.0 4. 2001:6f8:891:1::c2e9:c725 0.0% 201 41.1 48.4 40.8 211.0 26.1 5. 2001:6f8:1:0:87:86:69:214 36.8% 201 44.5 45.0 42.1 59.6 2.3 6. 2001:6f8:1:0:87:86:77:83 0.0% 201 45.6 44.8 42.7 62.1 1.9 7. 2003:0:1401:8001::1 28.9% 201 46.8 44.8 42.1 58.5 2.1 8. 2003:0:1308:4000::1 0.0% 201 50.2 51.0 49.3 80.4 3.5 9. 2003:0:1308:4009::2 0.0% 201 50.2 57.0 49.4 108.4 8.2 10. ae1.bb02.fra2.tfbnw.net 0.0% 201 51.8 51.8 49.7 81.2 3.8 11. ae4.bb02.cdg1.tfbnw.net 0.0% 201 61.0 71.7 60.3 100.5 15.3 12. ae7.bb01.lga1.tfbnw.net 0.0% 201 149.0 150.2 148.6 172.5 3.1 13. ae19.bb02.iad2.tfbnw.net 0.0% 201 155.8 151.7 148.7 184.0 5.7 14. ae9.bb04.frc1.tfbnw.net 0.0% 201 167.7 169.4 162.8 205.3 4.1 15. ae40.dr01.frc1.tfbnw.net 0.0% 201 159.4 173.7 158.2 234.4 10.3 16. po1022.csw06a.frc1.tfbnw.net 0.0% 201 159.8 164.2 159.2 778.6 43.6 17. v6-prod-01-06-frc1.facebook.com 0.0% 201 159.1 159.2 157.6 169.5 1.4
Problem reaching www.facebook.com
[ch] Jeroen Massar SixXS Staff on Wednesday, 05 June 2013 15:26:22
a trace does reveal some packet-loss to the main facebook page:
Please note that some routers do ICMP rate limitting and as can be seen there is a hop 17 there that is not responding to the probes used at all, which might be problematic if that hop should be sending ICMP Packet Too Big for instance. That said though, works for me(tm). As such, check the above mentioned things, as they will apply here too.
Problem reaching www.facebook.com
[us] Shadow Hawkins on Saturday, 08 June 2013 17:47:09
Jeroen Massar wrote:
Please note that some routers do ICMP rate limitting and as can be seen there is a hop 17 there that is not responding to the probes used at all, which might be problematic if that hop should be sending ICMP Packet Too Big for instance.
It's actually just replying from an address that's dropped by our edge ACLs. That device will never send a packet too big though, because its MTU is larger than the devices on either side of it.
Problem reaching www.facebook.com
[us] Shadow Hawkins on Saturday, 08 June 2013 17:41:08
Dennis Keitzel wrote:
Same here. I'm connected via deham02 and a trace does reveal some packet-loss to the main facebook page:
[....] 16. 2620:0:1cff:dead:beef::161f 0.0% 236 160.6 161.4 159.0 189.6 3.9 17. ??? 18. 2a03:2880:2110:3f07:face:b00c:0: 0.0% 236 159.2 159.2 157.8 174.7 1.4
Hop 17 doesn't respond because the reply is sourced from an address that's dropped by our (Facebook's) edge ACLs, so that specifically isn't an issue. If you're still experiencing problems, please email me (dsp@fb.com) a tcpdump of a failed tcp connection or two. Thanks.
Problem reaching www.facebook.com
[de] Shadow Hawkins on Saturday, 08 June 2013 20:42:04
Doug Porter wrote:
If you're still experiencing problems, please email me (dsp@fb.com) a tcpdump of a failed tcp connection or two. Thanks.
done!
Problem reaching www.facebook.com
[ch] Jeroen Massar SixXS Staff on Wednesday, 05 June 2013 15:24:34
I can "ping -6" the host without problem, and also enter via www.v6.facebook.com. But the regular page just don't work.
Sounds like a possible PathMTU issue. Check your tunnel's MTU setting (and if that matches the SixXS side which defaults to 1280), your firewall settings and also the TTL setting of your tunnel. tracepath6, if you have a Linux host, can be useful here. Next step would be to run a wireshark and check what goes wrong on the wire.
Problem reaching www.facebook.com
[se] Shadow Hawkins on Wednesday, 05 June 2013 17:52:19
Have experienced now that sometimes the site show up, after restarting the browser. But not always... and it doesn't matter which browser; IE, Chrome or Firefox. Nor the OS. And it's just for facebook.com. The rest of the web seems fine. Jeroen Massar wrote:
Sounds like a possible PathMTU issue. Check your tunnel's MTU setting (and if that matches the SixXS side which defaults to 1280), your firewall settings and also the TTL setting of your tunnel.
Changed the MTU from 1480 to 1280, but still got the same problem. Did a "aiccu test" and everything passed without any problem. Also did a tracepath6:
root@server2:~# tracepath6 www.facebook.com 1?: [LOCALHOST] pmtu 1280 1: gw-481.sto-01.se.sixxs.net 25.033ms 1: gw-481.sto-01.se.sixxs.net 50.643ms 2: sixxs-hy-demarc0.cust.ip6.p80.net 42.080ms asymm 1 3: 1890-sixxs.cr0-r87.hy-sto.se.ip6.p80.net 24.377ms asymm 2 4: 2001:16d8:1:1352::95 39.731ms 5: 10gigabitethernet1-2.core1.sto1.he.net 29.487ms 6: 10gigabitethernet3-2.core1.ams1.he.net 111.324ms asymm 8 7: no reply 8: no reply 9: no reply 10: no reply 11: no reply 12: no reply 13: no reply 14: no reply 15: no reply 16: no reply 17: no reply 18: no reply 19: no reply 20: no reply 21: no reply 22: no reply 23: no reply 24: no reply 25: no reply 26: no reply 27: no reply 28: no reply 29: no reply 30: no reply 31: no reply Too many hops: pmtu 1280 Resume: pmtu 1280
Got the same result on www.v6.facebook.com.
Problem reaching www.facebook.com
[ch] Jeroen Massar SixXS Staff on Wednesday, 05 June 2013 18:31:27
Summary: I'll kick somebody at Facebook to have a peek at this, seems some of their IPv6 front-end addresses are broken...
Changed the MTU from 1480 to 1280, but still got the same problem.
If the IPv4 path between your endpoint and the PoP is 1500, then you definitely should set the MTU to 1480 (when using proto-41 based tunnel). See the MTU FAQ for more details about this. A higher MTU typically is better though.
Did a "aiccu test" and everything passed without any problem.
The AICCU test does a very small test which can very basically tell you that your tunnel works, not much more. It does not do any MTU tests or anything like that either btw. This problem seems to solely affect facebook from your POV (it works from here for instance), but that can likely be caused by the simple fact that I am testing from a different ISP and thus completely different parameters are there.
Also did a tracepath6:
That more looks like it indicates a broken route. It seems I can reach it from the PoP itself though at this point in time (and that might just be the thing, that sometimes it is broken, other times it is not). From a bit of testing, the AAAA record for www.v6.facebook.com is always the same. The one for www.facebook.com depends it seems on the DNS resolver that one uses, thus likely geo-IP. I sometimes get 2a03:2880:10:8f01:face:b00c:0:9 which does not traceroute at all. While 2a03:2880:2110:9f07:face:b00c:0:1 for instance does work.
# traceroute6 www.facebook.com traceroute to www.facebook.com (2a03:2880:2110:9f07:face:b00c:0:1), 30 hops max, 80 byte packets 1 1890-sixxs.cr0-r87.hy-sto.se.ip6.p80.net (2001:16d8:aaaa:3::1) 0.280 ms 0.284 ms 0.310 ms 2 2001:16d8:1:1352::95 (2001:16d8:1:1352::95) 0.180 ms 0.174 ms 0.175 ms 3 10gigabitethernet1-2.core1.sto1.he.net (2001:7f8:d:ff::187) 0.509 ms 0.602 ms 0.535 ms 4 10gigabitethernet3-2.core1.ams1.he.net (2001:470:0:22f::1) 75.677 ms 75.730 ms 75.798 ms 5 br01.ams1.tfbnw.net (2001:7f8:1::a503:2934:1) 65.150 ms 65.263 ms 65.252 ms 6 ae1.bb01.ams2.tfbnw.net (2620:0:1cff:dead:beef::1612) 70.199 ms ae1.bb02.ams2.tfbnw.net (2620:0:1cff:dead:beef::1616) 70.432 ms ae1.bb01.ams2.tfbnw.net (2620:0:1cff:dead:beef::1612) 70.277 ms 7 ae3.bb02.lhr2.tfbnw.net (2620:0:1cff:dead:beee::2eb) 73.027 ms ae27.bb02.iad1.tfbnw.net (2620:0:1cff:dead:beef::481) 153.207 ms ae3.bb02.lhr2.tfbnw.net (2620:0:1cff:dead:beee::2eb) 73.908 ms 8 be5.bb02.dca1.tfbnw.net (2620:0:1cff:dead:beef::18de) 159.738 ms be5.bb01.dca1.tfbnw.net (2620:0:1cff:dead:beef::186e) 166.732 ms be5.bb02.dca1.tfbnw.net (2620:0:1cff:dead:beef::18de) 162.639 ms 9 ae4.bb02.frc1.tfbnw.net (2620:0:1cff:dead:beef::c2) 164.919 ms 160.648 ms ae8.bb04.frc1.tfbnw.net (2620:0:1cff:dead:beef::12ab) 160.575 ms 10 ae3.dr03.frc1.tfbnw.net (2620:0:1cff:dead:beef::1b3) 156.109 ms ae8.bb03.frc1.tfbnw.net (2620:0:1cff:dead:beef::12a8) 166.558 ms ae1.dr01.frc1.tfbnw.net (2620:0:1cff:dead:beef::8f) 162.152 ms 11 po1020.csw09d.frc1.tfbnw.net (2620:0:1cff:dead:beee::269) 156.766 ms ae3.dr04.frc1.tfbnw.net (2620:0:1cff:dead:beef::1b7) 157.203 ms po1020.csw09d.frc1.tfbnw.net (2620:0:1cff:dead:beee::269) 157.123 ms 12 edge-star6-shv-09-frc1.facebook.com (2a03:2880:2110:9f07:face:b00c:0:1) 161.477 ms 161.716 ms 165.940 ms
Seems Facebook picks up the traffic in Amsterdam but brings it themselves all the way to the (FRC) Forest City datacenter in North Virginia, USA.
$ traceroute6 2a03:2880:10:8f01:face:b00c:0:9 traceroute to 2a03:2880:10:8f01:face:b00c:0:9 (2a03:2880:10:8f01:face:b00c:0:9), 30 hops max, 80 byte packets 1 ge-1-3-0.breda.ipv6.concepts-ict.net (2001:838:1:1::1) 0.600 ms 0.587 ms 0.579 ms 2 2001:838:5:11::2 (2001:838:5:11::2) 0.647 ms 0.652 ms 0.643 ms 3 gi2-11.nikhef.ipv6.concepts-ict.net (2001:838:5:a::1) 1.946 ms 2.140 ms 2.213 ms 4 br01.ams1.tfbnw.net (2001:7f8:1::a503:2934:1) 5.146 ms 5.154 ms 5.235 ms 5 ae1.bb01.ams2.tfbnw.net (2620:0:1cff:dead:beef::1612) 2.485 ms 2.499 ms ae1.bb02.ams2.tfbnw.net (2620:0:1cff:dead:beef::1616) 2.667 ms 6 ae3.bb02.lhr2.tfbnw.net (2620:0:1cff:dead:beee::2eb) 13.830 ms ae3.bb01.lhr2.tfbnw.net (2620:0:1cff:dead:beee::20b) 10.967 ms ae3.bb02.lhr2.tfbnw.net (2620:0:1cff:dead:beee::2eb) 13.684 ms 7 be5.bb01.dca1.tfbnw.net (2620:0:1cff:dead:beef::186e) 147.620 ms ae18.bb02.iad2.tfbnw.net (2620:0:1cff:dead:beef::265) 87.861 ms 87.848 ms 8 ae35.bb01.iad2.tfbnw.net (2620:0:1cff:dead:beef::16a8) 88.720 ms ae8.bb05.prn1.tfbnw.net (2620:0:1cff:dead:beef::122) 155.068 ms ae35.bb01.iad2.tfbnw.net (2620:0:1cff:dead:beef::16a8) 88.668 ms 9 ae8.bb05.prn1.tfbnw.net (2620:0:1cff:dead:beef::122) 155.435 ms 155.679 ms ae11.bb02.prn1.tfbnw.net (2620:0:1cff:dead:beef::1d8) 204.624 ms 10 ae1.dr02.prn1.tfbnw.net (2620:0:1cff:dead:beef::1c5) 152.762 ms ae0.dr05.prn1.tfbnw.net (2620:0:1cff:dead:beef::33) 176.280 ms ae1.dr01.prn1.tfbnw.net (2620:0:1cff:dead:beef::1c1) 149.422 ms 11 * po1021.csw08d.prn1.tfbnw.net (2620:0:1cff:dead:beef::1935) 147.760 ms * 12 * * * 13 * * * 14 * * * 15 * * *
traceroute to 2a03:2880:10:8f01:face:b00c:0:9 (2a03:2880:10:8f01:face:b00c:0:9), 30 hops max, 80 byte packets 1 1890-sixxs.cr0-r87.hy-sto.se.ip6.p80.net (2001:16d8:aaaa:3::1) 0.274 ms 0.273 ms 0.295 ms 2 2001:16d8:1:1352::95 (2001:16d8:1:1352::95) 0.180 ms 0.177 ms 0.186 ms 3 10gigabitethernet1-2.core1.sto1.he.net (2001:7f8:d:ff::187) 0.486 ms 0.536 ms 0.570 ms 4 10gigabitethernet3-2.core1.ams1.he.net (2001:470:0:22f::1) 69.955 ms 70.020 ms 70.047 ms 5 br01.ams1.tfbnw.net (2001:7f8:1::a503:2934:1) 65.532 ms 65.620 ms 65.532 ms 6 ae1.bb02.ams2.tfbnw.net (2620:0:1cff:dead:beef::1616) 70.781 ms ae1.bb01.ams2.tfbnw.net (2620:0:1cff:dead:beef::1612) 70.667 ms 69.596 ms 7 ae3.bb02.lhr2.tfbnw.net (2620:0:1cff:dead:beee::2eb) 72.205 ms ae3.bb01.lhr2.tfbnw.net (2620:0:1cff:dead:beee::20b) 117.669 ms ae3.bb02.lhr2.tfbnw.net (2620:0:1cff:dead:beee::2eb) 74.926 ms 8 ae19.bb01.iad2.tfbnw.net (2620:0:1cff:dead:beef::259) 153.338 ms be5.bb01.dca1.tfbnw.net (2620:0:1cff:dead:beef::186e) 227.184 ms be5.bb02.dca1.tfbnw.net (2620:0:1cff:dead:beef::18de) 221.444 ms 9 ae36.bb02.iad1.tfbnw.net (2620:0:1cff:dead:beef::16a6) 149.467 ms ae8.bb05.prn1.tfbnw.net (2620:0:1cff:dead:beef::122) 223.893 ms ae36.bb01.iad1.tfbnw.net (2620:0:1cff:dead:beef::16a5) 160.950 ms 10 ae11.bb02.prn1.tfbnw.net (2620:0:1cff:dead:beef::1d8) 221.350 ms ae8.bb05.prn1.tfbnw.net (2620:0:1cff:dead:beef::122) 224.627 ms ae11.bb02.prn1.tfbnw.net (2620:0:1cff:dead:beef::1d8) 221.494 ms 11 ae1.dr02.prn1.tfbnw.net (2620:0:1cff:dead:beef::1c5) 225.774 ms po1020.csw08c.prn1.tfbnw.net (2620:0:1cff:dead:beef::192f) 221.380 ms ae33.dr06.prn1.tfbnw.net (2620:0:1cff:dead:beee::236) 226.276 ms 12 po1020.csw08b.prn1.tfbnw.net (2620:0:1cff:dead:beef::1927) 221.535 ms * 221.507 ms 13 * * * 14 * * *
Problem reaching www.facebook.com
[nl] Shadow Hawkins on Thursday, 06 June 2013 09:22:51
Jeroen Massar wrote:
Summary: I'll kick somebody at Facebook to have a peek at this, seems some of their IPv6 front-end addresses are broken...
From a bit of testing, the AAAA record for www.v6.facebook.com is always the same. The one for www.facebook.com depends it seems on the DNS resolver that one uses, thus likely geo-IP. I sometimes get 2a03:2880:10:8f01:face:b00c:0:9 which does not traceroute at all. While 2a03:2880:2110:9f07:face:b00c:0:1 for instance does work.
I confirm this is the same for me using the ams-05 PoP. Only 2a03:2880:2110:9f07:face:b00c:0:1 works. As a workaround my local DNS server (dnsmasq on TomatoUSB) is now set to serve that ip-address when requested to resolve www.facebook.com until this issue is resolved permanently by facebook or whomever manages this for them. Regards, Arjen
Problem reaching www.facebook.com
[nl] Shadow Hawkins on Thursday, 06 June 2013 16:20:36
Arjen A.M. Runsink wrote:
Jeroen Massar wrote:
Summary: I'll kick somebody at Facebook to have a peek at this, seems some of their IPv6 front-end addresses are broken...
From a bit of testing, the AAAA record for www.v6.facebook.com is always the same. The one for www.facebook.com depends it seems on the DNS resolver that one uses, thus likely geo-IP. I sometimes get 2a03:2880:10:8f01:face:b00c:0:9 which does not traceroute at all. While 2a03:2880:2110:9f07:face:b00c:0:1 for instance does work.
I confirm this is the same for me using the ams-05 PoP. Only 2a03:2880:2110:9f07:face:b00c:0:1 works. As a workaround my local DNS server (dnsmasq on TomatoUSB) is now set to serve that ip-address when requested to resolve www.facebook.com until this issue is resolved permanently by facebook or whomever manages this for them. Regards, Arjen
I got the same problem on nlams05. See this ticket: https://www.sixxs.net/tickets/?msg=tickets-9518434
Problem reaching www.facebook.com
[de] Shadow Hawkins on Thursday, 06 June 2013 21:14:21
Maybe offtopic, but can it be that www.enterprise.de is affected by the same issue?
Problem reaching www.facebook.com
[ch] Jeroen Massar SixXS Staff on Friday, 07 June 2013 02:52:14
Felix Kaechele wrote:
Maybe offtopic, but can it be that www.enterprise.de is affected by the same issue?
Quite offtopic.... but: From the US:
traceroute to www.enterprise.de (2620:103:e029:1da7::99), 30 hops max, 80 byte packets ... 2 int-0-4-0-0.r1.pao1.isc.org (2001:4f8:1b:1::8:1) 0.934 ms 1.114 ms 1.167 ms 3 int-0-3.r1.ord1.isc.org (2001:4f8:0:1::4a:2) 52.633 ms 52.856 ms 52.928 ms 4 2001:500:71:6::3 (2001:500:71:6::3) 52.597 ms 52.794 ms 52.781 ms 5 2001:500:71:fffe::2 (2001:500:71:fffe::2) 52.534 ms 52.698 ms 52.685 ms 6 Loopback0.GW5.KCY4.ALTER.NET (2600:806::5) 64.504 ms 64.262 ms 64.402 ms 7 2600:806:11f::2 (2600:806:11f::2) 69.514 ms 69.541 ms 69.619 ms 8 * * * 9 * * *
From Hetzner in Germany...
$ traceroute6 www.enterprise.de traceroute to www.enterprise.de (2620:103:e029:1da7::99), 30 hops max, 80 byte packets [..] 10 6b1.fft4.alter.net (2001:7f8::319e:0:1) 29.239 ms 29.809 ms * 11 * 2.gr-1-1-0.GW66.LAX9.ALTER.NET (2001:600:c:14::2) 180.438 ms 179.549 ms 12 Loopback0.GW5.KCY4.ALTER.NET (2600:806::5) 206.216 ms 206.171 ms 199.305 ms 13 2600:806:11f::2 (2600:806:11f::2) 198.119 ms 175.752 ms 175.017 ms 14 * * * 15 * * * 16 * * * 17 * * *
As such, can't reach it from here either. The prefix is in BGP but seems to not be going anywhere. I suggest you contact their network team as it is quite the broken network.
Problem reaching www.facebook.com
[gb] Shadow Hawkins on Friday, 07 June 2013 14:34:31
I have the same issue www.facebook.com works (only very) occasionally but www.v6.facebook.com works all the time for me. I can get there from the system that hosts my /64 and is my tunnel endpoint but anything on my /64 will not get there. I'm coming in from gblon03. Every other IPV6 website I've tried from my /64 and my tunnel endpoint works.
Problem reaching www.facebook.com
[gb] Shadow Hawkins on Saturday, 08 June 2013 07:32:00
I'm on gblon02 and have noticed the same issue. Glad to see it's not just me breaking something on my network!
traceroute to www.facebook.com (2a03:2880:2050:3f07:face:b00c:0:1), 30 hops max, 40 byte packets using UDP 1 XXXXXXXXXXXXXXX (XXXXXXXXXXX) 0.339 ms 0.293 ms 0.161 ms 2 gw-1643.lon-02.gb.sixxs.net (2a01:348:6:66a::1) 9.357 ms 9.281 ms 9.290 ms 3 gblon02.sixxs.net (2a01:348:0:4:0:3:1:1) 9.484 ms 9.599 ms 9.501 ms 4 ge-0-0-5-20.cs0.thw.uk.goscomb.net (2a01:348:0:4:0:3:0:1) 10.928 ms 10.290 ms 9.720 ms 5 xe-0-1-1.cs0.the.uk.goscomb.net (2a01:348::36:1:1) 11.080 ms 11.268 ms 10.593 ms 6 xe-0-1-0.cs0.gs2.uk.goscomb.net (2a01:348::24:1:1) 11.517 ms 11.012 ms 10.601 ms 7 xe-0-1-0-0.cs1.gs2.uk.goscomb.net (2a01:348::40:1:1) 14.085 ms 14.987 ms 13.933 ms 8 xe-0-1-0.cs0.sov.uk.goscomb.net (2a01:348::41:1:1) 14.701 ms 14.126 ms 13.095 ms 9 ge-1-1-5.rt0.sov.uk.goscomb.net (2a01:348::17:0:1) 10.410 ms 10.375 ms 18.174 ms 10 xe-0-0-1-0.rt0.thn.uk.goscomb.net (2a01:348::51:0:1) 24.229 ms 24.651 ms 23.531 ms 11 2001:7f8:4::80a6:2 (2001:7f8:4::80a6:2) 18.440 ms 18.057 ms 18.171 ms 12 ae2.bb02.lhr2.tfbnw.net (2620:0:1cff:dead:beee::40c) 18.171 ms 17.985 ms 19.356 ms 13 ae18.bb02.iad2.tfbnw.net (2620:0:1cff:dead:beef::265) 84.977 ms ae19.bb01.iad2.tfbnw.net (2620:0:1cff:dead:beef::259) 85.460 ms ae19.bb02.iad1.tfbnw.net (2620:0:1cff:dead:beef::318) 87.014 ms 14 ae2.dr03.ash3.tfbnw.net (2620:0:1cff:dead:beef::440) 84.399 ms ae2.dr02.ash3.tfbnw.net (2620:0:1cff:dead:beef::33d) 84.014 ms ae2.dr03.ash3.tfbnw.net (2620:0:1cff:dead:beef::440) 84.418 ms 15 po1022.csw03b.ash5.tfbnw.net (2620:0:1cff:dead:beef::10cf) 89.812 ms ae32.bb02.iad1.tfbnw.net (2620:0:1cff:dead:beee::405) 88.236 ms po1020.csw03d.ash5.tfbnw.net (2620:0:1cff:dead:beef::110f) 84.860 ms 16 * * * 17 edge-star6-shv-03-ash5.facebook.com (2a03:2880:2050:3f07:face:b00c:0:1) 84.784 ms 84.780 ms po1019.csw03a.ash5.tfbnw.net (2620:0:1cff:dead:beef::10c1) 89.800 ms
2: gw-1643.lon-02.gb.sixxs.net 11.334ms 3: gblon02.sixxs.net 11.555ms asymm 2 4: ge-0-0-5-20.cs0.thw.uk.goscomb.net 12.132ms asymm 3 5: xe-0-1-1.cs0.the.uk.goscomb.net 12.521ms asymm 4 6: xe-0-1-0.cs0.gs2.uk.goscomb.net 12.879ms asymm 5 7: xe-0-1-0-0.cs1.gs2.uk.goscomb.net 13.318ms asymm 6 8: xe-0-1-0.cs0.sov.uk.goscomb.net 14.123ms asymm 7 9: ge-1-1-5.rt0.sov.uk.goscomb.net 13.102ms asymm 8 10: xe-0-0-1-0.rt0.thn.uk.goscomb.net 14.312ms asymm 9 11: no reply
Problem reaching www.facebook.com
[ch] Jeroen Massar SixXS Staff on Saturday, 08 June 2013 13:47:52
Just in case: The Facebook network team is aware of this problem and is looking deeply into it...
Problem reaching www.facebook.com
[dk] Shadow Hawkins on Monday, 10 June 2013 07:47:07
Jeroen Massar wrote:
Just in case: The Facebook network team is aware of this problem and is looking deeply into it...
Fwiw, it seems Opera does fallback to ipv4 quicker, when there is a problem with ipv6.
Problem reaching www.facebook.com
[ch] Jeroen Massar SixXS Staff on Monday, 10 June 2013 15:55:50
Fwiw, it seems Opera does fallback to ipv4 quicker, when there is a problem with ipv6.
Opera is just webkit now right? :) Note that fallback also depends on the operating system, eg OSX "records" the quality of connections and then prefers on or the other.
Problem reaching www.facebook.com
[us] Shadow Hawkins on Saturday, 08 June 2013 17:32:29
It'd be really helpful to get tcpdumps/pcaps of the problem. We're looking into it, but do not have a lot of data to work with. Please email pcaps or other debug data to me at dsp@fb.com. Thanks for your help, and sorry for the connectivity issues.
Problem reaching www.facebook.com
[nl] Shadow Hawkins on Saturday, 08 June 2013 22:54:26
Doug Porter wrote:
It'd be really helpful to get tcpdumps/pcaps of the problem. We're looking into it, but do not have a lot of data to work with. Please email pcaps or other debug data to me at dsp@fb.com. Thanks for your help, and sorry for the connectivity issues.
An e-mail from me is under way to you, with pcap dump of the issue, as I have exactly the same problem as described before since a couple of days now.
Problem reaching www.facebook.com
[nl] Shadow Hawkins on Wednesday, 12 June 2013 10:01:47
Well, whatever has been changed, it works now. Best regards, Arjen
Problem reaching www.facebook.com
[de] Shadow Hawkins on Tuesday, 11 June 2013 23:03:32
The issue seems to be resolved for me. I didn't had any connection problems for the last 48h or so.
Problem reaching www.facebook.com
[gb] Shadow Hawkins on Wednesday, 12 June 2013 16:05:39
Facebook has been working for a couple of days for me now. Whatever they did seems to have fixed it yay!
Problem reaching www.facebook.com
[se] Shadow Hawkins on Wednesday, 12 June 2013 21:57:27
Working here too. Good job!
Problem reaching www.facebook.com
[gb] Shadow Hawkins on Monday, 12 August 2013 08:42:35
Charlie MacDonald wrote:
Facebook has been working for a couple of days for me now. Whatever they did seems to have fixed it yay!
Been having the same problems for a couple of months with both facebook and any https google service. And it does appear to be ONLY https that it's affecting, and the browser sticks at "establishing secure connection". If I then go straight to the live pop status, I see: "Encap.Pkt Too Big". Got Win8, but same story on the win7 laptop, via cable or wireless. So, I just turn off ipv6 and everything works. I wasn't aware of v6.facebook, but you're right, that seems to work perfectly. When I ping facebook, I do indeed get an ipv6 address, so it's looking that up just fine. To add confusion to the mix, if I use IE11 rather than my usual Chrome, I can get Facebook pretty much straight away, but google gmail/docs/calendar etc still won't load. Back on Chrome, it seems that once Facebook or Gmail finally loads, it's after several minutes and attempts (almost like something needs to "warm up") and then after that it works just fine. Strange, eh? PS - here are some of the Encap.Pkt Too Big errors I see around the time I'm trying to load FB and Gmail.
18648, last: 2a03:2880:10:cf07:face:b00c:0:1 2013-08-12 08:01:10 (1376294470; 0 days 00:00:08 ago) 8666, last: 2600:1417:9:193::90 2013-08-12 08:03:18 (1376294598; 0 days 00:00:00 ago) 18692, last: 2001:838:2:1::30:67 2013-08-12 08:06:16 (1376294776; 0 days 00:00:51 ago)
Problem reaching www.facebook.com
[ch] Jeroen Massar SixXS Staff on Monday, 12 August 2013 08:48:39
If I then go straight to the live pop status, I see: "Encap.Pkt Too Big".
Unlike most of the other lines, seeing these packets is a good thing, as it means that the PoP is sending these replies back to the origin of the packet. (now, we do hope that that origin and it's routers process them as they should). Your best way to figure out what is going wrong here is to get a Wireshark and capture all packets (IPv6 + ICMPv6 at minimum) to see what might go wrong. Note that browsers differ in how they connect to websites, they tend to have their own Happy Eyeball settings and thus might use IPv4 and IPv6 in mysterious orders, thus making you think that IE11 works, while Chrome does not and vice versa. Hence wireshark, that is the only way to check if things work or not.
Problem reaching www.facebook.com
[gb] Shadow Hawkins on Monday, 12 August 2013 09:21:41
Thanks Jeroen. I'll get my head around Wireshark later; but something suddenly occurred to me. We have Powerline Adapters (Ethernet over Power) - the ADSL router is at one end of the building by the phone master socket, then at the other end, the signal comes out of the power socket into a wireless router. I just tried plugging the laptop directly into the router, and it didn't seem to have any of these IPV6 problems. Can't find anyone having similar problems on Google, so I'm wondering if it was just fluke or coincidence. Would Wireshark show me this? Is the "Encap.Pkt Too Big" a possible indication of something my end, or purely a tunnel issue? Sorry to ask all these newb questions - I did google it, I promise!
Problem reaching www.facebook.com
[ch] Jeroen Massar SixXS Staff on Monday, 12 August 2013 11:13:36
We have Powerline Adapters (Ethernet over Power)
As most of these are just Ethernet Bridges they should operate just fine, unless they do not properly do multicast and/or filter IPv6 in general. I've got a couple of Devolo AVPro+'s and these work just fine with IPv6.
Would Wireshark show me this?
Yes, though one likely has to dig a bit.
Is the "Encap.Pkt Too Big" a possible indication of something my end, or purely a tunnel issue?
Standard Ethernet has an MTU of 1500, and as most hosts on the Internet are connected to Ethernet the defacto standard is 1500. IPv6 has a minimum MTU of 1280 and IPv6 tunnels thus default to that too (though for SixXS this can be changed, see the MTU FAQ). When a packet thus comes from eg Google/Facebook and arrives at the PoP the packet is likely 1500 bytes in size, the PoP then wants to send it to your tunnel where only a maximum packet of 1280 will go, thus the PoP sends back a "ICMPv6 Packet Too Big" to the origin, which will (if not dropping those ICMPv6 packets) retransmit the packet with a maximum of 1280 bytes.
Problem reaching www.facebook.com
[gb] Shadow Hawkins on Sunday, 22 December 2013 17:08:43
Jeroen Massar wrote:
> Would Wireshark show me this? Yes, though one likely has to dig a bit.
I dug a bit, then I dug a bit more. Got no-where and realised life is to short to be messing with something that should just work. So I unticked ipv6 protocols from Win7 wireless laptop and Win8 LAN desktop about 5 days after last posting here. Turned it all back on about a month ago and it's been good as gold - not failed once! Nothing else has changed this end. So I don't know whether it was facebook and google, or sixxs or the pop provider, but it appears to have fixed itself now. :)

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

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker