Priority: High
Complexity: C4
Owner: Daniel Wagner <daniel.wagner@bmw-carit.de>
- Owner: Samuel Ortiz <sameo@linux.intel.com>
+ 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
See http://www.mail-archive.com/connman@connman.net/msg01653.html
-- WiSPR support
-
+- main.conf FallbackTimeservers, FallbackNameservers
Priority: Medium
- Complexity: C4
- Owner: Marcel Holtmann <marcel@holtmann.org>
-
- Based on the portal detection parsing results, and provisioned
- credentials, ConnMan should be able to initiate a WiSPR authentication.
-
-
-- DNS caching
-
- Priority: Low
- Complexity: C4
-
- A simple initial implementation would see ConnMan's dnsproxy
- caching the DNS record based on their TTL.
+ Complexity: C2
+ Owner:
+ Both entries should take a string list as arguments and can contain
+ mixed combination of fully qualified domain names, IPv4 and IPv6
+ addresses. In absence of main.conf or if this entry is not present
+ then no fallback servers are used. These configuration file values
+ will obsolete plugins/meego.c and plugins/google.c.
+ See http://lists.connman.net/pipermail/connman/2012-March/008605.html
-- Power management
+- main.conf DefaultAutoConnectTechnologies
Priority: Medium
- Complexity: C4
- Owner: Samuel Ortiz <sameo@linux.intel.com>
-
- Implement a simple device pm hook that ConnMan's core code would
- use whenever it decides to put devices in power save mode. Although
- the kernel runtime power management code should take care of that,
- not all driver (especially WiFi ones) implement runtime PM hooks.
+ Complexity: C2
+ Owner:
+ The default autoconnect value for a new service that has not been seen. After
+ that it can be changed on a per service level via AutoConnect property.
+ The default value if not present should be "ethernet,wifi".
+ See http://lists.connman.net/pipermail/connman/2012-March/008605.html
-- IPv6 gateway handling
+- main.conf PriorityTechnologies
Priority: Medium
- Complexity: C4
-
- We should be able to switch between IPv6 only services and thus
- change the default IPv6 gateway on the fly. For that we need to
- improve the connection.c code to properly handle IPv6 gateways.
-
-
-- IP ranges allocation and check
-
- Priority: High
Complexity: C2
+ Owner: Patrik Flykt <patrik.flykt@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.
+ Handle automatic switch from one technology to another one. By default
+ this value should be empty and no automatic switching is happening as
+ long as technology is connected. The list is ordered.
+ See http://lists.connman.net/pipermail/connman/2012-March/008605.html
- Personal firewall
Priority: Low
Complexity: C8
+ Owner: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
- Extend the iptables code and provide a D-Bus API for personal firewalling.
+ Discuss and implement a basic and safe firewalling strategy into
+ Connman. Provide a D-Bus API for personal firewalling.
- PACRunner extensions
WiFi
====
-- Ad-Hoc support
-
- Priority: Medium
- Complexity: C2
- Owner: Samuel Ortiz <sameo@linux.intel.com>
-
-
-- Fast Connect
-
- Priority: Low
- Complexity: C4
- Owner: Samuel Ortiz <sameo@linux.intel.com>
-
-
- EAP-AKA/SIM
Priority: Medium
Priority: Low
Complexity: C1
- Owner: Henri Bragge <henri.bragge@ixonos.com>
-- EAP-GTC
+- Wireless background scan
- Priority: Low
- Complexity: C1
- Owner: Henri Bragge <henri.bragge@ixonos.com>
+ Priority: Medium
+ Complexity: C4
+ 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.
- WiFi p2p
VPN
===
-- l2tp support
-
- Priority: Low
- Complexity: C2
- Owner: Mohamed Abbas <mohamed.abbas@intel.com>
+- IPsec
+ Priority: Medium
+ Complexity: C4
+ Owner: Jukka Rissanen <jukka.rissanen@linux.intel.com>
-- pptp support
- Priority: Low
- Complexity: C2
- Owner: Mohamed Abbas <mohamed.abbas@intel.com>
+Tools
+=====
-
-- IPsec
+- 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.
-- Split tunnelling
+User Interface
+==============
+
+- GNOME3 UI
Priority: Low
- Complexity: C8
- Dependencies: Core:Private networks
+ Complexity: C4
+ Owner: Alok Barsode <alok.barsode@linux.intel.com>
- 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.
+ A GNOME3 shell user interface would make it easier for mainstream distros
+ users to use ConnMan.