http://bugzilla.novell.com/show_bug.cgi?id=520492 User meissner@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=520492#c1 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |locilka@novell.com |ovo.novell.com | --- Comment #1 from Marcus Meissner 2009-07-14 16:02:41 MDT --- -> yast2-installation. but it will be difficult to detect if there is no dhcp intentional or unintentional... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=520492 User locilka@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=520492#c3 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka@novell.com AssignedTo|locilka@novell.com |mzugec@novell.com --- Comment #3 from Lukas Ocilka 2009-07-15 06:55:37 MDT --- We could use something similar to root-password (not entered in first stage). However, it's not so easy and definitely it's not a Major bug rather an Enhancement. YaST Network could ask user whether they want to configure network manually only in case: * There are some network devices (with link connected, or it is a WiFi) * There is no DHCP offered (/usr/sbin/dhcpcd-test has to be installed) * NetworkManager is NOT installed (if there is a WiFi) As you can see, it's not trivial to find out a user uses static configuration. Moreover, it's not easy to guess what a user really wants without asking them, there are several options how to solve this: * Detect the issue even before the installation is started and ask user in installation proposal. * Detect the issue adjust the second stage accordingly (add non-automatic network-proposal run) -- quite uneasy to do. * Detect the issue and propose to use manual (not automatic) configuration. We currently support just switching to the non automatic configuration. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=520492 User mzugec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=520492#c5 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mschmidkunz@novell.com Info Provider| |mschmidkunz@novell.com --- Comment #5 from Michal Zugec 2009-07-16 04:10:06 MDT --- I see 3 possibilities to solve this problem: 1 - In the very first dialog (when you can change automatic/non-automatic configuration) inform user in case that it's not possible to obtain IP address via DHCP (using dhcpcd-test utility). Some red text - better that popup. I vote for this option. 2 - Same as 1., but in last proposal dialog of 1st stage. Problem is, that we have already too much text there. Disadvantage is that text will be "hidden" 3 - During automatic configuration in 2nd stage when proposed network (using DHCP) is not available, show interactive dialog to configure static IP configuration. But this is IMHO too big untested change with small benefit for "usual" users Martin, what's your opinion? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=520492 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |ASSIGNED -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=520492 https://bugzilla.novell.com/show_bug.cgi?id=520492#c10 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner@novell.com --- Comment #10 from Martin Vidner 2011-06-27 11:11:32 CEST --- The program to use is dhcpcd-test, and we don't use it in YaST now. (We used to call it, not only to detect DHCP but to prefill the static config, which we disabled after it turned out that it triggered a needless address change for existing DHCP leases. Details in bnc#61214) I will provide it in YaPI::NETWORK::DHCPAvailable() BTW, while looking for an appropriate place, I found that there are two places where network can be configured during the 1st stage: 1) inst_lan (yast2-network.rpm) - disabled in SetNetworkActivationModule unless install.inf has ConfigureNetwork=1 2) inst_mode -> inst_network_check -> inst_network_setup Messy :-/ -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=520492 https://bugzilla.novell.com/show_bug.cgi?id=520492#c12 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|mvidner@novell.com | Resolution| |WONTFIX --- Comment #12 from Martin Vidner 2011-08-18 10:53:17 CEST --- IMHO solving the original bug would be overengineering. (especially given the current, er, complexity of the code involved) It is perfectly fine to set up the network after the installation. -- 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.