Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
If rfkill driven, use rfkill soft block/unblock. If not, request the
device to be enabled or disabled.
|
|
|
|
|
|
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)
|
|
|
|
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
|
|
Refactor how a device list is enabled/disabled: this will be useful
for coming patches. Simplify also the code, and remove useless gotos.
|
|
Keep track of the zero-second no proxy callback timeout and remove
it when freeing up the WISPr context.
|
|
|
|
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.
|
|
The nat struct was not freed when it is was removed from the hash.
|
|
We copied too much data into addrinfo struct which corrupted
the protocol and channel fields.
Fixes BMC#25726
|
|
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.
|
|
|
|
|
|
|
|
When hardblocking a technology, it should disable the devices which belongs
to that technology. When un-hardblocking it should do the same but taking
care about user setting (it will enable the devices if only enable_persistent
is on).
|
|
On some hardware, there exist two rfkill entities for the same type
with a cascading issue: if one is soft blocked, the other one is
hardblocked. But if the hardblock switch is set, all are hardblocked.
This patch figures out that a technology is hardblocked only if all
related rkill events get the same hardblock value.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The inet_rtnl_cb_data struct allocated in __connman_inet_rtnl_talk()
was not deallocated if we expected data from kernel.
|
|
Calculate transmit time used in NTP as the reception time minus
the delta of the monotonic receive and transmit times. When
calculated this way, it does not matter if the time happens to
be set to something else between the sending and receiving of the
NTP packet.
On sending the added monotonic time and the previous transmit time
are saved at the same point in time. On reception the monotonic time
is evaluated after the packet has been received by ConnMan. This is
in contrast to the actual reception wall clock time which is added
by the kernel. The difference between the reception times on a normal
system is about 100µs, which is neglible.
|
|
|
|
|
|
|
|
The structure can now be directly freed, since the reference count
is always one. As a result, remove wispr_portal_context_unref()
function.
|
|
Remove reset_service_usage() as it is now obsolete with the
refcount always being equal to one.
|
|
There is no need to refcount while doing Agent API calls, since
outstanding Agent API calls are removed when the service is
disconnected.
Also remove wispr_portal_context_ref() as it is no longer used.
|
|
connman_wispr_portal_context is initialized with refcount set to one.
Don't reference it an additional times while doing asynchronous calls
if the calls can be cancelled. Unreference the structure when done.
|
|
Add a '--nobacktrace' command line switch to let the system
handle stack traces. The default is to let ConnMan handle them
as before
|
|
PrefixLength is exposed as a byte in the API, but code was
waiting for a string when setting a new value.
|
|
|
|
|
|
Up to now an empty or wrong ConnectionType was interpreted as 'any'.
If the ConnectionType is either wrong ignore it. If no ConnectionType
setting is passed in during creation of the session choose 'any'.
|
|
Up to now an empty AllowedBearers was interpreted as match any. Let's
make the match all explicit by expecting '*'. If an empty
AllowedBearers is provided, we interpret this as no match. In this
case the application will never get an online notifcation.
|
|
|
|
|
|
Basic types are not used for the configuration anymore.
|
|
Let's ask the plugin for the default configuration. AllowedBearers
and ConnectionType are not yet taken fromt the plugin. Instead
the user configuration will be taken.
|
|
|
|
Instead of passing basic datatypes between the session core and the
policy plugin, provide a complex data structure which holds
the session configuration.
|
|
Rename bearer_info to connman_session_bearer. Use also 'bearer' as local
variable instead of 'info' to avoid confusion with session_info.
|
|
Instead of passing in some string to identify we can use the
connman_session pointer. This allows us to keep the way sessions
are identfied away from the core, e.g. using the D-Bus owner id or
something else.
|
|
|
|
|