Bug 8972

Summary:	Consider NetworkManager as full replacement of old ifcfg scripts and make network available when NM is installed
Product:	Mageia	Reporter:	Frank Griffin <ftg>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	Normal	CC:	nic, ouaurelien
Version:	Cauldron
Target Milestone:	Mageia 9
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	networkmanager	CVE:
Status comment:	Old bug. Debate between 2 infrastuctures: one old and less developed upstream, one newer, more robust and more used/developed upstream
Bug Depends on:
Bug Blocks:	7557

Description Frank Griffin 2013-02-05 17:42:59 CET

As installed, NM creates new connections (interfaces) with System Connection unchecked, but Connect Automatically checked..  The effect of this is that NM will not attempt to connect the interface until a user who has configured the connection logs on to a desktop.

Because network-up uses a timeout after which it lets network applications start anyway, this pretty much guarantees that an NM-controlled interface won't be active at the time that most network services start.

Checking System Connection causes NM to bring the interface up during its own startup, and should be the default.

Manuel Hiebel 2013-02-10 13:57:55 CET

Blocks: (none) => 7557

Comment 1 Nic Baxter 2015-02-12 02:26:26 CET

Should this stay open?

CC: (none) => nic

Comment 2 Frank Griffin 2015-02-12 12:50:28 CET

Why not ?  Nobody's made a counter-argument.

Comment 3 Samuel Verschelde 2016-10-15 21:55:31 CEST

Assigning to all packagers collectively since networkmanager has no registered maintainer.

Assignee: bugsquad => pkg-bugs

Comment 4 Frank Griffin 2019-02-19 23:24:42 CET

I'm not sure what's going on here.  There is no longer a System distinction, and I believe that NM activates the connection during boot, but it appears to be activated again when the desktop initializes (you get a popup saying that the interface is up).

Does the desktop popup simply reflect the fact that the interface is already up and this user has access to it ?

Comment 5 Frank Griffin 2020-01-18 06:17:00 CET

Ping ?

Comment 6 Aurelien Oudelet 2021-05-21 02:55:08 CEST

If you follow https://wiki.mageia.org/en/Switching_to_networkmanager 

Under Mageia 8,

Previously configured Ethernet connections (with drakconnect) are activated next reboot with NetworkManager.service and settings are carried over the switch (fixed ip, dns, dhcp,...).

For WiFi connections, I will see this in the next few hours.

CC: (none) => ouaurelien

Comment 7 Aurelien Oudelet 2021-05-22 15:13:23 CEST

Hum, for WiFi connection, it must be configured in drakconnect before for settings being already fulfilled in NetworkManager (NM).

But, you can in facts use NM to set WiFi up, after. To have WiFi enabled at boot time, you have to set password for every users.


But, this bug report is to have NetworkManager enabled and already configured when system is installed with DrakX (Classic ISO) or with Draklive-install.
For now, this is not the case.

Severity: normal => enhancement
Summary: "System Connection" should be on by default for NM => Consider NetworkManager as full replacement of old ifcfg scripts and make network available when NM is installed
Status comment: (none) => Old bug. Debate between 2 infrastuctures: one old and less developed upstream, one newer, more robust and more used/developed upstream
Target Milestone: --- => Mageia 9

Comment 8 Aurelien Oudelet 2021-05-22 15:16:46 CEST

More on this,

The debate was closed in favour on stickying on Mageia Control Centre using ifcfg scripts with drakconnect.

As soon as we have network features not available in drakconnect, but they are in NetworkManager, we will switch.

Remark: GNOME Desktop, too tied to NM, is already switched when installing it from Live ISO (not from Classic ISO).

We could consider switching to NM on Plasma Desktop and other Desktops. But, stick on Drakconnect/ifcfg on server only installation (or without Desktop Session).