Bug 130456 - Usability issue with network configuration: default gateway
Summary: Usability issue with network configuration: default gateway
Status: RESOLVED DUPLICATE of bug 44721
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Martin Vidner
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-25 10:47 UTC by Kaushal Kumar
Modified: 2005-11-03 15:39 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kaushal Kumar 2005-10-25 10:47:10 UTC
In the Network Address Setup, the 'Default Gateway' field does not have an 'Update via DHCP' option.

For DHCP,
- If the field is left blank, it internally updates the gateway via dhcp.
- If it is not left blank and is provided with a gateway ip, it makes the network unreachable.

For my production network, I was giving 164.99.152.1 as default gateway. Though, all the settings were correct, the network was still unusable. Then, got to know from IS&T that route needs to be left blank in dhcp configuration. So, it worked finally.

However, for an end user, it is difficult to guess this. It would be nice if an 'Update via dhcp' is provided below 'Default Gateway'. It would give a clue to the user that dhcp can provide the gateway, if it is left blank.
Comment 1 Michael Gross 2005-10-25 13:31:26 UTC
Sounds plausible.
Setting this to an enhancement for 10.1
Comment 2 Martin Vidner 2005-11-03 15:39:41 UTC
I am working on a better layout.

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