On 2020-01-05 14:47, Robert G (Doc) Savage via users wrote:
On Sat, 2020-01-04 at 22:30 -0800, Samuel Sieb wrote:
> On 1/4/20 9:56 PM, Robert G (Doc) Savage via users wrote:
>> # nmcli connection
>>
>> ...
>>
>> eth0: unavailable
>>
>> "Intel Ethernet"
>>
>> ethernet (e1000e), E8:6A:64:35:53:D8, hw, mtu 1500
>
> That looks like the output from "nmcli" by itself. "nmcli
connection"
> or just "nmcli c" should only show one line per connection.
Ah, you're right. Here's the correct output:
# nmcli connection
NAME UUID TYPE DEVICE
ATT9qua6QD 29a52e1f-717d-4e1a-887c-6a0d799a24b6 wifi wlp0s20f3
virbr0 0b4b7d6f-4f0b-46d8-8556-d3c56cc31a02 bridge virbr0
eth0 3a1a7b73-df5e-37b9-a9af-dbc49d4120b3 ethernet --
This still indicates that the eth0 device isn't available.
I don't think that means "unavailable".
If I run "nmcli c down eth0" I get the same output.
I assume you get a time-out if you run
nmcli c up eth0
?
--
The key to getting good answers is to ask good questions.