wpa_supplicant issues resolved

Thilo Six T.Six at gmx.de
Fri Apr 28 18:37:09 UTC 2006

Hash: RIPEMD160

Howard Coles Jr. wrote the following on 28.04.2006 03:25:
> Just in case someone upgrades from Breezy to Dapper and uses wpa_supplicant 
> you might want to keep an eye on this.
> When I upgraded some weird things happened, most notably the script that 
> starts wpa_supplicant (/etc/init.d/wpasupplicant) was not updated to reflect 
> the new location of the daemon.
> the script has a line that says:
> DAEMON=/usr/sbin/wpa_supplicant
> The problem is that there was no softlink to its real location in that 
> directory.
> You will need to change it to:
> DAEMON=/sbin/wpa_supplicant
> Another thing that happened was that my config files were blown away, however 
> (thankfully) they were backed up.  (with a dpkg extension)
> check /etc/default for wpasupplicant (where the options for interface, driver, 
> and config file are stored).
> check for /etc/wpa_supplicant.conf (which in the newer versions is moved 
> to /etc/wpa_supplicant/wpa_supplicant.conf)
> Also make sure your /etc/network/interfaces file is still what you expect.  
> I'm not sure wpa_supplicant changed this, it may have been ifplugd.  
> I'm still trying to figure out why udev is still creating /dev/null with root 
> only access every time the udev package is updated.  However, I've at least 
> figured out the wpa_supplicant issue.

Could you please put your findings in Launchpad?

This will prevent others to fall in this pitfall.

If you need help with that, I will and others here, too.

bye Thilo
- --
i am on Ubuntu 2.6 KDE
- - some friend of mine

gpg key: Ox4A411E09

Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the kubuntu-users mailing list