iwconfig

--iwconfigv1.2.0

Converts `iwconfig` command output to JSON

Linuxcommand

$ iwconfig | jc-rs --iwconfig

A real pair

From the reference corpus (generic/iwconfig.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.

iwconfiggeneric

wlp5s0    IEEE 802.11  ESSID:"BLABLABLA"  
          Mode:Managed  Frequency:5.18 GHz  Access Point: E6:63:DA:16:50:BF   
          Bit Rate=6 Mb/s   Tx-Power=30 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=58/70  Signal level=-52 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:1766   Missed beacon:0

expected outputjson

[
  {
    "name": "wlp5s0",
    "protocol": "IEEE 802.11",
    "essid": "BLABLABLA",
    "mode": "Managed",
    "frequency": 5.18,
    "frequency_unit": "GHz",
    "access_point": "E6:63:DA:16:50:BF",
    "bit_rate": 6.0,
    "bit_rate_unit": "Mb/s",
    "tx_power": 30,
    "tx_power_unit": "dBm",
    "retry_short_limit": 7,
    "rts_threshold": false,
    "fragment_threshold": false,
    "power_management": true,
    "link_quality": "58/70",
    "signal_level": -52,
    "signal_level_unit": "dBm",
    "rx_invalid_nwid": 0,
    "rx_invalid_crypt": 0,
    "rx_invalid_frag": 0,
    "tx_excessive_retries": 0,
    "invalid_misc": 1766,
    "missed_beacon": 0
  }
]

Fixture coverage

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

Magic syntax

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

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