On 1/30/20 6:54 PM, Mike Wright wrote:
On 1/30/20 3:17 PM, sean darcy wrote:
> On 1/25/20 5:59 PM, Samuel Sieb wrote:
>> On 1/25/20 2:18 PM, sean darcy wrote:
>>> On 1/25/20 3:33 PM, Samuel Sieb wrote:
>>>> On 1/25/20 9:06 AM, sean darcy wrote:
>>>>> On FC31 I can't persistently rename the interfaces, see:
>>>>>
https://bugzilla.redhat.com/show_bug.cgi?id=1777893
>>>>>
>>>>> So I want to use FC31 interface names : enp1s0 and enp0s20u3.
>>>>>
>>>>> I've used nmtui to set up the interfaces. But NM won't
activate
>>>>> them because they are "strictly unmanaged" !!
>>>>>
>>>>> How do I fix that ?
>>>>>
>>>>> Is there some other way to persistently activate the interface ?
>>>>
>>>> What does "nmcli d" show?
>>>> _______________________________________________
>>>
>>> It shows the state as unmanaged.
>>
>> Try "nmcli d set enp1s0 managed on". I'm not sure if that's a
>> persistent change though.
>
> Well that didn't work:
Usually booleans can be expressed as 0/1, false/true, off/on, no/yes,
among others.
However, the nmcli manpage specifically states:
nmcli device set <device> managed { yes | no }
Just for spit and giggles try:
nmcli device set eth0 managed yes
My hunch is the manpage is incomplete. Let us know.
Mike Wright
_______________________________________________
Good idea, but alas, no :
#nmcli d
DEVICE TYPE STATE CONNECTION
eth1 ethernet connected eth1
wlan0 wifi unavailable --
eth0 ethernet unmanaged --
lo loopback unmanaged --
# nmcli device set eth0 managed yes
# nmcli d
DEVICE TYPE STATE CONNECTION
eth1 ethernet connected eth1
wlan0 wifi unavailable --
eth0 ethernet unmanaged --
lo loopback unmanaged --