On 1/9/21 10:59 AM, Neal Gompa wrote:
On Fri, Jan 8, 2021 at 8:52 PM Tejas Guruswamy
wrote: On 07/01/2021 08:43, Neal Gompa wrote:
On Thu, Jan 7, 2021 at 9:23 AM Axel Braun
wrote: ...
2. yast2-network learns how to configure NetworkManager via its API or by writing native NetworkManager keyfiles. This is actually the preferred way to do it, since the keyfiles format is the native format and supports all the features of NetworkManager, including telling NM to use encrypted stores for credentials. This is also the _required_ format for VPN configuration.
The podcaster(s) also noted that setting up YaST Network in the installer but choosing NetworkManager for after install, means (surprisingly to them) a duplicate network setup required after first boot.
Wicked has been broken for years for the desktop, which is why NetworkManager is the default for all cases except for servers. I would actually prefer to change it to NetworkManager for servers too, but that's blocked on fixing YaST.
Not sure if "fixing YaST" is the right wording here. The fact of YaST being wicked-centric instead of NM-centric is a decision, rather than a bug/defect. That being said, there are plans to implement partial support to configure Network Manager through YaST in the future (full-fledged configuration will likely remain out of scope since there are already tons of command-line and graphical tools to configure NM in an already installed system). Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions