Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 10 Aug 2021 19:59:15 +0000
To:     "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
From:   Michael Yartys <michael.yartys@protonmail.com>
Reply-To: Michael Yartys <michael.yartys@protonmail.com>
Subject: Not able to roam on FT-SAE network
Message-ID: <NB-cdP_zWop55KKgEYOXNh25URknq08i4hqQ2mRF9aVBi6YFIlJaYIk9pg1ewyJY7hLC1x8mtEFX5WyutbN3YZRoyaJMvOpn7MH2GsUTv7o=@protonmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hi

I've been running an FT-SAE network for quite some time now, and I've long =
noticed that my both my laptops with Intel 7260AC cards are unable to roam =
from one AP to another. When I move the laptops to an area with poor signal=
 strength the background scanning of NetworkManager/hostapd is triggered as=
 expected and a roam appears to be initiated, but instead of successfully r=
oaming to the other AP with better signal strength it ends up returning to =
the current AP. This keeps on happening until I either manually disable and=
 re-enable wifi, or if I move back to an area where the current AP has good=
 signal strength. The laptops are running the following distros, kernels an=
d wpa_supplicant versions:

-- Laptop 1 --
* Fedora 34
* 5.13.8-200
* wpa_supplicant v2.9

-- Laptop 2 --
* Ubuntu 20.04.2 LTS
* 5.11.0-25
* wpa_supplicant v2.10-devel-hostap_2_9-2285-gc3155a725 (recent snapshot)

I can provide relevant logs from wpa_supplicant and the APs to developers p=
ersonally.

Michael