>> >> * WLAN list manipulation: The current phase 1 API does not include the >> ability to modify the list of known WLANs. In phase 0, this was possible, >> though it required editing the text file. In phase 0.5, the GUI allows >> you to modify the list, using some basic libnwam functions. >> >> We discussed making this list another library object, which would be >> operated on with a set of functions much like the existing objects. >> This would be a non-trivial addition to the phase 1 work. >> >> Another possibility might be to keep the existing interface, and look >> at updating after phase 1 is completed. >> >> In any case, we can't have a regression here: the user needs to be able >> to modify the list via the GUI. >> >> > I?ve been trying to figure out a way of pushing the known > wifi config data into the existing config model for NCUs, ENMs > and locations - i.e. .conf files in which each line consists of > a name followed by a set of property/type/values tuples. The > known wifi config doesn?t really fit this model, so I think > the best thing is to stick with the existing interfaces and backend > file format with some slight modifications for consistency with the > rest of phase 1 libnwam. Phase 1 spec (besides the GUI) doesn't discuss wireless networks at all. I think everything that Phase 0 and 0.5 added should be included in Phase 1 in one way or another.
We also need to determine if BSSID's are used to connect to wlans or not? If they are not used, then I vote for not including them in the known_wifi_nets list. The list and file can get pretty long with the same ESSID. There was some discussion at http://www.opensolaris.org/jive/thread.jspa?threadID=83358 about how the BSSID's came about. (http://defect.opensolaris.org/bz/show_bug.cgi?id=5460) > > Also, the phase 0.5 libnwam API includes a few other > functions which we may need - a rescan trigger function > (libnwam_start_rescan()), wlan selection > (libnwam_select_wlan()). retrieval/freeing of most recent > cached wlan list (libnwam_get_wlan_list(), > libnwam_free_wlan_list()). Which of these, if any, > do we need for phase 1? > I think all of them are needed. The functionalities provided by phase 0.5 are needed for phase 1 also. As for prioritizing wlans to connect to when multiple available wlans are in the known list, we can use the ordering in this list. The GUI can provide a "Move up"/"Move down" for reordering (along with the "delete" it currently provides) .... This is in the "Connection Properties: Wireless" screenshot in the GUI specs for Phase 1. Anurag
