delta/NetworkManager.git/src/dns, branch th/cli-strsplit

dns: don't stat relative paths when detecting resolved use

2017-11-19T13:29:16+00:00

NetworkManager daemon has no defined working directory.
It makes no sense to ever open or stat relative paths.
Just skip them.

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

dns: check for relative paths and stub-resolve.conf when detecting systemd-resolved

2017-11-19T13:25:59+00:00

Fix resolved detection, the symlink target is usually relative to the
root, such that in chroots the file points to a file inside the
chroot. But keep absolute targets too, as these may have been in use
with older version of systemd. Add support for stub-resolv.conf
detection.

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

core: merge IPv4 and IPv6 implementations in NMDnsManager

2017-11-09T08:29:39+00:00

core: replace nm_dns_ip_config_data_get_dns_priority()

2017-11-08T13:46:31+00:00

Add instead nm_ip_config_get_dns_priority(). If we want to treat NMIP4Config/NMIP6Config
generically, then the accessor should be right there.

policy: merge IPv4 and IPv6 implementation of update_ip_dns()

2017-11-08T13:03:26+00:00

core: use nm_close()

2017-10-19T13:49:58+00:00

Use nm_close() in the core to catch any improper use of close().

core: rework tracking of gateway/default-route in ip-config

2017-10-10T06:46:47+00:00

Instead of having 3 properties @gateway, @never_default and @has_gateway
on NMIP4Config/NMIP6Config that determine the default-route, track the
default-route as a regular route.

The gateway setting is the configuration knob for the default-route.
Since an NMIP4Config/NMIP6Config instance only has one gateway property,
it cannot track more then one default-routes (see related bug rh#1445417).
Especially with policy routing, it might be interesting to configure a
default-route in multiple tables.

Also, later it might be interesting to allow adding default-routes as
regular static routes in a connection, so that the user can configure additional
route parameters for the default-route or add default-routes in multiple tables.

With this patch, default-routes now have a rt_source property according to their
origin.

Also, the previous commits of this branch broke handling of the
default-route :) . That should be working now again.

dns: merge IPv4 and IPv6 implementation for update_add_ip_config()

2017-10-09T20:05:35+00:00

How nice would it be to have a NMIPConfig class that is
agnostic for IPv4 and IPv6. Another small step, in unifying
v4 and v6.

core: support tracking default-route in NMIP4Config/NMIP6Config

2017-09-08T09:11:21+00:00

Default-routes are for the most part like regular routes. Add support to
track them like regular routes in NMIP4Config/NMIP6Config.

One thing is, sometimes we need to figure out whether an ip-config
instance has a default-route. For that, keep track of the best
default-route (there might be multiple) and expose it. That is
the most complicated part of this patch, because there are so many
places where the list of routes gets modified (replace, intersect,
subtract, merge, add), and they all need to take care of updating
the best default-route.

In a next patch, NMDefaultRouteManager will be dropped and default-routes
will be tracked by NMIP4Config/NMIP6Config.

dns: use 127.0.0.53 address in /etc/resolv.conf with systemd-resolved

2017-09-07T13:29:57+00:00

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