On 10/09/2009 23:46, Renee Danson Sommerfeld wrote: > (Following up on discussion in > http://defect.opensolaris.org/bz/show_bug.cgi?id=10151) > >>> 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? > > The bug in question was about (mis)behavior when multiple wireless > links were available in the system. From an nwamd/state machine > point of view, we've resolved the problems; if a lower-priority > wireless link is in use, and a higher priority one becomes available, > we do make the switch. > > But additional questions were raised during discussion of the bug. > Looking at the code, the WLAN_NEED_CHOICE event is specific to a link, > and the nwam_wlan_select() interface requires that a link name be > specified. So in the case where nwamd is trying two wireless links > in parallel, event consumers (the GUI!) could potentially see two > separate WLAN_NEED_CHOICE events; and the state machine will move > forward with whichever link it receives a response for. > > So, Darren: does that meet with your expectations? Will the GUI handle > that scenario?
It should - the NEED_CHOICE will only prompt for a selection. The menus will be populated with possibly two entries for visible networks, with the name of the device added to the essid, so you can choose which one you prefer to use, this already exists in Phase 0.5... HTH, Darren.
