AgeCommit message (Collapse)AuthorFilesLines
2013-02-01Release 1.11upstream/1.111.11Marcel Holtmann2-1/+13
2013-01-30dundee: Set network available is needed only when scanningPatrik Flykt1-2/+0
2013-01-30ofono: Set network available is needed only when scanningPatrik Flykt1-2/+0
2013-01-30ethernet: Set network available is needed only when scanningPatrik Flykt1-2/+0
2013-01-30README: Add kernel options needed for tetheringPatrik Flykt1-0/+17
2013-01-30TODO: Update TODO with Bluez 4.x removal taskPatrik Flykt1-10/+4
2013-01-30bluetooth: Implement tethering for the Bluez 5 bluetooth pluginPatrik Flykt1-0/+117
2013-01-30technology: Support multiple technology driversPatrik Flykt1-49/+111
As tethering is enabled on the technology level, both the bluetooth and the bluetooth_legacy plugin need to register technology drivers for CONNMAN_SERVICE_TYPE_BLUETOOTH. Modify the technology code to create a list of registered technology drivers instead of a single technology driver pointer.
2013-01-30bluetooth: Connect and disconnect a PAN NAP networkPatrik Flykt1-5/+137
Implement connect and disconnect functionality for a ConnMan network. On network creation check the connection status of the Bluez 5 Network1 object and set the network to connected when needed.
2013-01-30service: Must not return NULL with a synchronous GDBus method callPatrik Flykt1-2/+0
If NULL is returned, GDBus will call the registered function repeatedly.
2013-01-30bluetooth: Expose Bluez 5 org.bluez.Network1 objects as networksPatrik Flykt1-4/+133
Create ConnMan networks for those Bluez 5 org.bluez.Network1/Device1 objects that support PAN NAP. A network is created or removed in response to the Network1/Device1 being created or when the Device1 object's UUID changed. The ConnMan network struct is added to and removed from the ConnMan device when the device is created, enabled or disabled.
2013-01-30network: Allow more than one network driver register the same typePatrik Flykt1-10/+0
Allowing more than one network driver to register the same network type requires the network driver to properly identify which networks belong to it in the network driver probe function.
2013-01-30bluetooth_legacy: Check network in probe functionPatrik Flykt1-4/+18
The network probed can belong to the new Bluez 5 bluetooth plugin or to this plugin. Check if this plugin created the network and proceed accordingly.
2013-01-30bluetooth: Keep track of Bluez 5 org.bluez.Network1 objectsPatrik Flykt1-0/+172
Set up functions monitoring Bluez 5 org.bluez.Network1 objects being added and removed. Add a GDBusProxy for the org.bluez.Device1 object that corresponds to the Network1 object. Set up functions monitoring Network1 'Connected' and Device1 'UUID' properties.
2013-01-30bluetooth: Expose Bluez 5 adapters as ConnMan devicesPatrik Flykt1-0/+308
Set up functions monitoring Bluez 5 objects being added and removed using GDBusProxy. When an adapter appears, create a new device for it and set up a watch function for the adapter's 'Powered' property. Keep the adapter 'Powered' property in sync with the device state and if they differ reset the adapter to the device state. Also update the Bluez 5 adapter 'Powered' property when the device is enabled or disabled.
2013-01-30technology: Enable/disable individual devices also with rfkillPatrik Flykt1-4/+16
In order to keep ConnMan devices in sync with Bluz 5 adapters, the individual devices need to be enabled/disabled also when unblocking/blocking them with rfkill. Thus enable devices after unblocking and disable devices before blocking with rfkill.
2013-01-30bluetooth: Register technology driverPatrik Flykt1-1/+31
2013-01-30bluetooth: Add new bluetooth pluginPatrik Flykt2-0/+51
2013-01-30bluetooth: Rename bluetooth plugin to bluetooth_legacyPatrik Flykt2-8/+11
Set the plugin priority to CONNMAN_PLUGIN_PRIORITY_LOW and the technology priority to -10. Update strings to "bluetooth_legacy" and use ordinary string instead of ident.
2013-01-30technology: Check technology driver probe function before callingPatrik Flykt1-1/+5
2013-01-30technology: Remove technology driver by pointerPatrik Flykt1-2/+4
Compare the technology driver pointer to the driver being unregistered as the function is supposed to remove only the given driver. Also check if the driver has a remove function before calling it.
2013-01-30technology: Remove unnecessary comparison and gotoPatrik Flykt1-5/+1
2013-01-30ofono: Use ordinary string instead of identPatrik Flykt1-1/+1
The string is only used for debugging purposes.
2013-01-30dundee: Use ordinary string instead of identPatrik Flykt1-1/+1
The string is only used for debugging purposes.
2013-01-30network: Unset driver on failed matchPatrik Flykt1-1/+3
2013-01-28gresolv: Destroy query at the relevant place when parsing the responseTomasz Bursztyka1-4/+2
parse_response() will eventually call sort_and_return_results() which in turn will call the result function. But the result function might cancel the gresolv. At that point all queries belonging to this gresolv are destroyed. Returning back to parse_response(), it calls again destroy_query() on an already destroyed one. Thus leading to a crash. Same issue with query_timeout() Reported by Daniel Wagner
2013-01-24service: Notify leaving online state when downgrading it to readyTomasz Bursztyka1-1/+3
Fixes BMC#25862
2013-01-24ipconfig: IPv6 was enabled too earlyJukka Rissanen1-2/+3
When enabling IPv6 ipconfig, we enable kernel IPv6 support too early. The ipconfig might get unreffed which will disable ipconfig and thus disable kernel IPv6 support. By moving kernel IPv6 enabling after the ipconfig unref call, we make sure that IPv6 kernel support is properly enabled. This is related to fix in commit d479904ecaa2bd9
2013-01-20gdbus: Check for valid path before handling propertiesMarcel Holtmann1-0/+6
2013-01-18dnsproxy: DNS response answer count was incorrectly setJukka Rissanen1-1/+1
We set the answer count in host byte order instead of network byte order when sending cached AAAA record. This problem is only seen in special case when an AAAA record is generated by us when there is IPv4 address in cache but no IPv6 address for the host.
2013-01-16network: Do not report any error when removing a connecting networkTomasz Bursztyka1-1/+2
When connecting a network, if it's related technology is disabled, this network will raise an error through the agent. Leading to a possible retry request from the user, then to a crash if the user does so. Thus, we prevent any error to be raised in such situation and silently disconnect the connecting network instead.
2013-01-16network: Move up code about set_connected() and set_disconnectedTomasz Bursztyka1-625/+627
2013-01-16service: Trigger autoconnect when AutoConnect flag is enabledJukka Rissanen1-0/+3
2013-01-16ipconfig: Do not disable IPv6 in lower up stateJukka Rissanen1-12/+0
Disabling IPv6 in lower up causes problems in IPv6 connectivity. The interface IPv6 status can stay in disabled state because of races. So this patch reverts the commit 4ce90440a70abce7de537777 and lets service IPv6 state go to READY when we get an auto configured address for the interface. Fixes BMC#25929
2013-01-15service: Update notifier state when relevant while getting readyTomasz Bursztyka1-1/+2
When getting 1 service to online, and disonnecting it: Manager state stays at 'ready'. This is due to service updating the notifier about its state 'ready' 2 times. Once when connecting: idle -> ready, and once when disconnecting: online -> ready.
2013-01-15agent: Keep track of the driver to unref user context relevantlyTomasz Bursztyka1-2/+3
Fixes BMC#25884
2013-01-11gweb: Make sure to destroy the lookup before calling any result functionTomasz Bursztyka1-2/+4
Program received signal SIGSEGV, Segmentation fault. Backtrace: 0 0x00000000004219fe in _debug (resolv=0x75f9a0, file=0x497267 "gweb/gresolv.c", caller=0x497598 "destroy_lookup", format=0x497278 "lookup %p id %d ipv4 %p ipv6 %p") at gweb/gresolv.c:136 1 0x0000000000421ac5 in destroy_lookup (lookup=0x760e40) at gweb/gresolv.c:154 2 0x00000000004224ce in sort_and_return_results (lookup=0x760e40) at gweb/gresolv.c:520 3 0x0000000000422597 in query_timeout (user_data=0x760510) at gweb/gresolv.c:542 4 0x00007ffff7b1b26b in g_timeout_dispatch (source=0x760ea0, callback=<optimized out>, user_data=<optimized out>) at gmain.c:4095 5 0x00007ffff7b1a643 in g_main_dispatch (context=0x6f5110) at gmain.c:2784 6 g_main_context_dispatch (context=0x6f5110) at gmain.c:3288 7 0x00007ffff7b1a988 in g_main_context_iterate (dispatch=1, block=<optimized out>, context=0x6f5110, self=<optimized out>) at gmain.c:3359 8 g_main_context_iterate (context=0x6f5110, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3296 9 0x00007ffff7b1ade5 in g_main_loop_run (loop=0x6f4fe0) at gmain.c:3553 10 0x0000000000442a5f in main (argc=1, argv=0x7fffffffdea8) at src/main.c:705 Reported by Daniel Wagner
2013-01-11gsupplicant: Return max SSIDs to scan given by wpa_supplicantPatrik Flykt2-12/+2
Although it seems wpa_supplicant can handle 4 SSIDs in version 0.7.x and 16 starting with 0.8.x, in practise this does not work. Return the value reported without relying on wpa_supplicant internals to handle the situation. In order for hidden scans to work properly, the minimum value needs to be 1.
2013-01-08build: Do not use deprecated AM_CONFIG_HEADERJulien Massot1-1/+1
The long-obsoleted AM_CONFIG_HEADER macro was removed in automake 1.13. Use AC_CONFIG_HEADERS instead.
2013-01-08inet: Fix error handling when bridging interfacesForest Bond1-18/+22
Functions that add and remove interfaces to and from bridges now return an appropriate error code.
2013-01-08inet: Fix error handling when adding/removing routesForest Bond1-84/+152
Functions that add and remove routes now return an appropriate error code. EEXIST and ESRCH are ignored when adding and removing routes (respectively) to reduce spurious error messages in the logs.
2013-01-08vpn-provider: Check if providers list is NULL before using itPatrik Flykt1-0/+3
2013-01-06gdbus: Fix memory leak on properties_set()Anderson Lizardo1-1/+6
The pointer returned by dbus_message_iter_get_signature() must be freed with dbus_free(). Fixes this memory leak: ==1857== 16 bytes in 1 blocks are definitely lost in loss record 104 of 251 ==1857== at 0x402BF52: realloc (in /usr/lib/valgrind/ ==1857== by 0x415E286: dbus_realloc (in /lib/i386-linux-gnu/ ==1857== by 0x415E70B: ??? (in /lib/i386-linux-gnu/ ==1857== by 0x415F17B: ??? (in /lib/i386-linux-gnu/ ==1857== by 0x414CB33: dbus_message_iter_get_signature (in /lib/i386-linux-gnu/ ==1857== by 0x8053239: properties_set (object.c:899) ==1857== by 0x5FFFFF: ??? ==1857==
2013-01-05gdbus: Check signature of property value before calling setterMarcel Holtmann1-0/+5
2013-01-04TODO: Remove the storage migration taskPatrik Flykt1-9/+0
2013-01-04storage: Remove storage migration codePatrik Flykt3-177/+0
2013-01-04TODO: Remove WiMAX removal taskPatrik Flykt1-13/+0
2013-01-04doc: Remove WiMAX info from documentationPatrik Flykt2-36/+20
2013-01-04core: Remove WiMAX definitions from codePatrik Flykt15-83/+10
2013-01-04plugins: Remove WiMAX plugin filesPatrik Flykt3-1822/+0