diff options
| author | Lubomir Rintel <lkundrak@v3.sk> | 2019-09-12 09:51:06 +0200 |
|---|---|---|
| committer | Lubomir Rintel <lkundrak@v3.sk> | 2019-09-12 09:51:06 +0200 |
| commit | 0a7c87ce4a44289e6d94489e3a800d3a63bf5fd8 (patch) | |
| tree | 38b264cf5c0a27c98be30d1f5f2b30f8d2a781b3 /clients/cli/nmcli.c | |
| parent | 4af856a71bca00c396b0e41fb0bd9f01b6a36a36 (diff) | |
| download | NetworkManager-lr/nmcli-kill-switch.tar.gz | |
cli: add kill switch indication to "nmcli" outputlr/nmcli-kill-switch
There is some guess work done on the client side. Perhaps the
o.fd.NM.Device could be extended to indicate which kill switch is the
device disabled by. This could be good enough for now though.
Diffstat (limited to 'clients/cli/nmcli.c')
| -rw-r--r-- | clients/cli/nmcli.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/clients/cli/nmcli.c b/clients/cli/nmcli.c index 599369bf25..7eb9ef82dd 100644 --- a/clients/cli/nmcli.c +++ b/clients/cli/nmcli.c @@ -52,6 +52,7 @@ [NM_META_COLOR_DEVICE_FIRMWARE_MISSING] = "31", \ [NM_META_COLOR_DEVICE_PLUGIN_MISSING] = "31", \ [NM_META_COLOR_DEVICE_UNAVAILABLE] = "2", \ + [NM_META_COLOR_DEVICE_DISABLED] = "31", \ [NM_META_COLOR_MANAGER_RUNNING] = "32", \ [NM_META_COLOR_MANAGER_STARTING] = "33", \ [NM_META_COLOR_MANAGER_STOPPED] = "31", \ @@ -558,6 +559,7 @@ parse_color_scheme (char *palette_buffer, [NM_META_COLOR_DEVICE_FIRMWARE_MISSING] = "device-firmware-missing", [NM_META_COLOR_DEVICE_PLUGIN_MISSING] = "device-plugin-missing", [NM_META_COLOR_DEVICE_UNAVAILABLE] = "device-unavailable", + [NM_META_COLOR_DEVICE_DISABLED] = "device-disabled", [NM_META_COLOR_DEVICE_UNKNOWN] = "device-unknown", [NM_META_COLOR_MANAGER_RUNNING] = "manager-running", [NM_META_COLOR_MANAGER_STARTING] = "manager-starting", |