Another problem with the network, a machine after upgrade from 12.3 to 13.1 (zypper dup method), as always, at the first boot the eth0 device is renamed to ens3. After applying the suggested workaround, to reverse to the old network device naming method (ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules), finally the eth0 come up... BUT! no ip address is assigned to it, and the config files appears to be right: cat /etc/sysconfig/network/ifcfg-eth0 BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='192.168.90.30/24' MTU='' NAME='RTL-8139/8139C/8139C+' NETMASK='255.255.255.0' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' also, no changes with a rcnetwork restart. No strange errors into messages: 2013-11-29T15:32:06.604297+01:00 linux-msvu systemd[1]: Starting LSB: Configure network interfaces and set up routing... 2013-11-29T15:32:12.446662+01:00 linux-msvu network[4124]: Setting up network interfaces: 2013-11-29T15:32:16.216453+01:00 linux-msvu network[4124]: lo 2013-11-29T15:32:16.854238+01:00 linux-msvu network[4124]: lo IP address: 127.0.0.1/8 2013-11-29T15:32:18.440045+01:00 linux-msvu systemd[1]: Starting ifup managed network interface eth0... 2013-11-29T15:32:25.953618+01:00 linux-msvu systemd[1]: Started ifup managed network interface eth0. 2013-11-29T15:32:26.197811+01:00 linux-msvu network[4124]: ..done..doneSetting up service network . . . . . . . . . . . . ...done Also, yast reports the correct configuration of the network interface, but is not activated. What can be? As i can see, this problem is not present in 64bit version. Cordially, Claudio. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org