AgeCommit message (Collapse)AuthorFilesLines
2012-12-19require python-gobjectsubmit/trunk/20121219.192236accepted/trunk/20121219.192230Anas Nashif2-1/+7
2012-12-19bootstrap correctlyAnas Nashif1-1/+1
2012-12-19run autogenAnas Nashif1-0/+1
2012-12-19add packagingAnas Nashif2-0/+93
2012-10-26Release 1.91.9Marcel Holtmann2-1/+10
2012-10-26technology: Do not proceed with tethering if technology is not enabledTomasz Bursztyka1-0/+4
Fixes BMC#25846
2012-10-25systemd: prevent duplicate logging messages in journalMarti Raudsepp1-0/+1
By default, both stdout and syslog messages go to the systemd journal, which results in duplicate messages being logged. Thanks to Vinicius Costa Gomes for pointing out this problem.
2012-10-25technology: Do not presume a technology being hardblocked when createdTomasz Bursztyka1-6/+2
This fixes an issue with the TechnologyAdded signal when the first un-hardblock event occurs: - when a technology was created, D-Bus registration was done and hardblock was set to TRUE even if there was no evidence that the technology was rfkill driven - when the technology was updated to be rfkill driven, hardblock was already set to TRUE and thus the technology was not unregistered - when an rfkill event un-hardblocks the technology, the TechnologyAdded signal was not sent since the technology was already registered to D-Bus
2012-10-25dnsproxy: Add reply host part length checkingPatrik Flykt1-5/+17
Check that the first part of the name is not of zero length before attempting to calculate the length of the domain part. Also ensure the domain lenght checking does not run outside of the receive buffer. Also add debug messages for ids and lengths in order to pinpoint any possible problems.
2012-10-23wispr: Free wispr portal context in the relevant placeTomasz Bursztyka1-11/+11
This fixes 2 issues: - calling __connman_service_ipconfig_indicate_state() might lead to restart wispr_portal check, so context should not be freed afterward but beforehand. - freeing the context in wispr_manage_message() should not happen since wispr_manage_message() will return back to wispr_portal_web_result() where we can still use the context. Thanks to Julien Massot <> who reported the issue and provided logs.
2012-10-22device: Do not mark connecting networks unavailableTomasz Bursztyka1-1/+2
When autoscan fallback code is started, it sets scanning to true which in turn marks all networks unavailable except for the ones that are already connected. When connecting during an ongoing autoscan, the connection attempt stops autoscan and all unavailable networks are removed, also the one to be connected. The fix is to ignore both connected and connecting networks when marking networks unavailable.
2012-10-19network: Fix typo in debug printJukka Rissanen1-1/+1
2012-10-19web: Make debug func print more useful informationJukka Rissanen1-3/+11
The file and function name are printed in debug prints.
2012-10-19gresolv: Remove query from queue before destroying the queryJukka Rissanen1-1/+1
The order of actions is important here.
2012-10-19gresolv: Make sure we will not receive DNS data after closingJukka Rissanen1-1/+3
We must close the channel when freeing the resolver object, otherwise we might still receive data when the resolver has been freed already. Fixes BMC#25757
2012-10-19gresolv: Add more debug printsJukka Rissanen1-5/+31
2012-10-19gresolv: Make debug func print more useful informationJukka Rissanen1-3/+11
The file and function names are printed in debug prints.
2012-10-18service: Prefer user connected services with SingleConnectedTechnologyPatrik Flykt1-0/+20
Don't override user connected services with the ones selected by the preferred technology list when SingleConnectedTechnology is enabled. Do this by checking each connected service sorted in the beginning of the service list for the userconnect flag.
2012-10-18service: Clear user connected flag on disconnectPatrik Flykt1-2/+2
Remember whether the service was connected by the user via D-Bus until the service gets disconnected.
2012-10-18service: Keep only a single connected technology if configuredPatrik Flykt1-0/+33
If SingleConnectedTechnology is enabled in main.conf, disconnect any previously connected services when the new service enters ready state.
2012-10-18main: Add SingleConnectedTechnology main.conf variablePatrik Flykt1-0/+12
2012-10-18main.conf: Add SingleConnectedTechnology descriptionPatrik Flykt1-0/+12
2012-10-18service: Fix default service switching and setting gatewayPatrik Flykt1-2/+3
Calling switch_default_service() didn't change the service order since the services were already sorted that way. Also update the gateway immediately.
2012-10-18main.conf: Update preferred technology descriptionPatrik Flykt1-6/+7
2012-10-18service: A preferred service in state ready is good enoughPatrik Flykt1-5/+1
Simplify the preferred service selection such that a connected service is good enough, especially since a connecting service will also terminate the search for the current preferred one.
2012-10-18service: Don't trigger autoconnect when neither service is preferredPatrik Flykt1-3/+0
Don't trigger a new autoconnect when neither the default nor the new service is preferred. Rely on the fact that normal autoconnect selection mechanism has done the work for us already.
2012-10-17client: Add Remove() method support for serviceTomasz Bursztyka3-0/+38
2012-10-17client: Fix various memory leaks in monitor and services partsTomasz Bursztyka2-2/+13
2012-10-17client: Fix some memory leaks in data_manager partTomasz Bursztyka1-18/+40
2012-10-17client: Fix some memory leaks in commands partTomasz Bursztyka1-81/+78
2012-10-16gresolv: Remove the lookup for realJukka Rissanen1-1/+1
The call to g_resolv_cancel_lookup() will do nothing because we just removed the lookup from the queue. The fix is to remove the lookup directly and not call the cancel function.
2012-10-16technology: Fix hardblocked state on non hw rfkillable switch addedTomasz Bursztyka1-13/+17
If hardblock is on and a new device is inserted and detected as not hardblocked, then it will be possible to enable/disable it (soft rfkill) independently to the main hw rfkill switch.
2012-10-16technology: Recompute hardblocked state on rfkill remove eventTomasz Bursztyka1-0/+7
This fixes the case of cascading rfkill switches: if enabled, hard rfkilling such technology might generate contradictory events. 1 - first all switches are hardblocked 2 - then one of these switch (usually: device's switch) gets fully unblocked 3 - then this same switch gets removed Step 2 is in contradiction with step 1, so we need to care about such switch getting removed by recomputing the hardblocked state.
2012-10-16technology: Properly handle rfkill driven stateTomasz Bursztyka1-9/+43
2012-10-16device: Add a getter for powered propertyTomasz Bursztyka2-0/+6
2012-10-16technology: Use the right method to enable or disableTomasz Bursztyka1-22/+27
If rfkill driven, use rfkill soft block/unblock. If not, request the device to be enabled or disabled.
2012-10-16technology: Change enabled to a boolean and refactor accordinglyTomasz Bursztyka1-25/+20
2012-10-16technology: Refactor and split functions setting enabled stateTomasz Bursztyka1-25/+29
2012-10-16technology: Refactor rfkill event handling according to soft/hard blockTomasz Bursztyka1-22/+35
No need to proceed with softblocked if technology is already hardblocked. Apply offlinemode and persistant state according to softblocked state. (saner logic and helped to cleanup code from style point of view too)
2012-10-16technology: Add and handle a marker for softblock statusTomasz Bursztyka1-5/+11
2012-10-16technology: Add a marker to know if a technology is rfkill drivenTomasz Bursztyka1-3/+10
Useful for coming patches: enabling/disabling technologies will be done differently whether technology is rfkill driven or not: - if rfkill driven -> enabled will rely on rfkill states - if not -> enabled will rely on driver/devices states
2012-10-16technology: Refactor how a technology is enabled or disabledTomasz Bursztyka1-38/+28
Refactor how a device list is enabled/disabled: this will be useful for coming patches. Simplify also the code, and remove useless gotos.
2012-10-16wispr: Keep track of proxy callback timeoutPatrik Flykt1-2/+10
Keep track of the zero-second no proxy callback timeout and remove it when freeing up the WISPr context.
2012-10-16wifi: Do not start autoscan if interface was not readyTomasz Bursztyka1-1/+4
2012-10-16gsupplicant: Send -ENOLINK error on scan reply if interface was not readyTomasz Bursztyka1-1/+9
2012-10-16gsupplicant: Add a new state according to 'interface_disabled'Tomasz Bursztyka3-1/+11
When soft rfkill is on, wpa_supplicant sets the interface disabled and sends a state named 'interface_disabled'. Taking this information into account fixes the following issue: - disable wifi (user setting) and hard rfkill it - then un-hard rfkill it, whereafter rfkill states (soft/hard) will go like this: * from 1/1 to 0/0 * from 0/0 to 1/0 when 0/0 occurs, connman will request to enable wifi The problem with this is that enabling wifi takes quite some time and in between ConnMan will soft block wifi to disable it (according to previous user setting). Thus it will request to disable wifi but since enabling is still going on, this request won't do anything. Meanwhile wpa_supplicant will also catch the soft rfkill event and wpa_supplicant will set the state to 'interface_disabled', but since it's not handled properly by ConnMan, the wifi_enable() callback will be called and the function will assume wifi got enabled.
2012-10-16rfkill: Return the error when write() failsTomasz Bursztyka1-3/+6
2012-10-16gresolv: Remove all pending lookups when resolver is removedJukka Rissanen1-0/+4
Remove all lookups found in queue when GResolv object is removed.
2012-10-16gresolv: Avoid accessing already freed memoryJukka Rissanen1-3/+6
We must remove the lookup from lookup queue and query from query queue before calling user callback. The callback might unref the GResolv which in turn would remove the lookup/query what we are trying to access after the callback is returned. So it is enough to remove the lookup or query entry from queue before cb is called and then manually remove it after the callback has returned.
2012-10-15iptables: Ignore module loading errorJukka Rissanen1-6/+7
In iptables 1.4.9 module loading gives an error even if the module is built in. Ignore the loading errors because the missing iptables support is noticed when trying to get the iptables socket options.