← All posts Networking

Use ip route get to prove the Linux route for one destination

The Tryssh team ·

For ip route get, the safest approach is a bounded operational change, not a command pasted without context. This runbook starts with effective state, shows the smallest candidate action, and finishes by repeating the real user or system path.

TL;DR: Ip route get asks the kernel how it would route a specific flow, including source address, interface, gateway, table, and policy results. Capture a baseline with ip -br address, make the reviewed change only when the evidence matches, then verify with ip route get 203.0.113.10 and keep the rollback ready.

Audience: operators who understand IP addresses and ports and can capture bounded network evidence without collecting payloads unnecessarily. This guide assumes familiarity with Linux networking and a change window appropriate to the system.

Use ip route get to prove the Linux route for one destination observe, interpret, change, and verify workflow

The direct answer

The selected source, table, next hop, and interface match the intended topology and the real flow succeeds. That is the success condition for ip route get; command completion by itself is not enough.

The important boundary is name resolution, route selection, neighbor reachability, firewall policy, transport state, and application listener. Ip route get asks the kernel how it would route a specific flow, including source address, interface, gateway, table, and policy results. If an observation does not identify which side of that boundary failed, collect a narrower observation before changing state.

How the mechanism works

For ip route get, use this mental model: a connection moves from a name to an address, through route and policy lookup, into a transport socket, and finally to the process bound to the selected address and port. The model prevents a common mistake—treating configuration text, control-plane acceptance, process state, and end-user behavior as the same proof.

Follow four stages:

  1. Observe: identify the exact host, object, version, owner, and active configuration.
  2. Interpret: write the expected result, the abnormal result, and what would remain inconclusive.
  3. Change: apply one reviewed action at the narrowest layer that contradicts the baseline.
  4. Verify: repeat the original path and compare the same evidence, including adjacent safety controls.

Preflight and safety boundary

Preserve a second management path before changing routes, resolver state, interfaces, or firewall rules, and redact payloads and private topology from captures.

Before ip route get, record UTC time, the current version or digest, the exact target, recent changes, and who owns the workload. The rollback for this runbook is: keep a timed or out-of-band rollback, restore the captured route exactly, and verify both forward and return paths.

Do not continue if the target identity is ambiguous, the current state cannot be saved, the only recovery session would be at risk, or the proposed command affects more objects than the brief names.

Capture the read-only baseline

Run these commands one at a time. Replace example names and addresses deliberately; do not paste production secrets into a transcript.

ip -br address
ip rule show
ip route show table all
ip route get 203.0.113.10

Interpret the baseline before moving on:

  • Expected: the selected source, table, next hop, and interface match the intended topology and the real flow succeeds.
  • Abnormal: policy rules select another table, the next hop is unreachable, or return traffic uses a different path.
  • Inconclusive: missing output can also mean the wrong context, permissions, namespace, log window, binary, or target. Prove those assumptions before treating absence as health.

Save the decisive output, exit status, and timestamp. Redact credentials, customer data, private topology, tokens, and complete environment dumps.

Apply the smallest candidate change

The following is state-changing example syntax, not an instruction to run it unchanged:

sudo ip route replace 203.0.113.0/24 via 192.0.2.1 dev eth0

For ip route get, the proposed change is acceptable only when the read-only baseline predicts its effect and the rollback is available. The key risk is: replacing a route over SSH can sever the management session and every flow sharing that prefix.

Prefer an immutable artifact, validated configuration, dry-run, transaction, candidate object, or staged target when the tool supports one. Record the exact command and UTC time so later telemetry can be correlated to the change.

Verify the result from the outside in

ip route get 203.0.113.10
ping -c 2 192.0.2.1
curl --connect-timeout 5 http://203.0.113.10/

Verification for ip route get has three layers:

  1. The control plane or command reports the intended effective state.
  2. The process, resource, or data path reflects that state without a new pressure signal.
  3. The original user-visible or dependent-system path succeeds from an independent vantage point.

If ip route get 203.0.113.10 succeeds but the original path still fails, stop. The change may have repaired a local symptom while DNS, policy, routing, caching, dependency, or client state remains broken.

Failure branches

The baseline does not match this runbook

When policy rules select another table, the next hop is unreachable, or return traffic uses a different path, do not force the candidate command. Return to identity and scope, compare a healthy peer only through effective settings, and name a new falsifiable mechanism.

The change succeeds but behavior does not

A successful sudo ip route replace 203.0.113.0/24 via 192.0.2.1 dev eth0 proves that one interface accepted a request. It does not prove convergence, readiness, data compatibility, external routing, or client recovery. Re-run the same evidence at each downstream boundary.

The change makes the system worse

Execute the written rollback: keep a timed or out-of-band rollback, restore the captured route exactly, and verify both forward and return paths. Preserve the failed candidate and relevant logs long enough to explain the outcome; do not destroy the evidence with broad cleanup or repeated restarts.

Operator checklist

  • Confirm the exact target, context, identity, version, and active owner.
  • Capture the read-only baseline and one disconfirming observation.
  • Label sudo ip route replace 203.0.113.0/24 via 192.0.2.1 dev eth0 as state-changing during review.
  • Keep recovery access and rollback independent of the path being edited.
  • Change one layer, record UTC time, and wait for its real convergence boundary.
  • Verify the original path, adjacent controls, resource pressure, and persistence.
  • Update the runbook when observed behavior differs from the source-reviewed model.

Investigate it in Tryssh

Tryssh keeps the command, approval boundary, output, and verification beside the host conversation.

Tryssh can preserve this evidence loop and show a state-changing command for human approval. It does not make the operator's identity, recovery access, rollback, or platform authority decisions.

Evidence and review status

This ip route get runbook was source-reviewed on 2026-07-29 against current first-party documentation. The commands are illustrative and use example targets. The page does not claim that the change was reproduced across every distribution, managed service, version, network, or workload.

Limitations and trade-offs

Replacing a route over SSH can sever the management session and every flow sharing that prefix. Managed platforms may generate configuration, restrict privileges, replace local state, or expose a different control plane than the upstream project. Confirm the installed version and provider contract before applying a repair.

Search visibility is not proof of operational correctness. Treat this page as a decision aid, preserve independent recovery, and stop when the evidence contradicts its assumptions.

Related operator runbooks

Continue with systemd-resolved troubleshooting, mtr vs traceroute, the Linux networking foundation guide, and the SSH hardening checklist.

Sources and further reading