[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
I did some tracing at the 802.11 level and have come to the conclusion that this failure to connect is caused by the client not being able to support the key exchange and authentication protocols and algorithms published by the access point in the probe response. The RSN (Robust Security Network) information published by the Intel AX201 (Comet Lake) adapter in my test machine is as follows. Tag: RSN Information Tag Number: RSN Information (48) Tag length: 32 RSN Version: 1 Group Cipher Suite: 00:0f:ac (Ieee 802.11) TKIP Group Cipher Suite OUI: 00:0f:ac (Ieee 802.11) Group Cipher Suite type: TKIP (2) Pairwise Cipher Suite Count: 2 Pairwise Cipher Suite List 00:0f:ac (Ieee 802.11) AES (CCM) 00:0f:ac (Ieee 802.11) TKIP Pairwise Cipher Suite: 00:0f:ac (Ieee 802.11) AES (CCM) Pairwise Cipher Suite OUI: 00:0f:ac (Ieee 802.11) Pairwise Cipher Suite type: AES (CCM) (4) Pairwise Cipher Suite: 00:0f:ac (Ieee 802.11) TKIP Pairwise Cipher Suite OUI: 00:0f:ac (Ieee 802.11) Pairwise Cipher Suite type: TKIP (2) Auth Key Management (AKM) Suite Count: 3 Auth Key Management (AKM) List 00:0f:ac (Ieee 802.11) PSK 00:0f:ac (Ieee 802.11) PSK (SHA256) 00:0f:ac (Ieee 802.11) SAE (SHA256) Auth Key Management (AKM) Suite: 00:0f:ac (Ieee 802.11) PSK Auth Key Management (AKM) OUI: 00:0f:ac (Ieee 802.11) Auth Key Management (AKM) type: PSK (2) Auth Key Management (AKM) Suite: 00:0f:ac (Ieee 802.11) PSK (SHA256) Auth Key Management (AKM) OUI: 00:0f:ac (Ieee 802.11) Auth Key Management (AKM) type: PSK (SHA256) (6) Auth Key Management (AKM) Suite: 00:0f:ac (Ieee 802.11) SAE (SHA256) Auth Key Management (AKM) OUI: 00:0f:ac (Ieee 802.11) Auth Key Management (AKM) type: SAE (SHA256) (8) RSN Capabilities: 0x008c ...0 = RSN Pre-Auth capabilities: Transmitter does not support pre-authentication ..0. = RSN No Pairwise capabilities: Transmitter can support WEP default key 0 simultaneously with Pairwise key 11.. = RSN PTKSA Replay Counter capabilities: 16 replay counters per PTKSA/GTKSA/STAKeySA (0x3) ..00 = RSN GTKSA Replay Counter capabilities: 1 replay counter per PTKSA/GTKSA/STAKeySA (0x0) .0.. = Management Frame Protection Required: False 1... = Management Frame Protection Capable: True ...0 = Joint Multi-band RSNA: False ..0. = PeerKey Enabled: False ..0. = Extended Key ID for Individually Addressed Frames: Not supported .0.. = OCVC: False Tag: RSN eXtension (1 octet) Tag Number: RSN eXtension (244) Tag length: 1 RSNX: 0x20 (octet 1) = RSNX Length: 0 ...0 = Protected TWT Operations Support: 0 ..1. = SAE Hash to element: 1 00.. = Reserved: 0x0 This is non negotiable. So the only option for the client if cannot support what is proposed is to ignore it. I think this bug should probably be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
Tried again with an intel AX210 wifi6 pcie card same results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
With ap_scan forced to 1 in NetworkManager the error message disappears but the problem still exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
Ok, Looking through the code. ap_scan is being set to 2 in nm-supplicant- config.c. if (is_adhoc || is_ap) priv->ap_scan = 2; else priv->ap_scan = 1; This is the only place where this is done. The code for wpa_supplicant from the the official source at https://w1.fi/cgit/hostap/ does not contain the warning message! This is only present in the ubuntu source package. I have not checked the debian source yet. I might try a build of Network Manager that forces ap_scan to 1 and see if that gets round the iwlwifi problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
Tracked down the code that manipulates ap_scan.
roger@dragon:~$ cat ap-scan
34:guint32ap_scan;
93:priv->ap_scan = 1;
303:return NM_SUPPLICANT_CONFIG_GET_PRIVATE(self)->ap_scan;
572:priv->ap_scan = 2;
574:priv->ap_scan = 1;
1417:priv->ap_scan = 0;
./src/core/supplicant/nm-supplicant-config.c
2454:_LOGT("assoc[" NM_HASH_OBFUSCATE_PTR_FMT "]: interface ap_scan set to
%d",
./src/core/supplicant/nm-supplicant-interface.c
130:/* ap_scan=2 mode - try to associate with each SSID. */
698:if (wpa_s->conf->ap_scan != 0 &&
701:"overriding ap_scan configuration");
702:wpa_s->conf->ap_scan = 0;
706:if (wpa_s->conf->ap_scan == 0) {
730:if (wpa_s->conf->ap_scan == 2)
814:wpa_s->conf->ap_scan == 2) {
819:} else if (wpa_s->conf->ap_scan == 2) {
821: * User-initiated scan request in ap_scan == 2; scan with
./wpa_supplicant/scan.c
1092: dbus_uint32_t ap_scan = 1;
1094: if (!dbus_message_get_args(message, NULL, DBUS_TYPE_UINT32, &ap_scan,
1100: if (wpa_supplicant_set_ap_scan(wpa_s, ap_scan)) {
./wpa_supplicant/dbus/dbus_old_handlers.c
2696: dbus_uint32_t ap_scan = wpa_s->conf->ap_scan;
2699: &ap_scan, error);
2716: dbus_uint32_t ap_scan;
2719: &ap_scan))
2722: if (wpa_supplicant_set_ap_scan(wpa_s, ap_scan)) {
2724:"ap_scan must be 0, 1, or 2");
./wpa_supplicant/dbus/dbus_new_handlers.c
244:if (wpa_s->conf->ap_scan == 1)
255:if (wpa_s->conf->ap_scan == 1)
./wpa_supplicant/wps_supplicant.c
207:wpa_config_read_reg_dword(hk, TEXT("ap_scan"), &config->ap_scan);
562:wpa_config_write_reg_dword(hk, TEXT("ap_scan"), config->ap_scan,
./wpa_supplicant/config_winreg.c
632:"eapol_version", "ap_scan", "bgscan",
721:"eapol_version", "ap_scan",
3028: { "ap_scan", wpa_cli_cmd_ap_scan, NULL,
3030: " = set ap_scan parameter" },
./wpa_supplicant/wpa_cli.c
4456: int ap_scan = atoi(cmd);
4457: return wpa_supplicant_set_ap_scan(wpa_s, ap_scan);
./wpa_supplicant/ctrl_iface.c
166:if (wpa_s->conf->ap_scan == 1 && wpa_s->current_ssid) {
1415: if (wpa_s->conf->ap_scan == 2 || ap ||
1490: if ((wpa_s->conf->ap_scan == 2 && !wpas_wps_searching(wpa_s)))2119:
if (wpa_s->conf->ap_scan == 1 &&
2134: /* When using scanning (ap_scan=1), SIM PC/SC interface can be
./wpa_supplicant/events.c
994:if (config->ap_scan != DEFAULT_AP_SCAN)
995:fprintf(f, "ap_scan=%d\n", config->ap_scan);
./wpa_supplicant/config_file.c
3516: config->ap_scan = DEFAULT_AP_SCAN;
4130: { INT(ap_scan), 0 },
./wpa_supplicant/config.c
220:if (wpa_s->conf->ap_scan == 0 &&
934:old_ap_scan = wpa_s->conf->ap_scan;
937:if (old_ap_scan != wpa_s->conf->ap_scan)
2005: wpa_s->conf->ap_scan == 2 &&
2007: /* Use ap_scan==1 style network selection to find the network
2265: wpa_s->conf->ap_scan == 2) {
2432: } else if (wpa_s->conf->ap_scan == 1) {
2784: * @ap_scan: AP scan mode
2785: * Returns: 0 if succeed or -1 if ap_scan has an invalid value
2788:int wpa_supplicant_set_ap_scan(struct wpa_supplicant *wpa_s, int ap_scan)
2793: if (ap_scan < 0 || ap_scan > 2)
2796: if (ap_scan == 2 && os_strcmp(wpa_s->driver->name, "nl80211") == 0) {
2798: "Note: nl80211 driver interface is not designed to
be used with ap_scan=2; this can result in connection failures");
2802: if (ap_scan == 2 && ap_scan != wpa_s->conf->ap_scan &&
2805: wpa_printf(MSG_ERROR, "ap_scan = %d (%d) rejected while "
2806: "associating", wpa_s->conf->ap_scan, ap_scan);
2811: old_ap_scan = wpa_s->conf->ap_scan;
2812: wpa_s->conf->ap_scan = ap_scan;
2814: if (old_ap_scan != wpa_s->conf->ap_scan)
2960: wired = wpa_s->conf->ap_scan == 0 &&
3306: if (wpa_s->conf->ap_scan == 2 &&
3309: "Note: nl80211 driver interface is not designed to
be used with ap_scan=2; this can result in connection failures");
5206: return wpa_s->conf->ap_scan == 2 ||
./wpa_supplicant/wpa_supplicant.c
163:/* ap_scan=2 mode - try to associate with each SSID. */
1019: if (wpa_s->conf->ap_scan != 0 &&
1022: "overriding ap_scan configuration");
1023: wpa_s->conf->ap_scan = 0;
1027: if (wpa_s->conf->ap_scan == 0) {
1066: if (wpa_s->conf->ap_scan == 2)
1150: wpa_s->conf->ap_scan == 2) {
1155: } else if (wpa_s->conf->ap_scan == 2) {
1157:* User-initiated scan request in ap_scan == 2; scan with
./wpa_supplicant/scan.c
3514: dbus_uint32_t ap_scan = wpa_s->conf->ap_scan;
3517: &ap_scan, error);
3535: dbus_uint32_t ap_scan;
3538: &ap_scan))
3541: if (wpa_supplicant_set_ap_scan(wpa_s, ap_scan)) {
3543:"ap_scan mu
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
I am also seeing this problem. My motherboard has an onboard Intel AX201 wireless module. 'lshw -class network' reports. I am running ubuntu 24.04-1. *-network description: Ethernet interface product: Comet Lake PCH CNVi WiFi vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 00 serial: 64:6e:e0:6a:ec:30 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical configuration: broadcast=yes driver=iwlwifi driverversion=6.8.0-44-generic firmware=77.ad46c98b.0 QuZ-a0-hr-b0-77.u ip=10.161.0.1 latency=0 link=yes multicast=yes resources: iomemory:400-3ff irq:16 memory:4010514000-4010517fff Network manager journal shows this. NetworkManager[1595]: [1726655621.9126] device (wlo1): Activation: starting connection 'onboard' (eba7700f-707a-4fc7-9953-3eab2412e732) NetworkManager[1595]: [1726655621.9127] audit: op="connection-activate" uuid="eba7700f-707a-4fc7-9953-3eab2412e732" name="onboard" pid=1 uid=1000 result="success" NetworkManager[1595]: [1726655621.9127] device (wlo1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1595]: [1726655621.9134] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') NetworkManager[1595]: [1726655621.9135] device (wlo1): Activation: (wifi) access point 'onboard' has security, but secrets are required. NetworkManager[1595]: [1726655621.9135] device (wlo1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1595]: [1726655621.9139] device (wlo1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1595]: [1726655621.9142] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') NetworkManager[1595]: [1726655621.9143] device (wlo1): Activation: (wifi) connection 'onboard' has security, and secrets exist. No new secrets needed. NetworkManager[1595]: [1726655621.9143] Config: added 'ssid' value 'test1' NetworkManager[1595]: [1726655621.9143] Config: added 'mode' value '2' Sep 18 11:33:41 dragon NetworkManager[1595]: [1726655621.9143] Config: added 'frequency' value '2437' NetworkManager[1595]: [1726655621.9143] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 SAE' Sep 18 11:33:41 dragon NetworkManager[1595]: [1726655621.9143] Config: added 'psk' value '' NetworkManager[1595]: [1726655621.9650] device (wlo1): supplicant interface state: disconnected -> completed NetworkManager[1595]: [1726655621.9651] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Started Wi-Fi Hotspot "test1" NetworkManager[1595]: [1726655621.9651] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> completed NetworkManager[1595]: [1726655621.9651] device (wlo1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') NetworkManager[1595]: [1726655622.1322] dnsmasq-manager: starting dnsmasq... NetworkManager[1595]: [1726655622.1360] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') dnsmasq[12242]: started, version 2.90 cachesize 150 dnsmasq[12242]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset nftset auth cryptohash DNSSEC loop-detect inotify dumpfile dnsmasq[12242]: chown of PID file /run/nm-dnsmasq-wlo1.pid failed: Operation not permitted dnsmasq-dhcp[12242]: DHCP, IP range 10.161.0.10 -- 10.161.0.254, lease time 1h dnsmasq[12242]: reading /etc/resolv.conf dnsmasq[12242]: using nameserver 127.0.0.53#53 dnsmasq[12242]: cleared cache NetworkManager[1595]: [1726655622.1539] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') NetworkManager[1595]: [1726655622.1540] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') NetworkManager[1595]: [1726655622.1543] device (wlo1): Activation: successful, device activated. wpa_supplicant journal shows this and no further messages. wpa_supplicant[1596]: wlo1: AP-DISABLED wpa_supplicant[1596]: wlo1: CTRL-EVENT-DISCONNECTED bssid=64:6e:e0:6a:ec:30 reason=3 locally_generated=1 wpa_supplicant[1596]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all wpa_supplicant[1596]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD wpa_supplicant[1596]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=GB wpa_supplicant[1596]: Note: nl80211 driver interface is not designed to be used with ap_scan=2; this can result in connection failures wpa_supplicant[1596]: wlo1: interface state UNINITIALIZED->ENABLED wpa_supplicant[1596]: wlo1: AP-ENABLED wpa_supplicant[1596]: wlo1: CTRL-EVENT-CONNECTED - Connection to 64:6e:e0:6a:ec:30 completed [i
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
Supplementary information you may find useful. The Wi-Fi module on Pi-4 is not able to act as an Access Point *and* scan for wi-fi addresses at the same time. On Raspbian, this is dealt with by (1) specifying a fixed channel; and (2) adding the following line to /etc/dhcpcd.conf: nohook wpa_supplicant and (3) disabling (masking?) the wpa_supplicant service. If the wpa_supplicant service is running, any attempt to scan for wi-fi devices will take down the access point connection. For some reason, on Rasbiam (Debian derived), the network manager *fork*s wpa_supplicant in order to do a wifi scan when restarting, if the wpa_supplicant service has been disabled or masked, unless the nohook wpa_supplicant line is added. This happens early in the network manager restart, and can cause various unpleasant symptoms ranging from occasional drops all the way up to a fullblown deathspiral of all network services depending on timing. I'm not sure what the equivalent fix is on Ubuntu; but my reading of the message is: "This device is not able to do wi-fi scans when operating as an access point". I'm currently running Ubuntu 21.04, which uses a different network stack, I think (no wpa_supplicant, no hostapd), so I can't try workarounds myself. It sounds like 18.04 is using the old network stack, so the raspbian changes will probably work on Ubuntu 18.04 as well. In the meantime, I'm going to resume my search for the equivalent fix for an almost identical problem on the new network stack used by 21.04. :-P -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
I currently disagree on the WPA3 relation. >From "nmcli d show": 802-11-wireless-security.key-mgmt: wpa-psk >From "lshw -class network": configuration: broadcast=yes driver=rtl88XXau ip=10.42.0.1 multicast=yes wireless=IEEE 802.11bgn >From "sudo iwlist wlan0 scanning" from another PC and isolating my own AP: Channel:1 Frequency:2.412 GHz (Channel 1) Quality=52/70 Signal level=-58 dBm Encryption key:on ESSID:"hotspot-inside" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf= Extra: Last beacon: 100ms ago IE: Unknown: 000E686F7473706F742D696E73696465 IE: Unknown: 010882848B960C121824 IE: Unknown: 030101 IE: Unknown: 2A0104 IE: Unknown: 32043048606C IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (2) : PSK unknown (6) IE: Unknown: 2D1A3C0A1F2C0101 IE: Unknown: 3D160100 IE: Unknown: DD180050F2020101810003A427A442435D0062322E00 IE: Unknown: DD5C0050F204104A0001101044000102103B000103104700100157F558E17B51C98DC14CDEAE50195910210001 201023000120102400012010420001201054000810110001201008000231481049000600372A000120 IE: Unknown: DD0700E04C00020004 Note the "IEEE 802.11i/WPA2 Version 1" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
add: error/failure only happens when security is set to WPA3-Personal WPA2 hotspot works fine! this is: Intel Wireless 8260 driver=iwlwifi-5.4.0-42 firmware=36.77d01142.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
hotspot function also fails for me checked /etc/NetworkManager/NetworkManager.conf:wifi.scan-rand-mac-address=no also grep -r 'ap_scan=2' /etc turned up nothing so i am puzzled where/why ap_scan=2 would be set installed hostapd pkg but this did not fix it tangential: seems redhat had this failure mode in 2017 and nixos in 2019, dunno if related, workarounds vary https://github.com/NixOS/nixpkgs/issues/67956 https://bugzilla.redhat.com/show_bug.cgi?id=1463245 https://bugzilla.redhat.com/show_bug.cgi?id=1518190 probably related to https://marc.info/?l=linux-kernel&m=151221956904515&w=2 ** Bug watch added: github.com/NixOS/nixpkgs/issues #67956 https://github.com/NixOS/nixpkgs/issues/67956 ** Bug watch added: Red Hat Bugzilla #1463245 https://bugzilla.redhat.com/show_bug.cgi?id=1463245 ** Bug watch added: Red Hat Bugzilla #1518190 https://bugzilla.redhat.com/show_bug.cgi?id=1518190 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
add: DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wpasupplicant (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
No worries, I've just moved it there. :) ** Also affects: wpasupplicant (Ubuntu) Importance: Undecided Status: New ** No longer affects: cloud-init (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
Weird... I thought I selected 'wpasupplicant' as affected package. Sorry for the mistake ** Description changed: Ubuntu 20.04 LTS ARM (Running on a raspberry Pi) Logfile: - NetworkManager[1345]: [1593736912.7230] policy: auto-activating connection 'hotspot-inside' (37c28408-978a-48e0-a135-9867e3a45c64) + NetworkManager[1345]: [1593736912.7230] policy: auto-activating connection 'hotspot-inside' (37c28408-978a-48e0-a135-9867e3a45c64) NetworkManager[1345]: [1593736912.7248] device (wlx00c0caab435c): Activation: starting connection 'hotspot-inside' (37c28408-978a-48e0-a135-9867e3a45c64) - NetworkManager[1345]: [1593736912.7252] device (wlx00c0caab435c): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') - NetworkManager[1345]: [1593736912.7261] manager: NetworkManager state is now CONNECTING + NetworkManager[1345]: [1593736912.7252] device (wlx00c0caab435c): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') + NetworkManager[1345]: [1593736912.7261] manager: NetworkManager state is now CONNECTING NetworkManager[1345]: [1593736912.7449] device (wlx00c0caab435c): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') NetworkManager[1345]: [1593736912.7459] device (wlx00c0caab435c): Activation: (wifi) access point 'hotspot-inside' has security, but secrets are required. NetworkManager[1345]: [1593736912.7460] device (wlx00c0caab435c): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1345]: [1593736912.7530] device (wlx00c0caab435c): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') - NetworkManager[1345]: [1593736912.7557] device (wlx00c0caab435c): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') - NetworkManager[1345]: [1593736912.7566] device (wlx00c0caab435c): Activation: (wifi) connection 'hotspot-inside' has security, and secrets exist. No new secrets needed. - NetworkManager[1345]: [1593736912.7571] Config: added 'ssid' value 'hotspot-inside' - NetworkManager[1345]: [1593736912.7572] Config: added 'mode' value '2' - NetworkManager[1345]: [1593736912.7573] Config: added 'frequency' value '2412' - NetworkManager[1345]: [1593736912.7574] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' - NetworkManager[1345]: [1593736912.7574] Config: added 'psk' value '' - NetworkManager[1345]: [1593736912.7575] Config: added 'proto' value 'RSN' - NetworkManager[1345]: [1593736912.7575] Config: added 'pairwise' value 'CCMP' - NetworkManager[1345]: [1593736912.7576] Config: added 'group' value 'CCMP' - wpa_supplicant[1358]: Note: nl80211 driver interface is not designed to be used with ap_scan=2; this can result in connection failures + NetworkManager[1345]: [1593736912.7557] device (wlx00c0caab435c): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') + NetworkManager[1345]: [1593736912.7566] device (wlx00c0caab435c): Activation: (wifi) connection 'hotspot-inside' has security, and secrets exist. No new secrets needed. + NetworkManager[1345]: [1593736912.7571] Config: added 'ssid' value 'hotspot-inside' + NetworkManager[1345]: [1593736912.7572] Config: added 'mode' value '2' + NetworkManager[1345]: [1593736912.7573] Config: added 'frequency' value '2412' + NetworkManager[1345]: [1593736912.7574] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' + NetworkManager[1345]: [1593736912.7574] Config: added 'psk' value '' + NetworkManager[1345]: [1593736912.7575] Config: added 'proto' value 'RSN' + NetworkManager[1345]: [1593736912.7575] Config: added 'pairwise' value 'CCMP' + NetworkManager[1345]: [1593736912.7576] Config: added 'group' value 'CCMP' + wpa_supplicant[1358]: Note: nl80211 driver interface is not designed to be used with ap_scan=2; this can result in connection failures wpa_supplicant[1358]: Using interface wlx00c0caab435c with hwaddr 00:c0:ca:ab:43:5c and ssid "hotspot-inside" - * NetworkManager Connection definition: * [connect
