[Bug 213050] New: More clear default gateway DHCP configuration
https://bugzilla.novell.com/show_bug.cgi?id=213050 Summary: More clear default gateway DHCP configuration Product: SUSE Linux 10.1 Version: Final Platform: i686 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: cmorve69@yahoo.es QAContact: jsrain@novell.com I must say that I do not use DHCP myself. But looking in a problem with another guy I saw this: - I understand that the default gateway can be set by DHCP - Since in /etc/sysconfig/network/dhcp I have by default 'DHCLIENT_SET_DEFAULT_ROUTE="yes"' I suppose that Suse really uses the default gateway that the server sets. - When you use DHCP, in the DNS YaST2 module you have the options "Change Hostname via DHCP" and "Update Name Servers and Search List via DHCP" - When you use DHCP, in the routing YaST2 module you can set the default gateway bbut there isn't any "Update Default Gateway via DHCP" option. So the problem is that the lack of an "Update Default Gateway via DHCP" option when there is the equivalent for DNS is confusing. What an user should think? That default gateway can't be set via DHCP? If he knows is possible he probably will think that Suse isn't able to do it. What if the user doesn't wants to set the default gateway via DHCP but wants to set via DHCP the other network parameters? He will need to modify sysconfig? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213050 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |yast2-maintainers@suse.de |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213050 kmachalkova@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #1 from kmachalkova@novell.com 2006-11-08 05:04 MST ------- Nice enhancement, and this finally can be done in the routing module, but we're far beyond the text freeze. Translated into normal speech - we cannot easily add new UI strings in this phase, because the final round of translations is already over. Will fix for SLE, but I don't expect the fix to appear in the box before 10.3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213050 kmachalkova@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Component|YaST2 |YaST2 Product|SUSE Linux 10.1 |openSUSE 10.3 Resolution| |LATER Version|Final |unspecified ------- Comment #2 from kmachalkova@novell.com 2007-02-09 08:12 MST ------- -> 10.3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213050 User kmachalkova@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=213050#c3 Katarina Machalkova <kmachalkova@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|LATER |FIXED --- Comment #3 from Katarina Machalkova <kmachalkova@novell.com> 2008-09-01 02:54:44 MDT --- Already implemented (yast lan -> Global options) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com