Age | Commit message (Collapse) | Author | Files | Lines |
|
Fixes BMC#24986
|
|
test-connman services also reports the identifier only. This makes
copy&paste with the mouse a bit simpler.
|
|
In __connman_service_connect() we call __connman_ipconfig_enable()
which takes a ref on the ipconfig object. Later when the service
state machine is updated service takes another ref.
When the device disapears during operation (the user didn't call
Service.Disconnect()), we do not call __connman_ipconfig_disable()
anymore which would drop one ref.
|
|
We don't have yet an ipconfig for this interface, that means
the service.c does not yet know this interface. In order to
be able to get into sync we disable IPv6 auto connection at this point.
If the service state machine decides to connect, it will enable it
again.
|
|
|
|
When enabling IPv6 when loading the Service properties, the Service
state machine gets out of sync when AutoConnect is disabled.
At this point we should only load the properties and let the
Service state machine decide when to enable the ipconfigs.
And the good news is that the core handles this already.
|
|
We need also to set the Favorite flag to true in order to let
the services to be auto connected.
|
|
|
|
Ethernet networks should honor the AutoConnect feature as the rest
of the network types.
Just register the network object at the core when we get LOWER_UP.
Then the core can decide when to connect to the network.
There is no behavior change when AutoConnect is enabled, So if the
user plugs the cable the ethernet network will automatically connect
as it was before.
If AutoConnect is disabled, the core will not connect to the network
automatically.
|
|
|
|
|
|
|
|
It is possible that because the rtnl messages arrive
asynchronously, we might end up having two default gateways
that are both active at the same time. If that happens, we try
to downgrade the one that is not yet active.
|
|
|
|
There can be multiple active gateways in the system at the same
time so we must check them all when updating gateway info.
|
|
VPN could be using wrong phy link data if there are multiple
active links.
|
|
These routes are not needed.
|
|
Get the active gateway pointer only after the gateway hash
has been manipulated by add_gateway(). It is possible that
we are accessing stale pointer otherwise.
|
|
Notify default service changed only if we actually changed
the default service.
|
|
When nameserver are removed by __connman_connection_gateway_remove()
then remove only certain type nameserver (IPv4 or IPv6). This is
needed so that we do not loose IPv4 routes if only IPv6 nameservers
are to be removed. This is needed when there are multiple connected
services.
|
|
|
|
This is needed so that gateways are set properly when service
triggers online checks.
|
|
|
|
|
|
|
|
Fixes BMC#24964
|
|
Fixes BMC#24965
|
|
|
|
Fixes BMC#24942
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
According the D-Bus API, the Service interface accepts
variant types.
|
|
According the D-Bus API, the Clock interface accepts
variant types.
|
|
Removed services hash table need not be consulted when sending
ServicesAdded signals as the service structures have already been
deleted. Also clean up both added and removed hash tables after the
signals have been sent.
|
|
Log of segfault:
...
connmand[676]: src/network.c:check_dhcpv6() reply (nil)
connmand[676]: src/network.c:check_dhcpv6() re-send router solicitation 3
connmand[676]: src/inet.c:__connman_inet_ipv6_send_rs()
connmand[676]: Aborting (signal 11) [connmand]
|
|
connman_technology_add_device() calls __connman_device_enable()
but since the device is already enabled, the calls does not propagate
through to __connman_technology_enabled via connman_device_set_powered.
|
|
Pass NULL rather than 0 when calling time(2) to follow prefered
stylistic convention.
|
|
Pass NULL rather than 0 when calling time(2) to follow prefered
stylistic convention.
|
|
This patch sets the BOOTP secs field in a RFC 951- and 2131-compliant
manner for DHCPv4 DISCOVER and REQUEST/SELECT packets.
Certain DHCP servers, such as that implemented in Mac OS X (< 10.7)
for its "Internet Sharing" feature, refuse to issue a DHCP lease to
clients that have not set a non-zero value in their DISCOVER or
REQUEST packets. In fact, based on http://hints.macworld.com/article.php?
story=20071223001432304, it's not non-zero but a value greater than four (4)
seconds to allow another "authoritative" DHCP server on the subnet to reply
first.
Side-by-side packet analysis of Mac OS X, iOS, Android, ISC and
Windows clients show that these clients set the BOOTP 'secs' field and
are successfully issued a DHCP lease by Mac OS X. By contrast, a
connman-based client will issue 10 back-to-back DISCOVER packets and
will not be returned a DHCP OFFER from the server.
|
|
|
|
Not all allocated blocks info data structure have a pool associated.
|
|
|
|
|
|
GetProperties() does not return the services path anymore. Instead
the GetServices() method should be used.
|
|
GetProperties() does not return the services path anymore. Instead
the GetServices() method should be used.
|