See http://www.mail-archive.com/connman@connman.net/msg01653.html
-- IP ranges allocation and check
-
- 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.
-
-
- Personal firewall
Priority: Low
security integration.
+- Favorite service migration removal
+
+ Priority: Medium
+ Complexity: C1
+ When: 12/2012
+
+ Remove service migration code that moves services from default.profile
+ to the current directory-based structure.
+
WiFi
====
Priority: Medium
Complexity: C4
- Owner: Samuel Ortiz <sameo@linux.intel.com>
+ Owner: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
While connected ConnMan should offload the background scanning to
wpa_supplicant. Wpa_supplicant allows for a fancy background scan
Complexity: C2
+- Previous WPS pin code sending
-Bluetooth
-=========
+ Priority: Medium
+ Complexity: C2
-- DUN client
+ Provide previous WPS pin code in PreviousPassphrase field if WPS was used.
- Priority: Low
- Complexity: C4
- Owner: Mario Tokarz <mario.tokarz@bmw-carit.de>
+Bluetooth
+=========
Cellular
Owner: Jukka Rissanen <jukka.rissanen@linux.intel.com>
-- Split tunnelling
-
- Priority: Low
- Complexity: C8
- Dependencies: Core:Private networks
- Owner: Jukka Rissanen <jukka.rissanen@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.
-
-
Tools
=====