<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Wireguard on Puppeteers Oy</title>
		<link>https://www.puppeteers.net/tags/wireguard/</link>
		<description>Recent content in Wireguard on Puppeteers Oy</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Tue, 13 Apr 2021 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.puppeteers.net/tags/wireguard/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Making per-link DNS servers added by Wireguard to systemd-resolved survive NetworkManager connection changes</title>
				<link>https://www.puppeteers.net/blog/making-per-link-dns-servers-added-by-wireguard-to-systemd-resolved-survive-networkmanager-connection-changes/</link>
				<pubDate>Tue, 13 Apr 2021 00:00:00 +0000</pubDate>
				<guid>https://www.puppeteers.net/blog/making-per-link-dns-servers-added-by-wireguard-to-systemd-resolved-survive-networkmanager-connection-changes/</guid>
				<description>&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; the problem described in this article seems to be resolved in Fedora 36 (NetworkManager 1.38.0-2.fc36). It is still present in Fedora 35 (NetworkManager 1.32.12-2.fc35).&lt;/p&gt;&#xA;&lt;p&gt;The title of this blog post may seem familiar to some, as &lt;a href=&#34;https://www.puppeteers.net/blog/making-per-link-dns-servers-pushed-from-openvpn-to-systemd-resolved-survive-networkmanager-connection-changes/&#34;&gt;I solved this problem&lt;/a&gt; for OpenVPN earlier. I won&amp;rsquo;t repeat myself here, so please check the &lt;a href=&#34;https://www.puppeteers.net/blog/making-per-link-dns-servers-pushed-from-openvpn-to-systemd-resolved-survive-networkmanager-connection-changes/&#34;&gt;OpenVPN article&lt;/a&gt; to understand why this is happening.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.wireguard.com/&#34;&gt;Wireguard&lt;/a&gt; servers - unlike &lt;a href=&#34;https://openvpn.net/community/&#34;&gt;OpenVPN&lt;/a&gt; servers - are not able to push any settings such as DNS servers to their clients. However, Wireguard client itself is able to run PostUp commands to configure per-link DNS. The same approach can be used with OpenVPN &amp;ldquo;up&amp;rdquo; scripts as well, if you prefer having full control at the client-side. Here&amp;rsquo;s a Wireguard example:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Manage Linux client DNS settings in OpenVPN and Wireguard</title>
				<link>https://www.puppeteers.net/blog/manage-linux-client-dns-settings-in-openvpn-and-wireguard/</link>
				<pubDate>Tue, 31 Mar 2020 00:00:00 +0000</pubDate>
				<guid>https://www.puppeteers.net/blog/manage-linux-client-dns-settings-in-openvpn-and-wireguard/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://openvpn.net/&#34;&gt;OpenVPN&lt;/a&gt; and &lt;a href=&#34;https://www.wireguard.com/&#34;&gt;Wireguard&lt;/a&gt; are both used to provide secure, remote access to an organization&amp;rsquo;s internal services such as network shares (NFS and Samba), desktops and servers (SSH and RDP) or web services. Linux is generally a first-class citizen as far as clients are concerned but with one exception: accessing DNS through the VPN tunnel.&lt;/p&gt;&#xA;&lt;p&gt;OpenVPN servers have the concept of pushing settings such as DNS servers to client. This happens by emulating a DHCP server. Windows OpenVPN clients for example are able to process this information automatically to update the (per-link) DNS server settings automatically. But Linux traditionally has not had this capability without support from &amp;ldquo;up&amp;rdquo; and &amp;ldquo;down&amp;rdquo; scripts. When one is using &lt;a href=&#34;https://www.freedesktop.org/software/systemd/man/systemd-resolved.service.html&#34;&gt;systemd-resolved&lt;/a&gt; the traditional ways such as using resolvconf or modifying /etc/resolv.conf directly no longer work or cause issues. Fortunately there is a good script, &lt;a href=&#34;https://github.com/jonathanio/update-systemd-resolved&#34;&gt;update-systemd-resolved&lt;/a&gt;, for automating the DNS server setup process for systemd-resolved. Basically it takes the list of DNS settings OpenVPN provides and converts them into dbus calls that modify the running systemd-resolved&amp;rsquo;s configuration.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
