Bug 731756

Summary: Yast2 network will not assign a static ip properly to eth0
Product: [openSUSE] openSUSE 12.1 Reporter: James Rome <jamesrome>
Component: NetworkAssignee: Martin Vidner <mvidner>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Critical    
Priority: P5 - None CC: bwiedemann, engineering, forgotten_RXJHfymTBF, mfilka
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description James Rome 2011-11-21 16:26:26 UTC
User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2

I have reinstalled the release version of 12.1 3 times now with the same result.
The default setup has networking working with DHCP. But I need a static address.
I go into yast2 and look. The default configuration has a static address with ip=0.0.0.0 and mask=/32, and no gateway. very strange.
I change it, the way I have been doing since SuSE 8:
ip=192.168.1.13
mask=255.255.255.0
gateway=192.168.1.1
dns=75.75.75.75 and 75.75.76.76
hostname=jarfx

And as soon as I exit yast, networking dies. And I cannot get it back again by undoing the above. I am totally frustrated! I also tried installing sysvinit-init, but this did not help.

I can get networking back by choosing NetworkManager, but that is unsuccessful at changing the ip address to a static one.


Reproducible: Always

Steps to Reproduce:
1. Clean install of 12.1. Networking works, but ip address is set to static and 0.0.0.0/32
2. Try to change ip to a static one as above.
3. Networking dies when yast tries to start it, and nothing brings it back
Actual Results:  
Networking dies

Expected Results:  
shopuld get a static address and should work
Comment 1 James Rome 2011-11-21 16:44:59 UTC
This has something to do with the fact that there is now a device br0. I am thinking this is related to xen. But there are no instructions I can find on how to configure br0 + eth0. I changed something by configuring br0, and networking started again. But as soon as I tried to set a static address, it died again and would not come back.
Comment 2 steve edmonds 2011-11-25 01:16:47 UTC
I just file a bug 732696, may be related, found it by setting a static address.
After you change to your static settings and finish yast, run sudo /sbin/ifup eth0 and see if eth0 comes up (steve@linux-vlkq:~> /sbin/ifconfig)
Comment 3 Forgotten User RXJHfymTBF 2011-11-28 10:34:31 UTC
Having similar situation when changing from DHCP to static IP Using NetworkManager. NM asks for authentication first, then after I enter the required IP information and click "Save", the authentication screen pops up for a second and then NM settings window closes without saving the static IP, and connection drops.
Comment 4 Forgotten User RXJHfymTBF 2011-11-30 14:56:15 UTC
The Network Manager static IP error has been fixed with the latest (30th Nov 2011) update.
Comment 5 James Rome 2011-11-30 15:46:57 UTC
So, if you install Xen, what is the proper procedure for setting up a static address for the OpenDSUSE desktop, given just one card?
Comment 6 Bernhard Wiedemann 2011-12-22 13:44:08 UTC
When you install xen, it will automatically setup br0 as bridge that contains eth0. This means that eth0 MUST NOT have an IP-Address other than 0.0.0.0/32 in order for networking to work.
To setup a static IP-Address, you edit the bridge's configuration instead.
/etc/sysconfig/network/ifcfg-br0 is the raw config, if you don't want to use yast2 lan
Comment 7 Michal Filka 2012-03-15 12:10:28 UTC
same as bnc#732696
workaround which works for me: reboot with statically assigned IP.

*** This bug has been marked as a duplicate of bug 732696 ***