3

I have not used wpa_supplicant before, so am confused as to whether a valid connection is being made. I used wpa_passphrase to get a psk and made that output my wpa_supplicant.conf. I then connect with:

wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf

and this is the output:

rfkill: Cannot open RFKILL control device
ioctl[SIOCSIWAP]: Operation not permitted
wlan0: Trying to associate with e8:04:62:23:57:d0 (SSID='Guest' freq=2412 MHz)
wlan0: Associated with e8:04:62:23:57:d0
wlan0: WPA: Key negotiation completed with e8:04:62:23:57:d0 [PTK=CCMP GTK=CCMP]
wlan0: CTRL-EVENT-CONNECTED - Connection to e8:04:62:23:57:d0 completed (auth) [id=0 id_str=]

It seems to connect but there are errors at the start, what do they mean? Do they affect the connection or does this look like I am connected correctly? I ask this as I try to give wlan0 an address with dhcp pr udhcpc and it does not get one, any idea why?

I have tried these two wpa_supplicant.conf's

network={
        ssid="Guest"
        #psk="xxxxxxxx"
        psk=<numbers>
}

and

update_config=1
network={
        ssid="Guest"
        proto=RSN
        key_mgmt=WPA-PSK
        pairwise=CCMP TKIP
        group=CCMP TKIP
        psk=<numbers>
        }

Both give the same thing

|improve this question
  • Try with sudo or as root – Milind Dumbare Mar 19 '15 at 11:51
  • Hi Miline it's a root shell. – Paul Mar 19 '15 at 11:52
  • Can you paste your /etc/wpa_supplicant.conf – Milind Dumbare Mar 19 '15 at 12:00
  • Does your system have /dev/rfkill? Does your kernel have RFKILL enabled? – Milind Dumbare Mar 19 '15 at 12:08
  • @Miline I pasted them above now, I dont see any reference to rfkill which might be why I get the error, but would it affect my connection if I dont have it? – Paul Mar 19 '15 at 12:14
2

Those two errors of rfkill are by Rfkill, a tool for enabling and disabling wireless devices. Most of the time the kernel does not have rfkill enabled in it. And so there is no /dev/rfkill file present, and rfkill command will give errors like rfkill: Cannot open RFKILL control device

Control device here means /dev/rfkill

|improve this answer
  • How can you get around this problem? Is there an alternative solution that doesn't require using Rfkill? – Andrew Mar 14 '18 at 15:58
  • Which problem? Enabling/Disabling rfkill or? – Milind Dumbare Mar 14 '18 at 22:06
  • I guess my question is this: Are the rfkill errors preventing successful connection? – Andrew Mar 15 '18 at 5:53
  • I don't think so. Its just that rfkill interface might not be available if rfkill is not available. – Milind Dumbare Mar 15 '18 at 22:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.