You are not logged in.
Hello,
I've been having issues with netcfg2 connecting to my wireless network, but until today I always could easily do
netcfg2 bdp
after boot and everything was just OK. Today I started playing a little with TIMEOUT and DHCP_TIMEOUT values to see if I could fix this and out of nowhere I started getting some wpa_supplicant errors. Now not only I can't connect at boot but also I get this error when trying to connect manually:
netcfg2 bdp
:: bdp up [BUSY]
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.
- wpa_supplicant did not start, possible configuration error [FAIL]
Here's my profile bdp, for the record:
CONNECTION="wireless"
INTERFACE="wlan0"
SCAN="yes"
SECURITY="wpa"
ESSID="network-name-here"
KEY='very-large-key-here'
IP="dhcp"
DHCLIENT="yes"
DCHP_TIMEOUT=20
TIMEOUT=30
Any clues?
Last edited by alexmatos (2009-06-24 12:08:48)
Offline
If this happens, you can usually fix it by:
sudo killall wpa_supplicant
sudo rm -rf /var/run/wpa_supplicant
Don't worry, it shouldn't be a permenant problem
Scott
Offline
If this happens, you can usually fix it by:
sudo killall wpa_supplicant sudo rm -rf /var/run/wpa_supplicant
Don't worry, it shouldn't be a permenant problem
Scott
Wow, that's was a quick response!
I forgot to mention that I always do that and I can connect, but it comes back after every boot.
Offline
That means that wpa_supplicant is not stopped correctly.
Try to stop wpa_supplicant manually and then reboot - see what happens when you try to connect to your network.
Zl.
Offline
What does your rc.conf look like? Is it trying to start networking a couple of different ways, perhaps?
Scott
Maybe it is. This is the relevant part:
NETWORKS=(ethernet bdp hdm allan)
AUTO_NETWORKS=(auto-wireless wlan0)DAEMONS=(syslog-ng @net-profiles @net-auto netfs crond @cpufreq @sensors alsa hal fam @mysqld !mpd @openntpd @httpd gdm)
I read that I should not put wireless profiles under NETWORKS, only wired ('ethernet' in my case). I'm going to try that now and come back for feedback.
EDIT:
Nice guess, Scott! I changed to
NETWORKS=(ethernet)
AUTO_NETWORKS=(auto-wireless wlan0)
and it seems to be working OK (I rebooted a couple of times and it all went well). I must say this is indeed much more clear for wireless profiles, since I don't want to put every one of them in my rc.conf. The odd thing is that it used to work with my old config until I changed the profile by adding DHCP_TIMEOUT=20 and removing DHCLIENT="yes".
Thanks to all who helped! This is now solved.
Last edited by alexmatos (2009-06-24 12:02:33)
Offline