bssid / freq_list not respected in wpa_supplicant.conf (assuming this may be an issue with the kernel wifi driver?)

[anfractuosity]

Describe the bug

I set the ssid, bssid, freq_list of my 5GHz AP by doing:

ssid="blah" bssid=.... freq_list=5220

In my wpa_supplicant.conf

However, the Pi 4B, will at some point fallback from the 5GHz connection to my 2.4GHz AP, even though it has a different bssid and frequency.

(I have also tried removing the ssid and leaving just the bssid, but then it didn't connect at all)

I found other people having the same issue - https://raspberrypi.stackexchange.com/questions/116486/choose-a-specific-wifi-ap-or-frequency however the freq_list parameter doesn't prevent the wifi changing to a different bssid / frequency for me.

Expected behaviour

I would expect after specifying the bssid that the Pi would not connect to alternative bssids.

Actual behaviour

Alternative bssids are connected to, than the one specified in wpa_supplicant.conf

System

Raspberry Pi 4 Model B Rev 1.2 PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)"

[kwinz]

I have the same issue. freq_list option in wpa_supplicant.conf seems to be ignored.

[bpsib]

My guess is that this is something to do with firmware roaming support. It can be turned off by creating /etc/modprobe.d/brcmfmac.conf and add the following: options brcmfmac roamoff=1

I haven't had chance to try this myself so let me know if this fixes the issue.

[lobstaj]

My guess is that this is something to do with firmware roaming support. It can be turned off by creating /etc/modprobe.d/brcmfmac.conf and add the following: options brcmfmac roamoff=1

I haven't had chance to try this myself so let me know if this fixes the issue.

This works like a charm, thank you very much!

[anfractuosity]

I've just been testing setting bssid again recently in wpa_supplicant, using the latest kernel/raspberry pi OS.

Even without roamoff=1, it seems to be currently sticking to the 5GHz channel for me.

Will keep my eye on it, to see if it ever changes.

[milux]

My guess is that this is something to do with firmware roaming support. It can be turned off by creating /etc/modprobe.d/brcmfmac.conf and add the following: options brcmfmac roamoff=1

I haven't had chance to try this myself so let me know if this fixes the issue.

Negative for me. :disappointed:

[bpsib]

Negative for me. 😞

@milux Did you reboot? It didn't work for me until I rebooted.

[milux]

Negative for me. 😞

@milux Did you reboot? It didn't work for me until I rebooted.

Of course I did. I'm aware of the fact that changes to kernel module parameters generally require a reboot to take effect. :wink: I tried to force the WiFi module to stick with 5 GHz in client configuration, and failed multiple times.

Meanwhile, I simply accepted that the driver(s) are too buggy to reliably setup WiFi client and WiFi AP via the same network interface, and ordered a separate USB WiFi dongle. :shrug: