Thomas Haller 88756703cf clients: set routing search domain with nameservers when importing WireGuard profile ... When the users configure a DNS server on the interface, they likely want to use it, regardless whether there is a default route on the device. For that to work, add an explicit "~" search domain. Otherwise, by default NetworkManager only adds the special search domain only on devices that have a "best default route" (nm_ip_config_best_default_route_is). But that only considers a best default route in the main table, and WireGuard (with ipx-auto-default-route) adds the default route to a separate table. The heuristic to determine best devices works not well with policy routing, so explicitly add this search domain during import. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/405		2020-04-08 12:33:56 +02:00
..
cli	cli: hide nm_cli global variable from public headers	2020-04-04 19:28:41 +02:00
cloud-setup	license: Add license using SPDX identifiers to meson build files	2020-02-17 13:16:57 +01:00
common	clients: set routing search domain with nameservers when importing WireGuard profile	2020-04-08 12:33:56 +02:00
tests	clients/tests: comment return code by signal in test output	2020-03-23 13:30:13 +01:00
tui	meson: merge branch 'inigomartinez/meson-license'	2020-03-28 12:45:19 +01:00
meson.build	license: Add license using SPDX identifiers to meson build files	2020-02-17 13:16:57 +01:00
nm-online.c	all: use nm_clear_pointer() instead of g_clear_pointer()	2020-03-23 11:22:38 +01:00