Routing table explainer
Paste the output of ip route, netstat -rn or route print to read every route field by field, see which default route wins, and ask which route a destination would use, by longest prefix and then metric.
RetiParsed in your browser: the text never leaves this page, and no route is changed or queried.
The parse runs entirely in your browser on the text you paste: nothing is sent anywhere, and no route is read from or written to any host. Each line is matched against the layout the command's manual documents, every route is reduced to the same fields (destination prefix, next hop, interface, metric, type, protocol, scope, source, table and flags), and the lookup applies basic match, longest match and the lowest metric, the pruning rules of RFC 1812, over the tables a default Linux policy consults. Anything not understood is shown as printed, never dropped.
- ip-route(8), iproute2Route types, tables, and the via, dev, proto, scope, src, metric, onlink and pref fields (read 2026-10-19)
- ip-rule(8), iproute2The three default rules: local, main, default, in that order
- rtnetlink(7)The type, protocol and scope values the kernel defines
- route(8) and netstat(8), net-toolsThe Kernel IP routing table columns and the U H G R D M A C ! flags
- netstat(1), FreeBSD 15.1The BSD flag letters
- netstat.1, Apple network_cmdsThe macOS flag letters (C, c, I, i, m, r, W, Y, g)
- Microsoft Learn, route and The IP routing tableThe route print columns and the lowest-metric rule; Active versus Persistent Routes from KB 2966111
- RFC 1812, section 5.2.4.3Basic match, longest match, and the default route as the route of prefix length zero