<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Mango-Router on Peter Richardt</title>
    <link>https://www.richardts.com/tags/mango-router/</link>
    <description>Recent content in Mango-Router on Peter Richardt</description>
    <generator>Hugo</generator>
    <language>de-DE</language>
    <lastBuildDate>Mon, 07 Aug 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.richardts.com/tags/mango-router/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SOLVED WireGuard VPN clients can’t resolve internal hostnames.</title>
      <link>https://www.richardts.com/posts/solved-wireguard-vpn-clients-cant-resolve-internal-hostnames/</link>
      <pubDate>Mon, 07 Aug 2023 00:00:00 +0000</pubDate>
      <guid>https://www.richardts.com/posts/solved-wireguard-vpn-clients-cant-resolve-internal-hostnames/</guid>
      <description>&lt;p&gt;Since AVM Fritzbox can provide VPN connectivity via WireGuard, it was a target to connect a Mango Router from Gli Net to it to have a permanent tunnel between the remote office (holiday) and the Head Quarter (Home).&lt;/p&gt;
&lt;p&gt;The configuration itself already could be easier, but once it was up and running, it was fine.&lt;/p&gt;
&lt;p&gt;Only one thing was annoying, that the clients couldn&amp;rsquo;t resolve the internal hostnames in the remote network.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
