Bugzilla – Bug 131117
random changes of wlan essid to "any"
Last modified: 2005-12-19 20:58:49 UTC
How to repoproduce: 1. Configure wlan0 in YaST2. 2. Manually change /etc/sysconfig/network/ifcfg-wlan-id-* WIRELESS_ESSID="any" to name of preferred ESSID (there is no GUI tool to set it - see bug 118765). 3. Test - wireless works. 4. Add new sound card (in my case it was hotplugged usb0). 5. Configure new card in YaST2 network configuration. Actual result: Your WIRELESS_ESSID is lost. Wireless connects to bad AP. Expected result: Do not reset wireless configuration while adding usb0.
Martin and Ladislav: Can you take care of that, please?
Always, always attach the logs, please. http://www.opensuse.org/Bug_Reporting_FAQ#YaST Anyway, that other bug makes me wonder: did you use yast2 sysconfig in step 1 instead of yast2 lan? If yes, why?
Created attachment 56033 [details] y2log.bz2
I think that the sound configuration is not related to the ESSID problem at all. ESSID is probably changed by the network module.
Sorry for typo - usb0 was not a sound card, but network card. < 4. Add new sound card (in my case it was hotplugged usb0). > 4. Add new network card (in my case it was hotplugged usb0).
(Sound is not involved, so removing Lada.) The log shows (grep ESSID) that WIRELESS_ESSID in ifcfg-wlan-* was always set to either "wia" or "any", never "". And if you had it set on any, no wonder it could connect to a different AP. A possible problem *might* be that after changing the essid in yast, iwconfig could not pass it to the driver. But that is only my guess. Can you reproduce and describe the problem in more detail? Check the ifcfg contents and iwconfig output after yast runs.
I cannot reproduce. It is possible, that this change was not done by YaST, but by netapplet. But I cannot reproduce this with netapplet anyway.
Reopening. The overwrite ocurred after use of kismet or after subsequent rcnetwork restart. # ls -al --full-time /etc/sysconfig/network/ifcfg-wlan* -rw-r--r-- 1 root root 665 2005-11-23 10:02:27.000000000 +0100 /etc/sysconfig/network/ifcfg-wlan-id-00:60:b3:6b:d3:c5 /var/log/messages: Nov 23 10:02:08 utx kernel: device wlan0 entered promiscuous mode Nov 23 10:02:21 utx SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled. Nov 23 10:02:21 utx SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... Nov 23 10:02:22 utx SuSEfirewall2: batch committing... Nov 23 10:02:22 utx SuSEfirewall2: Firewall rules successfully set Nov 23 10:02:23 utx syslog-ng[3663]: Changing permissions on special file /dev/xconsole Nov 23 10:02:23 utx syslog-ng[3663]: Changing permissions on special file /dev/tty10 Nov 23 10:02:23 utx dhcpcd[4898]: terminating on signal 15 Nov 23 10:02:23 utx modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.wlan0 to /etc/resolv.conf Nov 23 10:02:24 utx kernel: device wlan0 left promiscuous mode Nov 23 10:02:24 utx kernel: wlan0: New link status: Disconnected (0002) Nov 23 10:02:25 utx SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled. Nov 23 10:02:25 utx SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... Nov 23 10:02:25 utx SuSEfirewall2: batch committing... Nov 23 10:02:25 utx SuSEfirewall2: Firewall rules successfully set Nov 23 10:02:26 utx SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled. Nov 23 10:02:26 utx SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... Nov 23 10:02:26 utx SuSEfirewall2: batch committing... Nov 23 10:02:26 utx SuSEfirewall2: Firewall rules successfully set Nov 23 10:02:26 utx kernel: wlan0: New link status: Association Failed (0006) Nov 23 10:02:26 utx SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled. Nov 23 10:02:26 utx SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... Nov 23 10:02:27 utx SuSEfirewall2: batch committing... Nov 23 10:02:27 utx SuSEfirewall2: Firewall rules successfully set Nov 23 10:02:27 utx kernel: wlan0: New link status: Disconnected (0002) Nov 23 10:02:28 utx kernel: wlan0: New link status: Connected (0001) y2log does not contain any message in this time.
Created attachment 58864 [details] /etc/sysconfig/network/ifcfg-wlan-id-00:60:b3:6b:d3:c5 Overwritten file.
Created attachment 58865 [details] /etc/sysconfig/network/ifcfg-wlan-id-00:60:b3:6b:d3:c5 Previous version of this file restored from backup.
I doubt that rcnetwork or kismet would overwrite an ifcfg, but let's have the maintainers confirm that. I think that a way to find out the culprit is using lastcomm (acct.rpm), when the problem happens yet again.
No script from sysconfig writes ifcfg-* files. But i remember net-applet which did. But afaik we don't have net-applet anymore (i'm not sure). Marian, Kismet?
kismet doesn't touch the ifcfg
then try lastcomm
It has nothing to do with kismet. It appeared again, probably in the moment, when provider have had a short outage. It seems to be a "feature" of netapplet. At least I am able to find string '"any"' in the sources. Reassigning to maintainer. Increasing to Critical. In some situations it causes network breakage and loss of mails.
Robert, is netapplet really overwriting the config file?
Yes, that is its MO. It generates the config files and then runs ifup.
The purpose of netapplet is to make it easy to switch between wired and various wireless networks. If multiple networks are available, it connects to the strongest signal (of course you can change the connection). Network Manager is much smarter and connects only to 'trusted' networks and uses the most recently used trusted network if there are multiple available so that after an initial selection you should never get this. This should solve the problem going forward.