Implement RFC5837 (ICMP for Interface and Next-Hop Identification)

Describe the feature you'd like

Support to parse RFC5837 (ICMP for Interface and Next-Hop Identification).

Describe alternatives you've considered

n/a

Additional context

Hello,

if there is interest in implementing support for RFC5837 (ICMP for Interface and Next-Hop Identification) I have a lab running with Arista EOS and RFC5837 enabled.

Traceroute (-e) has support for RFC5837 since 2.1.4 (Ubuntu 24.04 LTS and Debian Trixie got it): https://sourceforge.net/projects/traceroute/files/traceroute/traceroute%202.1.4/

Arista's doc 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

Interfaces names optionally contain hostname (Ethernet1@arista-rfc5837-rt3 instead of Ethernet1). Interface ID, MTU and IP address is also in the ICMP extension.

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 a capture and configs here:

https://www.ltri.net/download/19b9cd22-2f03-4d38-9a5e-21b6bd908b33/arista-icmp-error-extensions.tar

Contact me privately (via the methods indicated at ltri.net) and I can provide IPs that route through those RFC5837 enabled Arista nodes.

trippy shows unknown options when running with -e --tui-icmp-extension-mode all.

I will not be able to provide a PR with this feature; my ability stops at checking out and compiling a branch.

CC @ytti

Thanks, Lukas