I have a been a openSuSE or SuSE user since 9.3. This is the first time this has happened to me and though it may not apply to the 12.1, it appears to me to be. I have installed 12.1 a second time and the same problem develops. After the initial start the internet service does not come up on the next boot I am using Kubuntu at the moment]. Using YAST [the system comes up fine - but no network connection] I restart the connection, but after the next boot, that does not work either. Another problem that is minor in appearance is that a correct password for login either for the main user or root does not work the first time, but does on the second try. I do slip with my fingers now and then, but it continues to happen with careful typing. I need to know if especially the first one is a 12.1 problem, or where else to turn next. I have perused the forums at this moment and I could not find anyone else with this problem, but unless they have some other machines or systems to log in with I guess they may be out there.
The second of those problem is reported as Bug 728554.
I’m not sure about your first problem. Most people are not having network problems. Some more information would help. Are you getting an IP address? (Check the output of “/sbin/ifconfig -a”).
I am also having problem with my OpenSUSE 12.1. I already tried using 11.4 and so far no problem encountered but upon using the 12.1 I notice that the network interfaces configuration lost. This happens when I configured the network interfaces eth0 and eth1 to use static IP Address. when I hit ifconfig the eth0 and eth1 are nowhere to be seen only lo. I already tried 10x reinstalling but the same problem. I really think that this is a bug as I check for the online update if it will be fixed somehow. Hope it does soon as I will be deploying more server in a couple of days.
an update today when I tried using shorewall. upon installion no proble, using yast. but when I rebooted the server the problem comes in. an error running shorewall and again the network interfaces are gone. even tried rebooting to which the above issue should be fixed but no luck. the worst part is ssh program is dead an unavailable to start. I am not sure why but what I am sure is my shorewall is running OK and all the configurations.
I hope this might help for the next bug release.
Seeing nothing to help here and the BugZilla thread regarding the second problem I found a similar thread. One of the replies suggested some terminal code which did not appear to work for me. A couple replies there talked of resetting the network settings which I do via YAST so that it automatically starts at boot - for which I could find no control via YAST. Venturing on I looked at /etc/sysconfig/ settings via YAST. I went to network then general and changed to yes the connection slow and connected check from default no to yes. I think it was the latter change because the machine responded at that point. At any, then and after a few restarts the network is a go! Plus the login password problem also seems to be gone - I thought they might be related! could be not connected] But it would appear that this is one possible fix. jeffrey K raloff
I have used (open(SUSE) since version 5.x and never had any (home) network problems. I have tried 12.1 from RC1 to the release, and I have the same problem as jkraloff. I set up the network as I had in 11.4 (ifup, dhcp4 +6). ‘rcnetwork restart’ worked sometimes - sometimes no IPv4 address, sometimes no IPv6 address, sometimes nothing- despite changing various setting in /etc/sysconfig/network. At the moment I have binned 12.1 until this bug is sorted. Ivan G. Russell
Same problem. No Internet connection and I have no clue how to fix it.
My network isn’t working in openSUSE 12.1 either. I’ve used the same settings I use in my current openSUSE 11.4 installation that works without any network problem:
=== Global Options ===
Network setup method: Traditional method with ifup
Name Server 1: 192.168.1.1 (this is my ADSL router)
Default IPv4 Gateway: 192.168.1.1
=== eth0 (cable connected) ===
Activate device: On Cable Connection (I’ve also tried “At Boot Time”; but it made no difference)
ifplugd priority: 0
Statically assigned IP address: 192.168.1.2
Subnet mask: /24 (meaning 255.255.255.0 apparently)
=== eth1 (cable not connected) ===
Activate device: On Cable Connection (I’ve also tried “At Boot Time” and “Never”; but it made no difference)
ifplugd priority: 0
Statically assigned IP address: 192.168.1.3
Subnet mask: /24
My motherboard has 2 ethernet ports and I use one of them. I’ve also tried swapping the connected ports. After an hour of trial & error, network service and PC restarts I got frustrated and gave up. Back to 11.4 now. 
Any pointers would be appreciated.
I forgot to add:
I get the following message (repeatedly) when I try to ping 192.168.1.1, 192.168.1.2 or 192.168.1.3 :
From 192.168.1.2 icmp_seq=1 Destination Host Unreachable
…
…
There are no error messages when I restart the network service via:
service network restart
Thanks in advance for your time & suggestions.
Most people are not having network problems. Some more information would help. Are you getting an IP address? (Check the output of “/sbin/ifconfig -a”).
Looks like I have same issue - I get IP from DHCP, but no default gateway set when system starts.
Currently I use workaround:
killall dhcpcd (wait 10 sec)
dhcpcd wlan0
This time default gateway is set correctly and internet works fine
I wonder has anybody already filed a bug report for this issue?
I have exactly the same problem. Are there any suggested workarounds so we don’t have to manually restart dhcpcd after every boot?
I think I know what’s happening, at least in my case. The first clue is (surprise!) in /var/log/messages:
dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
This message comes from /etc/netconfig.d/dns-resolver. A quick look at that code shows a reference to a function called netconfig_check_md5_and_move located in /etc/sysconfig/network/scripts/functions.netconfig. This function checks /etc/resolv.conf against an MD5 hash in /var/adm/netconfig/md5/etc/resolv.conf. If the current /etc/resolv.conf file doesn’t match the hash, the function doesn’t update /etc/resolv.conf. This is fine if you only connect to a single network and the nameserver values in /etc/resolv.conf are appropriate for that network. If you move between networks, your /etc/resolv.conf may refer to a previous network’s currently unreachable nameservers so no Internet for you! :’( Running dhcpcd manually bypasses all of this logic and overwrites /etc/resolv.conf with values appropriate for your current network. Of course, this puts it out of sync with the MD5 hash in /var/adm/netconfig/md5/etc/resolv.conf so dns-resolver will never update resolv.conf again.
I was able to fix my problem by doing the following:
- sudo rm /etc/resolv.conf
- sudo rm /var/adm/netconfig/md5/etc/resolv.conf
- reboot
Now, my resolv.conf is properly updated and I can get to the Internet without manually running dhcpcd.
After much messing about, I’ve got it going! Remove package “systemd-sysvinit” and replace with the old “sysvinit”.