http://qa.mandrakesoft.com/show_bug.cgi?id=1146
------- Additional Comments From [EMAIL PROTECTED] 2003-03-13 21:21 ------- One step forward, one step back in today's cooker. On the initial summary panel, the network has gone back to showing as "configured" even though it is not. However, if you proceed to configure it anyway, the autodetect now correctly checks "lan" as something that was detected. The issue is that Mandrake apparently assumes/installs a DHCP client by default, but doesn't (or maybe can't) check to see if that works. As a result, the user is told that his network is configured even though it has not been successfully configured, and will probably not try to configure it correctly because of that. Since nowhere is the user told "we're assuming you use DHCP", the natural inclination is to assume that Mandrake knows what it is talking about and has configured a working network. But, of course, the network *doesn't* work. I think at the least you have to change the "configured" to "defaulted to DHCP", and get the "Warning" out of the Drakconnect dialog unless you have verified that the network, as configured, actually works. ------- 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: UNCONFIRMED 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.
