Red Hat Bugzilla – Bug 374281
Unconfigured wireless devices should not be used
Last modified: 2014-03-16 23:11:26 EDT
Description of problem:
A system was configured with static IP and a specific DNS server on the ethernet
port. Although there is an Atheros wireless card in that system, I was neither
told that it was there nor to configure it. When I booted the system, I
discovered that it's not connected to the internet. It turned out that the
unconfigured wireless interface was brought up and configured with dhclient.
The wireless device associated to some access point and received a different
gateway address. Also, /etc/resolv.conf was overwritten.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Fedora on a system with a wireless and a ethernet device.
2. Configure the ethernet device with a static IP and DNS address during the
3. Reboot the system in presence of a an AP disconnected from network.
The static route is lost, /etc/resolv.conf is lost, the wireless interface is
associated to the AP.
The wireless interface is down, the network settings are preserved.
I can understand when connections are established over unconfigured wired links,
although it would be great if the routes and the DNS servers were fully restored
after the link goes away.
But bringing up wireless interfaces the user wasn't even told about and
connecting to a random AP borders to a crime. In fact, people were arrested and
fined for using unsecured APs without permission.
Unless the user selects ESSID and wireless security settings (possibly "any
ESSID" and "no security"), no wireless device, built-in or hotplugged, should be
brought up, let alone allowed to overwrite user specified DNS configuration.
Technically, they're configured, in that a config file is written. (If you look,
you'll have /etc/sysconfig/network-scripts/ifcfg-<whatever>). But that can be
changed to not configure them to be brought up on boot by default.
Changed in kudzu-18.104.22.168-1/1.2.80-1. Note that this doesn't affect
configurations already written.
kudzu-22.214.171.124-1 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update kudzu'
It's working correctly with the new kudzu. Thank you!
kudzu-126.96.36.199-1 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 249420 has been marked as a duplicate of this bug. ***