<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VPN on Mi&amp;Bee Blog</title><link>/en/tags/vpn/</link><description>Recent content in VPN on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Fri, 20 Jan 2017 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/vpn/rss.xml" rel="self" type="application/rss+xml"/><item><title>Building a Cross-City LAN with Docker</title><link>/en/archives/mi-docker-net/</link><pubDate>Fri, 20 Jan 2017 00:00:00 +0000</pubDate><guid>/en/archives/mi-docker-net/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;At the time, I had servers both at home and at the office and wanted unified management, but the two internal networks were isolated. Traditional port forwarding was too cumbersome, and some services I didn&amp;rsquo;t want exposed to the public internet. After trying several approaches, I found Docker OpenVPN to be the most hassle-free solution.&lt;/p&gt;
&lt;p&gt;I chose Docker OpenVPN over traditional VPN mainly because containerized deployment is extremely convenient, and certificate management is much simpler. The end result was great — I could access various services on the remote internal network via domain names, saving a lot of configuration hassle.&lt;/p&gt;</description></item></channel></rss>