|
|
| Line 49: |
Line 49: |
| * The problem for wifi is that when APs are available after a while, wpa_supplicant will connect to the AP automatically. But with this new architecture, it should wait for connect() to be called by NetworkManager. | | * The problem for wifi is that when APs are available after a while, wpa_supplicant will connect to the AP automatically. But with this new architecture, it should wait for connect() to be called by NetworkManager. |
| * '''Action''': wifi will tell us how wifi works (scan, associate, connect, disconnect, etc). | | * '''Action''': wifi will tell us how wifi works (scan, associate, connect, disconnect, etc). |
| === 2014/07/17 ===
| |
| * https://wiki.mozilla.org/TPE_RIL_Network_team/NetworkManagerEnhancement/2014-07-17
| |
| * https://www.evernote.com/shard/s118/nl/12803510/a5361aee-034e-49d9-8bab-bfd335e5bc20/
| |
| * Attendee:
| |
| ** Vincent, Chuck, Henry, Dimi, Ethan
| |
| * Topic:
| |
| ** Discuss the impact of NetworkManager enhancement to WifiWorker.
| |
| * Agenda:
| |
| ** Behaviors of nsINetworkInterface::connect()/disconnect() in WifiWorker.
| |
| ** How to deal with different modes: WiFi, Wifi-Tethering and Wifi-Direct?
| |
| ** How does WifiWorker report connection status to NetworkManager?
| |
| * Conclusions:
| |
| ** Suggest to add an attribue to nsINetworkInfo to indicate the interface is connectable or not.
| |
| *** '''readonly attribute boolean connectable;''' /* TRUE for WAN interfaces; FALSE for LAN interfaces, e.g. Tethering */
| |
| ** WiFi network interface exists only when WiFi is enabled.
| |
| *** nsINetworkInterface::connect() will “enable all networks” in WiFi.
| |
| *** nsINetworkInterface::disconnect() will “disable all networks” in WiFi.
| |
| *** We cannot specify a certain SSID (AP) in connect()/disconnect().
| |
| ** Tethering interfaces (Hotspot/USB) exist only when Tethering is enabled.
| |
| *** nsINetworkInfo::connectable = FALSE;
| |
| *** nsINetworkInterface::connect()/disconnect() have no effect on such interfaces.
| |
| ** Wifi-Direct interface exists only when Wifi-Direct is enabled.
| |
| *** nsINetworkInterface::connect() will enable WifiP2p function (e.g. enable WPS)
| |
| *** nsINetworkInterface::disconnect() will disable WifiP2p function.
| |
| ** NetworkManager observes the events for network state changes (the same as now).
| |
| * '''To-Be-Discussed:'''
| |
| ** If multiple network interfaces are connected, how does NetworkManager decide routing policy?
| |
| ** How to override NetworkManager’s network policy with user preference?
| |
| *** For example, the user prefers WiFi to Ethernet, or prefers Data Connection to WiFi?
| |
| ** When interfaces are registered/unregistered, network policy should be re-calculated.
| |
| ** Will NetworkManager bring up an interface automatically after it is unregistered?
| |
|
| |
|
| = Routing improvements = | | = Routing improvements = |