ip-route

--ip-routev1.0.0

Converts `ip route` command output to JSON

Linuxcommandslurpable

$ ip route | jc-rs --ip-route

A real pair

From the reference corpus (ubuntu-18.04/ip_route.json). The left pane is the input the fixture ships; the right pane is the corpus's expected JSON. CI compares jc-rs with it field by field under the published differential. Hover a value to see where it came from.

ip routeubuntu-18.04

default via 10.0.2.2 dev enp0s3 proto dhcp metric 100
10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100
169.254.0.0/16 dev enp0s3 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown

expected outputjson

[
  {
    "ip": "default",
    "via": "10.0.2.2",
    "dev": "enp0s3",
    "proto": "dhcp",
    "metric": 100
  },
  {
    "ip": "10.0.2.0/24",
    "dev": "enp0s3",
    "proto": "kernel",
    "scope": "link",
    "src": "10.0.2.15",
    "metric": 100
  },
  {
    "ip": "169.254.0.0/16",
    "dev": "enp0s3",
    "scope": "link",
    "metric": 1000
  },
  {
    "ip": "172.17.0.0/16",
    "dev": "docker0",
    "proto": "kernel",
    "scope": "link",
    "src": "172.17.0.1",
    "status": "linkdown"
  }
]

Guides using this parser

Native JSON or jc-rs? →

Fixture coverage

2/2oracle-valid pairs match under the published structural JSON comparison

Magic syntax

jc-rs ip routejc-rs runs the command itself and parses what it prints. Recognised for: `ip route`

Source: crates/jc-rs-parsers/src/network/ip_route.rs. jc-rs targets the schemas defined by the original Python tool. Fixture coverage above is the measured evidence for this parser; test the inputs your pipeline depends on. Compare