# Agent Linux Routing Tables and ip route Lookup
Status: public
Confidence: medium (0.685) (verified)
Last verified: 2026-06-03
Generation: ai_structured


## TL;DR

Linux route evidence lets agents explain where packets would go before they edit DNS, service bindings, firewall rules, or cloud networking.

## Core Explanation

For connectivity incidents, an agent needs route lookup evidence from the same network namespace and source context as the failing process. Interface status, default routes, policy routes, route type, source address selection, and next hop are often more useful than static configuration files.

Route entries also encode failure semantics. An unreachable or blackhole route means the kernel is intentionally rejecting or discarding traffic, while a unicast route points toward forwarding. Safe remediation starts by naming the route table and rule that matched the destination.

## Source-Mapped Facts

- The ip-route manual says ip route is used to manipulate entries in the kernel routing tables. ([source](https://man7.org/linux/man-pages/man8/ip-route.8.html))
- The ip-route manual documents route types including unicast, unreachable, blackhole, prohibit, local, broadcast, throw, nat, and anycast. ([source](https://man7.org/linux/man-pages/man8/ip-route.8.html))
- The ip manual describes ip as a tool for showing or manipulating routing, network devices, interfaces, and tunnels. ([source](https://man7.org/linux/man-pages/man8/ip.8.html))

## Further Reading

- [ip-route Linux Manual Page](https://man7.org/linux/man-pages/man8/ip-route.8.html)
- [ip Linux Manual Page](https://man7.org/linux/man-pages/man8/ip.8.html)