Re: Short-circuited traceroutes on FIOS

[Lee <ler762 () gmail com>]

On 12/10/19, Christopher Morrow <morrowc.lists () gmail com> wrote:
> On Tue, Dec 10, 2019 at 5:36 PM Nimrod Levy <nimrodl () gmail com> wrote:
> > Is that unique to the FiOS gateway device? I don't use their router and my
> > traces go right out.
>
> I also don't use their device  and:
> $ traceroute 205.132.109.90
> traceroute to 205.132.109.90 (205.132.109.90), 30 hops max, 60 byte packets
>  1  _gateway (192.168.100.1)  3.085 ms  2.990 ms  2.795 ms
> ....
> 15  * 12.250.138.90 (12.250.138.90)  65.970 ms *^C
>
> -chris
> (perhaps this is location specific? I'm in the ashburn-ish-area-ish)

It's protocol specific.  Windows tracert uses icmp instead of udp.
On a linux box try
  ping -t 2 205.132.109.90

You should get a time to live exceeded but the Verizon router gives
you an echo reply instead.

Regards,
Lee


> > On Tue, Dec 10, 2019 at 3:08 PM Joe Maimon <jmaimon () jmaimon com> wrote:
> > > Apparently Verizon FIOS is a red herring, terminating ICMP traceroutes
> > > right on their gateways.
> > >
> > > More internet breakage. Thanks for the information to all who responded.
> > >
> > > Random control test.
> > >
> > > C:\Users\Home>tracert -d 1.4.5.6
> > >
> > > Tracing route to 1.4.5.6 over a maximum of 30 hops
> > >
> > >    1    15 ms     5 ms    <1 ms  172.18.24.1
> > >    2     3 ms    23 ms    24 ms  192.168.2.33
> > >    3     3 ms     6 ms     3 ms  1.4.5.6
> > >
> > > Trace complete.
> > >
> > >
> > > Joe
> > >
> > > Joe Maimon wrote:
> > > > Anyone have an idea why there are some destinations that on
> > > > residential verizon fios here in NY area terminate right on first
> > > > external hop?
> > > >
> > > > There seems to be a CDN common denominator here. On other networks
> > > > with more typical BGP paths and traceroutes, users are reporting
> > > > issues accessing these sites.
> > > >
> > > > C:\Users\Home>tracert www.usfoods.com
> > > >
> > > > Tracing route to statics.usfoods.com [205.132.109.90]
> > > > over a maximum of 30 hops:
> > > >
> > > >   1     3 ms    <1 ms    <1 ms  172.18.24.1
> > > >   2     4 ms     3 ms     3 ms  192.168.2.33
> > > >   3    17 ms     6 ms     3 ms  statics.usfoods.com [205.132.109.90]
> > > >
> > > > Trace complete.
> > > >
> > > > C:\Users\Home>tracert atworkhp.americanexpress.com
> > > >
> > > > Tracing route to atworkhp.americanexpress.com.akadns.net
> > > > [139.71.19.87]
> > > > over a maximum of 30 hops:
> > > >
> > > >   1     2 ms    <1 ms    <1 ms  172.18.24.1
> > > >   2     3 ms     4 ms    23 ms  192.168.2.33
> > > >   3    21 ms    11 ms     5 ms atworkhomepage2.americanexpress.com
> > > > [139.71.19.87]
> > > >
> > > > Trace complete.
> > > >
> > > > C:\Users\Home>tracert portal.discover.com
> > > >
> > > > Tracing route to e14577.x.akamaiedge.net [23.51.172.254]
> > > > over a maximum of 30 hops:
> > > >
> > > >   1     3 ms     1 ms    18 ms  172.18.24.1
> > > >   2    21 ms     7 ms     6 ms  192.168.2.33
> > > >   3     4 ms     2 ms     2 ms
> > > > a23-51-172-254.deploy.static.akamaitechnologies.com [23.51.172.254]
> > > >
> > > > Trace complete.