http://qa.mandrakesoft.com/show_bug.cgi?id=1146
------- Additional Comments From [EMAIL PROTECTED] 2003-29-08 16:40 ------- The last cooker I built from full install (early August) still had this problem. Let me reiterate: The install assumes that the machine is using DHCP without asking. It sets some default settings that should work for most DHCP clients, and then marks the Network as "Configured" in the summary. In addition, if you check "Configure" to do it yourself, you are warned that Mandrake has already configured the network, and that you don't have to. The problem is that on a fixed-IP machine which will NOT be a DHCP client, the default configuration doesn't (and can't) work. Drakxconnect ought to be able to detect that by trying to bring the network up after doing the default configuration. If the network won't initialize successfully, then it is NOT configured, and the drakxconnect dialog invoked from Summary should NOT say that it is. In other words, assuming a default DHCP scenario is fine, but don't go telling the installer that the network is configured (much less warning him that he doesn't have to try to configure it again) unless you've verified that the default settings you used actually work. Many SOHO users used fixed-IP networks to simplify addressing of server machines, and those new to Linux will believe you if you tell them the network is working when it is not. Worse, they will believe you if you tell them not to mess with your default settings. So, the network won't work, and they won't know what to do about it. -- Configure bugmail: http://qa.mandrakesoft.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. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: NEEDINFO creation_date: description: Today's cooker seems to be deciding that it needs the network before it's been configured from the Network tab of the Summary page. It assumes DHCP, and installs dhcpcd-client, and then appears to hang. The hang is because it is timing out looking for a DHCP server, and there is none. The hang eventually times out, but when I actually get the Summary dialog and go to configure the network, it tells me that the network was already configured and I can leave it as is. It doesn't seem to realize that it never managed to connect with DHCP, and it shouldn't be trying it anyway.
