route

--routev1.9.0

Converts `route` command output to JSON

Linuxcommand

$ route | jc-rs --route

A real pair

From the reference corpus (nixos/route-ee.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.

routenixos

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface    MSS   Window irtt
default         _gateway        0.0.0.0         UG    202    0        0 ens33    0     0      0
192.168.71.0    0.0.0.0         255.255.255.0   U     202    0        0 ens33    0     0      0

expected outputjson

[
  {
    "destination": "default",
    "gateway": "_gateway",
    "genmask": "0.0.0.0",
    "flags": "UG",
    "metric": 202,
    "ref": 0,
    "use": 0,
    "iface": "ens33",
    "mss": 0,
    "window": 0,
    "irtt": 0,
    "flags_pretty": [
      "UP",
      "GATEWAY"
    ]
  },
  {
    "destination": "192.168.71.0",
    "gateway": "0.0.0.0",
    "genmask": "255.255.255.0",
    "flags": "U",
    "metric": 202,
    "ref": 0,
    "use": 0,
    "iface": "ens33",
    "mss": 0,
    "window": 0,
    "irtt": 0,
    "flags_pretty": [
      "UP"
    ]
  }
]

Fixture coverage

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

Magic syntax

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

Source: crates/jc-rs-parsers/src/network/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