On 2020-08-02 21:30, Sam Varshavchik wrote:
ToddAndMargo via users writes:
> On 2020-08-01 16:27, Ed Greshko wrote:
>> [egreshko@meimei ~]$ nmcli device status
>> DEVICE TYPE STATE CONNECTION
>> enp2s0 ethernet connected enp2s0
>> virbr0 bridge connected virbr0
>> vnet0 tun connected vnet0
>> 78:00:9E:27:6B:3D bt disconnected --
>> wlp4s0 wifi disconnected --
>> lo loopback unmanaged --
>> virbr0-nic tun unmanaged --
>>
>
> Ah poop! "disconnected" contains "connected"!
I've been slogging through nmcli too, for unrelated reasons, and invested some time
into read its manual page. Given that:
$ nmcli -t -f general.state device show eth0
GENERAL.STATE:100 (connected)
$ nmcli -t -f general.state device show eth1
GENERAL.STATE:20 (unavailable)
My eth0 is active, eth1 is not.
It isn't clear that a question is being asked.
But, unavailable would often equate to "no carrier".
--
The key to getting good answers is to ask good questions.