[SOLVED] WIFI not able to connect to WPA2 - laptop

treedust · 2017-01-13 01:54:12

I am currently booting from arch iso 2017.01.01

First thing I noticed upon booting is that the airplane mode button is active on my keyboard.

I have ran:

rfkill list
#results are 
0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
1: asus-wlan: Wireless LAN
    Soft blocked: no
    Hard blocked: no
2: asus-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no
1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

the results have lead me to conclude that the even thought the airplane mode button is bright red this mode is not enabled? I have read over Wireless network configurations and followed the article.

Step 1) stop the dhcpcd service with systemctl stop dhcpcd@<TAB>

systemctl stop dhcpd@enp3s0.service

Step 2) identify and ensure the correct driver for my wireless device is installed

lspci -k
...
02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
	Subsystem: Intel Corporation Dual Band Wireless-AC 7265
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
	Subsystem: ASUSTeK Computer Inc. Device 200f
	Kernel driver in use: r8169
	Kernel modules: r8169
...

dmesg | grep usbcore
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver uas
usbcore: registered new interface driver usbhid
usbcore: registered new interface driver btusb
usbcore: registered new interface driver uvcvideo

ip link
...
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
      link/ether ...
2: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
      link/ether ....

wlp2s0 is my interface

ip link set wlp2s0 up
dmesg | grep iwlwifi
#results
iwlwifi 000:02:00.0 Direct firmware load for iwlwifi-7265-23.ucode failed with error -2
iwlwifi 000:02:00.0 Direct firmware load for iwlwifi-7265-23.ucode failed with error -2
iwlwifi 000:02:00.0 loaded firmware version 22.361475.0 op_mode iwlmwm
iwlwifi 000:02:00.0 Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210 
iwlwifi 000:02:00.0 L1 Enabled - LTR Enabled 
iwlwifi 000:02:00.0 L1 Enabled - LTR Enabled 
iwlwifi 000:02:00.0 wlp2s0: renamed from wlan0
iwlwifi 000:02:00.0 L1 Enabled - LTR Enabled 
iwlwifi 000:02:00.0 L1 Enabled - LTR Enabled 
iwlwifi 000:02:00.0 L1 Enabled - LTR Enabled 
iwlwifi 000:02:00.0 L1 Enabled - LTR Enabled

Direct firmware load for iwlwifi-7265-23.ucode failed with error -2
So I do not have the firmware? If this is the case not sure how to have changes take affect from what is stated here

Step 3) configure the interface

iw dev wlp2s0 link
Not connected.

ip link show wlp2s0

3: wlp2s0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
    link/ether

I have noticed that LOWER_UP is missing between < > from the in my output in comparison to the wiki.

oh my device is supported as said here

with

iw dev wlan0 scan | less

i found the network I want to connect to.
Security: ** I know it needs a username and password ***

capability: ESS Privacy ShortPreamble ShortSlotTime RadioMeasure (0x1431)
RSN: * Version: 1
     * Group cipher: CCMP
     * Pairwise ciphers: CCMP
     * Authentication suites: IEEE 902.1X
     * Capabilities 4-PTKSA-RC 4-GTKSA-RC (0x0028)

wpa_supplicant -D nl80211,wext -i wlp2s0 -c <(wpa_passphrase "your_SSID" "your_key")
Successfully initialized wpa_supplicant
ioctl[SIOCSIWENCODEXT]: Invalid argument
ioctl[SIOCSIWENCODEXT]: Invalid argument

Is

 <(wpa_passphrase "your_SSID" "your_key")

not creating everything that is needed?
This has lead me to https://wiki.archlinux.org/index.php/WPA_supplicant
and from here:

dhcpcd wlp2s0 
wlp2s0: waiting for carrier
timed out
dhcpcd exited

Thank you for your help.

Last edited by treedust (2017-01-13 07:42:54)

Trilby · 2017-01-13 02:21:14

First, drop the -D flag from wpa_supplicant. I've never seen it solve a problem, but I've seen it create many. Second, did you see the NOTE box in the wiki page you linked to? Did you run that command in a root shell, or did you just use sudo? In either case, I prefer to never use process substitution like that for this: use wpa_passprhase to generate a stanza that you can add to your wpa_supplicant.conf

treedust · 2017-01-13 07:41:48

dropping the -D worked.
Using

ip link set wlp2s0 up
wpa_supplicant -B -i wlp2s0 -c <(wpa_passphrase "your_SSID" "your_key")
dhcpcd wlp2s0

I've run each line from the arch iso root shell.

Trilby · 2017-01-13 13:01:56

Glad it worked!

If you don't have access to ethernet, be sure to install wpa_supplicant and any other tools you will need for wireless connections along with the base install. Wpa_supplicant is available on the iso, but is not part of the base group that gets installed by default.

Arch Linux

#1 2017-01-13 01:54:12

[SOLVED] WIFI not able to connect to WPA2 - laptop

#2 2017-01-13 02:21:14

Re: [SOLVED] WIFI not able to connect to WPA2 - laptop

#3 2017-01-13 07:41:48

Re: [SOLVED] WIFI not able to connect to WPA2 - laptop

#4 2017-01-13 13:01:56

Re: [SOLVED] WIFI not able to connect to WPA2 - laptop

Board footer