<div dir="ltr">mtr -u 4.2.2.2 --report-wide <br>Start: 2019-12-10T21:26:20-0500<br>HOST: fedora-lenovo Loss% Snt Last Avg Best Wrst StDev<br> 1.|-- _gateway 0.0% 10 1.3 1.4 1.1 2.3 0.3<br> 2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0<br> 3.|-- <a href="http://b3346.nwrknj-lcr-21.verizon-gni.net">b3346.nwrknj-lcr-21.verizon-gni.net</a> 0.0% 10 6.7 4.8 2.2 8.2 1.9<br> 4.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0<br> 5.|-- <a href="http://0.ae1.br1.ewr6.alter.net">0.ae1.br1.ewr6.alter.net</a> 0.0% 10 18.9 6.2 3.6 18.9 4.6<br> 6.|-- <a href="http://lag-12.ear3.newark1.level3.net">lag-12.ear3.newark1.level3.net</a> 20.0% 10 3.9 3.3 2.2 4.4 1.0<br> 7.|-- <a href="http://ae-2-3602.ear2.newyork1.level3.net">ae-2-3602.ear2.newyork1.level3.net</a> 90.0% 10 5.6 5.6 5.6 5.6 0.0<br> 8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0<br><div><br></div><div>Verizon FIOS</div><div>They are blocking ICMP and returning false responses right at their gateway at the CO, not the CPE (I'm using my own router)</div><div><br></div><div>You have to do it using UDP to get real results of a traceroute.</div><div><br></div><div>- Javier</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Dec 10, 2019 at 3:56 PM Joe Maimon <<a href="mailto:jmaimon@jmaimon.com">jmaimon@jmaimon.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">This is not from a verizon CPE. Its happening on their CO internet <br>
gateway customer facing routers.<br>
<br>
tcptraceroute looks more legit<br>
<br>
Joe<br>
<br>
Nimrod Levy wrote:<br>
> Is that unique to the FiOS gateway device? I don't use their router <br>
> and my traces go right out.<br>
><br>
><br>
> On Tue, Dec 10, 2019 at 3:08 PM Joe Maimon <<a href="mailto:jmaimon@jmaimon.com" target="_blank">jmaimon@jmaimon.com</a> <br>
> <mailto:<a href="mailto:jmaimon@jmaimon.com" target="_blank">jmaimon@jmaimon.com</a>>> wrote:<br>
><br>
> Apparently Verizon FIOS is a red herring, terminating ICMP<br>
> traceroutes<br>
> right on their gateways.<br>
><br>
> More internet breakage. Thanks for the information to all who<br>
> responded.<br>
><br>
> Random control test.<br>
><br>
> C:\Users\Home>tracert -d 1.4.5.6<br>
><br>
> Tracing route to 1.4.5.6 over a maximum of 30 hops<br>
><br>
> 1 15 ms 5 ms <1 ms 172.18.24.1<br>
> 2 3 ms 23 ms 24 ms 192.168.2.33<br>
> 3 3 ms 6 ms 3 ms 1.4.5.6<br>
><br>
> Trace complete.<br>
><br>
><br>
> Joe<br>
><br>
> Joe Maimon wrote:<br>
> > Anyone have an idea why there are some destinations that on<br>
> > residential verizon fios here in NY area terminate right on first<br>
> > external hop?<br>
> ><br>
> > There seems to be a CDN common denominator here. On other networks<br>
> > with more typical BGP paths and traceroutes, users are reporting<br>
> > issues accessing these sites.<br>
> ><br>
> > C:\Users\Home>tracert <a href="http://www.usfoods.com" rel="noreferrer" target="_blank">www.usfoods.com</a> <<a href="http://www.usfoods.com" rel="noreferrer" target="_blank">http://www.usfoods.com</a>><br>
> ><br>
> > Tracing route to <a href="http://statics.usfoods.com" rel="noreferrer" target="_blank">statics.usfoods.com</a><br>
> <<a href="http://statics.usfoods.com" rel="noreferrer" target="_blank">http://statics.usfoods.com</a>> [205.132.109.90]<br>
> > over a maximum of 30 hops:<br>
> ><br>
> > 1 3 ms <1 ms <1 ms 172.18.24.1<br>
> > 2 4 ms 3 ms 3 ms 192.168.2.33<br>
> > 3 17 ms 6 ms 3 ms <a href="http://statics.usfoods.com" rel="noreferrer" target="_blank">statics.usfoods.com</a><br>
> <<a href="http://statics.usfoods.com" rel="noreferrer" target="_blank">http://statics.usfoods.com</a>> [205.132.109.90]<br>
> ><br>
> > Trace complete.<br>
> ><br>
> > C:\Users\Home>tracert <a href="http://atworkhp.americanexpress.com" rel="noreferrer" target="_blank">atworkhp.americanexpress.com</a><br>
> <<a href="http://atworkhp.americanexpress.com" rel="noreferrer" target="_blank">http://atworkhp.americanexpress.com</a>><br>
> ><br>
> > Tracing route to <a href="http://atworkhp.americanexpress.com.akadns.net" rel="noreferrer" target="_blank">atworkhp.americanexpress.com.akadns.net</a><br>
> <<a href="http://atworkhp.americanexpress.com.akadns.net" rel="noreferrer" target="_blank">http://atworkhp.americanexpress.com.akadns.net</a>> [139.71.19.87]<br>
> > over a maximum of 30 hops:<br>
> ><br>
> > 1 2 ms <1 ms <1 ms 172.18.24.1<br>
> > 2 3 ms 4 ms 23 ms 192.168.2.33<br>
> > 3 21 ms 11 ms 5 ms<br>
> <a href="http://atworkhomepage2.americanexpress.com" rel="noreferrer" target="_blank">atworkhomepage2.americanexpress.com</a><br>
> <<a href="http://atworkhomepage2.americanexpress.com" rel="noreferrer" target="_blank">http://atworkhomepage2.americanexpress.com</a>><br>
> > [139.71.19.87]<br>
> ><br>
> > Trace complete.<br>
> ><br>
> > C:\Users\Home>tracert <a href="http://portal.discover.com" rel="noreferrer" target="_blank">portal.discover.com</a><br>
> <<a href="http://portal.discover.com" rel="noreferrer" target="_blank">http://portal.discover.com</a>><br>
> ><br>
> > Tracing route to <a href="http://e14577.x.akamaiedge.net" rel="noreferrer" target="_blank">e14577.x.akamaiedge.net</a><br>
> <<a href="http://e14577.x.akamaiedge.net" rel="noreferrer" target="_blank">http://e14577.x.akamaiedge.net</a>> [23.51.172.254]<br>
> > over a maximum of 30 hops:<br>
> ><br>
> > 1 3 ms 1 ms 18 ms 172.18.24.1<br>
> > 2 21 ms 7 ms 6 ms 192.168.2.33<br>
> > 3 4 ms 2 ms 2 ms<br>
> > <a href="http://a23-51-172-254.deploy.static.akamaitechnologies.com" rel="noreferrer" target="_blank">a23-51-172-254.deploy.static.akamaitechnologies.com</a><br>
> <<a href="http://a23-51-172-254.deploy.static.akamaitechnologies.com" rel="noreferrer" target="_blank">http://a23-51-172-254.deploy.static.akamaitechnologies.com</a>><br>
> [23.51.172.254]<br>
> ><br>
> > Trace complete.<br>
> ><br>
> ><br>
> ><br>
><br>
<br>
</blockquote></div>