Core
====
-- connman_element removal
-
- Priority: Low
- Complexity: C8
-
-
-- DHCP lib server
+- Session API implementation
Priority: High
Complexity: C4
- Owner: Martin Xu <martin.xu@intel.com>
+ Owner: Daniel Wagner <daniel.wagner@bmw-carit.de>
+ Owner: Patrik Flykt <patrik.flykt@linux.intel.com>
+ The session API should provide a connection abstraction in order to
+ prioritize applications network accesses, prevent or allow network
+ and bearer roaming, or provide applications with a way to request
+ for periodic network connections. On-demand connections will be
+ implemented through this API as well.
+ See http://www.mail-archive.com/connman@connman.net/msg01653.html
-- On demand connection
- Priority: Medium
- Complexity: C4
- Owner: Samuel Ortiz <sameo@linux.intel.com>
-
- With on demand connection applications get connectivity access
- simply by trying to reach the network. They don't need to
- specifically request for a service connection, but ConnMan
- establishes it on their behalf.
- This feature counter part is idle disconnect. ConnMan needs to be
- able to close the on demand established connections by monitoring
- the link activity. This requires kernel support with e.g. the
- netfilter IDLETIMER target.
+- DNS caching
-- Avahi-zeroconf
-
- Priority: Medium
+ Priority: Low
Complexity: C4
- The IPv4 Link Local part should be integrated into DHCP-lib.
-
-- OpenVPN
-
- Priority: Low
- Complexity: C2
+ A simple initial implementation would see ConnMan's dnsproxy
+ caching the DNS record based on their TTL.
-- VPNc
+- IP ranges allocation and check
- Priority: Low
+ Priority: High
Complexity: C2
+ Guillaume Zajac <guillaume.zajac@linux.intel.com>
+ For both tethering and private networks, but also to detect invalid
+ static IP configurations, we need to have a core IP range layer
+ that manages all currently used IP blocks.
-- iptables wrapper
- Priority: High
- Complexity: C4
- Owner: Samuel Ortiz <sameo@linux.intel.com>
+- Personal firewall
- ConnMan needs to be able to set iptables rules and tables for both
- tethering and on demand connection.
- The main idea is to define an internal API for talking to the
- netfilter socket in order to set our tables and rules. Being in
- sync with the actual iptables library might be problematic.
- A less elegant solution would be a process based one, that would
- simply call the iptables executable.
-
-- Tethering
-
- Priority: Medium
+ Priority: Low
Complexity: C8
- Owner: Marcel Holtmann <marcel@holtmann.org>
- Dependencies: Core:iptables wrapper
- Dependencies: Core:DHCP lib server
-
- Bluetooth, USB and WiFi tethering.
- The tethering framework would typically allow sharing the 3G data
- link between WiFi, Bluetooth or USB clients.
- A bridge needs to be setup and all tethering connections are added
- to it. A DHCP server and a DNS proxy will be running on the bridge.
- Then IP forwarding and masquerading will be set between the default
- service and the bridge interface.
+ Owner: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
+ Discuss and implement a basic and safe firewalling strategy into
+ Connman. Provide a D-Bus API for personal firewalling.
-- Agent callbacks
- Priority: Medium
- Complexity: C2
+- PACRunner extensions
+ Priority: Low
+ Complexity: C4
-- pacrunner
+ Support more URI schemes, support multiple connections, tighter
+ security integration.
- Priority: High
- Complexity: C4
- Owner: Mohamed Abbas <mohamed.abbas@intel.com>
- pacrunner is a standalone daemon that downloads and interpret PAC
- files through a JavaScript interpreter. Once the interpretation is
- done, pacrunner is able to associate a proxy with an URL.
- pacrunner D-Bus interface exports a configuration API for passing
- it the PAC URLs. It also provide a FindProxyForURL() API for
- application to know which proxies to use.
- ConnMan will use pacrunner for both auto and manual proxy
- configurations. Then applications should talk to pacrunner (through
- libproxy for example) to find the right proxies.
- ConnMan will also use the FindProxyForURL() pacruner API for a more
- stable and accurate online detection code.
+WiFi
+====
-- Moving DNS proxy code to ConnMan core
+- EAP-AKA/SIM
Priority: Medium
Complexity: C2
+ Owner: Samuel Ortiz <sameo@linux.intel.com>
- Supporting DNS proxy or resolv.conf direct editing seems more than
- plenty as far as resolving is concerned. So the idea is to move the
- dnsproxy plugin code to ConnMan core and have an additional command
- line option in case one would like to stick with the current
- resolver.c code for editing resolv.conf.
+ This EAP is needed for SIM card based network authentication.
+ ConnMan here plays a minor role: Once wpa_supplicant is set up for
+ starting and EAP-AKA/SIM authentication, it will talk to a SIM card
+ through its pcsc-lite API.
-WiFi
-====
-
-- WPS
+- EAP-FAST
Priority: Low
- Complexity: C2
- Dependencies: Core:Agent callbacks
+ Complexity: C1
-- Ad-Hoc support
+- Wireless background scan
Priority: Medium
- Complexity: C2
- Dependencies: Core:Avahi-zeroconf
-
-
-- Fast Connect
-
- Priority: Low
Complexity: C4
- Dependencies: WiFi:libsupplicant
Owner: Samuel Ortiz <sameo@linux.intel.com>
+ While connected ConnMan should offload the background scanning to
+ wpa_supplicant. Wpa_supplicant allows for a fancy background scan
+ which frequency increases after the current connection signal level
+ drops below a defined threshold.
+ We should also be able to have wpa_supplicant do the background
+ scanning for us when we're not connected, if we have configured our
+ favorite networks.
-- EAP-AKA/SIM
+
+- WiFi p2p
Priority: Medium
Complexity: C2
- Owner: Samuel Ortiz <sameo@linux.intel.com>
- This EAP is needed for SIM card based network authentication.
- ConnMan here plays a minor role: Once wpa_supplicant is set up for
- starting and EAP-AKA/SIM authentication, it will talk to a SIM card
- through its pcsc-lite API.
-- EAP-Fast
+Bluetooth
+=========
+
+- DUN client
Priority: Low
- Complexity: C1
- Owner: Samuel Ortiz <sameo@linux.intel.com>
+ Complexity: C4
+ Owner: Mario Tokarz <mario.tokarz@bmw-carit.de>
-- EAP-GTC
- Priority: Low
- Complexity: C1
- Owner: Samuel Ortiz <sameo@linux.intel.com>
+Cellular
+========
-- WiFi p2p
+VPN
+===
+
+- IPsec
Priority: Medium
- Complexity: C2
+ Complexity: C4
+ Owner: Jukka Rissanen <jukka.rissanen@linux.intel.com>
-- WiFi CRDA setting through 3G country
+- Split tunnelling
Priority: Low
- Complexity: C2
- Owner: Samuel Ortiz <sameo@linux.intel.com>
+ Complexity: C8
+ Dependencies: Core:Private networks
+ Owner: Jukka Rissanen <jukka.rissanen@linux.intel.com>
- Setting the 802.11 country based on the 3G MNC/MCC.
+ The current VPN support puts the VPN interface at the top of the
+ service list, giving VPNs the default route. When doing split
+ tunneling, the system routes packet to the VPN interface for
+ private IPs, while going through the default interface for the rest
+ of the traffic.
-Bluetooth
-=========
+Tools
+=====
-- DUN client
+- Command line tool
Priority: Low
Complexity: C4
+ Owner: Patrik Flykt <patrik.flykt@linux.intel.com>
+
+ For platforms not running python, it could prove useful to provide them
+ with a native single binary command line tool.
-- DUN server
+User Interface
+==============
+
+- GNOME3 UI
Priority: Low
Complexity: C4
+ Owner: Alok Barsode <alok.barsode@linux.intel.com>
+
+ A GNOME3 shell user interface would make it easier for mainstream distros
+ users to use ConnMan.