[188194] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Facebook & Traceroute

daemon@ATHENA.MIT.EDU (Yang Yu)
Thu Mar 10 19:58:38 2016

X-Original-To: nanog@nanog.org
In-Reply-To: <CAL9jLaZZhuu-VA_1Pph4rFrj7xE9RSg_cZ0B1sfEt-frCzZCEA@mail.gmail.com>
From: Yang Yu <yang.yu.list@gmail.com>
Date: Thu, 10 Mar 2016 18:57:54 -0600
To: Christopher Morrow <morrowc.lists@gmail.com>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

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.

home help back first fref pref prev next nref lref last post