Skip to content

ICMP, Ping, and Traceroute

ICMP powers the most visible diagnostics: ping and traceroute. netverdict uses the same forwarding engine as data traffic, so diagnostic success or failure is tied to real route, ACL, NAT, and firewall state.

AreaLevelNotes
ICMP echoSupportedRequest/reply success and failure.
ICMP errorsBehaviour modelTTL expiry and unreachable-style failures for diagnostics.
PingSupportedDeterministic reachability command.
TracerouteBehaviour modelHop walk through the current forwarding path.
ICMPv6PartialEcho and ND-adjacent paths where implemented.
StandardCoverageNotes
RFC 792Behaviour modelIPv4 ICMP echo/error semantics.
RFC 4443PartialICMPv6 concepts for supported diagnostics.
FeatureStatusNotes
Echo request/replySupportedUses real topology reachability.
Source selectionSupportedInterface/source forms where parsed.
TTL expirySupportedUsed by traceroute.
ACL/firewall interactionSupportedDiagnostics can be denied by policy.
NAT interactionSupportedDiagnostic flows can be translated.
Extended ping optionsPartialCore options only.
CommandIOS-styleJunos-styleVyOS-styleNotes
ping 192.0.2.10SupportedSupportedSupportedICMP echo.
ping vrf BLUE 192.0.2.10SupportedPartialPartialVRF-aware diagnostic.
traceroute 192.0.2.10SupportedSupportedSupportedHop walk.

Ping and traceroute are not fake CLI responses. They ask the forwarding model whether traffic can traverse the topology under the current state.

Canonical example
ping 192.0.2.10
traceroute 192.0.2.10
show ip route 192.0.2.10

Vendor styles

IOS-style
ping 192.0.2.10
traceroute 192.0.2.10
ping vrf BLUE 192.0.2.10
Junos-style
ping 192.0.2.10
traceroute 192.0.2.10
ping routing-instance BLUE 192.0.2.10
VyOS-style
ping 192.0.2.10
traceroute 192.0.2.10
ping 192.0.2.10 vrf BLUE

Payload patterns, every extended ping knob, PMTUD nuance, MPLS traceroute label reporting, and vendor punctuation in output are simplified.