Arch Linux

vorpalblade

Member

Registered: 2013-11-07

Posts: 13

[Workaround] Wifi connects but does not allow internet access

When I connect using network manager or wifi-menu, I am unable to browse the internet or ping 192.168.1.1. I can connect to the network and get an ip address, but nothing else. It was working at one point, but is not anymore for some reason (it works under Windows 8).

$ sudo lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller
00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1
00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller
00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0)
00:1c.2 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 3 (rev d0)
00:1c.7 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 8 (rev d0)
00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family H97 Controller
00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller
01:00.0 VGA compatible controller: NVIDIA Corporation G96 [GeForce 9500 GT] (rev a1)
03:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)
04:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter

$ lsusb
Bus 002 Device 002: ID 8087:8001 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 1058:0820 Western Digital Technologies, Inc. My Passport Ultra (WDBMWV, WDBZFP)
Bus 003 Device 003: ID 040b:2000 Weltrend Semiconductor 
Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
Bus 003 Device 005: ID 0bda:0821 Realtek Semiconductor Corp. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

From lspci, I can see that I have the Realtek RTL8821AE wireless network adapter. To check and make certain that the firmware is getting loaded, I ran:

$ sudo dmesg | grep 8821
[    0.212074] pci 0000:04:00.0: [10ec:8821] type 00 class 0x028000
[    2.000913] rtl8821ae 0000:04:00.0: enabling device (0000 -> 0003)
[    2.046024] rtl8821ae: Using firmware rtlwifi/rtl8821aefw.bin
[    2.046028] rtl8821ae: Using firmware rtlwifi/rtl8821aefw_wowlan.bin
[    2.077024] rtl8821ae 0000:04:00.0 wlp4s0: renamed from wlan0
[    2.121134] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821
[    2.121136] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
[   78.969690] Modules linked in: rfcomm ext4 mbcache jbd2 ctr ccm cmac ecb fuse bnep ses enclosure uas btusb usb_storage btbcm btintel bluetooth crc16 mousedev nls_iso8859_1 nls_cp437 vfat fat arc4 iTCO_wdt iTCO_vendor_support intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp evdev mac_hid kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel rtl8821ae nouveau btcoexist rtl_pci psmouse aesni_intel serio_raw snd_hda_codec_realtek pcspkr aes_x86_64 lrw gf128mul snd_soc_rt5640 glue_helper ablk_helper cryptd rtlwifi snd_soc_rl6231 snd_hda_codec_generic snd_soc_core lpc_ich mxm_wmi wmi i2c_i801 ttm i2c_hid tpm_tis snd_compress mac80211 snd_hda_intel snd_pcm_dmaengine regmap_i2c nuvoton_cir tpm rc_core drm_kms_helper snd_hda_controller drm cfg80211 battery i2c_designware_platform

So the firmware is getting loaded.

Networking information:

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether d0:50:99:77:dd:c7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.106/24 brd 192.168.1.255 scope global dynamic enp3s0
       valid_lft 86098sec preferred_lft 86098sec
    inet6 fe80::d250:99ff:fe77:ddc7/64 scope link 
       valid_lft forever preferred_lft forever
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1280 qdisc mq state UP group default qlen 1000
    link/ether 4c:bb:58:b5:c0:83 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.118/24 brd 192.168.1.255 scope global dynamic wlp4s0
       valid_lft 85994sec preferred_lft 85994sec
    inet6 fe80::4ebb:58ff:feb5:c083/64 scope link 
       valid_lft forever preferred_lft forever

What I have tried:

• Reinstall

• Different linux distribution (Fedora)

What might be related:

• https://bbs.archlinux.org/viewtopic.php?id=191981 -- problem started occurring after Windows install, except with Wireless instead of Wired (so probably not WoL)

What I haven't tried:

• ndiswrapper

What shouldn't be a factor:

• https://bbs.archlinux.org/viewtopic.php?id=156283 -- using NetworkManager

EDIT: 
Thought that this was solved. It wasn't -- when I updated to NetworkManager 1.06, I had also done a reset. It appears that the reset button on my computer resets something that gets set improperly somehow.

WORKAROUND: 
Reset switch on computer case, if hooked up. If no reset switch, reseting the CMOS manually MAY work (not tested).

Last edited by vorpalblade (2015-09-05 12:16:31)

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,778

Website

Re: [Workaround] Wifi connects but does not allow internet access

What is the output of:

ls -l /etc/systemd/system/multi-user.target.wants
ping -c3 8.8.8.8
ping -c3 google.com

---

Jin, Jîyan, Azadî

vorpalblade

Member

Registered: 2013-11-07

Posts: 13

Re: [Workaround] Wifi connects but does not allow internet access

$ ls -l /etc/systemd/system/multi-user.target.wants
lrwxrwxrwx 1 root root 46 Aug 19 12:26 NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
lrwxrwxrwx 1 root root 40 Aug 19 12:10 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target

$ ping -c3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2007ms

$ ping -c3 google.com                              
ping: unknown host google.com

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,778

Website

Re: [Workaround] Wifi connects but does not allow internet access

Can you ping your router?

Whilst "connected", what is the output of:

ip a

If you stop NetworkManager, can you connect manually?
https://wiki.archlinux.org/index.php/Wi … nual_setup

Error messages from the manual attempt will probably prove illuminating.

---

Jin, Jîyan, Azadî

vorpalblade

Member

Registered: 2013-11-07

Posts: 13

Re: [Workaround] Wifi connects but does not allow internet access

I cannot ping my router.

Wireless card is wlp4s0:

# systemctl stop NetworkManager
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether d0:50:99:77:dd:c7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.106/24 brd 192.168.1.255 scope global dynamic enp3s0
       valid_lft 60769sec preferred_lft 60769sec
    inet6 fe80::d250:99ff:fe77:ddc7/64 scope link 
       valid_lft forever preferred_lft forever
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1280 qdisc mq state UP group default qlen 1000
    link/ether 4c:bb:58:b5:c0:83 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.117/24 brd 192.168.1.255 scope global dynamic wlp4s0
       valid_lft 60454sec preferred_lft 60454sec
    inet6 fe80::4ebb:58ff:feb5:c083/64 scope link 
       valid_lft forever preferred_lft forever

From the manual setup page:

# iw dev
phy#0
	Interface wlp4s0
		ifindex 3
		wdev 0x1
		addr 4c:bb:58:b5:c0:83
		type managed
# iw dev wlp4s0 link
Not connected.
# iw dev wlp4s0 scan
command failed: Network is down (-100)
# ip link show wlp4s0                   :(
3: wlp4s0: <BROADCAST,MULTICAST> mtu 1280 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 4c:bb:58:b5:c0:83 brd ff:ff:ff:ff:ff:ff

Ok. Its "down" right now. Let's bring it up

# ip link set wlp4s0 up
# ip link show wlp4s0  
3: wlp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1280 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 4c:bb:58:b5:c0:83 brd ff:ff:ff:ff:ff:ff

(If anyone else is following along with this post, look at the UP between the <>, not the DOWN)   
In the interest of keeping this post shorter, I'm leaving out the output from

# iw dev wlp4s0 scan

Since the access point I'm using uses WPA,

# wpa_supplicant -D nl80211,wext -i wlp4s0 -c <(wpa_passphrase "SSID" 'PASSWORD_WITH_!!_AND_"_')
Successfully initialized wpa_supplicant
wlp4s0: SME: Trying to authenticate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Trying to associate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Associated with 48:f8:b3:::
wlp4s0: WPA: Key negotiation completed with 48:f8:b3::: [PTK=CCMP GTK=TKIP]
wlp4s0: CTRL-EVENT-CONNECTED - Connection to 48:f8:b3::: completed [id=0 id_str=]

# dhclient wlp4s0
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether d0:50:99:77:dd:c7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.106/24 brd 192.168.1.255 scope global dynamic enp3s0
       valid_lft 59634sec preferred_lft 59634sec
    inet6 fe80::d250:99ff:fe77:ddc7/64 scope link 
       valid_lft forever preferred_lft forever
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1280 qdisc mq state UP group default qlen 1000
    link/ether 4c:bb:58:b5:c0:83 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.117/24 brd 192.168.1.255 scope global wlp4s0
       valid_lft forever preferred_lft forever
    inet6 fe80::4ebb:58ff:feb5:c083/64 scope link 
       valid_lft forever preferred_lft forever

At this point, I unplug the ethernet cord. Now what does pinging my router do?

$ ping -c3 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

--- 192.168.1.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2011ms

Ok, let's look at the link.

# iw dev wlp4s0 link
Connected to 48:f8:b3::: (on wlp4s0)
	SSID: SSID
	freq: 5745
	RX: 1223976 bytes (7544 packets)
	TX: 2137 bytes (22 packets)
	signal: -40 dBm
	tx bitrate: 6.0 MBit/s 40MHz

	bss flags:	short-slot-time
	dtim period:	1
	beacon int:	100

Note: tried setting static dhcp

# ip addr add 192.168.1.5/24 broadcast 192.168.1.255 dev wlp4s0
# ip route add default via 192.168.1.1

After turning NetworkManager back on (systemctl start NetworkManager), additional output appears from wpa_supplicant:

# wpa_supplicant -D nl80211,wext -i wlp4s0 -c <(wpa_passphrase "SSID" 'PASSWORD_WITH_!!_AND_"_')
Successfully initialized wpa_supplicant
wlp4s0: SME: Trying to authenticate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Trying to associate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Associated with 48:f8:b3:::
wlp4s0: WPA: Key negotiation completed with 48:f8:b3::: [PTK=CCMP GTK=TKIP]
wlp4s0: CTRL-EVENT-CONNECTED - Connection to 48:f8:b3::: completed [id=0 id_str=]
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=48:f8:b3::: reason=2 locally_generated=1
wlp4s0: Associated with 48:f8:b3:::
wlp4s0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
wlp4s0: WPA: Could not verify EAPOL-Key MIC - dropping packet
wlp4s0: Authentication with 48:f8:b3::: timed out.
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=48:f8:b3::: reason=3 locally_generated=1
wlp4s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSID" auth_failures=1 duration=10 reason=WRONG_KEY
wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSID" auth_failures=2 duration=23 reason=CONN_FAILED
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=48:f8:b3:9c:cb:bb reason=3 locally_generated=1
wlp4s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="SSID"
wlp4s0: SME: Trying to authenticate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Trying to associate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Associated with 48:f8:b3:::
wlp4s0: WPA: Key negotiation completed with 48:f8:b3::: [PTK=CCMP GTK=TKIP]
wlp4s0: CTRL-EVENT-CONNECTED - Connection to 48:f8:b3::: completed [id=0 id_str=]
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=48:f8:b3::: reason=3 locally_generated=1
wlp4s0: SME: Trying to authenticate with 48:f8:b3:9c:cb:bb (SSID='SSID' freq=2422 MHz)
wlp4s0: Trying to associate with 48:f8:b3:9c:cb:bb (SSID='SSID' freq=2422 MHz)
wlp4s0: Associated with 48:f8:b3:9c:cb:bb
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=48:f8:b3:9c:cb:bb reason=3 locally_generated=1
wlp4s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSID" auth_failures=1 duration=10 reason=WRONG_KEY
wlp4s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="SSID"
wlp4s0: SME: Trying to authenticate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Trying to associate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Associated with 48:f8:b3:::
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=48:f8:b3::: reason=3 locally_generated=1
wlp4s0: SME: Trying to authenticate with 48:f8:b3:9c:cb:bb (SSID='SSID' freq=2422 MHz)
wlp4s0: Trying to associate with 48:f8:b3::: (SSID='SSID' freq=2422 MHz)
wlp4s0: Associated with 48:f8:b3:::
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=48:f8:b3::: reason=3 locally_generated=1
wlp4s0: SME: Trying to authenticate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Trying to associate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Associated with 48:f8:b3:::
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=48:f8:b3::: reason=3 locally_generated=1
wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSID" auth_failures=2 duration=26 reason=CONN_FAILED
wlp4s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="SSID"
wlp4s0: SME: Trying to authenticate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Trying to associate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Associated with 48:f8:b3:::
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=48:f8:b3::: reason=3 locally_generated=1
wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSID" auth_failures=3 duration=57 reason=CONN_FAILED
wlp4s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="SSID"
wlp4s0: SME: Trying to authenticate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Trying to associate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Associated with 48:f8:b3:::
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=48:f8:b3::: reason=3 locally_generated=1
wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSID auth_failures=4 duration=95 reason=CONN_FAILED
wlp4s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="SSID"
wlp4s0: SME: Trying to authenticate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Trying to associate with 48:f8:b3::: (SSID='SSID' freq=5745 MHz)
wlp4s0: Associated with 48:f8:b3:::
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=48:f8:b3::: reason=3 locally_generated=1
wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSID" auth_failures=5 duration=103 reason=CONN_FAILED

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,778

Website

Re: [Workaround] Wifi connects but does not allow internet access

wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="SSID" auth_failures=1 duration=10 reason=WRONG_KEY

Are you sure the password is entered correctly?

I presume that you have replaced the actual SSID with "SSID" in your commands and the terminal output.

What is your hardware?

lspci -knn|grep -iA2 net

---

Jin, Jîyan, Azadî

vorpalblade

Member

Registered: 2013-11-07

Posts: 13

Re: [Workaround] Wifi connects but does not allow internet access

# lspci -knn|grep -iA2 net
03:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit Ethernet [1969:10a1] (rev 10)
	Subsystem: ASRock Incorporation Device [1849:10a1]
	Kernel driver in use: alx
--
04:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter [10ec:8821]
	Subsystem: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter [10ec:8821]
	Kernel driver in use: rtl8821ae
	Kernel modules: rtl8821ae

And I am quite sure that the password is entered correctly (copy and paste). The auth_failures didn't start happening until I started NetworkManager up again, so it was *probably* NetworkManager and wpa_supplicant fighting over the same interface (NetworkManager uses wpa_supplicant, IIRC).

I did replace my SSID with "SSID" in the pasted output and input. And removed part of the MAC address.

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,778

Website

Re: [Workaround] Wifi connects but does not allow internet access

It's a long shot but try:

# modprobe -rv rtl8821ae
# modprobe -v rtl8821ae options fwlps=0

If the module cannot be unloaded, then reboot and use this kernel parameter:

rtl8821ae.fwlps=0

If this does help, make the change permanent by adding a .conf file in /etc/modprobe.d/
https://wiki.archlinux.org/index.php/Ke … probe.d.2F

---

Jin, Jîyan, Azadî

vorpalblade

Member

Registered: 2013-11-07

Posts: 13

Re: [Workaround] Wifi connects but does not allow internet access

# modprobe -rv rtl8821ae
rmmod rtl8821ae
rmmod rtl_pci
rmmod rtlwifi
rmmod mac80211
rmmod cfg80211
rmmod btcoexist
# modprobe -v rtl8821ae options fwlps=0
insmod /lib/modules/4.1.5-1-ARCH/kernel/net/wireless/cfg80211.ko.gz 
insmod /lib/modules/4.1.5-1-ARCH/kernel/net/mac80211/mac80211.ko.gz 
insmod /lib/modules/4.1.5-1-ARCH/kernel/drivers/net/wireless/rtlwifi/rtlwifi.ko.gz 
insmod /lib/modules/4.1.5-1-ARCH/kernel/drivers/net/wireless/rtlwifi/rtl_pci.ko.gz 
insmod /lib/modules/4.1.5-1-ARCH/kernel/drivers/net/wireless/rtlwifi/btcoexist/btcoexist.ko.gz 
insmod /lib/modules/4.1.5-1-ARCH/kernel/drivers/net/wireless/rtlwifi/rtl8821ae/rtl8821ae.ko.gz options fwlps=0

Unfortunately, it did not appear to help. 
I just looked at the kernel versions for Arch and Fedora, and they are both 4.1.5. I'll check an earlier kernel version (4.0.4 from Fedora) and see if that works. If it does, then its probably a kernel bug.

EDIT: No, it does not appear to be a kernel bug.

Last edited by vorpalblade (2015-08-22 23:10:38)

vorpalblade

Member

Registered: 2013-11-07

Posts: 13

Re: [Workaround] Wifi connects but does not allow internet access

I ran an update today and it magically started working.
Here are the packages:

# pacman -Syu
colord-1.2.12-1  libnm-glib-1.0.6-1  networkmanager-1.0.6-1
             nm-connection-editor-1.0.6-1

Update: It was just intermittent -- and I gave up after that for awhile (didn't bother posting, etc.)
    Something I just tried www.susegeek.com/wireless/wireless-will … indows-xp/
    Its working right now, don't know if it will be in an hour (that was one issue that I was having while troubleshooting -- it wasn't always consistent).

Last edited by vorpalblade (2016-03-29 18:15:52)