Bugzilla – Bug 115448
Wlan interface is set up per default
Last modified: 2005-11-08 09:25:58 UTC
This is a installation of beta4plusplus YaST network proposal was dhcp for wlan interface and no config for wired interface. Of course internet connection test failed. Some info: - first device in lspci output: wired - first device in hwinfo --netcard output : wired - eth0: wired Why did YaST choose the wlan interface? If you don't know, whcih interface to choose, check if the wired interface has a link.
After internet connection test failed i went back to network configuration. In network card configuration overview i selected the wlan device and pressed 'delete'. Then i selected wired device and pressed 'edit'. Left dhcp default, Next, Next. Connection test failed again, because both interfaces were up with dhcp. The configuration file for the wlan device was still there
Wifi is explicitly preferred: http://w3d.suse.de/ext/features/configuration_network.html#configuration_network_wlan-config A shortcoming is that currently we can propose only one NIC. I don't see why the connection test should fail if both interfaces are up. But if you deleted one, it shouldn't stay up, of course. Please attach y2logs.
Created attachment 48981 [details] y2log of this machine
If you set up both with ifplugd, that would be fine. But only wlan is just guessed. And if wired has a link ... The test failed because there was no default route and possibly no nameserver. wlan interface had no address but was up. dhcp was running for both interfaces. The problem is that i told YaST to delete the wlan config and it did not delete it. So reload just set up wired additionally. But since there was already a dhcp running for wlan it did not set default route and nameserver. Known problem with two dhcp simultaneously. (use iflugd instead). Just to propose wlan is not a good idea.
I have located the problem with not deleting a configuration (it is related to bug 49859). As for using ifplugd by default, it is unfortunately quite late. Is it worth risking breakage at this point?
But the feature, to set up wlan automatically, is a bad feature. In most cases you will need manual interaction to set up a wlan device. Just setting dhcp and make the user believe that this might work is bad. You have the information 'link detected' from hwinfo. Even if you cannot rely on 'wlan no link', you can rely on 'wired link'. And ifplugd? We fixed that in the last days to work better with wlan devices (we don't really use ifplugd for a wlan device, but only use the ifplugd for the wired device to decide, which of the interfaces should be up. I would enable that per default on laptops, but aj has to decide.
Well, originally we rejected the feature because it uses no encryption by default. But there is a red warning and a direct hyperlink to set up wifi. See the discussion in the feature (comment 2). Or do you see other problems than that? Andreas, how about changing to use ifplugd by default? Back when it was discussed on suse-network http://mailman.suse.de/mlarch//SuSE/suse-network/2005/suse-network.2005.05/msg00005.html theer were objections that it does not work with wifi but as Cristian says it has been worked around lately.
Let's stay with the current status.
yast2-2.12.27 fixes deleting an interface during the installation after it has been written already.
*** Bug 115854 has been marked as a duplicate of this bug. ***
*** Bug 117005 has been marked as a duplicate of this bug. ***
Let's use ifplugd everywhere if this is the solution - and let's do this asap for STABLE.
yast2-network-2.13.0 uses ifplugd by default for all network cards. So ifplugd.rpm should go to the default selection, I think. Currently it is only in Laptop.
Only default or even minimal selection?
That depends on what the policy rules for the minimal selection are. Who decides? Yast is in miniml and by default it will require ifplugd. As always it will invoke the installer if the package is not there. Ifplug is only 90KB.
And it only rquires glibc. Andreas should decide.
Add it to minimal.
fixed.
*** Bug 121971 has been marked as a duplicate of this bug. ***
*** Bug 131625 has been marked as a duplicate of this bug. ***