[SOLVED] Wireless Auth Issue with Realtek RTL8192ee Wifi Adapter

abrasiv · 2015-04-14 05:24:01

Hello everyone. New guy to Arch Linux (loving it so far) with an odd (to me at least) problem regarding my specific realtek wifi adapter. It appears that my internal wireless adapter (RTL8192ee) connected fantastically when using the live usb during install, but it does not seem to want to work correctly on my actual installation. For now, I'm using a USB adapter that is able to authenticate and access my network using wifi-menu just fine, though I'd love to use my built-in wireless.

Here's a quick overview of what I have tried so far:

I've followed the wireless connectivity guide on the wiki, both using netctl/wpa_supplicant for a manual setup and wifi-menu for an easier set.
In addition, I even performed a clean re-install thinking I may have done something wrong when setting up Arch.
I've tried changing my resolv.conf to switch to an open DNS.
I've tried escaping any special characters in my password in both my netctl profile and my wpa_supplicant.conf
I've ensured only one wireless process is being used for this adapter at a time via "ps ax | grep wpa"

Here are the errors

abrasiv@workstation-b ~]$ sudo journalctl -xe
...
Apr 14 00:22:52 workstation-b kernel: wlan0: authenticate with 00:26:f2:5d:c0:12
Apr 14 00:22:52 workstation-b kernel: wlan0: send auth to 00:26:f2:5d:c0:12 (try 1/3)
Apr 14 00:22:52 workstation-b kernel: wlan0: send auth to 00:26:f2:5d:c0:12 (try 2/3)
Apr 14 00:22:52 workstation-b kernel: wlan0: send auth to 00:26:f2:5d:c0:12 (try 3/3)
Apr 14 00:22:52 workstation-b kernel: wlan0: authentication with 00:26:f2:5d:c0:12 timed out
Apr 14 00:22:53 workstation-b kernel: wlan0: authenticate with 00:26:f2:5d:c0:12
Apr 14 00:22:53 workstation-b kernel: wlan0: send auth to 00:26:f2:5d:c0:12 (try 1/3)
Apr 14 00:22:54 workstation-b kernel: wlan0: send auth to 00:26:f2:5d:c0:12 (try 2/3)
Apr 14 00:22:54 workstation-b kernel: wlan0: send auth to 00:26:f2:5d:c0:12 (try 3/3)
Apr 14 00:22:54 workstation-b kernel: wlan0: authentication with 00:26:f2:5d:c0:12 timed out
Apr 14 00:22:56 workstation-b kernel: wlan0: authenticate with 00:26:f2:5d:c0:12
Apr 14 00:22:56 workstation-b kernel: wlan0: direct probe to 00:26:f2:5d:c0:12 (try 1/3)
Apr 14 00:22:56 workstation-b kernel: wlan0: direct probe to 00:26:f2:5d:c0:12 (try 2/3)
Apr 14 00:22:56 workstation-b kernel: wlan0: direct probe to 00:26:f2:5d:c0:12 (try 3/3)
Apr 14 00:22:56 workstation-b kernel: wlan0: authentication with 00:26:f2:5d:c0:12 timed out
Apr 14 00:23:08 workstation-b dhcpcd[714]: timed out
Apr 14 00:23:08 workstation-b dhcpcd[714]: dhcpcd exited
Apr 14 00:23:08 workstation-b network[458]: DHCP IPv4 lease attempt failed on interface 'wlan0'
Apr 14 00:23:08 workstation-b network[458]: Failed to bring the network up for profile 'home'
Apr 14 00:23:08 workstation-b systemd[1]: netctl@home.service: main process exited, code=exited, status=1/FAILURE
Apr 14 00:23:08 workstation-b systemd[1]: Failed to start Networking for netctl profile home.
-- Subject: Unit netctl@home.service has failed
-- Defined-By: systemd

 
Using "wifi-menu" gives a different error:
 
Apr 14 00:26:44 workstation-b network[838]: WPA association/authentication failed for interface 'wlan0'
Apr 14 00:26:44 workstation-b network[838]: Failed to bring the network up for profile 'home'
Apr 14 00:26:44 workstation-b systemd[1]: netctl@home.service: main process exited, code=exited, status=1/FAILURE
Apr 14 00:26:44 workstation-b systemd[1]: Failed to start Networking for netctl profile home.
-- Subject: Unit netctl@home.service has failed

Pertinent Info

##### lscpi -k
[abrasiv@workstation-b ~]$ lspci -k
...
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192EE PCIe Wireless Network Adapter
        Subsystem: Realtek Semiconductor Co., Ltd. Device 001b
        Kernel driver in use: rtl8192ee
        Kernel modules: rtl8192ee

##### iw dev

[abrasiv@workstation-b ~]$ iw dev
phy#0
        Interface wlan0
                ifindex 3
                wdev 0x1
                addr 34:23:87:00:36:91
                type managed

##### ip link show wlan0 (I dont appear to have an issue detecting the hardware and enabling it using ip link, though I have to set it down in order to enable it via netctl.)

[abrasiv@workstation-b ~]$ ip link show wlan0
wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 34:23:87:00:36:91 brd ff:ff:ff:ff:ff:ff


##### My resolv.conf (note: I've tried to use Google's open DNS just to see if it was an internal issue with my network)

# /etc/resolv.conf#
#search <yourdomain.tld>
nameserver 192.168.1.1
#nameserver 8.8.8.8

##### My wpa_supplicant.conf (I've tried escaping the exclamation marks with a backslash. It does not appear to make a difference. I've also kept a backup copy of the original file with all the comments and examples in case I need it.)

ctrl_interface=DIR=/run/wpa_supplicant
# reading passphrase from stdin
network={
        ssid="home"
        psk="password!!"
        #psk=216316e96b1a60c1efc9f5cba400afce555ce987513da1322a4c1a14c2c132be
}

#####  Part of my dhcpcd.conf (I've tried to disable IPv6 from being used when it is leasing an IP address)
...
#Disable IPv6 in dhcpcd
noipv6rs
noipv6

##### dmesg | grep wlan0
[abrasiv@workstation-b ~]$ dmesg | grep wlan0
[  149.395832] wlan0: authenticate with 00:26:f2:5d:c0:12
[  149.432987] wlan0: send auth to 00:26:f2:5d:c0:12 (try 1/3)
[  149.442165] wlan0: authenticated
[  149.445071] wlan0: associate with 00:26:f2:5d:c0:12 (try 1/3)
[  149.455174] wlan0: RX AssocResp from 00:26:f2:5d:c0:12 (capab=0x411 status=0 aid=3)
[  149.495491] wlan0: associated
[  168.308395] wlan0: Connection to AP 00:26:f2:5d:c0:12 lost
[  169.441119] wlan0: authenticate with 00:26:f2:5d:c0:12
[  169.478408] wlan0: send auth to 00:26:f2:5d:c0:12 (try 1/3)
[  169.580499] wlan0: send auth to 00:26:f2:5d:c0:12 (try 2/3)
[  169.683758] wlan0: send auth to 00:26:f2:5d:c0:12 (try 3/3)
[  169.787033] wlan0: authentication with 00:26:f2:5d:c0:12 timed out
[  171.323797] wlan0: authenticate with 00:26:f2:5d:c0:12
[  171.360248] wlan0: send auth to 00:26:f2:5d:c0:12 (try 1/3)
[  171.462766] wlan0: send auth to 00:26:f2:5d:c0:12 (try 2/3)
[  171.566043] wlan0: send auth to 00:26:f2:5d:c0:12 (try 3/3)
[  171.669317] wlan0: authentication with 00:26:f2:5d:c0:12 timed out
[  173.702451] wlan0: authenticate with 00:26:f2:5d:c0:12
[  173.739267] wlan0: direct probe to 00:26:f2:5d:c0:12 (try 1/3)
[  173.941389] wlan0: direct probe to 00:26:f2:5d:c0:12 (try 2/3)
[  174.144605] wlan0: direct probe to 00:26:f2:5d:c0:12 (try 3/3)
[  174.347841] wlan0: authentication with 00:26:f2:5d:c0:12 timed out
[  986.922183] wlan0: authenticate with 00:26:f2:5d:c0:12
[  986.959011] wlan0: send auth to 00:26:f2:5d:c0:12 (try 1/3)
[  987.023521] wlan0: authenticated
[  987.024715] wlan0: associate with 00:26:f2:5d:c0:12 (try 1/3)
[  987.037546] wlan0: RX AssocResp from 00:26:f2:5d:c0:12 (capab=0x411 status=0 aid=3)
[  987.078060] wlan0: associated
[  997.087459] wlan0: deauthenticating from 00:26:f2:5d:c0:12 by local choice (Reason: 3=DEAUTH_LEAVING)

Sorry if this is poorly formatted. I'm not exactly sure what should and should not be included so I've tried to encapsulate as much as I could. Let me know if I've missed any important information. I've tried to include everything I've looked at, but I'm still a fairly beginner level linux user. Any help would be appreciated. Hopefully, a more practiced hand can point me in the correct direction.

Thank you in advance.

Last edited by abrasiv (2015-04-16 14:39:35)

Head_on_a_Stick · 2015-04-14 13:35:47

abrasiv wrote:

ctrl_interface=DIR=/run/wpa_supplicant
# reading passphrase from stdin
network={
        ssid="home"
        psk="password!!"
        #psk=216316e96b1a60c1efc9f5cba400afce555ce987513da1322a4c1a14c2c132be
}

How did you generate this file?

In my version, the first "psk=" entry is commented out and the second entry (generated by `wpa_passphrase`) is active.

Also, is your SSID really called "home"?

abrasiv · 2015-04-14 23:59:57

Head_on_a_Stick wrote:

How did you generate this file?
In my version, the first "psk=" entry is commented out and the second entry (generated by `wpa_passphrase`) is active.
Also, is your SSID really called "home"?

Thanks for the input. I generated it through wpa_passphrase by overwriting the wpa_supplicant.conf (as opposed to appending and not before I created a copy). I've tried it both with the straight up psk as plain text and the hashed version, but the hashed version still yields a DHCP timeout. I tested again just to make sure.

As for the issue of my SSID, I was merely erring on the side of caution and changed it when I posted my info. wpa_passphrase generated it, and it matches the SSID of my working USB adapter, which was set up via wifi-menu. It's simply a five character, no numbers or special characters, SSID. I can provide it if you think it would help at all, but I simply changed it along with the password (except for the relevant exclamation marks at the end which could cause an authentication issue if not escaped properly).

Head_on_a_Stick · 2015-04-15 12:27:01

abrasiv wrote:

I can provide it if you think it would help at all

No, that's fine.

The reason given in dmesg ("3=DEAUTH_LEAVING") suggests the router has dropped the connection (source), but if it worked in the live environment I'm inclined to think that perhaps there has been a kernel regression.

You could try the LTS kernel and see if that helps.

woodape · 2015-04-15 12:54:07

abrasiv wrote:

(except for the relevant exclamation marks at the end which could cause an authentication issue if not escaped properly).

What command did you use to establish a connection during the install and what command exactly did you use to generate the psk post install? I don't think you have to escape anything in your passphrase for special characters, just single quote the passphrase when generating the psk. I have all sorts of special characters in my passphrase and I don't escape anything. As you say you could have an authentication issue if the password isn't correctly formatted, and all your errors say you have an authentication issue. I would try the following command first:

wpa_passphrase SSID 'passphrase' >> /etc/wpa_supplicant.conf

Last edited by woodape (2015-04-15 12:55:48)

abrasiv · 2015-04-16 01:46:26

Head_on_a_Stick wrote:

You could try the LTS kernel and see if that helps.

Thanks for the suggestion. I'll see if it makes it anymore stable.

woodape wrote:

What command did you use to establish a connection during the install and what command exactly did you use to generate the psk post install? I don't think you have to escape anything in your passphrase for special characters, just single quote the passphrase when generating the psk.

I used wifi-menu during the installation process. I was surprised it worked straight out of the package as I had not realized the drivers were included in the 3.16 kernel. After I ran into issues and could not get it working, I tried the manual process (netctl/profiles) that was listed in the wiki. After that failed, I re-installed and tried only the manual process.

As for the escaping characters, I may have been mistaken or perhaps thinking of the netctl profiles instead of the wpa_supplicant.conf. Nothing is currently escaped in that file as it was generated by wpa_passphrase. I simply tried commenting/uncommenting both lines to see if either would help.

abrasiv · 2015-04-16 14:38:13

So I switched to the linux-lts kernel, as suggested by Head-on-a-Stick, and installed the drivers for RTL8192ee from the AUR. So far, everything looks to be working just fine.

After installing, I used wifi-menu and everything seemed to work without any issue. I'm going to mark this as solved since it's been working for a while on two separate wireless networks (with some minor packet loss on one network).

I would like to ask what exactly would be the cause of this on the vanilla kernel as opposed to the LTS kernel. I did some cursory research but I cant really see what the differences are between the two in terms of networking. Head-on-a-Stick, you mentioned kernel regression. I see the term tossed around when I search for it but I'm not exactly sure what this means. Could you share any light on this?

Again, thanks for your suggestions and insight to everyone who looked and responded.

Head_on_a_Stick · 2015-04-16 14:59:07

abrasiv wrote:

Head-on-a-Stick, you mentioned kernel regression. I see the term tossed around when I search for it but I'm not exactly sure what this means. Could you share any light on this?

It just means that the kernel worked in previous versions but not with the new version because of a newly introduced bug.

If you have some free time, you could try pinning the bug down:
https://wiki.archlinux.org/index.php/Bisecting_bugs

Arch Linux

#1 2015-04-14 05:24:01

[SOLVED] Wireless Auth Issue with Realtek RTL8192ee Wifi Adapter

#2 2015-04-14 13:35:47

Re: [SOLVED] Wireless Auth Issue with Realtek RTL8192ee Wifi Adapter

#3 2015-04-14 23:59:57

Re: [SOLVED] Wireless Auth Issue with Realtek RTL8192ee Wifi Adapter

#4 2015-04-15 12:27:01

Re: [SOLVED] Wireless Auth Issue with Realtek RTL8192ee Wifi Adapter

#5 2015-04-15 12:54:07

Re: [SOLVED] Wireless Auth Issue with Realtek RTL8192ee Wifi Adapter

#6 2015-04-16 01:46:26

Re: [SOLVED] Wireless Auth Issue with Realtek RTL8192ee Wifi Adapter

#7 2015-04-16 14:38:13

Re: [SOLVED] Wireless Auth Issue with Realtek RTL8192ee Wifi Adapter

#8 2015-04-16 14:59:07

Re: [SOLVED] Wireless Auth Issue with Realtek RTL8192ee Wifi Adapter

Board footer