On Fri, Dec 13, 2019 at 4:16 PM Javier J wrote:
>
> Is anyone from Verizon on this list? They probably are but not allowed to
> comment. I would love to know if there is an official comment on why they do
> this.
>
> It annoyed me when they first implemented and I was trying to diagnose an
> is
Is anyone from Verizon on this list? They probably are but not allowed to
comment. I would love to know if there is an official comment on why they
do this.
It annoyed me when they first implemented and I was trying to diagnose an
issue with a client.
Regarding your edge device:
Same here, I had
> On Dec 11, 2019, at 09:26 , Saku Ytti wrote:
>
> On Wed, 11 Dec 2019 at 19:14, Rob Foehl wrote:
>
>> Support claims that it was a mistake, but it's also been 15+ months and
>> it's pretty deliberate behavior. Draw your own conclusions...
>
> TTL decrement issues are fairly common across
On Wed, 11 Dec 2019, Javier J wrote:
If you have static addressing (biz account) then possibly different from
what I have.
In North NJ, 3 different accounts I can verify have ICMP blocked as of
sometime earlier this year or late last year so have to use udp to get a
real traceroute.
Could not
* 1.2.3.4
>
> 22 165 ms 158 ms * 1.2.3.4
>
> 23 237 ms 158 ms * 1.2.3.4
>
> 24 158 ms 290 ms * 1.2.3.4
>
> 25 158 ms 160 ms 158 ms 1.2.3.4
>
>
>
> Trace complete.
>
>
>
> C:\>
>
>
>
>
squale
Sent: Thursday, December 12, 2019 1:18 AM
To: Valdis Klētnieks
Cc: nanog@nanog.org
Subject: Re: Short-circuited traceroutes on FIOS
Traceroute is becoming more and more an expert's tool because interpretation of
its results isn't straightforward.
I had written a paper last ye
Traceroute is becoming more and more an expert's tool because
interpretation of its results isn't straightforward.
I had written a paper last year and mentioned its misuse in academia in the
context of estimating the number of energy-consuming devices between a
source and a destination.
Traceroute
On Wed, 11 Dec 2019 19:26:09 +0200, Saku Ytti said:
> On Wed, 11 Dec 2019 at 19:14, Rob Foehl wrote:
>
> > Support claims that it was a mistake, but it's also been 15+ months and
> > it's pretty deliberate behavior. Draw your own conclusions...
>
> TTL decrement issues are fairly common across mu
On Wed, 11 Dec 2019 at 19:14, Rob Foehl wrote:
> Support claims that it was a mistake, but it's also been 15+ months and
> it's pretty deliberate behavior. Draw your own conclusions...
TTL decrement issues are fairly common across multiple vendors and hw,
can be sw can be hw limit. Common issue
On Tue, 10 Dec 2019, 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?
They're returning fake ICMP echo replies from their BNGs for echo packets
with TTL=1, thus any ICMP traceroute (Wi
Greetings,
* Mike Hammett (na...@ics-il.net) wrote:
> How have we gone this long of a conversation without someone from FIOS
> stepping in and setting the record straight?
How have we gone this long without ipv6 on FIOS ...?
(though I've heard that it may have shown up in some places, I'm
cert
;North American Networking and Offtopic Gripes List"
Sent: Tuesday, December 10, 2019 1:47:17 PM
Subject: Short-circuited traceroutes on FIOS
Anyone have an idea why there are some destinations that on residential
verizon fios here in NY area terminate right on first external hop?
The
If you have static addressing (biz account) then possibly different from
what I have.
In North NJ, 3 different accounts I can verify have ICMP blocked as of
sometime earlier this year or late last year so have to use udp to get a
real traceroute.
Could not be deployed in all areas the same way.
I'm in the same region as Chris and I still can't make it fail. I wonder if
it's because I have static addressing?
On Tue, Dec 10, 2019 at 11:59 PM Christopher Morrow
wrote:
> On Tue, Dec 10, 2019 at 11:44 PM Lee wrote:
> > It's protocol specific. Windows tracert uses icmp instead of udp.
> >
On Tue, Dec 10, 2019 at 11:44 PM Lee wrote:
> 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.
that's hilariously bad :( I think
On 12/10/19, Christopher Morrow wrote:
> On Tue, Dec 10, 2019 at 5:36 PM Nimrod Levy 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
On Tue, Dec 10, 2019 at 5:36 PM Nimrod Levy 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
mtr -u 4.2.2.2 --report-wide
Start: 2019-12-10T21:26:20-0500
HOST: fedora-lenovo Loss% Snt Last Avg Best
Wrst StDev
1.|-- _gateway 0.0%101.3 1.4 1.1
2.3 0.3
2.|-- ??? 100.0100.0 0
Is that unique to the FiOS gateway device? I don't use their router and my
traces go right out.
On Tue, Dec 10, 2019 at 3:08 PM Joe Maimon wrote:
> Apparently Verizon FIOS is a red herring, terminating ICMP traceroutes
> right on their gateways.
>
> More internet breakage. Thanks for the inform
This is not from a verizon CPE. Its happening on their CO internet
gateway customer facing routers.
tcptraceroute looks more legit
Joe
Nimrod Levy wrote:
Is that unique to the FiOS gateway device? I don't use their router
and my traces go right out.
On Tue, Dec 10, 2019 at 3:08 PM Joe Maim
I had this issue while looking at Ripe Atlas measurements.
Turns out these Verizon boxes spoof ICMP with TTL = 3 (or 2, I don't
recall). Try doing a UDP or TCP based traceroute instead.
Maybe you're seeing the same problem.
Kind Regards,
Filip
On 12/10/19 8:47 PM, Joe Maimon wrote:
Anyone ha
wasn't vz pursuing some 'get the a cdn in the central office' for a
time? :) perhaps this is the manifestation of that? :)
or perhaps jared arranged to get links back from each CO to his
network gear in akamai-land?
I love conspiracies!
On Tue, Dec 10, 2019 at 2:48 PM Joe Maimon wrote:
>
> Anyon
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
115 ms 5
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
24 matches
Mail list logo
