http://qa.mandrakesoft.com/show_bug.cgi?id=1146
------- Additional Comments From [EMAIL PROTECTED] 2003-01-09 17:39 ------- I have no quarrel with DHCP by default, and I'm not suggesting that you configure for static IP if you can't bring up DHCP. I'm simply saying that you shouldn't give the user the impression that the network is working when it isn't. Static IP is not just used within companies. Any SOHO user who cares about his machines talking to each other (as opposed to just the gateway) is probably using static IP. Unless you go for dynamic DNS, that's the easiest way to keep server IPs from changing. Maybe you should use a green or red color code on the "Configure" button to indicate working/non-working, and change the text of the button to "DHCP" or "Static". -- 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.
