State of roaming support in wpa_supplicant 0.5.7

[LTI. - Ticmanis, Linards]

Hello all,

I would like to know, what is the state of seamless roaming support in wpa_supplicant 0.5.7 if the driver does not do its own roaming.

Specifically, I would like the following to happen in WPA-PSK mode:

1.) Scan regularly even while associated.
2.) If another AP has decidedly better signal level than the one we're on, reassociate with that other AP. Don't wait until the first AP is totally out of range.
3.) Do a decent handoff that minimizes the amount of lost pings (or other lost data).

I'm using the following configuration:

ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1
fast_reauth=1
network={
	ssid="hidden_stuff"
	mode=0
	scan_ssid=1
	key_mgmt=WPA-PSK
	psk="stuff"
}

With this configuration, the supplicant issues scans regularly, but doesn't switch APs until the connection has been lost, which means a good number of lost pings, about 5-10 seconds without any connectivity, and of course frequent retransmits in the case where the first AP never goes out of range completely but the signal gets pretty bad.

Is it possible to do what I want to do with wpa_supplicant? Or do I need to implement roaming in the driver in this case?

On first glance, the function wpa_supplicant_select_bss() in events.c doesn't seem to contain any prioritizing by signal quality. Am I correct that no such prioritizing takes place in the supplicant at this time?

I'd be glad for any help.

Best wishes,
-- 
Linards Ticmanis
H?ft & Wessel Aktiengesellschaft, Sitz Hannover
Handelsregister (Commercial register) : Amtsgericht Hannover HRB 57006
USt-ID (VAT) : DE 115681962 - WEEE-Reg.-Nr. DE 68170458
Vorstand (Board of Management) : Hansjoachim Oehmen (Vorsitzender / CEO), 
Peter Claussen (stv. Vorsitzender / COO), Thomas Wolf
Vorsitzender des Aufsichtsrates (Chairman of the Supervisory Board) : Prof. Dr. Dr. h.c. Klaus E. Goehrmann