Bug 133755

Summary: Refactor routing/dns configuration
Product: [openSUSE] SUSE Linux 10.1 Reporter: Michael Stather <kontakt>
Component: YaST2Assignee: Katarina Machalkova <kmachalkova>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: a.nolting, suse-beta
Version: RC 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Michael Stather 2005-11-14 21:25:39 UTC 
The configuration of the routing (gateway) and DNS/domain are reached by selecting a network interface and "editing" it, so they seem to be specific to each network interface. But they aren´t, there´s only one configuration for the entire system. In the user perspective, if you change the setting in one network interface the changes are applied to all of them. So IMO these settings don´t belong to the network interfaces but to a seperate category, perhaps reachable through the screen with the list of network interfaces. The current solution is very confusing for paople which don´t know linux well enough.
Comment 1 Quentin Jackson 2005-12-21 12:01:51 UTC 
I happen to agree with this also, would be much less confusing, however it may be neccessary to have it there for the sake of simplicity, perhaps a pop up box warning it will change it for all nics would be more appropriate.  Well that's my 2 cents worth anyway.
Comment 2 Michael Stather 2006-01-28 17:45:54 UTC 
As it seems possible to have a specific gateway for each nic but only one computer name and dns-server I suggest to keep the "routing" thing where it is but move the "Hostname and Nameserver" to the parent page.
Comment 4 Martin Vidner 2006-04-21 08:09:13 UTC 
After 10.1
Comment 5 Martin Vidner 2006-08-07 15:05:22 UTC 
*** Bug 195227 has been marked as a duplicate of this bug. ***
Comment 6 Alexander Nolting 2006-08-12 09:16:09 UTC 
A last comment from user side as a experienced user. In earlier versions of SuSE Linux this yast network configuration UI style and it's functional behavior was as it looks for: for each nic your were able to insert and use different dns and routing informations. And as the time comes were it (the configuration part) was changed in its functional behavior, there was no appropriate information in left help sidebar or other obviously way which says the user that the behavior had changed. But for example the UI style and the way user had to configure its nic suggests that all is like it was in other versions before. That has nothing to do with experienced or unexperienced users. It is one the best and strongest things Linux has, that your are able to configure your network you like or need it without any limitations. So please dont follow that "Keep it simple as possible" way and design for yast a network configuration solution that fits the opportunities Linux has.
Comment 7 Martin Vidner 2006-08-28 11:58:41 UTC 
Reassigning to the new co-maintainer of yast2-network.
Comment 8 Martin Vidner 2006-08-28 12:01:01 UTC 
second service...
Comment 9 Katarina Machalkova 2007-02-09 12:28:49 UTC 
-> 10.3
Comment 10 Katarina Machalkova 2007-06-15 12:45:03 UTC 
.
Comment 11 Katarina Machalkova 2007-06-15 12:48:12 UTC 
yast2-network user interface underwent major changes in 10.3. Reference: http://en.opensuse.org/YaST/Network_Card_Module
I think this can be closed as fixed