summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)AuthorFilesLines
2012-11-13inet: Fix resource leakDanny Jeongseok Seo1-3/+1
The socket was not closed when err < 0 is true.
2012-11-05session: Register session after policy plugin returned configDaniel Wagner1-75/+89
Move the configuration part of __connman_session_create() into session_create_cb(). With this change the policy plugin is able to do async work to retrieve a configuration.
2012-11-05session: Factor out user settings in __connman_session_create()Daniel Wagner1-23/+48
In order to be able to pass the user configuration provided through from the D-Bus Manager.SessionCreate() call to the callback we need to store the configuration into a local data data structure. This data structure can then be passed into the callback introduced later on.
2012-11-05session: Remove struct connman_session_bearerDaniel Wagner1-95/+34
Instead start using enum connman_service_type directly.
2012-11-05session: Handle no match case in parse_bearers()Daniel Wagner1-0/+9
2012-11-05session: parse_bearers() should check for invalid typesDaniel Wagner1-2/+9
2012-11-05session: Rename session_parse_allowed_bearers() to parse_bearers()Daniel Wagner1-5/+3
This function name was a source of confusion because in a later patch we introduce connman_session_parse_allowed_bearers() which will call parse_bearers(). With this change it should be more readable.
2012-11-05session: Remove match_all from connman_session_bearerDaniel Wagner1-35/+21
The match_all will be expressed through CONNMAN_SESSION_TYPE_UNKNOWN. The 'no match' case happens when allowed_bearers is NULL.
2012-11-05session: Remove name variable from connman_session_bearerDaniel Wagner1-7/+8
The string is only used when appending the bearer to the D-Bus message in append_allowed_bearers(). Let's use __connman_session_type2string() in append_allowed_bearers(). This saves a bit of memory.
2012-11-05session: Add callback to policy create()Daniel Wagner1-9/+23
Instead returning directly a config when create() is called in policy plugin, use a callback function for handing over a valid configuration from the plugin to the session core. This prepares support for asynchronous create call.
2012-11-05session: Policy register should check callback existenceDaniel Wagner1-0/+3
Let's ensure that the policy plugin has all necessary callbacks installed when connman_session_policy_register() is called. The rest of the code expects that the create() and destroy() callbacks exist whenever a plugin is used.
2012-11-05session: Pick directly first policy in listDaniel Wagner1-8/+3
There is no point in iterating over the list when we always pick the first element in the list.
2012-11-05session: Factor out memory release part of cleanup_sessionDaniel Wagner1-9/+14
We want to reuse this code snippet for the error case in __connman_session_create() too.
2012-11-05manager: Allow async CreateSession method callDaniel Wagner1-2/+6
The CreateSession D-Bus call should be marked as async call in order to allow the session core to defer the response.
2012-11-05storage: Add void if function does not have any argumentsDaniel Wagner2-7/+7
2012-11-02dhcp: Clear ipaddresses from ipconfig before starting DHCPJukka Rissanen1-0/+6
This is needed if manually configured addresses were used and later DHCP was taken into use. If the manually configured IP information (address, netmask and gateway) and the information given by DHCP is the same, DHCP will not set the IP address to the interface.
2012-11-02ipconfig: Add function to clear ipaddress informationJukka Rissanen2-0/+9
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 <jmassot@aldebaran-robotics.com> 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-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-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 Bursztyka1-0/+5
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-16rfkill: Return the error when write() failsTomasz Bursztyka1-3/+6
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.
2012-10-12nat: Memory leak when cleaning upJukka Rissanen1-0/+1
The nat struct was not freed when it is was removed from the hash.
2012-10-03dnsproxy: Do not overwrite protocol and channel in server structJukka Rissanen1-5/+26
We copied too much data into addrinfo struct which corrupted the protocol and channel fields. Fixes BMC#25726
2012-10-03technology: Do not expose a technology which is hard rfkilledTomasz Bursztyka1-4/+8
If hard rfkilled, a technology will not be exposed through DBus via GetTechnologies. If hard rfkill status changes, TechnologyAdded and TechnologyRemoved signals will be sent accordingly.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-07 03:11:19 +0000