The only upstream bug that seems potentially related is
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1024
. But that's more about ensuring that WPA auth has completed before
starting the DHCP renewal, and it's not clear to me how blocking ICMP
could avoid that problem.
I have the same symptoms on Ubuntu 22.04.1 on a 12th-gen Framework
laptop with Intel Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) device.
Every time wpa-supplicant chooses to associate with a different BSSID
(of the same SSID), the interface ends up being given a new IP address
by the DHCP server
I recently had the need to compile this against Linux 4.13 (from current
xenial hwe-edge).
I was able to use patches 0023-add-support-for-Linux-4.11.patch and 0024
-add-support-for-Linux-4.12.patch from bcmwl_6.30.223.271+bdcom-
0ubuntu1~1.2 as the basis for creating 0014-add-support-for-
** Summary changed:
- Xenial update to v4.4.26 stable release
+ Xenial update to v4.4.27 stable release
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each
4 matches
Mail list logo
