GNOME Bugzilla – Bug 766615
Hotspot Access Point mode fails for 802.11a (5GHz) band
Last modified: 2020-11-12 14:31:18 UTC
On Ubuntu 16.04, distro bug report: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1579512 $ apt-cache policy network-manager network-manager: Installed: 1.2.0-0ubuntu0.16.04.2 On a clean 16.04 amd64 install a Managed mode Access Point 'Hotspot' fails to initialize when the frequency band is set to 802.11a 5GHz. "Automatic" or "2.4GHz" both work (using 802.11g). $ lspci -nnk -s 02:00.0 02:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5100] Kernel driver in use: iwlwifi Kernel modules: iwlwifi $ journalctl -u NetworkManager.service ... [1462706989.5477] (wlp2s0): using nl80211 for WiFi device control [1462706989.5562] device (wlp2s0): driver supports Access Point (AP) mode ... [1462708489.5782] Config: added 'ssid' value 'TJ' [1462708489.5782] Config: added 'mode' value '2' [1462708489.5782] Config: added 'frequency' value '5180' [1462708489.5783] Config: added 'freq_list' value '5035 5040 5045 5055 5060 5080 5170 5180 5190 5200 5210 5220 5230 5240 5250 5260 5280 5290 5300 5320 5500 5520 5540 5560 5580 5600 5620 5640 5660 5680 5700 5745 5760 5765 5785 5800 5805 5825 4915 4920 4925 4935 4945 4960 4980' [1462708489.5783] Config: added 'key_mgmt' value 'WPA-PSK' [1462708489.5783] Config: added 'psk' value '<omitted>' [1462708489.5966] sup-iface[0x16a8ac0,wlp2s0]: config: set interface ap_scan to 2 [1462708515.0203] device (wlp2s0): Activation: (wifi) Hotspot network creation took too long, failing activation [1462708515.0204] device (wlp2s0): state change: config -> failed (reason 'supplicant-timeout') [50 120 11] [1462708515.0207] manager: NetworkManager state is now DISCONNECTED
Hi TJ, thanks for the report. AFAIS, it's not visible from the partial logging what's wrong. Would it be possible to provide a complete log, with debug logging enabled? [logging] level=TRACE in /etc/NetworkManager/NetworkManager.conf, followed by a systemctl restart NetworkManager. Thank you.
Created attachment 328306 [details] TRACE log activating connection "Access Point" $ sudo cat /etc/NetworkManager/system-connections/Access\ Point [connection] id=Access Point uuid=05b2e2ee-0e93-4d00-b080-681b61d3e036 type=wifi autoconnect=false interface-name=wlp2s0 permissions= secondaries= timestamp=1462991894 [wifi] band=a mac-address=34:02:86:FC:AD:55 mac-address-blacklist= mac-address-randomization=0 mode=ap seen-bssids=34:02:86:FC:AD:55; ssid=TJ [wifi-security] group= key-mgmt=wpa-psk pairwise= proto= psk=letmein2go [ipv4] dns-search= method=shared [ipv6] addr-gen-mode=stable-privacy dns-search= ip6-privacy=0 method=ignore
Ooops, my grep-ed output from syslog removed the (only) wpa_supplicant message so here it is, with context: -- May 21 11:18:37 T300CHI NetworkManager[30219]: <debug> [1463825917.3022] platform: signal: link changed: 2: wlp2s0 <DOWN;broadcast,multicast> mtu 1500 arp 1 wifi? init addrgenmode none addr 34:02:86:FC:AD:55 driver iwlwifi May 21 11:18:37 T300CHI NetworkManager[30219]: <debug> [1463825917.3024] device[0x143daa0] (wlp2s0): queued link change for ifindex 2 May 21 11:18:37 T300CHI kernel: [563811.179147] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready May 21 11:18:37 T300CHI wpa_supplicant[1278]: wlp2s0: Failed to start AP functionality May 21 11:18:37 T300CHI NetworkManager[30219]: <trace> [1463825917.3081] platform-linux: event-notification: NEWLINK, seq 0: 2: wlp2s0 <UP;broadcast,multicast,up> mtu 1500 arp 1 wifi? not-init addrgenmode none addr 34:02:86:FC:AD:55 May 21 11:18:37 T300CHI NetworkManager[30219]: <debug> [1463825917.3082] platform: signal: link changed: 2: wlp2s0 <UP;broadcast,multicast,up> mtu 1500 arp 1 wifi? init addrgenmode none addr 34:02:86:FC:AD:55 driver iwlwifi May 21 11:18:37 T300CHI NetworkManager[30219]: <debug> [1463825917.3082] device[0x143daa0] (wlp2s0): queued link change for ifindex 2 --
Nothing of help from wpa_supplicant itself either: $ sudo wpa_cli -g /run/wpa_supplicant/wlp2s0 wpa_cli v2.4 Copyright (c) 2004-2015, Jouni Malinen <j@w1.fi> and contributors This software may be distributed under the terms of the BSD license. See README for more details. Selected interface 'p2p-dev-wlp2s0' Interactive mode > log_level DEBUG OK <3>CTRL-EVENT-DISCONNECTED bssid=ec:43:f6:46:c0:81 reason=3 locally_generated=1 <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE <3>Failed to start AP functionality > quit
Created attachment 328308 [details] wpa-supplicant log wpa_supplicant log messages swallowed by systemd, not being passed on to rsyslogd it seems! Log file extract using: $ journalctl -n 0 -fu wpa_supplicant Finally found some clues: May 21 11:56:58 T300CHI wpa_supplicant[1278]: nl80211: Set freq 5180 (ht_enabled=0, vht_enabled=0, bandwidth=0 MHz, cf1=0 MHz, cf2=0 MHz) May 21 11:56:58 T300CHI wpa_supplicant[1278]: * freq=5180 May 21 11:56:58 T300CHI wpa_supplicant[1278]: * vht_enabled=0 May 21 11:56:58 T300CHI wpa_supplicant[1278]: * ht_enabled=0 May 21 11:56:58 T300CHI wpa_supplicant[1278]: nl80211: Failed to set channel (freq=5180): -22 (Invalid argument)
Created attachment 328309 [details] iw list (shows 5180 frequency is listed) $ iw list ... Frequencies: * 5180 MHz [36] (22.0 dBm) (no IR) * 5200 MHz [40] (22.0 dBm) (no IR) * 5220 MHz [44] (22.0 dBm) (no IR) * 5240 MHz [48] (22.0 dBm) (no IR) * 5260 MHz [52] (22.0 dBm) (no IR, radar detection) DFS state: usable (for 565001 sec) ...
Created attachment 328314 [details] syslog with NLDBG=4 and wpa_supplicant log_level DEBUG I rebuilt libnl3 with "--enable-debug" and enabled maximum level: $ grep Environment /lib/systemd/system/wpa_supplicant.service Environment="NLDBG=4" restarted wpa_supplicant and NM. $ sudo wpa_cli -g /run/wpa_supplicant/wlp2s0 log_level DEBUG the resulting combined syslog output of NM, wpa_supplicant, and libnl3 is attached.
There are "(Device or resource busy)" errors in wpa_supplicant, which indicate that something might use the device at the same time. It could be hostapd.
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).