Arch Linux

dviktor

Member

From: Moscow

Registered: 2015-10-18

Posts: 162

[SOLVED] Can't share Wi-Fi with NetworkManager, iwlwifi

Hello! Recently I've bought ASUS VivoMini VC65 nettop with Intel Dual Band Wireless AC 7265 adapter. Seems like I can connect to Wi-Fi networks but can't create my own to share my ethernet connection to my friends. wpa_supplicant is installed. I can see my wireless card in lspci and dmesg:

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

linux-firmware is installed. After creating network in NetworkManager and starting it no connection occurs and after about one minute NM drops any tries to establish connection. In journalctl I have (мар stays for March):

мар 05 06:33:58 desolve-nettop NetworkManager[410]: <info>  [1488684838.7875] device (wlp2s0): set-hw-addr: set MAC address to 1E:F7:45:57:5
6:E4 (scanning)
мар 05 06:33:58 desolve-nettop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
мар 05 06:33:58 desolve-nettop NetworkManager[410]: <info>  [1488684838.8276] device (wlp2s0): supplicant interface state: scanning -> disco
nnected
мар 05 06:33:58 desolve-nettop NetworkManager[410]: <info>  [1488684838.8331] device (wlp2s0): supplicant interface state: disconnected -> i
nactive
мар 05 06:33:58 desolve-nettop wpa_supplicant[444]: wlp2s0: Reject scan trigger since one is already pending
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5287] keyfile: add connection in-memory (c5ea5bf9-4b07-4d1b-a2bf-f24
58e368be8,"yoba")
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5328] device (wlp2s0): Activation: starting connection 'yoba' (c5ea5
bf9-4b07-4d1b-a2bf-f2458e368be8)
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5350] keyfile: update /etc/NetworkManager/system-connections/yoba (c
5ea5bf9-4b07-4d1b-a2bf-f2458e368be8,"yoba") and persist connection
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5353] audit: op="connection-add-activate" uuid="c5ea5bf9-4b07-4d1b-a
2bf-f2458e368be8" name="yoba" pid=666 uid=1000 result="success"
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5419] device (wlp2s0): state change: disconnected -> prepare (reason
 'none') [30 40 0]
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5459] device (wlp2s0): set-hw-addr: reset MAC address to 48:45:20:C0
:77:CC (preserve)
мар 05 06:34:08 desolve-nettop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5534] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0]
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5537] device (wlp2s0): Activation: (wifi) connection 'yoba' requires no security.  No secrets needed.
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5537] Config: added 'ssid' value 'yoba'
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5538] Config: added 'mode' value '1'
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5538] Config: added 'frequency' value '2412'
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5538] Config: added 'key_mgmt' value 'NONE'
мар 05 06:34:08 desolve-nettop wpa_supplicant[444]: Note: nl80211 driver interface is not designed to be used with ap_scan=2; this can result in connection failures
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5853] device (wlp2s0): supplicant interface state: inactive -> disconnected
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5855] sup-iface[0x18e4d00,wlp2s0]: config: set interface ap_scan to 2
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5878] device (wlp2s0): supplicant interface state: disconnected -> inactive
мар 05 06:34:08 desolve-nettop wpa_supplicant[444]: wlp2s0: Trying to associate with SSID 'yoba'
мар 05 06:34:08 desolve-nettop wpa_supplicant[444]: Could not set interface wlp2s0 flags (UP): Device or resource busy
мар 05 06:34:08 desolve-nettop wpa_supplicant[444]: nl80211: Failed to set interface into IBSS mode
мар 05 06:34:08 desolve-nettop wpa_supplicant[444]: wlp2s0: Association request to the driver failed
мар 05 06:34:08 desolve-nettop NetworkManager[410]: <info>  [1488684848.5942] device (wlp2s0): supplicant interface state: inactive -> disconnected
мар 05 06:34:08 desolve-nettop wpa_supplicant[444]: wlp2s0: Trying to associate with SSID 'yoba'
мар 05 06:34:08 desolve-nettop wpa_supplicant[444]: wlp2s0: Association request to the driver failed
мар 05 06:34:09 desolve-nettop wpa_supplicant[444]: wlp2s0: Trying to associate with SSID 'yoba'
мар 05 06:34:09 desolve-nettop wpa_supplicant[444]: wlp2s0: Association request to the driver failed
мар 05 06:34:10 desolve-nettop wpa_supplicant[444]: wlp2s0: Trying to associate with SSID 'yoba'
мар 05 06:34:10 desolve-nettop wpa_supplicant[444]: wlp2s0: Association request to the driver failed
мар 05 06:34:10 desolve-nettop wpa_supplicant[444]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="yoba" auth_failures=1 duration=10 reason=CONN_FAILED
мар 05 06:34:15 desolve-nettop wpa_supplicant[444]: wlp2s0: Trying to associate with SSID 'yoba'
мар 05 06:34:15 desolve-nettop wpa_supplicant[444]: wlp2s0: Association request to the driver failed
мар 05 06:34:15 desolve-nettop wpa_supplicant[444]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="yoba" auth_failures=2 duration=20 reason=CONN_FAILED
мар 05 06:34:25 desolve-nettop wpa_supplicant[444]: wlp2s0: Trying to associate with SSID 'yoba'
мар 05 06:34:25 desolve-nettop wpa_supplicant[444]: wlp2s0: Association request to the driver failed
мар 05 06:34:25 desolve-nettop wpa_supplicant[444]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="yoba" auth_failures=3 duration=30 reason=CONN_FAILED
мар 05 06:34:33 desolve-nettop NetworkManager[410]: <warn>  [1488684873.7735] device (wlp2s0): Activation: (wifi) Ad-Hoc network creation took too long, failing activation
мар 05 06:34:33 desolve-nettop NetworkManager[410]: <info>  [1488684873.7736] device (wlp2s0): state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
мар 05 06:34:33 desolve-nettop NetworkManager[410]: <warn>  [1488684873.7746] device (wlp2s0): Activation: failed for connection 'yoba'
мар 05 06:34:33 desolve-nettop NetworkManager[410]: <info>  [1488684873.7811] device (wlp2s0): state change: failed -> disconnected (reason 'none') [120 30 0]
мар 05 06:34:33 desolve-nettop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
мар 05 06:34:33 desolve-nettop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
мар 05 06:34:33 desolve-nettop NetworkManager[410]: <info>  [1488684873.7902] device (wlp2s0): set-hw-addr: set MAC address to 9A:AC:C8:61:FC:65 (scanning)
мар 05 06:34:33 desolve-nettop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
мар 05 06:34:33 desolve-nettop NetworkManager[410]: <info>  [1488684873.8366] device (wlp2s0): supplicant interface state: disconnected -> inactive
мар 05 06:34:33 desolve-nettop wpa_supplicant[444]: wlp2s0: Reject scan trigger since one is already pending

The one thing that confusing me is:

Note: nl80211 driver interface is not designed to be used with ap_scan=2; this can result in connection failures

Why NM uses nl80211 driver for my card? Isn't the iwlwifi the proper choice? Also I tried this:

[viktor@desolve-nettop ~]$ cat /etc/modprobe.d/iwlwifi.conf 
options iwlwifi 11n_disable=1
options iwlwifi swcrypto=1

but with no luck.

Any suggestions?

SOLUTION
After installing hostapd, changing mode of the Wi-Fi connection in NetworkManager to the Hotspot and setting WPA2-Personal authentication I was able to bring up my Wi-Fi network and share connection to my friends. Thread can be closed now

Last edited by dviktor (2017-03-07 13:20:24)