[PATCH 2/2] wnm: Add neigh ies to bss transition mgt request

Ben Greear greearb at candelatech.com
Tue Apr 9 10:54:43 PDT 2019


On 4/7/19 1:23 PM, Ben Greear wrote:
> 
> 
> On 04/07/2019 06:50 AM, Jouni Malinen wrote:
>> On Thu, Mar 21, 2019 at 07:33:26AM -0700, greearb at candelatech.com wrote:
>>> If a station requests a bss transition, then send add any
>>> configured neighbors to the response.
>>
>> Why? What would make those neighbors good candidates for the particular
>> station? I don't think this should be done without some tracking of how
>> the particular station is visible to the neighbors and how loaded the
>> channels are for each of the neighbors, i.e., this would require close
>> coordination between all the neighboring APs.
> 
> A controller can keep a close eye on everything and set/remove neighbors
> from each hostapd as it deems necessary.
> 
> I don't think this is something that individual hostapd will be able to
> manage themselves, but it would be nice to have hostapd handle sending
> the messages once it is properly configured.

After some more thinking on this, I would tend to agree that my initial approach
is too simplistic because different STAs requesting to the same AP should likely
get different answers (ie, one STA is better for Neigh-1 and another STA is better
for Neigh-2.

For a simple case, where we have no triangulation and X APs in an area, then
a simple controller could poke some info in the the neigh DB so each hostapd
would be up to date on how many STA are connected to each AP, for instance.

Would you be interested in a patch that allowed adding that to the neigh
DB and then (if neigh is so flagged), add the least-used AP(s)
to the response automatically?

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com




More information about the Hostap mailing list