Re: IWD 1.27 with brcmfmac not working for roaming

[James Prestwood <prestwoj@gmail.com>]

On 10/30/24 12:19 PM, Martin Petzold wrote:
> Dear James,
>
> I am still investigating several things. Also it seems the related 
> roaming environment is quite a challenge. Maybe if we manage this one, 
> others won't be a problem.
>
> Am 12.10.24 um 13:51 schrieb Arend van Spriel:
>> On 10/12/2024 1:06 PM, Martin Petzold wrote:
>>>> 3. If you say roaming can be handled by firmware (driver?) OR 
>>>> daemon (IWD), what is the best approach and how to configure it?
>>>
>>> This question is still open for me. In general the question, will 
>>> brcmfmac work with the laird firmware and IWD stable (really good) 
>>> also for roaming?
>>
>> In general it is best to let firmware take care of roaming. You can 
>> try using the module parameter 'roam_off' and see how well IWD takes 
>> care of roaming. I have never used IWD.
>
> What will happen if I use 'roam_off' to switch off roaming in firmware 
> (I understand roaming is done in firmware and not brcmfmac driver)?
>
> Would you expect it to work? And IWD taking over as it should?
>
> Additional question: Could there be any power_save enabled in my setup?
>
> (btw. some online sources tell the parameter 'roamoff' and not 
> 'roam_off')

IWD is not going to be able to roam because full mac cards don't expose 
the ability for userspace to control that, or didn't at least when 
fullmac support was added to IWD. It seems like this might be changing, 
but at this time IWD likely won't roam. And if the driver doesn't 
support CMD_AUTHENTICATE and CMD_ASSOCIATE its entirely not possible for 
userspace to initiate a roam on those drivers.

>
> Thanks,
>
> Martin
>