Bug 1152596

Summary:	improvement during network configuration
Product:	[openSUSE] openSUSE Distribution	Reporter:	ivo grimaldi <ivo.grimaldi>
Component:	Installation	Assignee:	E-mail List <yast2-maintainers>
Status:	RESOLVED FEATURE	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None	CC:	alynx.zhou, ivo.grimaldi, kanderssen
Version:	Leap 15.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description ivo grimaldi 2019-10-01 07:22:46 UTC

Hello everyone
I'm an admin of the Geekos Italia group on Telegram, a support group for openSUSE. 
We have see that, during the installation, most people do not compile the network section, they press "forward" "forward" "forward". In doing so, it does not correctly configure the network and at first reboot start by default wicked instead of Network Manager.
we would like to suggest you to modify the defautl settings, so that they are a little clearer and that you can configure Network Manager.
Thanks in advance for your prompt reply.

Comment 1 ivo grimaldi 2019-10-01 12:20:32 UTC

A solution could be to put Wiked as fallback in case network mmanager is not able to autoconfigure the wifi card.

To avoid such a fallback, also because often after installation and update, putting network manager works, a condition would be needed.

If the wifi card does not self-configure & the network card has a working gateway, switch to wiked, otherwise stay in network manager.

Comment 2 Knut Alejandro Anderssen González 2019-10-09 12:02:25 UTC

I would say that nowadays it is always Network Manager selected as the default backend.

In the past the conditions was.. in case of a laptop (NM) otherwise (Wicked).

The bug was reported for Leap 15.1.. so not sure if was in purpose or not.

Usually the main problem is when configuring the Wifi during installation (that uses Wicked) and then NetworkManager is selected as the default backend.

There will not be network available at all and you must configure the WiFI connection again (we would like to enhance this in the future)

But for the problem described, coud you please attach some logs with the scenario described?

Comment 3 ivo grimaldi 2019-10-09 12:19:44 UTC

it's not a bug but a feature request

Comment 4 Stefan Hundhammer 2019-12-03 11:22:34 UTC

Marked as feature request