From all the installs of 12.3 I have completed already and from the comments I have read in our private forum. It’s almost certain that whether you have wired or wireless (or both). Post install, your network will be dead.
Firstly, can I say, that typically I have always used ‘ifup’ on my main box, which only has a wired connection. However, since 12.2 I have changed this setting to Network Manager Controlled. Primary reason for this, is it avoids a bug and my machine boots quicker. I do suggest you use Network Manager, even if you only have a wired connection.
After your 12.3 install completes. Go to Yast > Network Devices > Network Settings
yes i do see this stupid boot delay on 12.2 and switching to NM made a whole lot of difference.
When i used ifup it takes probably a minute to start “NetworkManager.service” and then gives up.NM should never start if i use ifup. i think it is some kind of systemd related issue
I used “start” and that solved the problem for me. I assume that “restart” will just “start” if the network is not currently running.
Apart from that, the network problems of 12.3 RC2 seem to have been solved. Switching from “ifup” to “NetworkManager” with Yast does work. I didn’t try switching the other way.
Quoting from the release-notes:2.2. No Network after Installation
Directly after installation, NetworkManager is not started automatically
and thus WiFi cannot be configured. To enable networking (WiFi), reboot the
machine once manually.
That’s the newly revised release note (via online-update).
I have also found that using NM is faster, but I am not sure why that is true, but worth a try for anyone even though Network Manager is most often used with multiple Wireless connections or when a Wired and Wireless connection exists and both or more connections might be used. ifup has been considered to be best with a single dedicated connection, but from a speed standpoint, NM seems to be the best all around, at least for me using KDE.