- if you’re on (most modern distributions of) linux, forget that
route(1)even exists (and throw
ifconfigout in the same go) because it’s just absolutely frustrating. for probably 98% of what you need,
ip(1)is the cool you care about
generally speaking, these will cover you:
- when dealing with routing problems (even if just two hosts next to each other),
pingis an order that’s useful for a lot of what you need
mtr is nice because you can just let it keep running. press
d in its display to get a running history breakdown of packets. fantastic for intermittent issues!
traceroute is generally known already, but depending on the complexity of your networks in question you may want
traceroute-nanog or similar other ones. some of these are ASN-aware, which is useful.