[Cooker] [Bug 1146] [Installation] premature network configuration
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.
[Cooker] [Bug 1146] [Installation] premature network configuration
http://qa.mandrakesoft.com/show_bug.cgi?id=1146 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|NEEDINFO --- Additional Comments From [EMAIL PROTECTED] 2003-29-08 16:05 --- I don't see any network installation issues, have you still some ? -- 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.
[Cooker] [Bug 1146] [Installation] premature network configuration
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.
[Cooker] [Bug 1146] [Installation] premature network configuration
http://qa.mandrakesoft.com/show_bug.cgi?id=1146 --- Additional Comments From [EMAIL PROTECTED] 2003-11-06 14:21 --- My recollection from a June 1 cooker (the last I've been able to build - see bug 4039) is that the problem is still there. Basically, MDK is configuring a DHCP lan by default, which doesn't work if the system is static IP, and then 1) Saying in the Summary that the network has been configured, and 2) Warning the installer not to mess with it. MDK ought to be checking to see if the default DHCP configuration actually works. If it does, then the Summary is fine as is. If it doesn't, then the Summary should mark the network as not Configured so the user realizes that he has to do it himself. -- 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: ASSIGNED 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.
[Cooker] [Bug 1146] [Installation] premature network configuration
http://qa.mandrakesoft.com/show_bug.cgi?id=1146 --- Additional Comments From [EMAIL PROTECTED] 2003-11-06 20:35 --- I tried a network NFS install today. The early providing of the network data may have skewed the working of the network configuration from Summary. Anyway, the network showed up as configured lan (no not configured tag), but when I checked Configure and went through autodetect, the only device box checked was the modem. When I went through the configuration, the static info from the network-based install had been propagated to the dialog, except that the hostname field (which the dialog specifies must be filled in with the fully-qualified hostname) had only the simple hostname. This is probably because the network boot prompts have you enter the host and domain names separately. -- 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: ASSIGNED 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.
[Cooker] [Bug 1146] [Installation] premature network configuration
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.
[Cooker] [Bug 1146] [Installation] premature network configuration
http://qa.mandrakesoft.com/show_bug.cgi?id=1146 --- Additional Comments From [EMAIL PROTECTED] 2003-03-07 01:12 --- In todays' cooker, this is ALMOST fixed. The network now shows as not configured when the Summary panel appears initially. However, if you pursue configuration (I checked autodetect and expert), the result of the autodetect has the modem checked (this is correct, there is a modem) but not lan (which should be checked, because there is a 3c905 card that cooker has been detecting all along). If I manually check lan and proceed, the next panel says 3c905C-TX detected, do you have another ?, so the autodetect seems to be working --- it's just that the lan box isn't checked as is should be. Another nit is that if you proceed through the configuration dialog and deselect Automatic IP Address to use a static address, the Assign hostname from DHCP address box is not deselected, and you can't manually deselect it as long as the Automatic IP box is not selected. --- 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.
[Cooker] [Bug 1146] [Installation] premature network configuration
https://qa.mandrakesoft.com/show_bug.cgi?id=1146 --- Additional Comments From [EMAIL PROTECTED] 2003-02-21 23:33 --- Still happening with the Feb 21 cooker --- 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.
[Cooker] [Bug 1146] [Installation] premature network configuration
https://qa.mandrakesoft.com/show_bug.cgi?id=1146 --- Additional Comments From [EMAIL PROTECTED] 2003-02-09 03:23 --- Still happening with the Feb 8 Cooker. --- 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.
[Cooker] [Bug 1146] [Installation] premature network configuration
https://qa.mandrakesoft.com/show_bug.cgi?id=1146 --- Additional Comments From [EMAIL PROTECTED] 2003-02-07 01:57 --- This has changed in today's cooker, but the result is still inconsistent. The Summary panel still shows Network to be configured as lan, even though the configuration was done under the covers and didn't work --- it should show as not configured. However, when I click on that entry, the network dialog no longer has the warning about the interface already being configured (this is correct). If I pursue the configuration dialog, and select autodetect, I still get a display of device options that does not have lan (ethernet) selected even though the line entry for the selection reads LAN connection - ethernet card(s) detected. That selection should be selected. For that matter, I also have a modem in the machine, and even though the first selection reads Normal modem connection - detected on ttyS0, that selection isn't selected either. --- 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.
[Cooker] [Bug 1146] [Installation] premature network configuration
https://qa.mandrakesoft.com/show_bug.cgi?id=1146 --- Additional Comments From [EMAIL PROTECTED] 2003-02-07 02:02 --- Oh, sh$%#. My mistake. The warning doesn't show up until you actually select the lan option and proceed. I came back over here to comment the bug before I did that (I tend to forget details if I don't attend to them immediately). Everything is still the same as it was. --- 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.
[Cooker] [Bug 1146] [Installation] premature network configuration
https://qa.mandrakesoft.com/show_bug.cgi?id=1146 [EMAIL PROTECTED] changed: What|Removed |Added Summary|premature network |premature network |configuration |configuration --- Additional Comments From [EMAIL PROTECTED] 2003-01-31 23:45 --- This is a problem, but I'm not sure it's responsible for the hang. In today's cooker, the only hang I get is the one described by someone in the list, i.e. when the package install gets down to about 10-20 seconds to go, whatever package is being installed (it varies) stops with its progress bar at 100% for minutes at a time. However, when the Summary display comes up, Network shows configured as lan, which is misleading because it has NOT been successfully configured, and if you try to configure it again, you get a warning that it has already been configured and can be left as is, which is incorrect, since the configuration is set to dhcp and my network is not using dhcp. There is one new Network twist today that wasn't there yesterday: if I configure anyway and select autodetection, it autodetects and displays ethernet cards detected, but the lan selection is not selected (this is on the display listing different connection hardware like modem, etc.), giving the impression that autodetect couldn't find the card. --- 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] 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.
