http://defect.opensolaris.org/bz/show_bug.cgi?id=10151


Renee Danson Sommerfeld <renee.danson at sun.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CAUSEKNOWN                  |CLOSED
         Resolution|                            |WORKSFORME


--- Comment #6 from Darren Kenny <dkenny at opensolaris.org> 2009-09-09 
10:10:29 UTC ---
(In reply to comment #5)
> Can somebody retest this with the changes I integrated the other week.  We are
> constantly trying higher prio groups.  I'm not sure how that meshes with how
> the GUI prompts for wlans?

In what sense? We will only prompt for a wlan key if we get a KEY_NEEDED event.
How does that some into this?

--- Comment #7 from Renee Danson Sommerfeld <renee.danson at sun.com> 
2009-09-10 22:02:03 UTC ---
(In reply to comment #5)
> Can somebody retest this with the changes I integrated the other week.  We are
> constantly trying higher prio groups.

Yep, this resolves the problem that I was seeing.  I set up the User NCP with
three priority groups: priority 1, e1000g0; priority 2, wpi0; priority 3 pcan0.
pcan0 was a pccard wifi device.  With the ethernet unplugged and the radio off
for wpi0, pcan0 connected.  When I turned wpi0's radio back on, it connected at
the next scan interval, and pcan0 was disconnected.

> I'm not sure how that meshes with how
> the GUI prompts for wlans?

I think that's sort of a different question: how do we deal with asking the
users for wlan info when there are multiple wireless devices?  Is the
NEED_CHOICE event, or the nwam_wlan_select() reply tied to a particular
wireless link?  I think that question is orthogonal to this bug, so I'm going
to close it out. I'll start a thread about these questions on nwam-dev.

-- 
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.
You are the assignee for the bug.

Reply via email to