How to handle multiple SSIDs with the same BSS

[Witold Sowa]

Marcel Holtmann pisze:
> Hi Jouni,
> 
>>>> Actually, now that I added a preliminary implementation of BSS table
>>>> management into wpa_supplicant, I do have a unique identifier (unsigned
>>>> int) for each BSS. In other words, there should be no need to
>>>> concatenate BSSID and SSID in hex here and we could just use that new
>>>> identifier and make D-Bus code use the BSS table as the source of the
>>>> information.
>>> sounds great. This should make things work smoothly soon.
>> I converted the new D-Bus API to use the BSS table instead of scan
>> results. This will hopefully resolve the multi-SSID issue you mentioned
>> earlier. I did only minimal testing with the wpas-dbus-new.py script and
>> d-feet, so please let me know if I missed something in the changes.
> 
> I haven't done extensive testing yet, but so far it looks pretty good.
> 
Yeah, looks really good. Now we can add properties to BSS dbus objects
and send change notifications easily.

>> This does not add any new signals yet, but the BSS property changes
>> would be easily available from wpa_bss_update() in wpa_supplicant/bss.c.
> 
> I noticed the aging of the BSS and I do like that feature. How do you
> determinate when a BSS is too old and should be removed?
>
Seems like there are two aging criteria:
1) A BSS hasn't been seen in last two scan results
2) A BSS hasn't been seen within last 180 seconds (checked every 10 seconds)

Regards,
Witek.