David Anderson 25ce9885a2 net/dns: don't use NM+resolved for NM >=1.26.6. ... NetworkManager fixed the bug that forced us to use NetworkManager if it's programming systemd-resolved, and in the same release also made NetworkManager ignore DNS settings provided for unmanaged interfaces... Which breaks what we used to do. So, with versions 1.26.6 and above, we MUST NOT use NetworkManager to indirectly program systemd-resolved, but thankfully we can talk to resolved directly and get the right outcome. Fixes #1788 Signed-off-by: David Anderson <danderson@tailscale.com>		2021-04-23 21:13:19 -07:00
..
debug.go	Revert "cmd/tailscaled: split package main into main shim + package"	2021-03-25 09:06:00 -07:00
depaware.txt	net/dns: don't use NM+resolved for NM >=1.26.6.	2021-04-23 21:13:19 -07:00
install_darwin.go	cmd/tailscaled: remove tailscaled binary on uninstall-system-daemon	2021-03-31 15:44:04 -07:00
install_windows.go	ipn/ipnlocal: add file sharing to windows shell	2021-04-23 13:32:33 -07:00
tailscaled_notwindows.go	Revert "cmd/tailscaled: split package main into main shim + package"	2021-03-25 09:06:00 -07:00
tailscaled_windows.go	cmd/tailscaled: don't block ipnserver startup behind engine init on Windows	2021-04-20 22:26:27 -07:00
tailscaled.defaults	cmd/tailscaled: rename relaynode reference in defaults file comment	2020-03-13 14:38:04 -07:00
tailscaled.go	ipn/ipnlocal: add file sharing to windows shell	2021-04-23 13:32:33 -07:00
tailscaled.service	cmd/tailscaled/tailscaled.service: revert recent hardening for now	2021-02-01 13:37:48 -08:00