I'm not able to reproduce this issue but I can't restrict my router to use 802.11ac only, it also uses 802.11n in the 5GHz spectrum. Is there a way to check which standard is in use for a connection or is it possible to restrict which standard to use on the client side?
Brian, are you still seeing this issue with a current focal image and kernel 5.4.0-1009? FWIW, my log: Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd[1]: Starting Network Service... Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd[1]: Started WPA supplicant for netplan wlan0. Apr 29 06:17:46 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: Successfully initialized wpa_supplicant Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd-networkd[1593]: eth0: Gained IPv6LL Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd-networkd[1593]: Enumeration completed Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd-timesyncd[1092]: Network configuration changed, trying to establish connection. Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd-timesyncd[1092]: Network configuration changed, trying to establish connection. Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd[1]: Started Network Service. Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd-networkd[1593]: wlan0: IPv6 successfully enabled Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd-networkd[1593]: eth0: IPv6 successfully enabled Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd-timesyncd[1092]: Network configuration changed, trying to establish connection. Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd-networkd[1593]: eth0: DHCPv4 address 192.168.99.34/24 via 192.168.99.1 Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd-timesyncd[1092]: Network configuration changed, trying to establish connection. Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd-timesyncd[1092]: Network configuration changed, trying to establish connection. Apr 29 06:17:46 rpi-4b-rev1d1-17cf systemd-timesyncd[1092]: Initial synchronization to time server 192.168.99.1:123 (192.168.99.1). Apr 29 06:17:46 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1 Apr 29 06:17:47 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1 Apr 29 06:17:48 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1 Apr 29 06:17:49 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1 Apr 29 06:17:50 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1 Apr 29 06:17:51 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1 Apr 29 06:17:52 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1 Apr 29 06:17:53 rpi-4b-rev1d1-17cf kernel: ieee80211 phy0: brcmf_escan_timeout: timer expired Apr 29 06:17:55 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: Trying to associate with SSID 'pi-test' Apr 29 06:17:58 rpi-4b-rev1d1-17cf iwd[1176]: Unexpected connection related event -- is another supplicant running? Apr 29 06:17:58 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: Associated with e0:28:6d:9e:b9:25 Apr 29 06:17:58 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: CTRL-EVENT-CONNECTED - Connection to e0:28:6d:9e:b9:25 completed [id=0 id_str=] Apr 29 06:17:58 rpi-4b-rev1d1-17cf kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Apr 29 06:17:58 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Apr 29 06:17:58 rpi-4b-rev1d1-17cf systemd-udevd[712]: Network interface NamePolicy= disabled on kernel command line, ignoring. Apr 29 06:17:58 rpi-4b-rev1d1-17cf systemd-networkd[1593]: wlan0: Gained carrier Apr 29 06:17:58 rpi-4b-rev1d1-17cf systemd-networkd[1593]: wlan0: Connected WiFi access point: pi-test (e0:28:6d:9e:b9:25) Apr 29 06:17:58 rpi-4b-rev1d1-17cf systemd-networkd[1593]: wlan0: DHCPv4 address 192.168.99.39/24 via 192.168.99.1 Apr 29 06:18:00 rpi-4b-rev1d1-17cf systemd-networkd[1593]: wlan0: Gained IPv6LL Apr 29 06:19:21 rpi-4b-rev1d1-17cf dbus-daemon[1170]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.15' (uid=0 pid=1703 comm="/usr/bin/gdbus call --system --dest org.freedeskto" label="unconfined") Apr 29 06:19:21 rpi-4b-rev1d1-17cf systemd[1]: Starting PackageKit Daemon... Apr 29 06:19:21 rpi-4b-rev1d1-17cf PackageKit[1706]: daemon start Apr 29 06:19:21 rpi-4b-rev1d1-17cf dbus-daemon[1170]: [system] Successfully activated service 'org.freedesktop.PackageKit' Apr 29 06:19:21 rpi-4b-rev1d1-17cf systemd[1]: Started PackageKit Daemon. Apr 29 06:24:27 rpi-4b-rev1d1-17cf PackageKit[1706]: daemon quit Apr 29 06:24:27 rpi-4b-rev1d1-17cf systemd[1]: packagekit.service: Succeeded. Apr 29 06:25:01 rpi-4b-rev1d1-17cf CRON[1788]: pam_unix(cron:session): session opened for user root by (uid=0) Apr 29 06:25:01 rpi-4b-rev1d1-17cf CRON[1789]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )) Apr 29 06:25:02 rpi-4b-rev1d1-17cf CRON[1788]: pam_unix(cron:session): session closed for user root Apr 29 06:29:57 rpi-4b-rev1d1-17cf systemd[1]: Starting Cleanup of Temporary Directories... Apr 29 06:29:57 rpi-4b-rev1d1-17cf systemd[1]: systemd-tmpfiles-clean.service: Succeeded. Apr 29 06:29:57 rpi-4b-rev1d1-17cf systemd[1]: Finished Cleanup of Temporary Directories. Apr 29 06:31:20 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: Associated with e0:28:6d:9e:b9:25 Apr 29 06:31:20 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: CTRL-EVENT-CONNECTED - Connection to e0:28:6d:9e:b9:25 completed [id=0 id_str=] Apr 29 06:31:20 rpi-4b-rev1d1-17cf systemd-networkd[1593]: wlan0: Lost carrier Apr 29 06:31:20 rpi-4b-rev1d1-17cf systemd-networkd[1593]: wlan0: DHCP lease lost Apr 29 06:31:20 rpi-4b-rev1d1-17cf wpa_supplicant[1598]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Apr 29 06:31:20 rpi-4b-rev1d1-17cf systemd-networkd[1593]: wlan0: Gained carrier Apr 29 06:31:20 rpi-4b-rev1d1-17cf systemd-networkd[1593]: wlan0: DHCPv4 address 192.168.99.39/24 via 192.168.99.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1862760 Title: Unreliable 802.11ac connection on our raspi images Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in linux-firmware source package in Bionic: New Status in linux-firmware-raspi2 source package in Bionic: New Status in linux-raspi2-5.3 source package in Bionic: New Status in netplan.io source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware-raspi2 source package in Eoan: New Status in linux-raspi2-5.3 source package in Eoan: New Status in netplan.io source package in Eoan: New Status in linux-firmware source package in Focal: New Status in linux-firmware-raspi2 source package in Focal: Triaged Status in linux-raspi source package in Focal: New Status in netplan.io source package in Focal: New Bug description: We were not able to completely pin-point the issue yet, so this is more of a blanket bug for the current issues we are seeing. We don't know where exactly the issue can be located. While preparing and testing 18.04.4, certification reported issues with our uc18 images on the pi4 with wifi ac tests. One of our engineers (Brian) confirmed it locally with a wifi access point restricted only to 802.11ac. After some additional testing, he noticed that he had the same unreliable symptoms for both the classic and core images, as well as the 19.10.1 classic images. The symptoms seem to vary, from inability to detect 802.11ac APs, inability to connect and/or receive an IP address and no traffic getting through. We will provide all the information that we have. Raspbian works better in this regard. We have pulled in the wifi firmware bits from Raspbian and using those, and that seems to resolve all flakiness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
