Bug 396213 - Can't assign a static ip address via NetworkManager to ethernet interface
Summary: Can't assign a static ip address via NetworkManager to ethernet interface
Status: RESOLVED DUPLICATE of bug 378802
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Network (show other bugs)
Version: RC 1
Hardware: i686 openSUSE 11.0
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Tambet Ingo
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-01 13:22 UTC by Dennis Sieben
Modified: 2008-06-09 08:58 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
The requested yast2 logs (295.94 KB, application/x-compressed-tar)
2008-06-06 20:55 UTC, Dennis Sieben
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Sieben 2008-06-01 13:22:08 UTC
If I try to assign a static ip address with to my ethernet interface on a ThinkPad T61 with the NetworkManager I have no luck. Even if I set the static ip in YaST this doesn't matter. This was running in the last Beta, at least the YaST way brought a result there. But now everything is broken. The only way for me was to set the ip address on the interface with the ifconfig command.

It seems like the static ip change is not correctly send to NetworkManager because you fina messages such as "Activation (eth0) Beginning DHCP transaction." inside the log even after setting the static ip.
Comment 1 Robert Vojcik 2008-06-03 15:08:34 UTC
Hello, 
could you send all yast2 logs ?
If you are unsure follow:
http://en.opensuse.org/Bugs/YaST

Thanks
Comment 2 Dennis Sieben 2008-06-06 20:55:34 UTC
Created attachment 220817 [details]
The requested yast2 logs
Comment 3 Dennis Sieben 2008-06-06 20:56:26 UTC
Removed needinfo state
Comment 4 Dennis Sieben 2008-06-06 21:17:38 UTC
One addition to this. After a restart the ip is set. But nevertheless this is a bug. Don't think we are on windows here, that we have to restart the system after every change ;-) .
Comment 5 Tambet Ingo 2008-06-09 08:58:20 UTC
This is a duplicate of 378802. It's fixed in upstream, but I can't check in this patch for 11.0 anymore. An alternative for rebooting is to kill nm-system-settings process (it gets restarted automatically).

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