Netwo errorrk Manager в Linux: "Нет подключения к сети", "device is strictly unmanaged "

December

2023

11:52

Netwo errorrk Manager в Linux: "Нет подключения к сети", "device is strictly unmanaged "

linux

22 December 2023 11:52

In one of the experimental attitudes, Linux saw a network error. It is manifested in the fact that Ping passes, but Networkmanager показывает значок "Нет сети" и не работает управление сетью через "Параметры соединений".

Connection parameters - Netwo settingrk Manager (иконка в углу экрана).
If there is a network card, Ethernet connection is added automatically.

Symptoms

Problem No. 1: It is impossible to connect to such a network, error "Connection 'wire connection 1' is notavailable on device eth0 because device is strictly unmanaGed "

Problem No. 2: Netwo network iconrk Manager"Inactive, more precisely shows the absence of a network.

Problem No. 3: does not display "Information about the connection" for the wired connection. It is impossible to see the IP address with a graphic way.

Problem No. 4: The parameters of the compounds - the last use - "Never" .

Solution

1) fix the file/etc/NetworkManager/NetworkManager.conf

sudo nano /etc/NetworkManager/NetworkManager.conf

Instead of [ifPdown] managed=false указать [ifupdown] managed=trUE :

[main]
Plugins = ifpdown, keyfile

[ifupdown]
managed=trUE

[device]
wifi.scan-rand-mac-address=no

This will solve the problem "Device isrictly unmanaGed "

2) make sure that there are no unguided devices in the folder /etc/NetworkManager/
Normally, the following commands should not display anything to the screen:

sudo grep -ri unmanaged-devices /etc/NetworkManager/conf.d/
sudo grep -ri unmanaged-devices /etc/NetworkManager/

4) on the second problem: Add ETHErnet в список исключений неуправляемых устройств в файле /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf

sudo nano /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf

Normally the contents of the file should be:

[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma,except:type:ethernet

If except:type:ethernet нет - добавляем в конец строки ,except:type:ethernet
And save the file.

5) since NETPL is used in modern Linuxan с описанием типичного подключения в конфигурационном файле формата yaml, проверяем netplaN:

ls /etc/netplan/
cat 00-installer-config.yamL.

network:
  renderer: networkD.
  ethernets:
    enp1s10:
      dhcp4: true
      dhcp6: true
  version: 2

The name of the network card must correspond to the display of the command ip a. For example, enp1s10 .

Read more about NetPlan see.article. If the configuration is correct (see above), we use it:

sudo netplan aPPLY

6) Launch and allow the automatic launch of network services:

sudo systemctl start systemd-networkD.
sudo systemctl enable systemd-networkD.
sudo systemctl start NetworkManager.serVice
sudo systemctl enable NetworkManager.serVice

7) re -read the configuration of the Netwo servicerkManager

sudo systemctl reload NetworkManager.serVice

Netwo applet badgerkManager в строке состояния тоже изменяется на символ гнезда RJ-45 проводного подключения.
After the last action, the network appears and can be controlled (the right mouse button - the parameters of the joints).

IPV4 settings by default

Wending connection parameters in Netwoek manager можно менять в соответствии со своими требованиями.
Below was given the default settings:

Basic : "Connect automatically to the network with priority" - 0, "All users can connect to this network."
Ethernet :

Device - ENP2S0
Mtu - automatically
WakE on Lan - by default
Channel coordination - ignore
Parameters IPV4:
Address: 192.168.1.101
Network mask: 24
Gateway: 192.168.1.1

IPV4 addresses can be corrected within certain limits.

Link to Source:
*Ubuntu Error: Connection activation failed: Connection is not available on device because device is strictly unmanaGed

Blog about Radio and Linux