>> How about this case where RSSI is disabled for SSID1 and and SSID 4
>> and only SSID2 and SSID3 needs RSSI filter.
>>
>> SSID1, SSID2, RSSI, SSID3, RSSI, SSID4
>>
>> Wouldn't this change set RSSI of SSID3 to SSID1 and SSID4 ?
>> Did i miss to understand anything ?
>
>It's not a case that was previously supported. Previously, all you could
>do was
>
>{ SSID1 | SSID2 | SSID3 } + RSSI
>
>Now, you can do
>
>{ (SSID1, RSSI1) | (SSID2, RSSI2) | (SSID3, RSSI3) }
>
>IOW, it wouldn't change anything - note how the RSSI value before used
>to set request->rssi_thold, and not request->matchsets[i].rssi_thold.
>
>johannes
Agree your change and got your idea.
I am thinking like, Include RSSI only for SSID which require threshold limit check.
For other cases where SSID doesn't require rssi limit check, we can exclude adding RSSI attr for that SSID.
{ (SSID1) | (SSID2, RSSI2) | (SSID3) }
In that way, wpa_supplicant do not have to pass RSSI attr always for each SSID (case like, few SSID requires RSSI and few SSID doesn't require RSSI).
Anyway, I am fine with your change.
-Raja--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
