http://defect.opensolaris.org/bz/show_bug.cgi?id=4993
Darren Kenny <dkenny at opensolaris.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|INCOMPLETE |NEW
--- Comment #2 from Darren Kenny <dkenny at opensolaris.org> 2009-05-06
02:06:31 ---
(In reply to comment #1)
> there's a few issues here. Dealing with the resolved one first -
> WLAN keys are now named by ESSID only, and ESSID/BSSID combination keys
> from phase 0(.5) will be migrated to ESSID-only keys - see 8547. So if
> you enter a key for sunwifi say, it will be valid for all APs of that
> ESSID name, not just ones that share the BSSID. As regards continuously
> monitoring signal strength, we still do periodic scans, and if another
> preferred known AP (perhaps with the same ESSID) with a higher signal strength
> is encountered (assuming signal strength drops below scan_level (a new SMF
> property) we connect to it instead. Continuously monitoring signal strength
> isn't really feasible I don't think, but we could drop the scan interval down
> from 120s to every minute perhaps. Would that be sufficient? Thanks!
I believe that there are two things:
1) The periodic scan - this keeps NWAM aware of all other networks, and I think
that's fine at 120 seconds.
2) For a currently connected network, this is specifically looking at the
signal strength for only that network - which we do in the UI to show signal
strength information - it's not that expensive, and if you do something like a
running average (e.g. from the last 10 samples, with a sample taken every 2
seconds) then you can relatively quickly discover when the currently connected
network goes so weak it's unusable and then react quickly - having the user
wait for the next periodic scan isn't very usable and very unlike what happens
on other OSes.
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
