You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2021-03-01 01:12:48
- kmph
- Member
- Registered: 2015-08-29
- Posts: 6
Can't connect to WiFi (reason: 15)
A new Arch installation.
Trying to establish a connection fails:
Script started on 2021-03-01 01:08:08+01:00 [TERM="linux" TTY="/dev/tty1" COLUMNS="240" LINES="67"]
[root@myhostname ~]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether a8:a1:59:54:75:fc brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether d0:37:45:dd:b0:cd brd ff:ff:ff:ff:ff:ff
[root@myhostname ~]# systemctl start iwd
[root@myhostname ~]# iwctl device list
Devices
--------------------------------------------------------------------------------
Name Address Powered Adapter Mode
--------------------------------------------------------------------------------
wlan0 d0:37:45:dd:b0:cd on phy0 station
[root@myhostname ~]# iwctl station wlan0 scan
[root@myhostname ~]# iwctl staiton wlan0 get-networks
Invalid command
[root@myhostname ~]# iwctl station wlan0 get-networks
Available networks
--------------------------------------------------------------------------------
Network name Security Signal
--------------------------------------------------------------------------------
<redacted> psk ****
<redacted> 8021x ****
<redacted> psk ****
<redacted> psk ****
<redacted> 8021x ****
<redacted> psk ****
<redacted> psk ****
<redacted> psk ***
<redacted> psk ***
<redacted> psk ****
<redacted> psk ****
<redacted> psk ****
<redacted> psk ****
<redacted> psk **
<redacted> psk **
<redacted> psk **
<redacted> psk **
<redacted> psk ***
<redacted> psk ***
<redacted> psk ***
<redacted> psk ***
<redacted> psk ***
<redacted> psk **
<redacted> psk **
<redacted> psk **
<redacted> psk **
<redacted> psk **
<redacted> psk **
<redacted> psk **
<redacted> psk **
<redacted> psk **
<redacted> psk **
<redacted> open ***
<redacted> open **
[root@myhostname ~]# iwctl iwctl station wlan0 --passphrase <redacted> station wlan0 connect <redacted>
Operation failed
[root@myhostname ~]# exit
exit
Script done on 2021-03-01 01:12:29+01:00 [COMMAND_EXIT_CODE="1"]Unfortunately, it's hard to figure out the problem if all that is shown to me is just 'Operation failed'.
Relevant parts of the output of journalctl:
Mar 01 01:08:18 myhostname systemd[1]: Starting Wireless service...
Mar 01 01:08:18 myhostname kernel: NET: Registered protocol family 38
Mar 01 01:08:18 myhostname iwd[558]: Wireless daemon version 1.12
Mar 01 01:08:18 myhostname systemd[1]: Started Wireless service.
Mar 01 01:08:18 myhostname audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 01 01:08:18 myhostname systemd[1]: Reached target Network.
Mar 01 01:08:18 myhostname iwd[558]: station: Network configuration is disabled.
Mar 01 01:08:18 myhostname kernel: kauditd_printk_skb: 14 callbacks suppressed
Mar 01 01:08:18 myhostname kernel: audit: type=1130 audit(1614557298.768:40): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 01 01:08:18 myhostname iwd[558]: Wiphy: 0, Name: phy0
Mar 01 01:08:18 myhostname iwd[558]: Permanent Address: d0:37:45:dd:b0:cd
Mar 01 01:08:18 myhostname iwd[558]: Bands: 2.4 GHz
Mar 01 01:08:18 myhostname iwd[558]: Ciphers: CCMP TKIP BIP
Mar 01 01:08:18 myhostname iwd[558]: Supported iftypes: ad-hoc station ap p2p-client p2p-go
Mar 01 01:08:18 myhostname iwd[558]: Wiphy phy0 will only use the default interface
Mar 01 01:08:19 myhostname iwd[558]: CMD_SET_CQM failed: Operation not supported
Mar 01 01:11:45 myhostname kernel: wlan0: authenticate with 90:5c:44:82:42:e5
Mar 01 01:11:45 myhostname kernel: wlan0: send auth to 90:5c:44:82:42:e5 (try 1/3)
Mar 01 01:11:45 myhostname kernel: wlan0: authenticated
Mar 01 01:11:45 myhostname kernel: wlan0: associate with 90:5c:44:82:42:e5 (try 1/3)
Mar 01 01:11:45 myhostname kernel: wlan0: RX AssocResp from 90:5c:44:82:42:e5 (capab=0x1411 status=0 aid=1)
Mar 01 01:11:45 myhostname kernel: wlan0: associated
Mar 01 01:11:45 myhostname kernel: wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 90:5c:44:82:42:e5
Mar 01 01:11:50 myhostname iwd[558]: 4-Way handshake failed for ifindex: 3, reason: 15
Mar 01 01:11:50 myhostname kernel: wlan0: deauthenticating from 90:5c:44:82:42:e5 by local choice (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)Wireless card is TP-Link TL-WN881NND Low-profile.
PS1. Couldn't connect to wifi during system installation either. Was adviced on IRC to temporarily use mobile phone tethering to connect to the internet during installation (this worked) in the hope that updated firmware packages will be installed this way and wifi connection will work after installation. Unfortunately, this is not the case, even though I did install linux-firmware as instructed in the wiki.
PS2. Wifi works on Linux Mint. Sadly I wiped the Mint installation while installing Arch. Wifi works fine on Windows as well. (Mint was giving me freezes & crashes on this PC and this is the reason why I'm trying to install Arch.)
PS3. Why is the output of script so messy? I had to do a lot of manual editing to be able to post this file here...
Thank you in advance for help with resolving this issue!
Offline
#2 2021-03-01 08:30:59
- seth
- Member
- Registered: 2012-09-03
- Posts: 52,068
Re: Can't connect to WiFi (reason: 15)
Wifi works on Linux Mint
Same iwd procedure or rather networkmanager+wpa_supplicant?
Wifi works fine on Windows as well
Ceterum censeo: 3rd link in my signature.
Why is the output of script so messy?
It's hard to comment on messyness when only presented with a sanitized version 
On topic:
The error typically indicates a mismatching password. To rule out any conversion issues: is the passphrase ascii only?
In doubt try setting it to "correcthorsebatterystaple" and whether you can then connect.
Offline
#3 2021-03-01 12:26:34
- kmph
- Member
- Registered: 2015-08-29
- Posts: 6
Re: Can't connect to WiFi (reason: 15)
I checked - it seems Linux Mint uses networkmanager+wpa_supplicant.
The password IS ASCII only.
I booted into the liveUSB, used the phone tethering workaround, arch-chrooted into the locally installed system, removed iwd and installed wpa_supplicant. Rebooted into local Arch installation.
Used wpa_supplicant -B -i interface -c <(wpa_passphrase MYSSID passphrase) - wow it finally succeeded.
Having configured and started systemd-networkd and systemd-resolved as per https://wiki.archlinux.org/index.php/Systemd-networkd and https://wiki.archlinux.org/index.php/Systemd-resolved I was finally able to do ping archlinux.org and it succeeded.
Hopefully I will now be able to configure the system to be usable.
I have no idea why was iwd consistently failing while wpa_supplicant finally succeeded.
Windows Fast-Boot is disabled as far as I'm aware.
Offline
Pages: 1