TPE RIL Network team/NetworkManagerEnhancement/2014-07-17: Difference between revisions
Jump to navigation
Jump to search
Ethantseng (talk | contribs) (Created page with "Time: 2014/717, 4-5pm Attendee: Vincent, Chuck, Henry, Dimi, Ethan '''Topic''': Discuss the impact of NetworkManager enhancement to WifiWorker. '''Agenda''' * Behaviors of n...") |
No edit summary |
||
| Line 1: | Line 1: | ||
Time | == Time == | ||
2014/717, 4-5pm | |||
== Attendee == | |||
Vincent, Chuck, Henry, Dimi, Ethan | |||
== Topic == | |||
Discuss the impact of NetworkManager enhancement to WifiWorker. | |||
== Agenda == | |||
* Behaviors of nsINetworkInterface::connect()/disconnect() in WifiWorker. | * Behaviors of nsINetworkInterface::connect()/disconnect() in WifiWorker. | ||
* How to deal with different modes: WiFi, Wifi-Tethering and Wifi-Direct? | * How to deal with different modes: WiFi, Wifi-Tethering and Wifi-Direct? | ||
* How does WifiWorker report connection status to NetworkManager? | * How does WifiWorker report connection status to NetworkManager? | ||
== Conclusions == | |||
# Suggest to add an attribue to nsINetworkInfo to indicate the interface is connectable or not. | # Suggest to add an attribue to nsINetworkInfo to indicate the interface is connectable or not. | ||
interface nsINetworkInfo { | interface nsINetworkInfo { | ||
| Line 26: | Line 30: | ||
#* nsINetworkInterface::disconnect() will disable WifiP2p function. | #* nsINetworkInterface::disconnect() will disable WifiP2p function. | ||
# NetworkManager observes the events for network state changes (the same as now). | # 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? | # If multiple network interfaces are connected, how does NetworkManager decide routing policy? | ||
# How to override NetworkManager’s network policy with user preference? | # How to override NetworkManager’s network policy with user preference? | ||
Revision as of 03:04, 24 July 2014
Time
2014/717, 4-5pm
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.
interface nsINetworkInfo {
…...
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?