So here's what I did:
chkconfig NetworkManager off chkconfig network off chkconfig wpa_supplicant on
I checked /etc/sysconfig/wpa_supplicant:
INTERFACES="-iwlan0" DRIVERS="-Dwext" OTHER_ARGS="-f /var/log/wpa_supplicant.log -P /var/run/wpa_supplicant.pid"
For that last one, I removed the "-u" option since it said it's required for use with NetworkManager. Since I'm not using NM, I removed it.
In /etc/wpa_supplicant/wpa_supplicant.conf I have:
ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel
network={ #scan_ssid=1 ssid="Nymphadora" key_mgmt=WPA-PSK proto=WPA2 pairwise=TKIP group=TKIP psk=72c2778558c782b95aa87a1b15565617bf1db09bd4880aedfba86c943f6eee50 }
That psk line was generated from wpa_passphrase.
Then I restarted the server. When it came back up, ifconfig showed:
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1104 (1.0 KiB) TX bytes:1104 (1.0 KiB)
wlan0 Link encap:Ethernet HWaddr 00:87:35:1C:07:BF UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
So, wireless didn't connect?
Looking at /var/log/messages, I see this:
kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
My wireless is configured as a WPA2-PSK, I'm not entirely sure if /etc/wpa_supplicant/wpa_supplicant.conf is actually correct ...
On Fri, Jan 10, 2014 at 10:17 PM, Barry Brimer lists@brimer.org wrote:
On Fri, 10 Jan 2014, Ashley M. Kirchner wrote:
Ok, got it installed and I can get the interface to scan and I can see
all
of the available cells (all of my neighbors), including my own. However when I do a test connect, this is what I get back:
Trying to associate with e0:46:9a:35:fb:98 (SSID='Nymphadora' freq=2412
MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy Association request to the driver failed Associated with 00:00:00:00:00:00 CTRL-EVENT-DISCONNECTED bssid=e0:46:9a:35:fb:98 reason=0
Over and over and over again.
Please note, NetworkManager is still running. If I stop NM, that
interface
disappears and an attempt to scan tells me:
iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down
So evidently, I need NM running for the interface to be present. How
can I
do that without NM?
On Fri, Jan 10, 2014 at 9:29 PM, Barry Brimer lists@brimer.org wrote:
<snip>
Great ... now how do I configure this sucker? When I turn NM off, that interface disappears. I'm assuming I can create an 'ifcfg-wlan0' configuration but what do I need to put in there so it knows to connect
to
my home wireless (with password) and all of that fun and exciting
stuff,
and continue to do that over a reboot.
Using wpa_supplicant. If it is not installed, yum install wpa_supplicant and you will need to edit /etc/sysconfig/wpa_supplicant and /etc/wpa_supplicant/wpa_supplicant.conf. Examples are in /usr/share/doc/wpa_supplicant-* or plenty of them online .. You probably also need to rename/mv the SXXwpa_supplicant in your /etc/rcX.d to start wpa_supplicant before network.
You don't need NM. I don't ever use it. I wonder if NM is causing the problem. I would stop NM and make sure you have wpa_supplicant set up right .. or at least the part in /etc/sysconfig/wpa_supplicant and then stop network and wpa_supplicant, start wpa_supplicant and try iwlist wlan0 scan. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos