Re:Traceroute Lies: A Typical Misinterpretation Of Output
by stephengillie on Sunday October 15, 2017 @08:57AM
(#15476919)
Great post. This is a very clear explanation of the routing situation. The last image is especially good.
What's needed is some kind of L2 Traceroute. It's maddening that an increasingly common piece of routing infrastructure is invisible to almost all common troubleshooting tools.
Edit: Cisco has one for their routers [0]. Since each hop would have to be traced locally, an L2 Trace would require orchestrating against all hardware devices in the route which introduces legal complications. A new discovery protocol might be needed.
What's needed is some kind of L2 Traceroute. It's maddening that an increasingly common piece of routing infrastructure is invisible to almost all common troubleshooting tools.
Edit: Cisco has one for their routers [0]. Since each hop would have to be traced locally, an L2 Trace would require orchestrating against all hardware devices in the route which introduces legal complications. A new discovery protocol might be needed.
[0] https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6...