http://defect.opensolaris.org/bz/show_bug.cgi?id=10084
--- Comment #2 from amaguire <alan.maguire at sun.com> 2009-08-08 10:07:13 ---
(In reply to comment #1)
> (In reply to comment #0)
> > On startup the GUI expects that the nwam_wlan_t data fetched from the wlan
> > cache would tell us which wlan is in use when connected.
> >
> > But this would seem to not be the case, since I'm currently connected, but
> > the
> > nwam_wlan_t contents don't have any connected flags set to TRUE:
> >
> >
> > (dbx) print wlans[0..1]
> > wlans[0..2] =
> > [0] = {
> > essid = "DarrenLucanLinksys"
> > bssid = "0:21:29:94:55:38"
> > signal_strength = "weak"
> > security_mode = 3U
> > speed = 108U
> > channel = 1U
> > bsstype = 1U
> > keyindex = 1U
> > have_key = B_FALSE
> > selected = B_FALSE
> > connected = B_FALSE
> > }
> > [1] = {
> > essid = "DOVADO"
> > bssid = "0:16:a6:10:1d:18"
> > signal_strength = "good"
> > security_mode = 1U
> > speed = 108U
> > channel = 9U
> > bsstype = 1U
> > keyindex = 1U
> > have_key = B_FALSE
> > selected = B_FALSE
> > connected = B_FALSE
> > }
> > (dbx) dladm show-wifi
> > LINK STATUS ESSID SEC STRENGTH MODE
> > SPEED
> > ath0 connected DOVADO none good g
> > 12Mb
>
> The problem here is that although when a subsequent scan is done, we do set
> these values correctly, on initial connect we don't edit the cached scan
> results to reflect the fact we've just connected. This leaves a window of
> ~120s where the fact that we're connected isn't reflected in the scan results.
> The solution is on connection success to set connected/selected/have_key for
> the WLAN we've connected to.
...and the other thing we need to do is to trigger a scan results event
when we change such things so the GUI gets an updated view of the state.
--
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.
