gdhcp: Remove obsolete load lease function
gdhcp: Add unalignment macros

The alignment macros are copied from Bluez.
gdhcp: Use host byte order internally

Convert to network byte order just before sending the packet.
gdhcp: Use data size specific option setting function

Instead of using dhcp_add_simple_option() the gdhcp now uses
three functions for setting uint8, uint16 and uint32 values.
nat: Memory leak when cleaning up

The nat struct was not freed when it is was removed from the hash.
gresolv: Remove lookup from correct queue

The lookup must be removed from lookup queue and not from query
queue when cancelling the lookup. Otherwise it is possible that
we might access an already removed lookup that is still found in
lookup queue.

Fixes BMC#25728
gdhcp: Returned IP address is already in host byte order
iptables: Ignore module loading error

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.
gresolv: Avoid accessing already freed memory

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.
gresolv: Remove all pending lookups when resolver is removed

Remove all lookups found in queue when GResolv object is removed.
rfkill: Return the error when write() fails
gsupplicant: Add a new state according to 'interface_disabled'

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.
gsupplicant: Send -ENOLINK error on scan reply if interface was not ready
wifi: Do not start autoscan if interface was not ready
wispr: Keep track of proxy callback timeout

Keep track of the zero-second no proxy callback timeout and remove
it when freeing up the WISPr context.
technology: Refactor how a technology is enabled or disabled

Refactor how a device list is enabled/disabled: this will be useful
for coming patches. Simplify also the code, and remove useless gotos.
technology: Add a marker to know if a technology is rfkill driven

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
technology: Add and handle a marker for softblock status
technology: Refactor rfkill event handling according to soft/hard block

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)
technology: Refactor and split functions setting enabled state