Awesome, can't. see the actual Arista url, would be interesting in specifics.
Arista supports RFC5837 since EOS version 4.33.0F on all platforms except cEOS (containers). A public config guide is available here (look for "Support for Extended ICMP Errors" halfway down, it is long): https://www.arista.com/en/um-eos/eos-ethernet-ports https://web.archive.org/web/20260910180814/https://www.arista.com/en/um-eos/... It is enabled per VRF and can be limited by ACL. It will report back the interface ID, interface name (as it appears in EOS), it's MTU and IP address. The interface name can optionally include the hostname, but that is it; and those 2 strings cannot be modified manually - they are what they are. Arista interface names are not wirespeed dependent, they are always called Ethernet (or Port-Channel), so compared to reverse DNS it looks like the service provider is not able to provide a string of it's own choosing. There is an optional "Node ID extension codepoints" setting, which when set Wireshark fails to parse, I did not read the RFC so I'm not quite sure what this is about; according to the Arista docs it is about identifying the source node (indeed the hex data contains the hostname; not the interface/ipv4 or ipv6 addresses that the configuration suggests). You can find capture and configs here: https://www.ltri.net/download/19b9cd22-2f03-4d38-9a5e-21b6bd908b33/arista-ic...
If we can find actual production traceroute, we're sure to get implementations in:
https://github.com/fujiapple852/trippy https://github.com/lance0/ttl
I have filed feature requests for both with those captures.
At least trippy will already print all unknown EOs too, so you don't need tshark to confirm.
Yes, with -e --tui-icmp-extension-mode all trippy shows unknown extensions. Lukas