On Tuesday 16 September 2008 10:25:10 Kalle Valo wrote: >> My main problem is that adding a beacon threshold to mac80211 >> isn't a > Still I don't see a problem here, all the mac80211 drivers > should already now report similar signal strenght to the > mac80211 in comparable level. And we could later allow something similar to "iwconfig ethX sens Y" to modify the the threshold (or whatever else we use, even some arbitrary calculated quality value). The possibility to modify this would allow the user to define how eager mac80211 is when it comes to roaming. I actually believe that we shouldn't use Quality as roaming decision base. From what I know, Quality also counts in re-transmissions, transfer speed (1 MBit/s is worse then 54 MBit/s) and whatever else. Therefore you can calculate quality only for the current conection. But when you scan, you only see signal strength and/or SNR of the APs in sight. You won't know their quality of those APs. But you could compare your current signal strength and/or SNR to the signal strength/SNR of the APs in sight. That would mean that you can use the Quality still for a decision "Should I do a background scan or not?". But you cannot use it for a decision "Should I switch to this AP or not?". And so I wonder why I should use quality in the first place if it brings me only so far ... -- 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
