nanog mailing list archives
Re: Facebook & Traceroute
From: Yang Yu <yang.yu.list () gmail com>
Date: Thu, 10 Mar 2016 18:57:54 -0600
On Thu, Mar 10, 2016 at 9:35 AM, Christopher Morrow <morrowc.lists () gmail com> wrote:
unclear, that traceroute was from someplace I don't own the network for... from another place I do though... 5 ae0.dr07.ash2.tfbnw.net (31.13.26.233) 4 ms ae0.dr05.ash3.tfbnw.net (31.13.29.21) 4 ms ae0.dr08.ash2.tfbnw.net (31.13.26.235) 2 ms 6 * * * 7 * * * 8 * * * 9 edge-star-mini-shv-07-ash4.facebook.com (66.220.156.68) 3 ms 3 ms 2 ms same-ish results, no spoofed bits.
https://atlas.ripe.net/measurements/3612424/#!probes I did a atlas measurement of 500 probes, 104 probes (21%) had their outside IP shown in traceroute. Some peers of AS32934 don't have ingress filtering. It seems all prefixes advertised by Facebook are ROA signed and valid tho.
Current thread:
- Facebook & Traceroute Sam Norris (Mar 09)
- Re: Facebook & Traceroute Christopher Morrow (Mar 09)
- RE: Facebook & Traceroute Sam Norris (Mar 09)
- Re: Facebook & Traceroute Christopher Morrow (Mar 10)
- Re: Facebook & Traceroute Yang Yu (Mar 10)
- RE: Facebook & Traceroute Sam Norris (Mar 09)
- Re: Facebook & Traceroute Christopher Morrow (Mar 09)
- Re: Facebook & Traceroute Brandon Martin (Mar 09)
- RE: Facebook & Traceroute Doug Porter (Mar 12)
