Arch Linux

Beerai

Member

Registered: 2015-04-13

Posts: 3

[Solved] Configuring wireless with WPA2

Hi everyone. I've managed to almost set up my wireless dongle (it's a TP-Link AC1200 USB dongle that uses the rtl8812au driver that I got from here).

I have been following this and when I execute

wpa_supplicant -B -i interface -c /etc/wpa_supplicant/example.conf

I get

Successfully initialized wpa_supplicant
nl80211: Driver does not support authentication/association or connect commands
Could not set interface enp0s29u1u1 flags (DOWN): Operation not permitted
Could not set interface enp0s29u1u1 flags (DOWN): Operation not permitted
Could not set interface enp0s29u1u1 flags (DOWN): Operation not permitted
Could not set interface enp0s29u1u1 flags (DOWN): Operation not permitted
Could not set interface enp0s29u1u1 flags (DOWN): Operation not permitted
Could not set interface enp0s29u1u1 flags (DOWN): Operation not permitted
Could not set interface enp0s29u1u1 flags (DOWN): Operation not permitted
Could not set interface enp0s29u1u1 flags (DOWN): Operation not permitted
Could not set interface enp0s29u1u1 flags (DOWN): Operation not permitted
Could not set interface enp0s29u1u1 flags (DOWN): Operation not permitted
enp0s29u1u1: Failed to initialize driver interface

even though I've already brought up the interface using ip link and have my access point's credentials in /etc/wpa_supplicant/example.conf. I've also tried running the same command with the -D flag and specifying the driver I installed (which is called "8812au" - I've checked that the module is loaded) and I get

Successfully initialized wpa_supplicant
enp0s29u1u1: Unsupported driver '8812au'

so I'm not entirely sure where to go next.

Something that is possibly related is that iw dev produces no output at all. I've had to use iwconfig to work with the interface. I have no idea why this is and have spent a lot of time trying to figure it out but ultimately iwconfig + wpa_supplicant sort of work so I used them. If anyone has any ideas on that issue, please do point them out. I would like to leave the deprecated iwconfig behind.

Last edited by Beerai (2015-04-14 10:50:14)

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: [Solved] Configuring wireless with WPA2

Are you running it as root? "Operation not permitted" suggests you are not.

Also, are you sure you are using the right interface? 'en....' usually means a wired device, and 'wl....' a wireless device.

Finally, wpa_supplicant drivers are not the same as device drivers - see wpa_supplicant(8), "AVAILABLE DRIVERS", for details.

Last edited by tomk (2015-04-13 16:52:37)

Head_on_a_Stick

Member

From: London

Registered: 2014-02-20

Posts: 7,749

Website

Re: [Solved] Configuring wireless with WPA2

I have been following this and when I execute

wpa_supplicant -B -i interface -c /etc/wpa_supplicant/example.conf

Shouldn't that be:

# wpa_supplicant -B -i $interface -c /wpa_supplicant/example.conf

With "$interface" replaced with the actual name of your wireless interface?

Please post the content of your example.conf configuration file and the output of:

ip l

---

Are you infected with Wetiko?

Beerai

Member

Registered: 2015-04-13

Posts: 3

Re: [Solved] Configuring wireless with WPA2

@tomk Yes, those messages are from when I run it as root. My apologies, I should have directly copied from my terminal.

I am sure it's the right interface because if I do iwconfig, I get

[beerai@archhost ~]$ iwconfig
enp12s0   no wireless extensions.

enp0s29u1u1  unassociated  Nickname:"<WIFI@REALTEK>"
          Mode:Auto  Frequency=2.412 GHz  Access Point: Not-Associated   
          Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

enp0s29u1u2  no wireless extensions.

I've played around with iwconfig and have determined that it is in face the wireless dongle and not my tethered phone (which is actually enp0s29u1u2). I was also a little confused when I saw 'en' instead of something starting with 'wl'.

@Head_on_a_Stick, Yes, it was. Sorry, it was late and I copied from the wiki rather than my terminal.

example.conf:

ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel
update_config=1
network={
        ssid="TP-LINK_5GHz_F599EA"
        #psk="Boeta2006"
        psk=b72e0e5e1f781fb67345ad62f18d0a10b1028d840ab64f00919e67a568467268
}

ip l

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s29u1u1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 14:cc:20:10:c8:50 brd ff:ff:ff:ff:ff:ff
3: enp12s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether bc:5f:f4:18:c0:90 brd ff:ff:ff:ff:ff:ff
4: enp0s29u1u2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 02:26:2a:04:07:7d brd ff:ff:ff:ff:ff:ff

and because it might be relevant, lsmod | grep 8812

8812au               1119185  0 
usbcore               199382  10 rndis_host,rndis_wlan,ehci_hcd,ehci_pci,usbhid,usbnet,8812au,xhci_hcd,xhci_pci,cdc_ether

Hopefully someone has some ideas. I don't think something is broken, I think I am just missing a step somewhere. Unfortunately, the wiki relies on

 iw 

and I can't get that to work for some reason. That's the root of my problem.

Last edited by Beerai (2015-04-14 10:17:24)

Beerai

Member

Registered: 2015-04-13

Posts: 3

Re: [Solved] Configuring wireless with WPA2

So, I managed to get my wireless working a few minutes ago and the answer has been sitting in my open tabs all along (guess from which page)! It turns out that wpa_supplicant uses the nl80211 driver. Running through the steps here but with the wext driver allowed me to connect.

Judging by this however, I'm going to have issues in the future because wext isn't being developed anymore (and I assume it will be deprecated in the near future).