proc-net-ipv6-route
--proc-net-ipv6-routev1.0.0Converts `/proc/net/ipv6_route` file to JSON
Linuxfileslurpable
$ jc-rs /proc/net/ipv6_routeA real pair
From the reference corpus (linux-proc/net_ipv6_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.
/proc/net/ipv6_routelinux-proc
00000000000000000000000000000001 80 00000000000000000000000000000000 00 00000000000000000000000000000000 00000100 00000001 00000000 00000001 lo fe800000000000000000000000000000 40 00000000000000000000000000000000 00 00000000000000000000000000000000 00000100 00000001 00000000 00000001 ens33 00000000000000000000000000000000 00 00000000000000000000000000000000 00 00000000000000000000000000000000 ffffffff 00000001 00000000 00200200 lo 00000000000000000000000000000001 80 00000000000000000000000000000000 00 00000000000000000000000000000000 00000000 00000004 00000000 80200001 lo fe80000000000000020c29fffea4e315 80 00000000000000000000000000000000 00 00000000000000000000000000000000 00000000 00000002 00000000 80200001 ens33 ff000000000000000000000000000000 08 00000000000000000000000000000000 00 00000000000000000000000000000000 00000100 00000004 00000000 00000001 ens33 00000000000000000000000000000000 00 00000000000000000000000000000000 00 00000000000000000000000000000000 ffffffff 00000001 00000000 00200200 lo
expected outputjson
Use the Left and Right arrow keys to highlight the matching value in the input.
[ { "dest_net": "00000000000000000000000000000001", "dest_prefix": "80", "source_net": "00000000000000000000000000000000", "source_prefix": "00", "next_hop": "00000000000000000000000000000000", "metric": "00000100", "ref_count": "00000001", "use_count": "00000000", "flags": "00000001", "device": "lo" }, { "dest_net": "fe800000000000000000000000000000", "dest_prefix": "40", "source_net": "00000000000000000000000000000000", "source_prefix": "00", "next_hop": "00000000000000000000000000000000", "metric": "00000100", "ref_count": "00000001", "use_count": "00000000", "flags": "00000001", "device": "ens33" }, { "dest_net": "00000000000000000000000000000000", "dest_prefix": "00", "source_net": "00000000000000000000000000000000", "source_prefix": "00", "next_hop": "00000000000000000000000000000000", "metric": "ffffffff", "ref_count": "00000001", "use_count": "00000000", "flags": "00200200", "device": "lo" }, { "dest_net": "00000000000000000000000000000001", "dest_prefix": "80", "source_net": "00000000000000000000000000000000", "source_prefix": "00", "next_hop": "00000000000000000000000000000000", "metric": "00000000", "ref_count": "00000004", "use_count": "00000000", "flags": "80200001", "device": "lo" }, { "dest_net": "fe80000000000000020c29fffea4e315", "dest_prefix": "80", "source_net": "00000000000000000000000000000000", "source_prefix": "00", "next_hop": "00000000000000000000000000000000", "metric": "00000000", "ref_count": "00000002", "use_count": "00000000", "flags": "80200001", "device": "ens33" }, { "dest_net": "ff000000000000000000000000000000", "dest_prefix": "08", "source_net": "00000000000000000000000000000000", "source_prefix": "00", "next_hop": "00000000000000000000000000000000", "metric": "00000100", "ref_count": "00000004", "use_count": "00000000", "flags": "00000001", "device": "ens33" }, { "dest_net": "00000000000000000000000000000000", "dest_prefix": "00", "source_net": "00000000000000000000000000000000", "source_prefix": "00", "next_hop": "00000000000000000000000000000000", "metric": "ffffffff", "ref_count": "00000001", "use_count": "00000000", "flags": "00200200", "device": "lo" } ]
Fixture coverage
1/1oracle-valid pairs match under the published structural JSON comparison
Magic syntax
jc-rs /proc/net/ipv6_routejc-rs reads this kernel-interface file directly and dispatches it through the matching /proc parser.Source: crates/jc-rs-parsers/src/proc/proc_net_ipv6_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