12.3 Network Fix - Post Install - Announcement Sticky

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

If Network Manager is already set, you will see a notification of this, which you can click OK to clear
https://dl.dropbox.com/u/10573557/All_Network/NM-ok.png

If it’s not the settings will open to global options, where you use the radio button to toggle to Network Manager
https://dl.dropbox.com/u/10573557/All_Network/NM-toggle.png

Next switch to the Hostname/DNS tab and set/change Hostname as required and I check as shown also
https://dl.dropbox.com/u/10573557/All_Network/Hostname.png

When done click OK to complete any/all changes
And the network should come to life. If it doesn’t, try a reboot.

so ifup in YaST no longer works in 12.3 ?

Yes it does

But I experience a boot issue where a call is made to Network Manager (Which if you are set to ifup) causes a delay in booting.
I had this in 12.2 too

So I just switched to NM

Perhaps I wasn’t clear, sorry.
ifup does work and of course you may not have the boot issue I experience?!

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

If this is as you describe it is realy a bug. A system should be able to run a network without NM even installed without any problems.

maybe a sticky in the Networking and/or Networking Wireless
forum(s) should point to this thread??


dd

I’m pretty sure that rebooting will give you a live network.
Or


# systemctl start network.service

or even


# /etc/init.d/network start

If I recall, this minor glitch was also there in 12.2

You mean “restart”

systemctl restart network.service

Probably everyone should read the “most annoying” stuff from this page openSUSE:Most annoying bugs 12.3 dev - openSUSE Wiki before installation

openSUSE 12.3 RC 1

  • Networking relatednetwork.service may not be running during install 2nd stage: Bug #800365
  • /etc/resolv.conf may not be updated by netconfig on creating new NetworkManager connection [1]](Access Denied)]
  • default route may not be set on first boot after upgrade

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.

By the way, the download site does list 12.3 now.

On 03/13/2013 01:06 PM, nrickert wrote:
> I’m pretty sure that rebooting will give you a live network.
> Or

there is info in the release notes…that seems to not have
rebooting involved…


dd
http://tinyurl.com/DD-Caveat

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).

Thanks! I followed your advice and it makes the boot on a 12.2 much faster!

Good to hear !

Could somebody try if

systemctl disable NetworkManager.service

solved this. If I understand systemd correctly this should disable the NetwokManager.

This solved my problem with 12.3, thank you. :slight_smile:

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.

THank You,

On 2013-03-13 18:36, nrickert wrote:
> Quoting from the release-notes:
> 2.2. No Network after
> Installation

Ugly.

As this was reported in several bugzillas, I don’t understand why they
did not solve it before release :-/


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

Even if they fix it now,the dvd,live cd will never get this fix. 12.3 is doomed .Nah!!!

browsing speed is similar in both for me on GNOME. But there is something going wrong when i boot with ifup on.It takes an extra minute to boot.