12.3 does not recognize network

English Network/Internet
1

I am a fairly experienced SuSE user. IO recently installed 12.3. The network did not work, and in accessing “Network Settings” I got the diagnostic message “The system network services are not compatible with this version.” The system uses an Intel 82579V network chip, and YAST says that the driver is installed. YAST lets me configure a network for the eth0 device, but it will not work. Accessing it from the “Network Settings” tab in Gnome continues to give the same diagnostic. The network does work on a Scientific Linux 6.4 (modified Red Hat Enterprise) operating system. What’s wrong? How can I install the network?

2

Have you rebooted your system?
https://www.suse.com/releasenotes/x86_64/openSUSE/12.3/#idm47462154155264

Maybe you have to enable DHCP?

To use GNOME’s Network Settings you have to swich to “User-controlled with NetworkManager” in YaST->Network->Network Settings (“Global Options” tab).

3

I have done all the above with no change in behavior.

4

Then please post your repo list:

zypper lr -d

The version of NetworkManager:

rpm -qi NetworkManager NetworkManager-gnome

And the output of this:

/sbin/ifconfig
loginctl
5

eth0 Link encap:Ethernet HWaddr F4:6D:04:59:E9:57
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:18 Memory:fbe00000-fbe20000

eth1 Link encap:Ethernet HWaddr F4:6D:04:59:E1:5B
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:85 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8226 (8.0 Kb) TX bytes:4184 (4.0 Kb)
Interrupt:18 Memory:fb800000-fb820000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:45 errors:0 dropped:0 overruns:0 frame:0
TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6333 (6.1 Kb) TX bytes:6333 (6.1 Kb)

     1       1000 nw               seat0           
     2          0 root             seat0
6

A few additional thing that may be worth mentioning: my ISP is rather fussy about using only IP V.4 protocols, so I reconfigured restricting the network to V.4 - no help; the system boots without errors, but I do not see a network startup in the log.

7

So you have 2 network interfaces, and eth1 appears to be up and running (it has a valid IP address).
So what is exactly your problem now?
You want eth0 as well? Do you have a cable connected there?
Please describe your network setup, what is eth0 connected to?

8

The problem was (was!) that even with this setup I could not access the network, and I continued to get the above mentioned error message. I could ping my network printer, so the basic connection was OK. Doing some looking in the log, I noticed that eth0 was doing a lot of searching and failing. Since it was not connected to anything, the failure was not a surprise, but its continued searches were. I disabled it, and things started working. Thanks.