ping
--pingv1.11.0Converts `ping` and `ping6` command output to JSON
LinuxmacOSFreeBSDcommand
$ ping | jc-rs --pingA real pair
From the reference corpus (ubuntu-22.04/ping-dest-unreachable.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.
pingubuntu-22.04
PING 10.0.3.22 (10.0.3.22) 56(84) bytes of data. From 10.0.0.1 icmp_seq=1 Destination Host Unreachable From 10.0.0.1 icmp_seq=2 Destination Host Unreachable From 10.0.0.1 icmp_seq=3 Destination Host Unreachable --- 10.0.3.22 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2049ms pipe 3
expected outputjson
Use the Left and Right arrow keys to highlight the matching value in the input.
{ "destination_ip": "10.0.3.22", "data_bytes": 56, "pattern": null, "destination": "10.0.3.22", "duplicates": 0, "packets_transmitted": 3, "packets_received": 0, "errors": 3, "packet_loss_percent": 100.0, "time_ms": 2049.0, "responses": [] }
Fixture coverage
40/40oracle-valid pairs match under the published structural JSON comparison
Magic syntax
jc-rs pingjc-rs runs the command itself and parses what it prints. Recognised for: `ping`, `ping6`Source: crates/jc-rs-parsers/src/network/ping.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