Also, Does someone have traceroute through ANET device, which returns the EO on TTL exceeded? If we can find actual production traceroute, we're sure to get implementations in: https://github.com/fujiapple852/trippy https://github.com/lance0/ttl At least trippy will already print all unknown EOs too, so you don't need tshark to confirm. On Tue, 8 Sept 2026 at 09:39, Saku Ytti <saku@ytti.fi> wrote:
On Tue, 8 Sept 2026 at 01:39, Lukas Tribus <lukas@ltri.eu> wrote:
Thanks, that would be RFC 5837, I did not know about that one.
Looks like Arista has joined Juniper in implementing this [1] and Linux has it since 6.19.
[1] https://arista.my.site.com/AristaCommunity/s/question/0D5Uw000001yvSvKAI/eos...
Awesome, can't. see the actual Arista url, would be interesting in specifics.
In Juniper the problem is a) basically one platform (QFX, no MX no PTX) b) TTL exceeded doesn't get the EO, making it basically useless
We've opened an ER for this, but it's not a priority for Juniper.
I feel like RFC5837 is such that once we get it, we wonder how we survive before it. But I seem to be fairly alone here (so wrong I guess), after many years of asking j-nsp and c-nsp to push their vendors for it. -- ++ytti
-- ++ytti