delta/NetworkManager.git/src/NetworkManagerUtils.c, branch th/NMStringTable

core: improve ifname matching of existing x generated connections (rh #1077743)

2014-03-21T08:24:13+00:00

DEVICE="ens3"
ONBOOT=yes
NETBOOT=yes
UUID="23466771-f5fa-4ca9-856f-eaf4a8e20c3f"
BOOTPROTO=none
IPADDR="10.0.0.2"
PREFIX="24"
GATEWAY="10.0.0.1"
HWADDR="52:54:00:12:34:56"
TYPE=Ethernet
NAME="ens3"

This ifcfg file results in connection.interface-name=ens3.
However, device-generated connection didn't set interface-name property.

Fix that by setting interface-name property when generating a connection. Also
allow matching connections if interface-name is not set in a connection.

https://bugzilla.redhat.com/show_bug.cgi?id=1077743

core: allow matching IPv6 'link-local' method to 'ignore' (rh #1073824)

2014-03-12T08:41:27+00:00

When an existing connection profile has IPv6 method 'ignore', NM doesn't simply
care about IPv6. Thus we should allow matching such a profile to devices with
just a link-local address.

The example can be a simple configuration like this:
/etc/sysconfig/network-scripts/ifcfg-ens3:
DEVICE="ens3"
ONBOOT=yes
NETBOOT=yes
UUID="aa17d688-a38d-481d-888d-6d69cca781b8"
BOOTPROTO=dhcp
HWADDR="52:54:00:32:77:59"
TYPE=Ethernet
NAME="ens3"

https://bugzilla.redhat.com/show_bug.cgi?id=1073824

core: move NMDevice's ip6_property_path() to NetworkManagerUtils

2014-03-04T22:04:01+00:00

core: match IPv4 'disabled' method to 'auto' when device has no link

2014-03-04T21:21:58+00:00

If IPv4 configuration did not succeed or the device has no IPv4 addresses
when NM restarts, it will detect the existing device configuration as
'disabled'.  This can happen when a bridge has no slaves and thus cannot
perform IPv4 addressing because it has no carrier (since bridge carrier
status depends on slave carriers).  When NM starts or restarts, it
sees the bridge has no IPv4 address and assumes the IPv4 method is
'disabled'.  This creates a new connection, which blocks any slave
connections from activating if they specify their master via UUID
 (since the bridge's active connection is generated).

Fix this by allowing matches from 'disabled' to 'auto' if the device
has no carrier, and there are no other differences between the
original and the candidate connections.

core: refactor connection matching and add testcase

2014-03-04T21:21:58+00:00

Refactor in preparation for some additional matching, and add testcases.

trivial: fix whitespace

2014-02-24T20:35:33+00:00

Signed-off-by: Thomas Haller

core: add function nm_utils_ip6_address_clear_host_address()

2014-02-14T20:40:58+00:00

Signed-off-by: Thomas Haller

core: add nm_utils_get_monotonic_timestamp_us() function

2014-02-14T14:53:11+00:00

Signed-off-by: Thomas Haller

core: minor change of logging output about monotonic_timestamp

2014-01-31T12:28:42+00:00

Make it more clear, what the current monotonic_timestamp is and
what's it's offset to CLOCK_BOOTTIME.

Signed-off-by: Thomas Haller

core: add nm_utils_get_monotonic_timestamp_* functions

2014-01-30T18:51:45+00:00

https://bugzilla.gnome.org/show_bug.cgi?id=720833

Signed-off-by: Thomas Haller