Maybe network.service isn’t started correctly? Type in
systemctl status network.service
when it doesn’t work after reboot.
And see also here, maybe that helps:
https://www.suse.com/releasenotes/i386/openSUSE/12.3/RELEASE-NOTES.en.html#sec.123.systemd-nm
Ok at first I thought it’s because of nm then I added NETWORKMANAGER=“no” into /etc/sysconfig/network/config
Then I remembered it could be the ifconfig inside /etc/init.d/boot.local so there I changed it to ifup eth0 and it works now.
Thanks for helping out.
That variable (“NETWORKMANAGER”) isn’t used anymore on 12.3.
Then I remembered it could be the ifconfig inside /etc/init.d/boot.local so there I changed it to ifup eth0 and it works now.
Thanks for helping out.
Why do you have that in /etc/init.d/boot.local? I didn’t have that in any (open)SUSE I’ve used so far. (I started with SuSE 8.1)
Just enable network.service like explained in the link above and all configured devices should be set up automatically on boot.
Got several scripts in that file, to execute on boot, just preference.
There seems to be a difference between “ifup eth0” and “ifconfig eth0 up”
If the interface is started with ifup it’s working, if started with ifconfig it fails.
This was not the case in 12.2 so I guess it may be a bug, or some form of regression.
Hm, I never used ifconfig for setting up network interfaces, always ifup.
Btw, from ifconfig’s man page:
**WARNING: **Ifconfig is obsolete on system with Linux kernel newer than 2.0. On this system
you should use ip. See the ip manual page for details
and this was added in 2008 with this changelog entry:
Tue Mar 4 10:30:18 CET 2008 - ms@suse.de
- added obsolete warning for ifconfig into man page (bnc #366477)
See also Access Denied
So it’s not that surprising if it doesn’t work anymore on kernel 3.7.10 I would say.
Regarding your setup: OK, fine with me, you can do it as you like. But how do you expect help from others when you have such a non-standard setup and don’t even mention it? :sarcastic:
Anyway, great that you got it working! 
Been looking at this “ifconfig” transition to “ip” for awhile.
IMO for now they can be used interchangeably, but moving towards the future “ip” should be used instead of “ifconfig.” I still believe “ifconfig” displays information more logically, but “ip” displays more complete information.
Yes, “ifup” is different than “ifconfig ifup” – IIRC it’s in the MAN pages. Can be significant, is not a bug and can be used to troubleshoot what ails your situation.
I highly recommend you browse the files at
/etc/sysconfig/network
These are the files YAST should be writing to, if you find something that isn’t correct AFAIK you can edit these files directly without a problem.
One or more of the files there should relate to your interface (likely ifcfg-eth0). Doublecheck that the contents do contain the following which would enable DHCP
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
HTH,
TSU