<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: HomeGrid VPN</title>
    <description>The latest articles on DEV Community by HomeGrid VPN (@homegrid_vpn).</description>
    <link>https://dev.to/homegrid_vpn</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3989224%2Fd5f24573-3182-42db-8fbd-b95f9e70d10e.png</url>
      <title>DEV Community: HomeGrid VPN</title>
      <link>https://dev.to/homegrid_vpn</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/homegrid_vpn"/>
    <language>en</language>
    <item>
      <title>Build a Private Family Bulletin Board with Memos, Caddy and HomeGrid VPN</title>
      <dc:creator>HomeGrid VPN</dc:creator>
      <pubDate>Wed, 18 Nov 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/homegrid_vpn/build-a-private-family-bulletin-board-with-memos-caddy-and-homegrid-vpn-4m02</link>
      <guid>https://dev.to/homegrid_vpn/build-a-private-family-bulletin-board-with-memos-caddy-and-homegrid-vpn-4m02</guid>
      <description>&lt;p&gt;Memos and Caddy can turn a Windows computer into a private family bulletin board for grocery lists and everyday notes. Caddy provides HTTPS for Android and iPhone, while HomeGrid VPN provides a remote path to the &lt;strong&gt;same home LAN IP address&lt;/strong&gt; used on Wi-Fi. This example needs neither a custom DNS server nor router port forwarding.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. One network diagram for home and remote access
&lt;/h2&gt;

&lt;p&gt;The board stays on a computer you control. Family members can use Memos for notes or shopping reminders without relying on a public-facing web server.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frf2etyykzo5ftkrp27o7.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frf2etyykzo5ftkrp27o7.png" alt="Network map of home Wi-Fi and remote VPN access" width="800" height="875"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;At home, Wi-Fi reaches the computer's LAN IP directly. Remotely, HomeGrid VPN relays traffic through Cloud Hub and Home Grid to the same address. Cloud Hub is not the Internet Exit.&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;On home Wi-Fi:&lt;/strong&gt; phone → computer LAN IP on TCP 8443 → Caddy → Memos.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Away from home:&lt;/strong&gt; phone → HomeGrid VPN → Cloud Hub → home Grid → the &lt;strong&gt;same&lt;/strong&gt; computer LAN IP.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Outbound Only:&lt;/strong&gt; both the remote device and home Grid initiate VPN connections to the Cloud Hub. No IPv4 port forward or IPv6 inbound rule is needed at home.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cloud Hub is not Internet Exit:&lt;/strong&gt; it relays VPN traffic; it does not host this board or store its posts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;HTTPS:&lt;/strong&gt; Caddy receives TLS on container port 443 (host port 8443) and proxies to Memos on container port 5230.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The implementation was tested on Windows 11 with WSL2 and Docker Desktop. The macOS notes are untested. HomeGrid VPN must have a working LAN route and appropriate &lt;a href="https://www.homegrid-vpn.com/guides/en/lan-acl/" rel="noopener noreferrer"&gt;LAN ACL permissions&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;
  
  
  2. Prepare Docker Desktop
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Windows:&lt;/strong&gt; install WSL2 and Ubuntu, then enable Ubuntu under &lt;strong&gt;Docker Desktop → Settings → Resources → WSL Integration&lt;/strong&gt;. If needed, run in an elevated PowerShell:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;wsl --install -d Ubuntu

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;macOS:&lt;/strong&gt; install Docker Desktop for Mac. WSL2 is not used. Verify from a terminal:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker --version
docker compose version
mkdir -p ~/family-bbs/conf ~/family-bbs/downloads
&lt;span class="nb"&gt;cd&lt;/span&gt; ~/family-bbs

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On Windows, run the shell commands inside WSL2 Ubuntu.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Complete Docker Compose file
&lt;/h2&gt;

&lt;p&gt;Save the following as &lt;code&gt;~/family-bbs/compose.yml&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;services&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;memos&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;image&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;neosmemo/memos:stable&lt;/span&gt;
    &lt;span class="na"&gt;container_name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;family-bbs-memos&lt;/span&gt;
    &lt;span class="na"&gt;restart&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;unless-stopped&lt;/span&gt;
    &lt;span class="na"&gt;ports&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"127.0.0.1:5230:5230"&lt;/span&gt;
    &lt;span class="na"&gt;volumes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;memos_data:/var/opt/memos&lt;/span&gt;
    &lt;span class="na"&gt;networks&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;bbs&lt;/span&gt;

  &lt;span class="na"&gt;caddy&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;image&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;caddy:2&lt;/span&gt;
    &lt;span class="na"&gt;container_name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;family-bbs-caddy&lt;/span&gt;
    &lt;span class="na"&gt;restart&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;unless-stopped&lt;/span&gt;
    &lt;span class="na"&gt;command&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"caddy"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"run"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"--config"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"/etc/caddy/caddyfile"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"--adapter"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"caddyfile"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="na"&gt;ports&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"8443:443"&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"8080:8080"&lt;/span&gt;
    &lt;span class="na"&gt;volumes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;./conf:/etc/caddy:ro&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;./downloads:/srv/downloads:ro&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;caddy_data:/data&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;caddy_config:/config&lt;/span&gt;
    &lt;span class="na"&gt;depends_on&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;memos&lt;/span&gt;
    &lt;span class="na"&gt;networks&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;bbs&lt;/span&gt;

&lt;span class="na"&gt;networks&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;bbs&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;

&lt;span class="na"&gt;volumes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;memos_data&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;caddy_data&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;caddy_config&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Memos and Caddy share the Compose-managed &lt;code&gt;bbs&lt;/code&gt; network; Caddy resolves &lt;code&gt;memos:5230&lt;/code&gt; through Docker DNS. The named volumes persist Memos data and Caddy’s internal CA keys.&lt;/p&gt;

&lt;p&gt;Host port 5230 is bound to &lt;code&gt;127.0.0.1&lt;/code&gt; only for initial setup and troubleshooting, so it is not exposed directly to the LAN. &lt;strong&gt;After validating the reverse proxy and remote route, remove Memos’ &lt;code&gt;ports:&lt;/code&gt; mapping and use HTTPS only.&lt;/strong&gt; Run &lt;code&gt;docker compose up -d&lt;/code&gt; after removing that mapping, then retest access.&lt;/p&gt;

&lt;p&gt;Start Memos and create its administrator account at &lt;code&gt;http://localhost:5230/&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker compose up -d memos

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  4. Enable HTTPS with Caddy’s internal CA
&lt;/h2&gt;

&lt;p&gt;Determine your computer’s LAN IP with &lt;code&gt;ipconfig&lt;/code&gt; on Windows or the macOS Network settings. &lt;strong&gt;&lt;code&gt;192.168.xxx.xxx&lt;/code&gt; below deliberately masks a real address and is not valid configuration.&lt;/strong&gt; Replace every occurrence with your own LAN IP before starting Caddy. Consider a DHCP reservation to keep that address stable.&lt;/p&gt;

&lt;p&gt;Save this as lowercase &lt;code&gt;~/family-bbs/conf/caddyfile&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight nginx"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;default_sni&lt;/span&gt; &lt;span class="mf"&gt;192.168&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;xxx&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;xxx&lt;/span&gt;
    &lt;span class="n"&gt;skip_install_trust&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="n"&gt;https&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="c1"&gt;//192.168.xxx.xxx {&lt;/span&gt;
    &lt;span class="n"&gt;tls&lt;/span&gt; &lt;span class="n"&gt;internal&lt;/span&gt;
    &lt;span class="n"&gt;reverse_proxy&lt;/span&gt; &lt;span class="n"&gt;memos&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="mi"&gt;5230&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="mi"&gt;8080&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;root&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;srv&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;downloads&lt;/span&gt;

    &lt;span class="nd"&gt;@cert&lt;/span&gt; &lt;span class="n"&gt;path&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;root&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;crt&lt;/span&gt;
    &lt;span class="n"&gt;header&lt;/span&gt; &lt;span class="nd"&gt;@cert&lt;/span&gt; &lt;span class="nc"&gt;Content&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Type&lt;/span&gt; &lt;span class="n"&gt;application&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;x&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;x509&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;ca&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;cert&lt;/span&gt;
    &lt;span class="n"&gt;header&lt;/span&gt; &lt;span class="nd"&gt;@cert&lt;/span&gt; &lt;span class="nc"&gt;Content&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Disposition&lt;/span&gt; &lt;span class="s2"&gt;"attachment; filename=root.crt"&lt;/span&gt;

    &lt;span class="nd"&gt;@profile&lt;/span&gt; &lt;span class="n"&gt;path&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;family&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;bbs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;mobileconfig&lt;/span&gt;
    &lt;span class="n"&gt;header&lt;/span&gt; &lt;span class="nd"&gt;@profile&lt;/span&gt; &lt;span class="nc"&gt;Content&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Type&lt;/span&gt; &lt;span class="n"&gt;application&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;x&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;apple&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;aspen&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;config&lt;/span&gt;

    &lt;span class="n"&gt;file_server&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;tls internal&lt;/code&gt; lets Caddy issue and renew certificates from its internal CA. &lt;code&gt;default_sni&lt;/code&gt; handles clients that omit SNI when connecting to an IP address. The &lt;code&gt;skip_install_trust&lt;/code&gt; directive prevents Caddy from trying to install its CA into the container trust store. Do not expose TCP 8080 to the public internet. The HTTP service on 8080 distributes the public CA certificate and iPhone profile during onboarding; HTTPS on 8443 serves the board.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; ~/family-bbs
docker compose config -q
docker compose up -d
docker port family-bbs-caddy

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Verify that both 8443 and 8080 are published. Open &lt;code&gt;https://192.168.xxx.xxx:8443/&lt;/code&gt; with your actual IP; a certificate warning is expected until you trust the CA.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Windows and macOS firewalls
&lt;/h2&gt;

&lt;p&gt;A service that responds on the computer itself may still be unreachable from another device. In the Windows test, switching the network profile to Public stopped an iPhone reaching the board; returning to Private restored access.&lt;/p&gt;

&lt;h3&gt;
  
  
  Windows
&lt;/h3&gt;

&lt;p&gt;Inspect the active profile:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="nc"&gt;Get&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;NetConnectionProfile&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="nc"&gt;Select&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Object&lt;/span&gt; &lt;span class="nc"&gt;InterfaceAlias&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;NetworkCategory&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For a network you trust, an elevated PowerShell can set it to Private. Replace the interface name:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="nc"&gt;Set&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;NetConnectionProfile&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;InterfaceAlias&lt;/span&gt; &lt;span class="s2"&gt;"Ethernet 2"&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;NetworkCategory&lt;/span&gt; &lt;span class="nc"&gt;Private&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Allow only local-subnet incoming traffic to HTTPS and the temporary certificate download service:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="nc"&gt;New&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;NetFirewallRule&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;DisplayName&lt;/span&gt; &lt;span class="s2"&gt;"Family BBS HTTPS"&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Direction&lt;/span&gt; &lt;span class="nc"&gt;Inbound&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Protocol&lt;/span&gt; &lt;span class="no"&gt;TCP&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;LocalPort&lt;/span&gt; &lt;span class="mi"&gt;8443&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Profile&lt;/span&gt; &lt;span class="nc"&gt;Private&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;RemoteAddress&lt;/span&gt; &lt;span class="nc"&gt;LocalSubnet&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Action&lt;/span&gt; &lt;span class="nc"&gt;Allow&lt;/span&gt;
&lt;span class="nc"&gt;New&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;NetFirewallRule&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;DisplayName&lt;/span&gt; &lt;span class="s2"&gt;"Family BBS Certificate Download"&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Direction&lt;/span&gt; &lt;span class="nc"&gt;Inbound&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Protocol&lt;/span&gt; &lt;span class="no"&gt;TCP&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;LocalPort&lt;/span&gt; &lt;span class="mi"&gt;8080&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Profile&lt;/span&gt; &lt;span class="nc"&gt;Private&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;RemoteAddress&lt;/span&gt; &lt;span class="nc"&gt;LocalSubnet&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Action&lt;/span&gt; &lt;span class="nc"&gt;Allow&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Do not duplicate rules that already exist. Whether &lt;code&gt;LocalSubnet&lt;/code&gt; also matches packets arriving through the Grid depends on the actual source address and routing/NAT. Check the effective source and narrowly adjust the rule if necessary.&lt;/p&gt;

&lt;h3&gt;
  
  
  macOS
&lt;/h3&gt;

&lt;p&gt;Open &lt;strong&gt;System Settings → Network → Firewall → Options&lt;/strong&gt;. Docker Desktop’s published traffic involves &lt;code&gt;com.docker.backend&lt;/code&gt;; confirm that relevant Docker processes may accept inbound connections.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker compose ps
lsof -nP -iTCP:8443 -sTCP:LISTEN
lsof -nP -iTCP:8080 -sTCP:LISTEN

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The macOS application firewall is primarily application-based, so allowing a Docker backend process is not the same as restricting it to these two ports. Use Docker port mappings carefully and consider &lt;code&gt;pf&lt;/code&gt; for more granular rules. This macOS workflow has not been tested end to end.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Distribute the CA to Android and iPhone
&lt;/h2&gt;

&lt;p&gt;Export only Caddy’s &lt;strong&gt;public CA certificate&lt;/strong&gt; , not its private key:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; ~/family-bbs
docker cp family-bbs-caddy:/data/caddy/pki/authorities/local/root.crt ./root.crt

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For iPhone, generate an unsigned certificate-only configuration profile with Python’s standard library:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;cd&lt;/span&gt; &lt;span class="o"&gt;~/&lt;/span&gt;&lt;span class="n"&gt;family&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;bbs&lt;/span&gt;
&lt;span class="n"&gt;python3&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&amp;lt;&lt;/span&gt;&lt;span class="s1"&gt;'PY'&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;plistlib&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;ssl&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;uuid&lt;/span&gt;
&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;pathlib&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;Path&lt;/span&gt;

&lt;span class="n"&gt;pem&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Path&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"root.crt"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;read_text&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;der&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;ssl&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;PEM_cert_to_DER_cert&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;pem&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;profile&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="s2"&gt;"PayloadType"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Configuration"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"PayloadVersion"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"PayloadIdentifier"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"com.family-bbs.ca"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"PayloadUUID"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;uuid&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;uuid4&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;upper&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"PayloadDisplayName"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Family BBS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"PayloadDescription"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Family BBS root CA certificate"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"PayloadOrganization"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Family BBS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"PayloadContent"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="s2"&gt;"PayloadType"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"com.apple.security.root"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"PayloadVersion"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"PayloadIdentifier"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"com.family-bbs.ca.root"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"PayloadUUID"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;uuid&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;uuid4&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;upper&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"PayloadDisplayName"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Family BBS CA"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"PayloadCertificateFileName"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"root.cer"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"PayloadContent"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;der&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nc"&gt;Path&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"family-bbs.mobileconfig"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;write_bytes&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="n"&gt;plistlib&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;dumps&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;profile&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;fmt&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;plistlib&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="no"&gt;FMT_XML&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="no"&gt;PY&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Copy the two files to the HTTP download directory:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;cp root.crt family-bbs.mobileconfig downloads/
docker &lt;span class="nb"&gt;exec&lt;/span&gt; family-bbs-caddy ls -l /srv/downloads/

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Device&lt;/th&gt;
&lt;th&gt;Download URL (replace the masked LAN IP)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Android&lt;/td&gt;
&lt;td&gt;&lt;code&gt;http://192.168.xxx.xxx:8080/root.crt&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;iPhone&lt;/td&gt;
&lt;td&gt;&lt;code&gt;http://192.168.xxx.xxx:8080/family-bbs.mobileconfig&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Android:&lt;/strong&gt; download &lt;code&gt;root.crt&lt;/code&gt;, find &lt;strong&gt;Install CA certificate&lt;/strong&gt; in device Settings, and select the file.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;iPhone:&lt;/strong&gt; download the &lt;code&gt;.mobileconfig&lt;/code&gt; with Safari, install it under &lt;strong&gt;Settings → General → VPN &amp;amp; Device Management&lt;/strong&gt; , then enable full trust under &lt;strong&gt;Settings → General → About → Certificate Trust Settings&lt;/strong&gt;. Installing the profile alone does not enable TLS trust.&lt;/p&gt;

&lt;p&gt;Both Android Chrome and iPhone Safari successfully loaded Memos over HTTPS without warnings in the Windows-based test.&lt;/p&gt;

&lt;h3&gt;
  
  
  Secure distribution matters
&lt;/h3&gt;

&lt;p&gt;Port 8080 uses HTTP and does not protect the certificate from in-transit substitution. &lt;strong&gt;Do not trust the file merely because it was downloaded on the home LAN.&lt;/strong&gt; Compare the CA fingerprint with one provided through a separate trusted channel:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;openssl x509 -in root.crt -noout -fingerprint -sha256

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Only install a CA on devices you administer. Protect the &lt;code&gt;caddy_data&lt;/code&gt; volume containing the CA private key, and consider disabling HTTP port 8080 after onboarding.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Remote access with HomeGrid VPN
&lt;/h2&gt;

&lt;p&gt;Register and run a home Grid using the &lt;a href="https://www.homegrid-vpn.com/guides/en/add-grid/" rel="noopener noreferrer"&gt;Grid setup guide&lt;/a&gt;. Keep dashboard-generated activation tokens private. Register the remote device and explicitly allow the destination &lt;strong&gt;LAN subnet&lt;/strong&gt; through &lt;a href="https://www.homegrid-vpn.com/guides/en/lan-acl/" rel="noopener noreferrer"&gt;LAN ACL&lt;/a&gt;; LAN ACL does not grant access to just one TCP port.&lt;/p&gt;

&lt;p&gt;Connect HomeGrid VPN away from home, then open &lt;strong&gt;the same&lt;/strong&gt; &lt;code&gt;https://192.168.xxx.xxx:8443/&lt;/code&gt; URL (using your actual LAN address). The server certificate remains valid for that LAN IP; no separate VPN-IP certificate is needed.&lt;/p&gt;

&lt;p&gt;An earlier experiment used DNAT inside the Grid container to direct traffic sent to its VPN IP on TCP 5230 toward Memos. &lt;strong&gt;After deleting that DNAT rule, access through the computer’s LAN IP on TCP 8443 still worked.&lt;/strong&gt; The published configuration therefore does not prescribe a custom DNAT rule. A functioning Grid-to-LAN route, return path, LAN ACL and host firewall permissions remain necessary.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Recreation caveat:&lt;/strong&gt; the test environment previously had a manually added connection to Docker’s default &lt;code&gt;bridge&lt;/code&gt; network. The exact remote path after recreating all containers with only the Compose-managed &lt;code&gt;bbs&lt;/code&gt; network has &lt;strong&gt;not&lt;/strong&gt; been retested. Verify both home Wi-Fi and cellular-plus-VPN after recreation. Overlapping LAN ranges at home and at the remote site can also affect routing.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Operate the family board responsibly
&lt;/h2&gt;

&lt;p&gt;Use separate Memos accounts and suitable post visibility; access to the VPN is not a replacement for app authentication. Keep the computer awake when the board must be available, and back up the Memos database to separate storage with a consistent backup method.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Check&lt;/th&gt;
&lt;th&gt;Result&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Windows Docker Desktop with Memos and Caddy&lt;/td&gt;
&lt;td&gt;Tested&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Android and iPhone trust of Caddy CA over home LAN HTTPS&lt;/td&gt;
&lt;td&gt;Tested&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Home LAN-IP access after removing the Grid’s old DNAT rule&lt;/td&gt;
&lt;td&gt;Tested&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Full container recreation with only the new Compose network&lt;/td&gt;
&lt;td&gt;Not yet tested&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;End-to-end macOS build&lt;/td&gt;
&lt;td&gt;Not yet tested&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The result is a small family service hosted on your own computer. HomeGrid VPN provides a path to the home LAN without exposing the Memos web server directly to the public internet.&lt;/p&gt;

&lt;p&gt;Originally published at &lt;a href="https://www.homegrid-vpn.com/blog/en/family-bbs-memos-vpn/" rel="noopener noreferrer"&gt;https://www.homegrid-vpn.com/blog/en/family-bbs-memos-vpn/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>selfhosted</category>
      <category>docker</category>
      <category>homelab</category>
      <category>vpn</category>
    </item>
    <item>
      <title>Business continuity planning for secure remote access and recovery</title>
      <dc:creator>HomeGrid VPN</dc:creator>
      <pubDate>Sun, 15 Nov 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/homegrid_vpn/business-continuity-planning-for-secure-remote-access-and-recovery-5aa7</link>
      <guid>https://dev.to/homegrid_vpn/business-continuity-planning-for-secure-remote-access-and-recovery-5aa7</guid>
      <description>&lt;p&gt;Keeping internal systems private while making secure remote access part of everyday work gives teams more ways to continue operating during a disruption. Start by identifying critical workflows, then test them off-site, prepare to rebuild and restore systems, and rehearse an independent path for emergency administration.&lt;/p&gt;

&lt;p&gt;Remote work comes with security challenges.&lt;/p&gt;

&lt;p&gt;Free Wi-Fi at airports, train stations, and cafés carries risks such as rogue access points and connection disruption. Exposing a VPN server or business application to the internet so employees can work off-site also requires controls against unauthorized access.&lt;/p&gt;

&lt;p&gt;But would bringing everyone back to the office really solve the problem?&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Internal systems should not be exposed to the internet unnecessarily. But that does not mean giving up remote work.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Even if working from the office meets all your needs today, you may not always be able to count on it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What hazard maps cannot tell you about business continuity
&lt;/h2&gt;

&lt;p&gt;Typhoon Faxai caused widespread power outages across Japan’s Kanto region and beyond in September 2019. Japan’s National Research Institute for Earth Science and Disaster Resilience reports that roughly 930,000 premises across nine prefectures, including Chiba, lost power. Restoration took about two weeks, with some hard-hit areas taking longer. Telecommunications and water services were also affected.&lt;/p&gt;

&lt;p&gt;A building may escape direct damage while employees lose power at home, transport shuts down, connectivity fails, or the recovery team cannot reach the office. Use hazard maps to understand local exposure, then account for power, connectivity, transport, and the people needed to restore service.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prepare for emergencies by making remote work part of everyday operations
&lt;/h2&gt;

&lt;p&gt;A business continuity plan (BCP) prepares a team to continue or resume critical work after a disruption. Remote work gives employees a way to keep working when they cannot reach the office.&lt;/p&gt;

&lt;p&gt;That takes advance preparation. Teams need remote connectivity, managed devices, authentication, access permissions, and a way to use business applications off-site. Putting these in place during normal operations gives responders more options to handle a disruption remotely.&lt;/p&gt;

&lt;p&gt;Using remote access regularly also helps uncover systems that staff cannot reach and operational problems they can address before an emergency. Everyday remote work can serve as a practical continuity exercise.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build continuity in five phases
&lt;/h2&gt;

&lt;p&gt;Moving every system to the cloud or preparing several sites at once takes time and money. The five phases below build on what you already have.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Phase&lt;/th&gt;
&lt;th&gt;Goal&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Inventory critical workflows and network dependencies&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Set up secure outbound remote access&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Test real work from outside the office&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;Extend network reach and prepare to rebuild and restore&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;Prepare independent emergency access and rehearse recovery&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Phase 1. Inventory critical workflows and their network dependencies
&lt;/h3&gt;

&lt;p&gt;Record which systems each workflow uses, which are already reachable from outside the office, and which ports or services are exposed to the internet. Include owners, authentication and connectivity dependencies, and the data needed to restart.&lt;/p&gt;

&lt;p&gt;Set a recovery time objective (RTO) and a recovery point objective (RPO) for each critical workflow. These identify how soon service should resume and how much recent data loss the business can tolerate. Use them to prioritize effort and spending.&lt;/p&gt;

&lt;h3&gt;
  
  
  Phase 2. Set up outbound remote access
&lt;/h3&gt;

&lt;p&gt;A conventional office VPN can be reached through a port forward on the office router. This can work with careful operation, including patching and controlling access to the public VPN endpoint.&lt;/p&gt;

&lt;p&gt;With an outbound design, an office gateway initiates a connection to a reachable hub, and remote clients connect to that hub as well. The office can keep its applications private without requiring an IPv4 port forward or an inbound IPv6 rule for the VPN. The hub remains a dependency for the private access path.&lt;/p&gt;

&lt;p&gt;HomeGrid VPN uses this outbound hub-and-spoke design. Its &lt;a href="https://www.homegrid-vpn.com/guides/en/lan-acl/" rel="noopener noreferrer"&gt;LAN ACL&lt;/a&gt; controls which devices can reach each destination LAN. Continue to manage device updates, user authentication, and application permissions. A pilot with one team or critical application provides a way to validate access before retiring unnecessary public entry points.&lt;/p&gt;

&lt;h3&gt;
  
  
  Phase 3. Test real work from outside the office
&lt;/h3&gt;

&lt;p&gt;Ask a small group to complete a representative workflow from home, a hotel, or another network. Check sign-in, file sharing, and application behavior through to task completion. Test what happens when connectivity drops or a user switches networks. Use these results to fix gaps and expand the pilot.&lt;/p&gt;

&lt;h3&gt;
  
  
  Phase 4. Extend network reach and prepare to restore systems
&lt;/h3&gt;

&lt;h4&gt;
  
  
  Extend private connectivity with Site Link
&lt;/h4&gt;

&lt;p&gt;An application hosted at headquarters may remain unreachable during an office outage. Moving selected workloads or recovery copies to a different site or cloud network can reduce that dependency.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.homegrid-vpn.com/blog/en/connect-lans-with-acl/" rel="noopener noreferrer"&gt;HomeGrid VPN Site Link&lt;/a&gt; can bring an office LAN or cloud VPC into the VPN through a supported Linux gateway. Verify routes and permissions from the alternate location. Plan redundancy separately, including where the application will run, how its data will be replicated or restored, and how clients will reach the recovered service.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi9jy2orphsx79ptgz7u4.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi9jy2orphsx79ptgz7u4.png" alt="Site Link connectivity and workload recovery" width="800" height="228"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Site Link provides private connectivity. Recovery also requires a place to run the application, restored data, and a way to redirect clients.&lt;/em&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  Use infrastructure as code and protect persistent data
&lt;/h4&gt;

&lt;p&gt;Infrastructure as code (IaC) lets a team recreate infrastructure from versioned definitions. Rebuilding replaceable components and backing up essential persistent data can reduce backup storage costs. Recovery still takes time, so compare a tested rebuild with snapshots or standby capacity where tight recovery objectives warrant them.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;AWS resource&lt;/th&gt;
&lt;th&gt;Example recovery approach&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;EC2&lt;/td&gt;
&lt;td&gt;Provision with Terraform, bootstrap with cloud-init, and restore application data&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Lambda&lt;/td&gt;
&lt;td&gt;Recreate configuration and redeploy the versioned application&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;ECS / Fargate&lt;/td&gt;
&lt;td&gt;Recreate the environment and deploy the preserved container image&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DynamoDB&lt;/td&gt;
&lt;td&gt;Restore data from backup and reapply surrounding configuration&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;RDS / Aurora&lt;/td&gt;
&lt;td&gt;Restore the database backup and reconnect the application&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;VPC / security groups&lt;/td&gt;
&lt;td&gt;Recreate network and security configuration with Terraform&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Protect the source, versioned artifacts, Terraform state, secrets, and encryption keys needed for recovery. Verify that the recovery team can obtain them when the original environment is unavailable.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frv6v9ybz1oxujyv8w3cf.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frv6v9ybz1oxujyv8w3cf.png" alt="Rebuild the environment and restore data" width="800" height="288"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Retain both infrastructure definitions and data, then combine them in a restore and verify the workload.&lt;/em&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  Automate backups and consider an offline copy
&lt;/h4&gt;

&lt;p&gt;Automate primary backups and test restores. S3 Object Lock and AWS Backup logically air-gapped vaults can help restrict deletion or alteration of retained data. Both remain online cloud services. Where the risk warrants it, keep an encrypted offline copy and set its refresh interval according to acceptable data loss. Treat an older offline copy as a last resort and verify that the recovery team can decrypt it.&lt;/p&gt;

&lt;h3&gt;
  
  
  Phase 5. Prepare independent emergency access and rehearse recovery
&lt;/h3&gt;

&lt;p&gt;AWS Systems Manager (SSM) can provide an emergency management path for supported EC2 and registered hybrid nodes without opening inbound management ports. Register the nodes ahead of time and keep SSM Agent running. Confirm that the agent can reach AWS endpoints over a path independent of the normal VPN and that operators can authenticate even when that VPN or the usual identity service is unavailable. The managed node still needs power and network connectivity to AWS.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw5ggo013vrmelpzav1s9.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw5ggo013vrmelpzav1s9.png" alt="Separate business and emergency management paths" width="800" height="220"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;During an SSM drill, confirm that the operator can authenticate and the managed node can reach AWS while the normal VPN is unavailable.&lt;/em&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  Grant only the emergency permissions the task requires
&lt;/h4&gt;

&lt;p&gt;Use a break-glass role with short-lived credentials and MFA. Scope the role to the required actions and managed nodes, and require approval where appropriate. For routine recovery actions, allow only approved Run Command documents for bounded tasks such as a status check or service restart. Keep generic command documents and interactive shell permissions outside that role where those capabilities are unnecessary. After use, revoke temporary access and review the audit records.&lt;/p&gt;

&lt;h4&gt;
  
  
  Rehearse access and restore a workload
&lt;/h4&gt;

&lt;p&gt;Simulate loss of the normal VPN and check that a named operator can carry out the intended emergency task through SSM. Restore a critical workload in an isolated recovery environment from Terraform and backups. Check that code, artifacts, keys, and credentials are available and that the application works with the restored data. Record the elapsed time and the newest usable data, then compare the results with the RTO and RPO.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with what you already have
&lt;/h2&gt;

&lt;p&gt;Pick one critical workflow, verify that it can be completed off-site, and test how you would restore it. Advance urgent work such as data protection and emergency communications whenever needed. Keeping both office and remote options available makes it easier to decide where work can resume during a disruption.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep work flexible while protecting internal systems
&lt;/h2&gt;

&lt;p&gt;Some tasks are best done face to face or require equipment at the office. For work that can continue off-site, keeping remote access available gives the team a way to operate during a disaster or an infrastructure outage.&lt;/p&gt;

&lt;p&gt;Office-based work may meet all your needs today. If the office becomes unavailable, you may wish you had kept a way to work remotely.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Internal systems should not be exposed to the internet unnecessarily. But that does not mean giving up remote work.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Build up the ability to continue and restore critical work even when a site or service goes offline.&lt;/p&gt;

&lt;h2&gt;
  
  
  References and related reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://nied-repo.bosai.go.jp/records/770" rel="noopener noreferrer"&gt;NIED study on power outages after Typhoon Faxai&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html" rel="noopener noreferrer"&gt;AWS Systems Manager Session Manager&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.aws.amazon.com/aws-backup/latest/devguide/logicallyairgappedvault.html" rel="noopener noreferrer"&gt;AWS Backup logically air-gapped vault&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.homegrid-vpn.com/blog/en/soho-office-virtualization-bcp/" rel="noopener noreferrer"&gt;Rethinking office-dependent work for small teams&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.homegrid-vpn.com/blog/en/free-wifi-safety/" rel="noopener noreferrer"&gt;Designing access to internal systems from public Wi-Fi&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Originally published at &lt;a href="https://www.homegrid-vpn.com/blog/en/bcp-network-recovery/" rel="noopener noreferrer"&gt;https://www.homegrid-vpn.com/blog/en/bcp-network-recovery/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>devops</category>
      <category>cybersecurity</category>
      <category>terraform</category>
      <category>remotework</category>
    </item>
    <item>
      <title>Public Wi-Fi risks explained, and how to use it more safely</title>
      <dc:creator>HomeGrid VPN</dc:creator>
      <pubDate>Sat, 07 Nov 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/homegrid_vpn/public-wi-fi-risks-explained-and-how-to-use-it-more-safely-2mi5</link>
      <guid>https://dev.to/homegrid_vpn/public-wi-fi-risks-explained-and-how-to-use-it-more-safely-2mi5</guid>
      <description>&lt;p&gt;Public Wi-Fi is useful, but using it safely means checking HTTPS certificates, protecting the traffic that needs a VPN, and understanding what happens when that VPN stops working. Wi-Fi encryption and HTTPS provide important protection without guaranteeing uninterrupted TCP connections. Choose a VPN by its authentication, transport, failure behavior, kill switch, and vulnerability response as well as its provider’s reputation.&lt;/p&gt;

&lt;p&gt;Hotel, cafe, and airport networks let us work remotely without consuming a mobile data allowance. “Public Wi-Fi” here includes both open networks and networks that share a password with many guests.&lt;/p&gt;

&lt;p&gt;While researching another networking issue, I came across the NDSS 2025 paper &lt;a href="https://www.ndss-symposium.org/ndss-paper/off-path-tcp-hijacking-in-wi-fi-networks-a-packet-size-side-channel-attack/" rel="noopener noreferrer"&gt;Off-Path TCP Hijacking in Wi-Fi Networks: A Packet-Size Side Channel Attack&lt;/a&gt;. It offers a useful starting point for separating what encryption protects from the risks it leaves behind.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can an encrypted Wi-Fi network still expose TCP connections to attack?
&lt;/h2&gt;

&lt;p&gt;Yes, under the conditions studied in the paper. The researchers inferred TCP state from the sizes of encrypted wireless frames without decrypting their contents. They demonstrated SSH connection termination in 19 seconds and injection into unencrypted HTTP traffic within 28 seconds. In their field evaluation, attacks against researcher-controlled connections succeeded in 75 of 80 Wi-Fi networks.&lt;/p&gt;

&lt;p&gt;That result is not a worldwide success rate. The attacker needed to join the same Wi-Fi, observe the victim’s wireless frames, and send packets with forged source addresses. Target identification and TCP response behavior also mattered. This is not an attack that anyone can launch from an arbitrary remote location.&lt;/p&gt;

&lt;p&gt;Client isolation can restrict direct communication between guests without eliminating observation of wireless frames. WPA2, WPA3, and client isolation remain valuable; none should be treated as protection against every traffic-analysis or connection attack.&lt;/p&gt;

&lt;h2&gt;
  
  
  HTTPS protects application data, not every aspect of its connection
&lt;/h2&gt;

&lt;p&gt;TLS provides confidentiality and integrity for application data. With HTTP/1.1 and HTTP/2, that data normally travels over TCP. TLS does not encrypt or authenticate TCP’s own sequence numbers or reset flag.&lt;/p&gt;

&lt;p&gt;An attacker able to deliver an acceptable forged TCP reset can therefore interrupt a TLS connection without decrypting its contents. TCP includes defenses against blind injection, described in &lt;a href="https://www.rfc-editor.org/rfc/rfc5961" rel="noopener noreferrer"&gt;RFC 5961&lt;/a&gt;; the research examines a side channel that helps infer the state those defenses depend on.&lt;/p&gt;

&lt;p&gt;This does &lt;strong&gt;not&lt;/strong&gt; mean a TCP attacker can freely read HTTPS or inject arbitrary application data that valid TLS will accept. The HTTP injection demonstration used unencrypted HTTP. HTTP/3 uses QUIC over UDP, so it is not the same outer-TCP case.&lt;/p&gt;

&lt;p&gt;A stalled video, interrupted download, or dropped remote session is not evidence of this attack. Weak radio coverage, congestion, timeouts, and ordinary network faults are common explanations.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbirwwih1fmfl6408mpk1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbirwwih1fmfl6408mpk1.png" alt="HTTPS encryption and TCP connection disruption concern different layers." width="800" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;HTTPS encryption and TCP connection disruption concern different layers.&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  A past OpenVPN experience, with an unknown cause
&lt;/h3&gt;

&lt;p&gt;I previously experienced unexplained disconnections while using OpenVPN in TCP mode on external Wi-Fi. Sometimes they coincided with login or authentication activity. At the time, I had chosen TCP because I associated it with reliability.&lt;/p&gt;

&lt;p&gt;The practical concern was that a disconnected VPN could leave the device using its ordinary internet connection. I added both a kill switch and connection monitoring with automatic reconnection to the application I was working on.&lt;/p&gt;

&lt;p&gt;The old logs are unavailable, so I cannot establish the cause or attribute those events to this research technique. The enduring lesson is about failure behavior: &lt;strong&gt;a kill switch limits unintended traffic, while automatic recovery reduces downtime.&lt;/strong&gt; They serve different purposes.&lt;/p&gt;
&lt;h2&gt;
  
  
  A TCP-based VPN can lose its outer transport
&lt;/h2&gt;

&lt;p&gt;Some SSL VPNs, OpenVPN configurations, and VPN relay paths use TCP outside the encrypted tunnel. If that TCP connection is terminated, the tunnel can become unavailable.&lt;/p&gt;

&lt;p&gt;What happens next depends on routing and firewall policy. With a working kill switch, intended traffic should remain blocked while protection is unavailable. Without one, traffic that can use the ordinary internet connection may leave directly. Private destinations reachable only through the VPN may simply stop working.&lt;/p&gt;

&lt;p&gt;For a full-tunnel VPN, a possible sequence is:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;An attack interrupts its outer TCP connection.&lt;/li&gt;
&lt;li&gt;The kill switch is absent, disabled, or ineffective.&lt;/li&gt;
&lt;li&gt;New or retried internet traffic uses the local connection directly.&lt;/li&gt;
&lt;li&gt;Direct HTTPS-over-TCP connections become exposed to TCP disruption on that path.&lt;/li&gt;
&lt;li&gt;A separate flaw in fallback, authentication, or session handling could create further risk.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The final step is conditional. The paper does not demonstrate that entire chain, and a TCP reset does not defeat TLS. An existing connection also does not necessarily survive a change of public source address; applications may establish new connections instead.&lt;/p&gt;

&lt;p&gt;Similarly, resetting TCP does not disconnect Wi-Fi itself or force a new login. Evil-twin access points, captive-portal phishing, HTTP fallback, and stolen session cookies are separate risks that should not be presented as automatic consequences of TCP disruption.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn66kbjbywughgs7jkvzm.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn66kbjbywughgs7jkvzm.png" alt="Behavior after VPN loss depends on the kill switch and routing policy." width="800" height="525"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Behavior after VPN loss depends on the kill switch and routing policy.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Confidentiality, integrity, and availability all matter
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Property&lt;/th&gt;
&lt;th&gt;What it means here&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Confidentiality&lt;/td&gt;
&lt;td&gt;Prevent unintended disclosure, including unprotected traffic after a tunnel failure&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Integrity&lt;/td&gt;
&lt;td&gt;Reject unauthorized changes, such as injected plaintext HTTP data&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Availability&lt;/td&gt;
&lt;td&gt;Keep legitimate users able to connect and recover from interruptions&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A kill switch can help confidentiality by blocking traffic, while also making the loss of connectivity visible. Reconnection improves availability but cannot replace blocking rules. Strong authentication also needs a recovery path when a legitimate user’s device fails.&lt;/p&gt;
&lt;h2&gt;
  
  
  Session protection needs its own checks
&lt;/h2&gt;

&lt;p&gt;A session cookie represents an authenticated state. If a token can be stolen and replayed, an attacker may not need the account password. Observing correctly protected HTTPS on the same Wi-Fi does not by itself reveal that token.&lt;/p&gt;

&lt;p&gt;For service operators, review the following separately from TCP resilience:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Require HTTPS for authentication and session-bearing requests.&lt;/li&gt;
&lt;li&gt;Mark authentication cookies &lt;code&gt;Secure&lt;/code&gt; and &lt;code&gt;HttpOnly&lt;/code&gt;, and select &lt;code&gt;SameSite&lt;/code&gt; deliberately.&lt;/li&gt;
&lt;li&gt;Use appropriate session expiry, logout invalidation, and reauthentication for sensitive operations.&lt;/li&gt;
&lt;li&gt;Apply authorization to every protected endpoint and API.&lt;/li&gt;
&lt;li&gt;Implement CSRF defenses appropriate to the application.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="na"&gt;Set-Cookie: __Host-session&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="nc"&gt;Path&lt;/span&gt;&lt;span class="o"&gt;=/&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="nc"&gt;Secure&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="nc"&gt;HttpOnly&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="nc"&gt;SameSite&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nc"&gt;Lax&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;__Host-&lt;/code&gt; prefix requires a secure origin, &lt;code&gt;Path=/&lt;/code&gt;, and no &lt;code&gt;Domain&lt;/code&gt; attribute in supporting browsers. &lt;code&gt;HttpOnly&lt;/code&gt; restricts script access to the cookie; it does not make an application immune to XSS. &lt;code&gt;SameSite&lt;/code&gt; controls cross-site cookie sending and is not a complete authorization or CSRF strategy.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;https://www.example.com&lt;/code&gt; and &lt;code&gt;https://api.example.com&lt;/code&gt; are different origins but ordinarily the same site. Separating an API does not automatically require &lt;code&gt;SameSite=None&lt;/code&gt;. Truly cross-site cookie authentication may require &lt;code&gt;SameSite=None; Secure&lt;/code&gt;, additional CSRF protection, and consideration of browser restrictions on third-party cookies. CORS configuration alone is not a CSRF defense.&lt;/p&gt;

&lt;h3&gt;
  
  
  CloudFront: decide what HTTP should do
&lt;/h3&gt;

&lt;p&gt;CloudFront’s Viewer Protocol Policy supports allowing HTTP and HTTPS, redirecting HTTP to HTTPS, or rejecting HTTP with HTTPS Only. For authenticated applications, plan to keep session-bearing traffic off plaintext HTTP. Choose rejection or redirection according to client and entry-point requirements, with HSTS where appropriate.&lt;/p&gt;

&lt;p&gt;A redirect cannot encrypt the initial HTTP request. HSTS protects requests once the browser knows the policy, or through applicable preloading. See &lt;a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/using-https-viewers-to-cloudfront.html" rel="noopener noreferrer"&gt;AWS’s HTTPS guidance&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do redirects and reauthentication stay on HTTPS?
&lt;/h3&gt;

&lt;p&gt;CloudFront or a reverse proxy may terminate HTTPS and communicate with the backend application over HTTP. That internal HTTP hop does not itself expose the traffic to an attacker on the user’s Wi-Fi. The relevant risk arises when the application mistakes the original HTTPS request for HTTP and generates an absolute &lt;code&gt;http://&lt;/code&gt; redirect or reauthentication URL.&lt;/p&gt;

&lt;p&gt;For example, it might return &lt;code&gt;Location: http://example.com/dashboard&lt;/code&gt; instead of &lt;code&gt;Location: https://example.com/dashboard&lt;/code&gt;. CloudFront or the proxy may &lt;a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/http-3xx-status-codes.html" rel="noopener noreferrer"&gt;pass that Location header through unchanged&lt;/a&gt;. The browser then attempts the HTTP navigation; an effective HSTS policy for that host upgrades it to HTTPS. Without such protection, an actual HTTP request and response can be observed or modified on untrusted Wi-Fi.&lt;/p&gt;

&lt;p&gt;A reload or reauthentication after a TCP interruption may exercise a rarely used code path and expose this defect. &lt;strong&gt;A TCP interruption does not automatically downgrade HTTPS. This is a conditional secondary risk involving an application flaw, not an attack directly demonstrated by the NDSS paper.&lt;/strong&gt; A relative redirect such as &lt;code&gt;Location: /callback&lt;/code&gt; normally resolves against the current HTTPS URL and is not itself a downgrade.&lt;/p&gt;

&lt;p&gt;The cookie protection discussed above remains distinct: &lt;code&gt;Secure&lt;/code&gt; prevents a session cookie from being sent in ordinary HTTP requests, but does not prevent HTTP response tampering or a forged login page. An incorrectly generated HTTP OAuth callback will also often be rejected by an authorization server’s redirect-URI matching or HTTPS requirements; it does not necessarily leak an authorization code.&lt;/p&gt;

&lt;p&gt;Check the application’s public URL configuration and its &lt;a href="https://docs.djangoproject.com/en/5.2/ref/settings/#secure-proxy-ssl-header" rel="noopener noreferrer"&gt;handling of trusted proxy headers&lt;/a&gt;, such as &lt;code&gt;X-Forwarded-Proto&lt;/code&gt;. Do not blindly trust client-supplied forwarding headers or assume that enabling HTTPS on every backend hop necessarily fixes URL generation. Alongside HSTS and cookie settings, verify login, logout, OAuth, and reauthentication after session expiry. &lt;strong&gt;Starting on HTTPS is not enough: browser-facing communication must remain on HTTPS throughout those flows.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If a SaaS provider controls these settings, ask for its documented behavior. A VPN cannot fix the service’s authorization or session-management defects.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do the SPA’s API requests also use HTTPS?
&lt;/h3&gt;

&lt;p&gt;A single-page application (SPA) loads HTML and JavaScript, then sends API requests from the browser. Those requests may pass through a reverse proxy or connect directly to a separate API, depending on their URLs and server-side routing. First, check that browser-to-API requests use HTTPS too; serving the frontend over HTTPS through CloudFront does not establish that.&lt;/p&gt;

&lt;p&gt;For example, the application might use &lt;code&gt;http://api.example.com&lt;/code&gt; as its API endpoint. From an HTTPS page, browsers normally block HTTP API calls made through &lt;code&gt;fetch()&lt;/code&gt; or similar APIs as &lt;a href="https://developer.mozilla.org/en-US/docs/Web/Security/Defenses/Mixed_content" rel="noopener noreferrer"&gt;mixed content&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Internal applications may also rely on browser exceptions or enterprise policies that relax mixed-content restrictions to keep legacy HTTP APIs working during development or operation. Microsoft Edge, for example, provides a &lt;a href="https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies/InsecureContentAllowedForUrls" rel="noopener noreferrer"&gt;policy allowing insecure content on specified sites&lt;/a&gt;. An application working on the corporate LAN does not ensure that it remains protected when the same device leaves the office. If the API remains reachable and the path is not protected by a VPN or another secure transport, its HTTP traffic may cross untrusted Wi-Fi. Check browser exceptions, managed policies, and the actual API destinations and routes.&lt;/p&gt;

&lt;p&gt;Separately, if an incorrect redirect or reauthentication flow loads the SPA itself over HTTP, without protection such as HSTS preventing it, subsequent API calls may also use HTTP. Login information actually sent over HTTP and API responses can then be observed or modified on untrusted Wi-Fi. A TCP interruption alone does not cause this situation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check more than the initial page: API calls, post-login navigation, and reauthentication after session expiry must also keep browser-facing communication on HTTPS.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep private administration services private where practical
&lt;/h2&gt;

&lt;p&gt;Databases, SSH, and remote desktop commonly use TCP. Publishing them adds authentication, patching, and access-control responsibilities. An IP allowlist or bastion can reduce exposure, but &lt;strong&gt;an IP allowlist is not authentication&lt;/strong&gt; , and neither guarantees the availability of the path to it.&lt;/p&gt;

&lt;p&gt;One alternative is to connect authorized devices to a private site or VPC through a VPN, leaving databases and administration services off the public internet. A UDP-based authenticated tunnel can also avoid exposing its inner TCP connection directly to the local Wi-Fi attacker.&lt;/p&gt;

&lt;p&gt;The tunnel does not replace application authentication, authorization, patching, VPC security groups, or network access controls. Nor does it guarantee that the underlying network will carry UDP.&lt;/p&gt;

&lt;h2&gt;
  
  
  Zero trust is not simply “stop using a VPN”
&lt;/h2&gt;

&lt;p&gt;Using SaaS directly can be appropriate. HTTPS and well-designed authentication can protect it without a VPN. But moving applications outside a corporate LAN does not by itself establish zero trust.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://csrc.nist.gov/pubs/sp/800/207/final" rel="noopener noreferrer"&gt;NIST’s Zero Trust Architecture&lt;/a&gt; focuses on decisions about resources, identities, devices, and access rather than assuming trust from network location. A VPN can coexist with those principles.&lt;/p&gt;

&lt;p&gt;A reverse proxy or ZTNA gateway can centralize authentication and restrict access per application. It also remains an entry point that needs maintenance and protection. Check that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Every protected route and API actually enforces authentication and authorization.&lt;/li&gt;
&lt;li&gt;Backends cannot be reached through an unintended bypass.&lt;/li&gt;
&lt;li&gt;Identity headers are accepted only from the trusted proxy and cannot be supplied by arbitrary clients.&lt;/li&gt;
&lt;li&gt;Session revocation works after logout, account disablement, or incident response.&lt;/li&gt;
&lt;li&gt;Cookies and tokens remain protected after the initial MFA or passkey login.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Public websites and webhook receivers may reasonably need a public gateway. Private development systems may fit a private-network design better. Evaluate the exposure and operational requirements rather than treating either architecture as universally safer.&lt;/p&gt;

&lt;p&gt;ZTNA and SASE can add valuable controls, including device evaluation and application-level authorization. Their names do not specify every transport or failure behavior. Ask whether a path uses TCP/TLS or UDP, what happens when it fails, and which authentication and session systems it depends on.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do SPA API calls also use the reverse proxy?
&lt;/h3&gt;

&lt;p&gt;The earlier SPA section examined HTTP versus HTTPS. Here, the question is which access controls each request passes through. Putting an internal application behind a reverse proxy does not ensure that API requests use it: they may bypass the proxy and connect to a separate endpoint. This can happen with SPAs built using React or Vite, and with client-side API calls in SSR applications such as those built with Next.js. The choice of technology alone does not establish the actual route.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Through the proxy&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;code&gt;Browser → HTTPS → Reverse Proxy → HTTP → Internal API&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;For example, the SPA requests &lt;code&gt;/api/users&lt;/code&gt; and the proxy forwards that path to the API. Browser-to-proxy traffic uses HTTPS. If the proxy applies authentication and authorization to the API routes too, it can enforce access there. HTTP on a private proxy-to-API segment is not directly exposed to the user’s public Wi-Fi.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Direct API access&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Browser → HTTPS → Reverse Proxy → SPA delivery
Browser → HTTP :8080 → EC2 API Server

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Here, the API request bypasses the proxy. Authentication protecting SPA delivery does not automatically protect that direct request. Independent API authentication and authorization can protect it; without them, business functions may be reachable without passing the proxy’s access checks.&lt;/p&gt;

&lt;p&gt;The mixed-content conditions in the earlier SPA section also apply to this direct HTTP example. Ordinary HTTP &lt;code&gt;fetch()&lt;/code&gt; or XHR calls from HTTPS pages are blocked; requests that actually succeed under exceptions or other conditions must be considered separately. CORS is a different control: allowing an origin through CORS does not itself disable mixed-content protection.&lt;/p&gt;

&lt;p&gt;If the API is reachable and HTTP actually crosses untrusted Wi-Fi without a VPN or equivalent path protection, transmitted login information and API requests or responses can be observed or modified. An internal-only API is not necessarily reachable from outside. Reconnection or reauthentication may expose an existing HTTP configuration, but TCP interruption does not itself cause a downgrade. This is a conditional application risk, not an attack directly demonstrated by the NDSS paper.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbf9tlilvz480n7vzyess.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbf9tlilvz480n7vzyess.png" alt="API requests through the proxy and directly to the backend" width="800" height="1125"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Proxy access controls do not automatically apply to a direct API path. HTTP is normally blocked; when it actually succeeds without VPN or equivalent path protection, plaintext can cross the Wi-Fi network.&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  Is a backend inbound port exposed for direct API access?
&lt;/h3&gt;

&lt;p&gt;Consider a Node.js or Spring Boot API on EC2 accessed directly at &lt;code&gt;http://api.example.com:8080&lt;/code&gt;. If an internet route reaches the instance’s public IP, its security group and host firewall may allow inbound traffic to the API port. The actual port might be 80, 3000, 5000, 8080, or another configured value.&lt;/p&gt;

&lt;p&gt;With a reachable path and a broad source rule such as &lt;code&gt;0.0.0.0/0&lt;/code&gt;, the API may be directly accessible from the internet. Proxy-side restrictions do not apply to that path. Even when the API independently enforces authentication and authorization, vulnerabilities in the publicly reachable API server remain a separate concern.&lt;/p&gt;

&lt;p&gt;This exposure is not inevitable. An architecture that &lt;a href="https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-update-security-groups.html" rel="noopener noreferrer"&gt;restricts backend traffic to the ALB&lt;/a&gt;, or uses an &lt;a href="https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-private.html" rel="noopener noreferrer"&gt;API Gateway private integration&lt;/a&gt;, need not open the EC2 API port to the whole internet. Direct API calls do not imply that every deployment exposes port 8080 globally.&lt;/p&gt;
&lt;h3&gt;
  
  
  Verify the route and the exposed entry points
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Use the browser’s Network panel to inspect API URLs and HTTP/HTTPS during login, session renewal, and reauthentication.&lt;/li&gt;
&lt;li&gt;Confirm whether API calls traverse the proxy. For direct calls, check HTTPS and the API’s own authentication and authorization.&lt;/li&gt;
&lt;li&gt;Review security groups and firewalls for unnecessary API ports and overly broad source ranges such as &lt;code&gt;0.0.0.0/0&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Check production devices for leftover development HTTP URLs or mixed-content exceptions and policies, and verify whether the actual route is protected by a VPN.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Where direct exposure is unnecessary, a properly secured reverse proxy or API gateway can provide access to a private backend. Applications used only by selected devices may instead be restricted to a VPN. &lt;strong&gt;Verify which requests pass through which controls, and which ports are exposed, rather than assuming the proxy protects every path.&lt;/strong&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Check the VPN’s actual transport, endpoint, and recovery path
&lt;/h2&gt;
&lt;h3&gt;
  
  
  Direct connections and relays have different conditions
&lt;/h3&gt;

&lt;p&gt;Some peer-to-peer VPNs fall back to a relay when direct connectivity fails. A TCP/TLS relay introduces an outer TCP connection even if the encapsulated VPN originally uses UDP. Others use UDP relays. The paper does not directly establish successful attacks against every such product.&lt;/p&gt;

&lt;p&gt;A self-hosted direct VPN needs an inbound-reachable endpoint. IPv4 may require port forwarding; IPv6 still needs suitable addressing, inbound firewall policy, and IPv6 at the connecting device. NAT traversal can change those requirements for peer-to-peer products.&lt;/p&gt;

&lt;p&gt;Do not equate every exposed VPN port with an exposed web login interface. WireGuard normally stays silent toward unauthenticated requests, which reduces the processing exposed before authentication. Software maintenance and endpoint exposure still deserve consideration.&lt;/p&gt;

&lt;p&gt;For those details, see &lt;a href="https://www.homegrid-vpn.com/blog/en/wireguard-outside-troubleshooting/" rel="noopener noreferrer"&gt;WireGuard troubleshooting outside the home&lt;/a&gt; and &lt;a href="https://www.homegrid-vpn.com/blog/en/wireguard-silence-outbound-only/" rel="noopener noreferrer"&gt;WireGuard silence and outbound-only design&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;
  
  
  Authentication is part of availability
&lt;/h3&gt;

&lt;p&gt;A service may require a web login or token before bringing up its tunnel. Correct TLS prevents a reset from exposing the credentials, but repeated interruption can still stop the user from completing authentication.&lt;/p&gt;

&lt;p&gt;Passkeys add phishing-resistant authentication tied to the legitimate service. Plan for recovery too. A synced passkey depends on recovery of its sync account; a device-bound credential or security key needs an independent backup or another supported recovery mechanism.&lt;/p&gt;

&lt;p&gt;Avoid circular dependencies, such as needing approval from the failed phone to recover the account that restores its passkeys. Register supported backup credentials, protect recovery codes, and verify that the recovery process works. Recovery should remain resistant to account takeover.&lt;/p&gt;
&lt;h2&gt;
  
  
  How WireGuard and HomeGrid VPN differ from an outer-TCP design
&lt;/h2&gt;

&lt;p&gt;WireGuard’s transport and HomeGrid VPN’s topology are separate design choices. Standard WireGuard uses UDP, while HomeGrid VPN connects Remote devices and site-side Grid or Spoke devices through a Cloud Hub.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Item&lt;/th&gt;
&lt;th&gt;VPN using outer TCP&lt;/th&gt;
&lt;th&gt;WireGuard / UDP with HomeGrid VPN&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Forged TCP reset&lt;/td&gt;
&lt;td&gt;Outer TCP may be a target&lt;/td&gt;
&lt;td&gt;No outer TCP connection to reset&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Recovery&lt;/td&gt;
&lt;td&gt;May need a new TCP connection&lt;/td&gt;
&lt;td&gt;WireGuard performs handshakes as needed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;User login during ordinary recovery&lt;/td&gt;
&lt;td&gt;Product-dependent&lt;/td&gt;
&lt;td&gt;Registered peers use WireGuard keys; routine recovery does not require a new web login&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Inner TCP traffic&lt;/td&gt;
&lt;td&gt;Can be encrypted within the VPN&lt;/td&gt;
&lt;td&gt;Encrypted and authenticated within the VPN&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Kill switch&lt;/td&gt;
&lt;td&gt;Product and setting-dependent&lt;/td&gt;
&lt;td&gt;Depends on the client and connection method&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Site-side inbound VPN endpoint&lt;/td&gt;
&lt;td&gt;Architecture-dependent&lt;/td&gt;
&lt;td&gt;Site initiates outbound communication to the Cloud Hub&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Network disruption&lt;/td&gt;
&lt;td&gt;TCP-specific and general failure modes&lt;/td&gt;
&lt;td&gt;UDP blocking, loss, and other failures remain possible&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;WireGuard’s connectionless design retains state for keys and handshakes without using TCP connection setup. It handles packet loss and authenticated endpoint changes, performing fresh handshakes when needed. A long outage can still cause inner SSH, RDP, or application connections to time out.&lt;/p&gt;

&lt;p&gt;An attacker on the local Wi-Fi cannot simply send forged inner TCP packets through the tunnel without passing WireGuard authentication. This prevents directly transplanting the paper’s technique into the authenticated tunnel. It does not hide all packet sizes or defeat every traffic-analysis method.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A kill switch is not a feature of the WireGuard protocol itself.&lt;/strong&gt; HomeGrid VPN’s behavior depends on the client and connection method. In particular, the documented Linux connection command has no kill switch and tunnels IPv4 only. Check the &lt;a href="https://www.homegrid-vpn.com/guides/en/add-linux-device/" rel="noopener noreferrer"&gt;Linux device guide&lt;/a&gt; before relying on it to protect internet traffic. Split-tunnel traffic outside a VPN is outside its protection by design.&lt;/p&gt;

&lt;p&gt;With HomeGrid VPN, site-side devices initiate connections to the Cloud Hub, so port forwarding and IPv6 inbound rules at the site are not prerequisites. This changes the entry points exposed at home or in an office; it does not eliminate trust in the Cloud Hub or its availability.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Cloud Hub is not necessarily the internet exit.&lt;/strong&gt; When a home Grid is the exit, internet destinations see the home’s public IP. The hub remains part of the route. See &lt;a href="https://www.homegrid-vpn.com/blog/en/how-homegrid-vpn-works/" rel="noopener noreferrer"&gt;how HomeGrid VPN works&lt;/a&gt; for the topology.&lt;/p&gt;

&lt;p&gt;Client-generated WireGuard keys authenticate registered peers. Initial registration and dashboard access still have their own authentication requirements. Lost devices need revocation and replacement. LAN ACLs restrict reachable LAN subnets; VPC-side controls and application authorization remain necessary.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1icki522io8opkmrylle.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1icki522io8opkmrylle.png" alt="With a home exit, traffic crosses the Cloud Hub before leaving through the home ISP." width="800" height="812"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;With a home exit, traffic crosses the Cloud Hub before leaving through the home ISP.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  A practical checklist for public Wi-Fi
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Confirm the network name with the venue and avoid lookalike access points.&lt;/li&gt;
&lt;li&gt;Never bypass unexpected HTTPS certificate warnings.&lt;/li&gt;
&lt;li&gt;Complete a required captive portal with only necessary information, then verify the VPN before sensitive work.&lt;/li&gt;
&lt;li&gt;Check the active transport, including relay fallback, and which traffic the VPN actually covers.&lt;/li&gt;
&lt;li&gt;Enable and verify supported kill-switch behavior, including reconnection, IPv6, and DNS handling.&lt;/li&gt;
&lt;li&gt;Check monitoring and recovery rather than assuming a disconnected VPN will reconnect.&lt;/li&gt;
&lt;li&gt;If the connection remains unreliable, use another network, such as mobile data, while considering its data allowance.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For work, also follow organizational policy and establish a recovery procedure for failed authentication devices. A TCP reset alone is not a reason to assume compromise, but persistent connectivity problems deserve investigation.&lt;/p&gt;
&lt;h2&gt;
  
  
  Review your home Wi-Fi too
&lt;/h2&gt;

&lt;p&gt;Public Wi-Fi is not the only place where network membership matters. A weak or widely shared home password can let unwanted devices join.&lt;/p&gt;
&lt;h3&gt;
  
  
  WPA2 and offline password guessing
&lt;/h3&gt;

&lt;p&gt;WPA2-Personal can expose material that lets an attacker test password candidates offline after capturing a suitable handshake. A published RTX 5090 Hashcat benchmark reports about 3.36 million candidates per second for mode 22000. It is one measurement, not a guaranteed cracking rate.&lt;/p&gt;

&lt;p&gt;For a password chosen uniformly from 62 uppercase letters, lowercase letters, and digits, a full search at that fixed rate would take approximately:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Length&lt;/th&gt;
&lt;th&gt;Time to exhaust the search space&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;8 characters&lt;/td&gt;
&lt;td&gt;2 years&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;10 characters&lt;/td&gt;
&lt;td&gt;7,900 years&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;12 characters&lt;/td&gt;
&lt;td&gt;30 million years&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;16 characters&lt;/td&gt;
&lt;td&gt;450 trillion years&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;20 characters&lt;/td&gt;
&lt;td&gt;6.6 × 10²¹ years&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;24 characters&lt;/td&gt;
&lt;td&gt;9.8 × 10²⁸ years&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;This assumes one GPU, no password bias, no dictionary advantage, and a constant rate. Expected discovery time is roughly half a full search. It is a scale illustration, not a lifetime security guarantee.&lt;/p&gt;

&lt;p&gt;A long phrase composed of predictable names, dates, or substitutions does not have the same distribution. Attackers prioritize likely candidates instead of exhaustively enumerating every string.&lt;/p&gt;
&lt;h3&gt;
  
  
  WPA3 improves authentication without removing every risk
&lt;/h3&gt;

&lt;p&gt;WPA3-Personal’s SAE is designed to resist the ordinary passive offline dictionary attack against WPA2-PSK. It does not make weak passwords, implementation defects, password disclosure, or online guessing irrelevant. WPA2/WPA3 transition deployments can retain risks associated with the shared password’s WPA2 use.&lt;/p&gt;

&lt;p&gt;Where devices support it, consider WPA3-Personal-only mode with a long random password. Check compatibility after changing the setting and keep supported firmware current.&lt;/p&gt;

&lt;p&gt;Python’s cryptographic random generator can create one:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;secrets&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;string&lt;/span&gt;

&lt;span class="n"&gt;alphabet&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;string&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ascii_letters&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;string&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;digits&lt;/span&gt;
&lt;span class="n"&gt;password&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;join&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;secrets&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;choice&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;alphabet&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;_&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="nb"&gt;range&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;32&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;password&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A 24–32 character random password is practical when devices support it and manual entry is infrequent. Store it with the SSID in a protected password manager, or keep an accurate paper backup in a controlled physical location. Plan for loss of the password manager or its authentication device. Avoid uncontrolled plaintext copies.&lt;/p&gt;

&lt;p&gt;If manual transcription matters, exclude ambiguous characters and compensate with sufficient length:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;secrets&lt;/span&gt;

&lt;span class="n"&gt;alphabet&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="s2"&gt;"ABCDEFGHJKLMNPQRSTUVWXYZ"&lt;/span&gt;
    &lt;span class="s2"&gt;"abcdefghijkmnopqrstuvwxyz"&lt;/span&gt;
    &lt;span class="s2"&gt;"23456789"&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;password&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;join&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;secrets&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;choice&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;alphabet&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;_&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="nb"&gt;range&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;32&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;password&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  EAP-TLS is also a learning project
&lt;/h3&gt;

&lt;p&gt;WPA2/WPA3-Enterprise with EAP-TLS uses client certificates and private keys rather than a shared password. It can support per-device lifecycle management, but requires a CA, certificate issuance and renewal, revocation, RADIUS, and appropriate validation of the authentication server’s certificate and name.&lt;/p&gt;

&lt;p&gt;I recently built a WPA2-Enterprise EAP-TLS environment using a Cisco Aironet 1830 and FreeRADIUS, with configuration profiles for iOS. Treat this as a learning example, and check equipment support and firmware lifecycle when choosing hardware.&lt;/p&gt;

&lt;p&gt;Protect profiles containing private keys during distribution and storage. PMF helps protect selected management frames, and guest isolation limits unnecessary device-to-device access. Neither should be described as a complete mitigation for the TCP side channel discussed here.&lt;/p&gt;

&lt;h2&gt;
  
  
  A familiar provider name is no longer enough
&lt;/h2&gt;

&lt;p&gt;Reports of data breaches and unauthorized access continue to show why security services need technical scrutiny. The &lt;a href="https://www.ipa.go.jp/security/10threats/10threats2026.html" rel="noopener noreferrer"&gt;IPA’s 2026 threat assessment&lt;/a&gt; is one current reference on organizational threats in Japan.&lt;/p&gt;

&lt;p&gt;A provider’s size, history, and adoption can inform a decision. &lt;strong&gt;Going forward, they should not replace checking how the service protects traffic and behaves when protection fails.&lt;/strong&gt; This does not mean reputation used to guarantee safety or that the NDSS paper suddenly made every VPN unsafe.&lt;/p&gt;

&lt;p&gt;Ask a provider:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;How are users and registered devices authenticated?&lt;/li&gt;
&lt;li&gt;What happens when a direct connection cannot be established?&lt;/li&gt;
&lt;li&gt;Can transport fall back to a TCP relay, and how can a user tell?&lt;/li&gt;
&lt;li&gt;Which traffic is blocked when the tunnel fails, including IPv6 and DNS?&lt;/li&gt;
&lt;li&gt;How do monitoring and automatic recovery work?&lt;/li&gt;
&lt;li&gt;How are authentication tokens protected and revoked?&lt;/li&gt;
&lt;li&gt;How can a legitimate user recover after losing an authentication device?&lt;/li&gt;
&lt;li&gt;How are outages communicated and resolved?&lt;/li&gt;
&lt;li&gt;How are vulnerabilities fixed and users notified?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Providers need not disclose sensitive implementation details to explain their basic security properties. If a serious issue remains unresolved and you cannot compensate for it, consider a different service.&lt;/p&gt;

&lt;p&gt;Apply exactly the same questions to HomeGrid VPN. WireGuard, client-generated keys, outbound connections, ACLs, and recovery behavior should be evaluated against your actual devices and requirements, rather than accepted as guarantees because of the product name.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use public Wi-Fi with an informed plan
&lt;/h2&gt;

&lt;p&gt;Encryption, reliable recovery, and authentication protect different things. HTTPS remains essential. A properly configured VPN can protect a chosen path, while its transport and failure rules determine what happens during disruption. Strong Wi-Fi authentication controls network membership; it does not replace application protection.&lt;/p&gt;

&lt;p&gt;Keep confidentiality, integrity, and availability in view. Understand what your service does, verify its supported behavior, and prepare a usable recovery path. That is a more practical response than either avoiding every public network or assuming an encrypted connection cannot be interrupted.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.ndss-symposium.org/ndss-paper/off-path-tcp-hijacking-in-wi-fi-networks-a-packet-size-side-channel-attack/" rel="noopener noreferrer"&gt;Wang et al., NDSS 2025 paper and PDF&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc5961" rel="noopener noreferrer"&gt;RFC 5961: TCP robustness against blind in-window attacks&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cheatsheetseries.owasp.org/cheatsheets/Session_Management_Cheat_Sheet.html" rel="noopener noreferrer"&gt;OWASP Session Management Cheat Sheet&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html" rel="noopener noreferrer"&gt;OWASP CSRF Prevention Cheat Sheet&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/pubs/sp/800/207/final" rel="noopener noreferrer"&gt;NIST SP 800-207: Zero Trust Architecture&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://fidoalliance.org/passkeys/" rel="noopener noreferrer"&gt;FIDO Alliance: Passkeys&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.wireguard.com/protocol/" rel="noopener noreferrer"&gt;WireGuard protocol and cryptography&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://arubanetworking.hpe.com/techdocs/aos/wifi-design-deploy/security/modes/wpa3-personal/" rel="noopener noreferrer"&gt;HPE Aruba Networking: WPA3-Personal&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/0x3444/hashcat_benchmarks/blob/main/NVIDIA_GeForce_RTX_5090.txt" rel="noopener noreferrer"&gt;Published RTX 5090 Hashcat benchmark&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.python.org/3/library/secrets.html" rel="noopener noreferrer"&gt;Python secrets module&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.freeradius.org/" rel="noopener noreferrer"&gt;FreeRADIUS&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Originally published at &lt;a href="https://www.homegrid-vpn.com/blog/en/free-wifi-safety/" rel="noopener noreferrer"&gt;https://www.homegrid-vpn.com/blog/en/free-wifi-safety/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>networking</category>
      <category>privacy</category>
      <category>vpn</category>
    </item>
    <item>
      <title>WireGuard Works on LAN but Not Remotely? Troubleshooting and Design Choices</title>
      <dc:creator>HomeGrid VPN</dc:creator>
      <pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/homegrid_vpn/wireguard-works-on-lan-but-not-remotely-troubleshooting-and-design-choices-14a5</link>
      <guid>https://dev.to/homegrid_vpn/wireguard-works-on-lan-but-not-remotely-troubleshooting-and-design-choices-14a5</guid>
      <description>&lt;p&gt;When WireGuard works on your home LAN but fails remotely, check whether packets actually reach the server before rebuilding keys or changing unrelated settings. A successful LAN test does not verify your public endpoint, upstream NAT, or inbound firewall rules.&lt;/p&gt;

&lt;p&gt;You installed WireGuard, tested it at home, and configured port forwarding. Then you turned off your phone’s Wi-Fi, tried over mobile data, and nothing worked.&lt;/p&gt;

&lt;p&gt;The first question is simple: &lt;strong&gt;does the UDP traffic from the remote device reach your WireGuard server?&lt;/strong&gt; Once you know where communication stops, you can decide whether to repair the direct connection or choose a design that connects outward from home.&lt;/p&gt;

&lt;h2&gt;
  
  
  First, distinguish a failed handshake from failed LAN access
&lt;/h2&gt;

&lt;p&gt;An enabled WireGuard tunnel is not proof that its peer is communicating.&lt;/p&gt;

&lt;p&gt;On a Linux server, inspect the latest handshake:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;wg show wg0

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Replace &lt;code&gt;wg0&lt;/code&gt; with your interface name. On phones and Windows, check the app’s handshake information and logs.&lt;/p&gt;

&lt;p&gt;Generate traffic to an address configured to use the tunnel, such as the other peer’s VPN address, and compare the results. WireGuard stays quiet when there is nothing to send, so an old handshake timestamp during an idle period is not enough to diagnose a fault.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What happens during your test&lt;/th&gt;
&lt;th&gt;What to inspect next&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;The handshake does not update&lt;/td&gt;
&lt;td&gt;Endpoint, UDP reachability, listening port, firewall, keys&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The handshake updates, but the NAS is unreachable&lt;/td&gt;
&lt;td&gt;AllowedIPs, routes, forwarding, return path, NAS access rules&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;An IP address works, but a hostname does not&lt;/td&gt;
&lt;td&gt;DNS and name resolution&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Small transfers work, but larger transfers or some pages stall&lt;/td&gt;
&lt;td&gt;MTU and path restrictions&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A working handshake does not prove that traffic can reach a NAS or use your home connection as an internet exit.&lt;/p&gt;

&lt;p&gt;Reference: &lt;a href="https://www.wireguard.com/quickstart/" rel="noopener noreferrer"&gt;WireGuard Quick Start&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Test from outside your home network
&lt;/h2&gt;

&lt;p&gt;Testing your public IP or DDNS hostname while still connected to your home Wi-Fi introduces another variable: NAT loopback. Whether a router can send that connection back inside depends on its implementation and configuration.&lt;/p&gt;

&lt;p&gt;A failed loopback test does not prove that remote access fails. Conversely, a successful test using the server’s private LAN address does not test your ISP or port forwarding.&lt;/p&gt;

&lt;p&gt;Turn off your phone’s Wi-Fi and test over mobile data. Verify that its Endpoint points to the externally reachable address or hostname, rather than a private LAN address.&lt;/p&gt;

&lt;p&gt;This is an IPv4 example; replace the example hostname:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight ini"&gt;&lt;code&gt;&lt;span class="nn"&gt;[Peer]&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="py"&gt;Endpoint&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s"&gt;vpn.example.com:51820&lt;/span&gt;
&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;51820&lt;/code&gt; is a common example, not a required port. Match the client’s destination port to the router’s external UDP port. If you use DDNS, verify that the hostname points to your current public address.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Check whether your home connection can receive inbound IPv4
&lt;/h2&gt;

&lt;p&gt;A conventional IPv4 setup expects this path:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Remote device
    ↓ UDP
Home router's public IPv4 address
    ↓ Port forwarding
WireGuard server's private LAN address

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If another NAT sits upstream of your router, changing only your own router may not be enough.&lt;/p&gt;

&lt;h3&gt;
  
  
  Compare the router’s WAN address with your public IPv4 address
&lt;/h3&gt;

&lt;p&gt;Read the WAN IPv4 address in your router’s management interface. Compare it with the address reported by an IPv4 address-checking service from home. Do not accidentally compare a WAN IPv4 address with a browser’s IPv6 result.&lt;/p&gt;

&lt;p&gt;These ranges are not ordinary public IPv4 addresses:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;10.0.0.0/8&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;172.16.0.0/12&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;192.168.0.0/16&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;100.64.0.0/10&lt;/code&gt; — 100.64.0.0 through 100.127.255.255&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The first three are private address ranges. The last is shared address space used for purposes such as carrier-grade NAT. See &lt;a href="https://www.rfc-editor.org/rfc/rfc6598" rel="noopener noreferrer"&gt;RFC 6598&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you control both routers in a double-NAT setup, forwarding on the upstream router or changing the router arrangement may solve the problem. You may not have that control over an ISP’s CGNAT or an apartment building’s shared gateway.&lt;/p&gt;

&lt;p&gt;The address comparison is a clue, not a complete diagnosis. Check your service plan and connection technology too.&lt;/p&gt;

&lt;h3&gt;
  
  
  IPv4-over-IPv6 services have different restrictions
&lt;/h3&gt;

&lt;p&gt;Some ISPs, including providers in Japan, deliver IPv4 over an IPv6 access network. Do not assume every such service has the same inbound limitations.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Connection type&lt;/th&gt;
&lt;th&gt;What matters&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;MAP-E with a shared public IPv4 address&lt;/td&gt;
&lt;td&gt;Your allocated port set and the router’s forwarding support&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A typical DS-Lite service&lt;/td&gt;
&lt;td&gt;Provider-side NAT and whether inbound mappings are offered&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Double NAT inside your home&lt;/td&gt;
&lt;td&gt;Whether you can configure both routers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A building’s shared NAT&lt;/td&gt;
&lt;td&gt;Whether the building operator allows inbound mappings&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;With MAP-E, an assigned external UDP port may work even when &lt;code&gt;51820&lt;/code&gt; is unavailable. Whether the router can translate that port to a different internal port depends on the device.&lt;/p&gt;

&lt;p&gt;With a typical DS-Lite service, IPv4 NAT resides at the provider. A forwarding rule on your home router alone cannot establish an arbitrary inbound mapping there. Check the provider’s actual features and terms.&lt;/p&gt;

&lt;p&gt;References: &lt;a href="https://www.rfc-editor.org/rfc/rfc7597.txt" rel="noopener noreferrer"&gt;MAP-E, RFC 7597&lt;/a&gt;, &lt;a href="https://www.rfc-editor.org/rfc/rfc6333" rel="noopener noreferrer"&gt;DS-Lite, RFC 6333&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Match UDP, the destination address, and the listening port
&lt;/h2&gt;

&lt;p&gt;If the connection supports inbound access, inspect the forwarding rule:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Is the protocol UDP?&lt;/li&gt;
&lt;li&gt;Does the destination match the server’s current LAN address?&lt;/li&gt;
&lt;li&gt;Does the internal port match WireGuard’s listening port?&lt;/li&gt;
&lt;li&gt;Does the client’s Endpoint use the correct external port?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A DHCP address change can leave a forwarding rule pointing to the wrong machine. A DHCP reservation can make this easier to maintain.&lt;/p&gt;

&lt;p&gt;If WireGuard runs on the router itself, inspect rules permitting UDP traffic to the router, rather than forwarding to another LAN host.&lt;/p&gt;

&lt;p&gt;Containers and virtual machines add another boundary. Check the path from the host to the guest or container, including whether Docker publishes the UDP port rather than only TCP.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Observe packets with tcpdump
&lt;/h2&gt;

&lt;p&gt;Move from configuration screens to the actual traffic. On the Linux server, observe the listening port:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;tcpdump &lt;span class="nt"&gt;-ni&lt;/span&gt; any &lt;span class="s1"&gt;'udp port 51820'&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Use your real port. Enable the remote tunnel and generate traffic to a VPN destination. Stop the capture with &lt;code&gt;Ctrl+C&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;For a containerized server, inspect the host first and then the container if needed. A host capture on &lt;code&gt;any&lt;/code&gt; does not directly expose every interface in a separate network namespace.&lt;/p&gt;

&lt;h3&gt;
  
  
  No matching inbound UDP appears
&lt;/h3&gt;

&lt;p&gt;Check the Endpoint, external port, forwarding, upstream NAT, and the remote network’s UDP policy. Also verify the capture location and filter: &lt;strong&gt;an empty capture alone does not prove the ISP is blocking traffic.&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  UDP arrives, but the handshake does not update
&lt;/h3&gt;

&lt;p&gt;Packets reached that observation point. Now inspect the host firewall, actual listening port, peer public keys, and any configured preshared key.&lt;/p&gt;

&lt;p&gt;A packet visible in a capture may still be dropped by the host firewall. Its presence also does not prove it is an authenticated WireGuard request. Inspect specific rules and counters instead of disabling the entire firewall.&lt;/p&gt;

&lt;h3&gt;
  
  
  A generic UDP port checker is not decisive
&lt;/h3&gt;

&lt;p&gt;TCP-only checking tools cannot test a WireGuard endpoint. UDP does not provide the same simple connection test as TCP, and WireGuard normally does not answer unauthorized requests.&lt;/p&gt;

&lt;p&gt;Use an actual configured peer, handshake information, and packet observations together. A generic probe receiving no answer is not enough to declare the endpoint closed.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. If the handshake succeeds, inspect the LAN route
&lt;/h2&gt;

&lt;p&gt;If the server’s VPN address works but a separate NAS does not, inspect:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The client’s AllowedIPs for the NAS address or home subnet.&lt;/li&gt;
&lt;li&gt;The server’s peer configuration for the client’s VPN source address.&lt;/li&gt;
&lt;li&gt;IP forwarding and forwarding firewall rules on the server.&lt;/li&gt;
&lt;li&gt;The return route from the NAS to the VPN client.&lt;/li&gt;
&lt;li&gt;SNAT, if your design uses it instead of a return route.&lt;/li&gt;
&lt;li&gt;The NAS’s own firewall and service access rules.&lt;/li&gt;
&lt;li&gt;Overlapping address ranges between the remote LAN and the home LAN.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;AllowedIPs participates in outgoing peer selection and validates source addresses on received tunnel packets. OS routing also matters. &lt;code&gt;wg-quick&lt;/code&gt; normally derives routes from AllowedIPs, but other tools or settings may behave differently.&lt;/p&gt;

&lt;p&gt;References: &lt;a href="https://www.wireguard.com/#cryptokey-routing" rel="noopener noreferrer"&gt;WireGuard Cryptokey Routing&lt;/a&gt;, &lt;a href="https://git.zx2c4.com/wireguard-tools/about/src/man/wg-quick.8" rel="noopener noreferrer"&gt;wg-quick manual&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Test the VPN address, the NAS’s IP address, and then its hostname. Avoid changing DNS and MTU at the same time. For a relevant container example, see &lt;a href="https://www.homegrid-vpn.com/blog/en/docker-desktop-wireguard-mtu/" rel="noopener noreferrer"&gt;WireGuard MTU behavior in Docker Desktop&lt;/a&gt;; its values are not universal recommendations.&lt;/p&gt;

&lt;h2&gt;
  
  
  IPv6 removes port forwarding, not inbound access requirements
&lt;/h2&gt;

&lt;p&gt;Direct IPv6 may work when inbound IPv4 does not. However, it still requires a globally reachable server address and suitable inbound rules on both the router and server OS, as well as a reachable ISP path.&lt;/p&gt;

&lt;p&gt;A link-local address starting with &lt;code&gt;fe80::&lt;/code&gt;, or only a unique local address in &lt;code&gt;fc00::/7&lt;/code&gt; — commonly &lt;code&gt;fd…&lt;/code&gt; — is not an internet-reachable endpoint.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do not plan a trip around public Wi-Fi having IPv6
&lt;/h3&gt;

&lt;p&gt;The remote network needs IPv6 too. IPv4-only public Wi-Fi remains common, so &lt;strong&gt;do not build a travel setup that depends on reaching your home IPv6 endpoint directly from airport, café, or hotel Wi-Fi.&lt;/strong&gt; Correct home-side settings cannot create IPv6 connectivity on an IPv4-only remote connection.&lt;/p&gt;

&lt;p&gt;A paper presented at NDSS 2025, “Off-Path TCP Hijacking in Wi-Fi Networks: A Packet-Size Side Channel Attack,” examined 80 real-world Wi-Fi networks, including cafés and hotels. &lt;strong&gt;74 networks, or 92.5%, were IPv4-only; six, or 7.5%, had IPv6 capabilities.&lt;/strong&gt; This is not an exact worldwide adoption rate, but it supports the practical concern that IPv6 is often unavailable on public Wi-Fi. See &lt;a href="https://www.ndss-symposium.org/wp-content/uploads/2025-305-paper.pdf#page=11" rel="noopener noreferrer"&gt;Figure 10 and the accompanying text, PDF page 11&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Existing equipment and captive portals are part of the issue. A captive portal handles login or acceptance of terms before internet access. For example, &lt;a href="https://docs.netgate.com/pfsense/en/latest/captiveportal/index.html#ipv6" rel="noopener noreferrer"&gt;pfSense documents its captive portal as incompatible with IPv6&lt;/a&gt;. The whole guest-access system needs suitable support, not just its upstream internet connection.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Hotel Wi-Fi: IPv4 only
    ✕ No direct path to an IPv6 endpoint
Home WireGuard: global IPv6 address

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If mobile data works but hotel Wi-Fi does not, check IPv6 availability at the remote end before replacing keys or changing the server. Ordinary web browsing on Wi-Fi does not establish that IPv6 works.&lt;/p&gt;

&lt;p&gt;Switching to an IPv6-capable mobile connection or tethering consumes mobile data. A file transfer or remote work session that you expected to carry over free hotel Wi-Fi can instead use a roaming allowance and require additional data purchases or charges, depending on your plan.&lt;/p&gt;

&lt;p&gt;IPv6 direct access is not restricted exclusively to mobile networks: some Wi-Fi networks support it. But on an IPv4-only Wi-Fi network, you need another suitable connection. Mobile and roaming connections do not guarantee IPv6 either; check the carrier, plan, and visited network.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An IPv6-capable home does not make an IPv6-only VPN endpoint dependable on travel Wi-Fi.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Do not enable “IPv6 pass-through” based on its name alone. Check the router’s implementation and firewall behavior, since it can affect reachability of other LAN devices too.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faqz7xwmxe3z5k3ccv37e.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faqz7xwmxe3z5k3ccv37e.png" alt="IPv6 is needed at both ends" width="800" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Correct settings at home cannot provide IPv6 connectivity to an IPv4-only hotel network.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  A working connection still leaves an exposed endpoint to maintain
&lt;/h2&gt;

&lt;p&gt;Port forwarding and IPv6 inbound rules create paths for incoming connection attempts. &lt;strong&gt;Making the VPN work is only the start of maintaining that endpoint.&lt;/strong&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  Recent advisories show why exposed network devices need attention
&lt;/h3&gt;

&lt;p&gt;On June 22, 2026, Singapore’s Cyber Security Agency warned about credential-harvesting attacks against internet-facing FortiGate devices and VPN portals, including brute-force, dictionary, and credential-stuffing attempts. It recommended restricting or disabling internet-facing administrative access. See the &lt;a href="https://www.csa.gov.sg/alerts-and-advisories/advisories/ad-2026-007/" rel="noopener noreferrer"&gt;CSA advisory&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The February 2025 joint &lt;a href="https://www.cyber.gov.au/publication/security-considerations-for-edge-devices" rel="noopener noreferrer"&gt;Security considerations for edge devices&lt;/a&gt; guidance also discusses vulnerabilities, misconfiguration, denial of service, and avoiding direct internet exposure of management interfaces.&lt;/p&gt;

&lt;p&gt;These are not evidence that the same attacks work against a home WireGuard UDP endpoint. WireGuard peer authentication differs from password-based portals. They illustrate the wider operational issue: maintain the device and its exposed services, not just the VPN configuration.&lt;/p&gt;

&lt;p&gt;Ask whether you can keep up with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Updates for WireGuard, the OS, router, and management tools.&lt;/li&gt;
&lt;li&gt;Checking for accidentally exposed management interfaces, SSH, or NAS services.&lt;/li&gt;
&lt;li&gt;Revoking lost or retired devices’ keys.&lt;/li&gt;
&lt;li&gt;Limiting the LANs accessible after a VPN connection.&lt;/li&gt;
&lt;li&gt;Handling disruption from excessive traffic or service failures.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An open UDP port does not let an attacker without the required keys connect as an authorized peer. However, a vulnerability in reachable packet-processing code that can be exploited before authentication could create a different entry path. This is a design consideration, not a claim that WireGuard currently has such a vulnerability.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key authentication and silence toward unauthorized probes do not eliminate the need to maintain the system processing inbound packets.&lt;/strong&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  What can an attacker reach after a compromise?
&lt;/h3&gt;

&lt;p&gt;A stolen client key and a compromised VPN server are different incidents, but both require thinking about reachable networks.&lt;/p&gt;

&lt;p&gt;If NAS devices, workstations, development servers, and router management interfaces share a LAN without appropriate restrictions, an attacker may be able to explore and attack several devices from an initial foothold. This is lateral movement.&lt;/p&gt;

&lt;p&gt;Network reachability is not the same as permission to read files or administer a service. Service authentication and host firewalls still matter. Nevertheless, a broader reachable network gives an attacker more places to try stolen credentials or other vulnerabilities.&lt;/p&gt;

&lt;p&gt;The useful starting point is &lt;strong&gt;default deny: authorize only the LAN subnets a device needs.&lt;/strong&gt; Authenticating a peer answers who is connecting. Authorizing access answers which LANs that peer may reach.&lt;/p&gt;

&lt;p&gt;Subnet-level permissions also keep everyday administration manageable. You need not add a separate VPN rule every time you add another PC or NAS inside an already authorized LAN. Leave unrelated LANs unauthorized and separate networks with different protection requirements.&lt;/p&gt;

&lt;p&gt;A compromised authorized device may still be used as a stepping stone within its permitted reach. If it has another route into a different LAN, that path needs its own controls. Default deny remains useful because it avoids granting every connected device access to every LAN at the outset.&lt;/p&gt;

&lt;p&gt;You can build this with WireGuard peer-to-address mappings, forwarding firewall rules, and network segmentation. But permissions must stay aligned with device enrollment, removal, and key revocation. A broad “VPN to LAN: allow” rule does not provide that distinction, and client-side AllowedIPs alone should not enforce your access policy.&lt;/p&gt;

&lt;p&gt;If the VPN server itself is compromised with sufficient privileges, an attacker may also change controls on that server. Consider boundaries enforced elsewhere for important networks.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Running a home VPN means maintaining both its entry point and the access available beyond it.&lt;/strong&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  A home endpoint can reveal location clues
&lt;/h3&gt;

&lt;p&gt;WireGuard encrypts tunnel contents, not the destination address in the outer IP header. Someone positioned to observe traffic on your travel network may see connections to your home endpoint, whether it uses IPv4 or IPv6.&lt;/p&gt;

&lt;p&gt;GeoIP databases can provide country or regional estimates. ASN and ISP information can identify the associated network. These are clues, not an exact street address: &lt;a href="https://support.maxmind.com/knowledge-base/articles/maxmind-geolocation-accuracy" rel="noopener noreferrer"&gt;MaxMind explains that its GeoIP data cannot locate a specific household, person, or street address&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The concern is that a home-side address can become associated with activity on a travel network, potentially alongside account or repeated-connection records. An address alone does not establish that the destination is the user’s home. Changing the UDP port does not remove the address from the outer packets.&lt;/p&gt;
&lt;h3&gt;
  
  
  An attacker may target the router rather than WireGuard
&lt;/h3&gt;

&lt;p&gt;If an observer learns the home-side endpoint address, other internet-reachable functions on that address may also attract investigation. An exposed router management interface with an exploitable vulnerability could provide an entry path without breaking WireGuard authentication.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.jpcert.or.jp/tsubame/report/report202507-09.html" rel="noopener noreferrer"&gt;JPCERT/CC’s July–September 2025 observation report&lt;/a&gt; discusses routers with internet-accessible management interfaces and the risks of outdated firmware, unauthorized access, and use as attack infrastructure.&lt;/p&gt;

&lt;p&gt;Knowing an IP address does not make a LAN-only management interface reachable. With IPv6, the VPN server and router can also have different addresses. An actual attack still needs a reachable function and applicable conditions.&lt;/p&gt;
&lt;h3&gt;
  
  
  The residential connection itself can be valuable to attackers
&lt;/h3&gt;

&lt;p&gt;“There is nothing worth stealing at home” misses another motive. &lt;strong&gt;A residential internet connection can itself be useful as a relay for someone else’s traffic.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;On July 21, 2026, Japan’s NICT, together with the Ministry of Internal Affairs and Communications and the National Police Agency, published information on residential proxies abusing home IoT devices. Routers and cameras can relay traffic used to obscure the source of unauthorized access or fraud. NICT reported observing up to approximately 27,000 exit IP addresses in a day from January 2026 onward. That is an observation of exit addresses, not a count of routers all compromised through vulnerabilities. See &lt;a href="https://www.nict.go.jp/press/2026/07/21-1.html" rel="noopener noreferrer"&gt;NICT’s announcement&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;You are protecting more than files on your NAS. You also want to prevent your connection from becoming someone else’s relay.&lt;/p&gt;

&lt;p&gt;Public addresses can be discovered without observing your VPN traffic. Even so, there is no need to supply extra clues linking your travel activity to a home endpoint. &lt;strong&gt;Reducing unnecessary exposure of that endpoint and reducing directly reachable services are complementary choices.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Disable unnecessary WAN management, update firmware, and replace unsupported equipment. Updates are essential, but a fully patched device may still have an undisclosed or unpatched vulnerability. Price alone does not determine security.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reducing the attack surface is useful alongside patching. A secure WireGuard configuration does not establish that every other exposed function on your home network is secure.&lt;/strong&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Keep a direct endpoint, or change the connection design?
&lt;/h2&gt;

&lt;p&gt;A direct home WireGuard setup is a valid option when the connection supports it and you can manage the exposed endpoint, keys, and access rules.&lt;/p&gt;

&lt;p&gt;An outward connection from home is worth considering if you do not want to change a family home’s router or ISP, depend on IPv6 at your travel destination, or maintain home-side inbound rules.&lt;/p&gt;

&lt;p&gt;You can build a relay on a VPS yourself. That also means maintaining the public VPS, WireGuard, routes, firewall rules, keys, updates, and fault handling.&lt;/p&gt;
&lt;h3&gt;
  
  
  P2P without manual forwarding still receives direct traffic
&lt;/h3&gt;

&lt;p&gt;P2P VPNs that use NAT traversal establish direct connectivity by sending packets from both sides and creating NAT and firewall state that accepts the peer’s return packets.&lt;/p&gt;

&lt;p&gt;In other words, &lt;strong&gt;the path for packets from outside to inside is established dynamically.&lt;/strong&gt; This differs from a permanent forwarding rule accepting unsolicited traffic, and the permitted source range and lifetime depend on the NAT, firewall, and traversal method. But “no manual port forwarding” does not mean the home endpoint never receives direct external traffic.&lt;/p&gt;

&lt;p&gt;It also does not make traffic invisible. While a direct P2P connection is in use, an observer on the travel network may see the home-side public address and UDP port, along with timing and volume. Returning packets expose that endpoint as their source.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Not responding to an unauthorized scan does not hide the IP address and port used in a live connection.&lt;/strong&gt; Observing them does not decrypt the tunnel or establish that any arbitrary third party can connect.&lt;/p&gt;

&lt;p&gt;NAT traversal reduces manual forwarding work; it does not remove the packet-processing implementation or its maintenance needs. An on-path attacker and an unrelated off-path attacker have different opportunities, but a dynamically established path is not a substitute for vulnerability management.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Direct P2P and conventional direct home VPNs also share the exposure of a home-side endpoint address.&lt;/strong&gt; That address can become a clue for investigating other exposed router functions and attempting entry through a separate exploitable service. Keeping the home-side address out of the direct VPN path reduces unnecessary disclosure, including in a threat environment where residential connections are abused as proxies.&lt;/p&gt;

&lt;p&gt;Some products relay traffic when direct connectivity fails. In that case, the relay is the destination visible on the travel network. Check the actual connection path rather than treating every P2P session as identical.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpnb7mpiqld4k92fm0t36.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpnb7mpiqld4k92fm0t36.png" alt="Direct paths and Cloud Hub connections" width="800" height="550"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Top arrow: direct traffic path. Bottom arrows: connection initiation. Tunnel data flows both ways.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  HomeGrid VPN connects outward from home to a Cloud Hub
&lt;/h2&gt;

&lt;p&gt;HomeGrid VPN uses a hub-and-spoke design. Both Home and Remote connect to a Cloud Hub.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Remote ──→ Cloud Hub ←── Home
        Both initiate toward the hub

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Home uses outbound communication, so the design does not ordinarily require IPv4 port forwarding, IPv6 inbound rules, or DDNS at home. Remote does not need a direct path to Home’s public IPv4 or global IPv6 address.&lt;/p&gt;

&lt;p&gt;The VPN destination visible from travel Wi-Fi is the Cloud Hub. &lt;strong&gt;You do not need to present your home public address as the direct destination of that VPN connection.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This reduces the need for a direct home entry point and the occasions on which the VPN exposes your home endpoint. It does not automatically close unrelated management services already exposed on your router; review those separately.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Decision point&lt;/th&gt;
&lt;th&gt;Direct home WireGuard&lt;/th&gt;
&lt;th&gt;HomeGrid VPN&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Home-side connectivity&lt;/td&gt;
&lt;td&gt;Inbound IPv4 and forwarding, or IPv6 reachability and inbound rules&lt;/td&gt;
&lt;td&gt;Outbound connection to the Cloud Hub&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Router and ISP checks&lt;/td&gt;
&lt;td&gt;Public address, upstream NAT, inbound rules&lt;/td&gt;
&lt;td&gt;Reachability to the hub&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Remote connectivity&lt;/td&gt;
&lt;td&gt;A path to Home’s endpoint&lt;/td&gt;
&lt;td&gt;A path to the Cloud Hub&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;LAN authorization&lt;/td&gt;
&lt;td&gt;Design and maintain peer mappings and firewall rules&lt;/td&gt;
&lt;td&gt;Default-deny LAN ACL with per-device destination-LAN permissions&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;WireGuard server maintenance&lt;/td&gt;
&lt;td&gt;Maintain the server and related software yourself&lt;/td&gt;
&lt;td&gt;No self-managed WireGuard server maintenance when repurposing a PC as an appliance&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;When Home is the internet exit, the traffic path is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Remote → Cloud Hub → Home → Residential ISP → Internet

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The destination sees Home’s public exit address, as it would for ordinary internet access through that home connection. &lt;strong&gt;The Cloud Hub carries the VPN path; it is not the internet exit when Home is selected as the exit.&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Turn an old PC into an appliance with a USB drive
&lt;/h3&gt;

&lt;p&gt;Download the ISO image from the dashboard and write it to a USB drive with a suitable tool. Boot the old PC from that drive, let automatic installation run, and enter the activation token obtained from the dashboard. Connect it to the LAN to use it as the Home-side device.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You do not need to build and maintain a WireGuard server yourself with this appliance approach.&lt;/strong&gt; It reduces both inbound configuration work and self-managed VPN server maintenance. Updating the household router remains normal network maintenance regardless of which VPN you use.&lt;/p&gt;

&lt;h3&gt;
  
  
  VPN connectivity does not automatically grant LAN access
&lt;/h3&gt;

&lt;p&gt;HomeGrid VPN’s LAN ACL manages destination-LAN permissions for each connecting device. The initial state is &lt;strong&gt;default deny&lt;/strong&gt; : connecting to the VPN alone does not grant access to destination LANs. Newly registered devices and newly added LANs require explicit authorization.&lt;/p&gt;

&lt;p&gt;For example, allow your work PC to reach the work LAN while leaving a family phone unauthorized. &lt;strong&gt;VPN authentication and LAN authorization are separate decisions.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Permissions cover a destination subnet. Adding a PC or NAS within an already authorized LAN does not require adding each host to the VPN’s policy. This keeps everyday use simple while unrelated LANs remain closed. It is not a claim of per-host or per-port filtering.&lt;/p&gt;

&lt;p&gt;An authorized device can still become a stepping stone within its reachable networks. Service authentication, host firewalls, and segmentation remain useful for those boundaries.&lt;/p&gt;

&lt;p&gt;See &lt;a href="https://www.homegrid-vpn.com/guides/en/lan-acl/" rel="noopener noreferrer"&gt;Set where each device can go with LAN ACL&lt;/a&gt; for the configuration steps.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6v4axk0himk1gp6a168z.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6v4axk0himk1gp6a168z.png" alt="Default-deny LAN authorization" width="800" height="475"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;A VPN connection alone does not authorize LAN access. Permissions apply to the destination subnet.&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Use the combined connection and authorization model at low cost
&lt;/h3&gt;

&lt;p&gt;Authentication-linked access control is an established networking approach. You can implement it in a DIY WireGuard environment, but you also need to maintain the mapping between devices and permissions as devices and keys change.&lt;/p&gt;

&lt;p&gt;HomeGrid VPN offers outward Home connections and default-deny LAN ACLs as a low-cost option for homes and small environments. The value here is the combination of the connection and authorization functions needed for this use case, rather than replacing every feature of an enterprise firewall. Check &lt;a href="https://www.homegrid-vpn.com/en/" rel="noopener noreferrer"&gt;the official HomeGrid VPN site&lt;/a&gt; for current plans and conditions.&lt;/p&gt;

&lt;p&gt;If you use a family member’s connection, obtain the subscriber’s consent and check the ISP’s contract terms.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose the architecture after checking reachability
&lt;/h2&gt;

&lt;p&gt;Start with these checks:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Test from a genuinely external connection.&lt;/li&gt;
&lt;li&gt;Generate tunnel traffic and check the handshake.&lt;/li&gt;
&lt;li&gt;If it fails, inspect the connection type, Endpoint, and UDP forwarding.&lt;/li&gt;
&lt;li&gt;Observe packet arrival before moving to host firewall and peer settings.&lt;/li&gt;
&lt;li&gt;If it succeeds, inspect LAN routes and the return path.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A direct connection may be straightforward to repair. But making an endpoint reachable and maintaining it are different jobs. IPv6 leaves remote-network requirements in place, while direct P2P still exposes the home-side endpoint on the live traffic path.&lt;/p&gt;

&lt;p&gt;If you want to use travel Wi-Fi, reduce unnecessary disclosure of your home endpoint, avoid adding a direct home entry point, and authorize only the LAN subnets each device needs, &lt;strong&gt;HomeGrid VPN’s outward connection from Home is an option worth considering.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Before deployment, open &lt;strong&gt;HomeGrid VPN Connectivity Check&lt;/strong&gt; from the &lt;a href="https://www.homegrid-vpn.com/en/" rel="noopener noreferrer"&gt;HomeGrid VPN homepage&lt;/a&gt; to test whether your home network can communicate with HomeGrid VPN. Run it from the home network where you plan to install the device.&lt;/p&gt;

&lt;p&gt;For the routing and exit model, see &lt;a href="https://www.homegrid-vpn.com/blog/en/how-homegrid-vpn-works/" rel="noopener noreferrer"&gt;What is HomeGrid VPN? Using your home connection as a VPN exit&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Originally published at &lt;a href="https://www.homegrid-vpn.com/blog/en/wireguard-outside-troubleshooting/" rel="noopener noreferrer"&gt;https://www.homegrid-vpn.com/blog/en/wireguard-outside-troubleshooting/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>infrastructure</category>
      <category>linux</category>
      <category>networking</category>
    </item>
    <item>
      <title>WireGuard Silence Is Not Enough: An Outbound-Only VPN Design</title>
      <dc:creator>HomeGrid VPN</dc:creator>
      <pubDate>Thu, 29 Oct 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/homegrid_vpn/wireguard-silence-is-not-enough-an-outbound-only-vpn-design-456b</link>
      <guid>https://dev.to/homegrid_vpn/wireguard-silence-is-not-enough-an-outbound-only-vpn-design-456b</guid>
      <description>&lt;p&gt;WireGuard’s silence toward unauthenticated traffic does not hide its endpoint IP from observers along a connection’s path. An outbound-only relay design can preserve remote access without a public VPN listener at the home or office. The relay still needs an operator, and endpoint security, access control and availability remain part of the design.&lt;/p&gt;

&lt;p&gt;When vulnerabilities in VPN appliances make the news, replacing VPNs with SASE or ZTNA often becomes part of the discussion. Yet removing a VPN does not remove the need for remote access.&lt;/p&gt;

&lt;p&gt;People still need internal business systems while working from home, servers while traveling, home NAS devices and development environments, and connections between cloud and office networks. Losing those paths can interrupt everyday work.&lt;/p&gt;

&lt;p&gt;SASE and ZTNA can be useful options, but they do not automatically replace every kind of network traffic. A reverse-proxy ZTNA architecture may keep an application server private while exposing a proxy or authentication endpoint. Other ZTNA designs provide access to private networks. The category name alone does not establish what is publicly reachable.&lt;/p&gt;

&lt;p&gt;The practical question is &lt;strong&gt;how much public exposure can be removed while retaining a protected communication path&lt;/strong&gt; , and who will operate the infrastructure that remains.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. A VPN that appears hidden from users
&lt;/h2&gt;

&lt;p&gt;Some enterprise VPN clients first authenticate with a vendor service and then let the user select a destination. Employees do not need to know the gateway’s IP address or port; connection settings are centrally managed.&lt;/p&gt;

&lt;p&gt;That experience can make the VPN server appear hidden. But &lt;strong&gt;hiding an endpoint in a client interface is different from making the gateway unreachable from the internet&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;If the authenticated client subsequently connects directly to an organization’s appliance, that appliance may still accept incoming internet traffic. An attacker looking for exposed gateways does not have to sign in through the employee’s application.&lt;/p&gt;

&lt;p&gt;The system and client also need enough endpoint information to establish the connection, even if they do not display it. A hidden field in an application does not change the network’s exposure.&lt;/p&gt;

&lt;p&gt;Vendors that instead use outbound connections from a site to a relay should be assessed as a different architecture, rather than grouped with directly exposed gateways.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Residential public IPs are scanned too
&lt;/h2&gt;

&lt;p&gt;Internet-wide service discovery is not limited to large companies and data centers. Residential connections and small offices can also be included.&lt;/p&gt;

&lt;p&gt;The Shadowserver Foundation collects information about exposed services, while Censys continually scans the public IPv4 address space. These are legitimate security research activities; attackers can also use scanning techniques.&lt;/p&gt;

&lt;p&gt;The scanner does not need to know a subscriber’s name in advance. Searching address ranges can encounter a household or small business without anyone having explicitly shared its address.&lt;/p&gt;

&lt;p&gt;A router’s port-forwarding rule can deliver incoming packets to a VPN server on the LAN. Firewalls, CGNAT and other upstream conditions can prevent that reachability. Receiving a scan is not, by itself, evidence of compromise.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Keeping a public IPv4 address out of a contact list does not exclude it from automated discovery.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Doesn’t WireGuard ignore port scans?
&lt;/h2&gt;

&lt;p&gt;WireGuard is designed to remain silent toward unauthenticated traffic. It does not establish a normal handshake with someone lacking the required cryptographic credentials. A generic UDP scan therefore has difficulty confirming that WireGuard is running.&lt;/p&gt;

&lt;p&gt;This is a useful security property. UDP scan results also should not be interpreted as the same simple open/closed test commonly associated with TCP.&lt;/p&gt;

&lt;p&gt;But &lt;strong&gt;scan resistance does not make endpoint information secret&lt;/strong&gt;. If an IP address and UDP port are learned through another route, an observer can know where a client connects.&lt;/p&gt;

&lt;p&gt;That knowledge does not defeat WireGuard authentication. Endpoint discovery and unauthorized access are different problems, and discovering a destination is not equivalent to exploiting it.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Encrypted traffic still has an outer destination
&lt;/h2&gt;

&lt;p&gt;Suppose employees connect from home to a WireGuard server at the office. WireGuard encrypts the traffic inside the tunnel, but packets still need an outer destination IP and UDP port to reach the VPN endpoint.&lt;/p&gt;

&lt;p&gt;The same is true when the employee uses hotel Wi-Fi, a cafe network, a mobile hotspot, a travel router or a phone’s tethering connection.&lt;/p&gt;

&lt;p&gt;A network administrator or another observer with access to the relevant path may see endpoint IPs, ports and timing without reading the traffic inside the VPN tunnel. The observer’s actual access matters: being nearby does not automatically reveal all of that information.&lt;/p&gt;

&lt;h3&gt;
  
  
  Wi-Fi frames can be recorded for later analysis
&lt;/h3&gt;

&lt;p&gt;Wi-Fi transmits over radio. A third party within reception range may be able to collect and store wireless frames.&lt;/p&gt;

&lt;p&gt;Proper WPA2 or WPA3 encryption prevents an arbitrary recording from immediately revealing the IP packets inside it. Later decryption depends on the mode, captured handshake material, available keys and any relevant implementation weaknesses.&lt;/p&gt;

&lt;p&gt;In WPA2-Personal, a recording containing the necessary handshake material may be decrypted later if the required password or key information becomes available. WPA3-Personal uses SAE and provides a different protection: knowing the network password and recording the four-way handshake alone is not enough to decrypt an earlier connection. Per-connection key material would be needed. See the &lt;a href="https://www.wireshark.org/docs/wsug_html_chunked/Ch80211Keys.html" rel="noopener noreferrer"&gt;Wireshark WLAN decryption documentation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;An AP operator, or an observer farther along the network path, can ordinarily inspect outer IP destinations without breaking wireless encryption at all.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An observer does not need to decrypt WireGuard to identify its outer endpoint.&lt;/strong&gt; A recording that could not be interpreted when collected might reveal more later if the necessary conditions change. This does not mean that every saved Wi-Fi capture will eventually be decrypted.&lt;/p&gt;

&lt;p&gt;Even successful Wi-Fi decryption does not decrypt the WireGuard payload. The two layers must be kept distinct: encrypted application traffic and destination metadata have different exposure boundaries.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwj16xs2xzhthdppvljdm.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwj16xs2xzhthdppvljdm.png" alt="Wi-Fi and VPN encryption protect different layers" width="800" height="488"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Wi-Fi encryption and WireGuard encryption are separate. Distinguish outer endpoint metadata visible to an AP or path observer from traffic inside the VPN tunnel.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;WireGuard’s silent response behavior does not conceal that metadata from an observer already able to inspect the outer IP packets.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Other metadata can suggest a VPN endpoint
&lt;/h2&gt;

&lt;p&gt;Traffic observation is only one possible source of endpoint information. Public DNS records, published configurations, certificates associated with management interfaces and historical service observations can supply clues.&lt;/p&gt;

&lt;p&gt;A public hostname used in a VPN configuration may resolve to its endpoint. A management interface’s certificate can also leave hostname information in Certificate Transparency logs, which may help relate services.&lt;/p&gt;

&lt;p&gt;These are conditional examples. &lt;strong&gt;WireGuard itself is not a TLS VPN&lt;/strong&gt; , and its UDP listener does not publish a TLS certificate. An ASN or WHOIS record alone does not identify a running WireGuard service.&lt;/p&gt;

&lt;p&gt;A completely silent listener without related public endpoint information can be difficult for an arbitrary internet observer to identify. The narrower point is that silence does not guarantee endpoint secrecy across every other information source.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. A public VPN also needs continuing operations
&lt;/h2&gt;

&lt;p&gt;None of this means that WireGuard is inherently unsafe. A properly configured deployment can provide a protected VPN path.&lt;/p&gt;

&lt;p&gt;Running a public server also brings work beyond encryption: OS and WireGuard updates, key enrollment and revocation, firewall rules, routing maintenance, monitoring and incident recovery. More employees add more configuration and permission management.&lt;/p&gt;

&lt;p&gt;Access after connection matters too. If a VPN device can reach an entire internal LAN, compromise of a legitimately enrolled employee device can expose that permitted scope. That is an authorization and endpoint-security problem, rather than a failure of the tunnel’s cryptography.&lt;/p&gt;

&lt;p&gt;An organization that can sustain this work may reasonably run its own WireGuard infrastructure. A small team without dedicated network staff may find the continuing responsibility harder to carry.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Silent and unpublished are different properties
&lt;/h2&gt;

&lt;p&gt;An outbound-only hub-and-spoke design offers another way to use a VPN.&lt;/p&gt;

&lt;p&gt;In a direct deployment, a remote device connects to the office’s public endpoint. The office needs an internet-reachable VPN listener.&lt;/p&gt;

&lt;p&gt;With an outbound-only relay, the office gateway initiates a connection to a relay, and the remote device also connects to that relay. The office does not need a public VPN listener for this path.&lt;/p&gt;

&lt;p&gt;Here, &lt;strong&gt;outbound-only describes connection initiation&lt;/strong&gt;. Established tunnels carry requests and replies in both directions. The network must permit the outbound connection and its return traffic. IPv6 direct access is a separate case: avoiding IPv4 port forwarding does not remove the need to consider inbound firewall rules.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7tjxeozs38yz9j66ofuj.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7tjxeozs38yz9j66ofuj.png" alt="Connection initiation: direct versus outbound-only" width="800" height="638"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Arrows show tunnel initiation. Established VPNs carry requests and replies. The public relay listener and dependence on its operation remain.&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Property&lt;/th&gt;
&lt;th&gt;Direct office WireGuard&lt;/th&gt;
&lt;th&gt;Outbound-only relay design&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Inbound access at the site&lt;/td&gt;
&lt;td&gt;Required&lt;/td&gt;
&lt;td&gt;No public site listener required&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Remote device’s endpoint&lt;/td&gt;
&lt;td&gt;Office public endpoint&lt;/td&gt;
&lt;td&gt;Relay such as a Cloud Hub&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Public office VPN listener&lt;/td&gt;
&lt;td&gt;Present&lt;/td&gt;
&lt;td&gt;Not needed for this path&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Response to unauthenticated traffic&lt;/td&gt;
&lt;td&gt;Normally silent&lt;/td&gt;
&lt;td&gt;Depends on the relay protocol&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Office endpoint exposure&lt;/td&gt;
&lt;td&gt;Configuration or observation can reveal it&lt;/td&gt;
&lt;td&gt;Not the remote client’s direct endpoint&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Relay infrastructure&lt;/td&gt;
&lt;td&gt;Not needed for a direct path&lt;/td&gt;
&lt;td&gt;Required&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;When a remote connection is observed in the direct design, its destination can identify the office VPN endpoint. In the relay design, the directly observed destination is the relay. Learning that destination does not create a public VPN listener at the office.&lt;/p&gt;

&lt;p&gt;The relay itself remains reachable and needs appropriate protection. Consider information available to the relay operator and to observers of different network segments. This is not a promise that the office IP is hidden from everyone.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The goal is to avoid creating a public VPN listener at the site, rather than to guarantee that nobody can ever detect VPN use.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Can an AWS or VPS relay solve the problem?
&lt;/h2&gt;

&lt;p&gt;You can build this design yourself. For example, run a WireGuard relay on AWS or a VPS, and initiate the site connection toward it.&lt;/p&gt;

&lt;p&gt;That removes the site’s incoming listener, but it does not remove every public endpoint. The cloud relay becomes an internet-reachable service operated by your organization.&lt;/p&gt;

&lt;p&gt;A cloud provider’s address is not exempt from discovery. DNS records, certificates for associated services and other published information may suggest who operates an endpoint. Looking up an AWS IP alone does not reveal the customer, and an indiscriminate attacker does not need to identify the customer before probing an exposed service.&lt;/p&gt;

&lt;h3&gt;
  
  
  Automation reduces tasks, not every operational decision
&lt;/h3&gt;

&lt;p&gt;Infrastructure as Code tools such as Terraform can automate provisioning and networking. Updates, alerts, monitoring and some recovery actions can also be automated.&lt;/p&gt;

&lt;p&gt;However, a traffic spike still needs interpretation: legitimate business activity, a configuration error or an incident? An alert does not decide whether cutting access is proportionate to the potential business interruption.&lt;/p&gt;

&lt;p&gt;A critical vulnerability creates similar tradeoffs. Automatic updates can cause outages; someone still needs a policy for urgency, acceptable downtime, rollback and verification.&lt;/p&gt;

&lt;p&gt;Restoring a service also does not prove that a suspected compromise has been resolved. Automated recovery can restart a process without determining how it was accessed or whether credentials need revocation.&lt;/p&gt;

&lt;p&gt;Automating these judgments requires more classification rules, response policies, exception handling and validation. That automation itself becomes software that needs maintenance.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Provisioning a VPN automatically is different from safely operating a public VPN without human judgment.&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Small businesses have different staffing constraints
&lt;/h3&gt;

&lt;p&gt;A large organization may have dedicated infrastructure and security teams handling monitoring, vulnerabilities and recovery. A company with a handful or a few dozen employees may not be able to dedicate a person to VPN infrastructure alone.&lt;/p&gt;

&lt;p&gt;For someone combining this responsibility with their main job, night and weekend incidents can become a substantial burden. Investigating a compromise can also require expertise beyond ordinary maintenance.&lt;/p&gt;

&lt;p&gt;The useful decision is not only whether the team can build a working VPN today, but whether it can sustain its operation over the coming years.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. Who responds, and who compensates for an outage?
&lt;/h2&gt;

&lt;p&gt;Using an external VPN service raises reasonable questions: what happens if it is compromised, or unavailable when employees need it?&lt;/p&gt;

&lt;p&gt;Separate two responsibilities. Operational responsibility concerns who investigates, contains and restores the service. Contractual liability concerns which resulting business losses are compensated, and up to what amount. They are not interchangeable.&lt;/p&gt;

&lt;h3&gt;
  
  
  Major cloud contracts also limit liability
&lt;/h3&gt;

&lt;p&gt;Standard agreements from AWS, Microsoft Azure and Google Cloud include exclusions and limits, rather than promising full compensation for every business interruption. They commonly exclude categories such as indirect loss or lost profits, and use fees over a preceding period, often 12 months, in liability caps.&lt;/p&gt;

&lt;p&gt;The relevant examples are &lt;a href="https://aws.amazon.com/agreement/" rel="noopener noreferrer"&gt;AWS Customer Agreement section 9&lt;/a&gt;, &lt;a href="https://azure.microsoft.com/en-us/support/legal/subscription-agreement/" rel="noopener noreferrer"&gt;Microsoft Online Subscription Agreement section 6&lt;/a&gt; and &lt;a href="https://cloud.google.com/terms" rel="noopener noreferrer"&gt;Google Cloud Terms section 12&lt;/a&gt;, checked on October 29, 2026. The exact formula, exceptions and treatment of free services differ. Individual agreements, applicable law and SLA remedies also matter. These examples do not describe HomeGrid VPN’s own compensation terms.&lt;/p&gt;

&lt;p&gt;Companies still use external infrastructure because having a specialist operate a shared platform can be more practical than building, monitoring and maintaining everything themselves.&lt;/p&gt;

&lt;p&gt;With a self-managed public VPN, someone inside the company must investigate and decide how to restore it. With a service, the provider operates the shared infrastructure within the agreed scope.&lt;/p&gt;

&lt;p&gt;The customer still needs continuity planning, endpoint management, access permissions and backups. Evaluate the provider’s operating model, outage communications and recovery approach.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The operational value of a service does not depend on it assuming every financial consequence of an incident.&lt;/strong&gt; It can reduce the public infrastructure each customer has to operate independently.&lt;/p&gt;

&lt;h2&gt;
  
  
  10. How HomeGrid VPN combines WireGuard and outbound connections
&lt;/h2&gt;

&lt;p&gt;HomeGrid VPN uses WireGuard in a hub-and-spoke architecture. Remote devices and the office Grid each connect to a Cloud Hub.&lt;/p&gt;

&lt;p&gt;Because the Grid initiates toward the Cloud Hub, the office normally does not need IPv4 port forwarding, an IPv6 inbound rule or DDNS to establish this VPN path. Outbound access and return traffic must still be allowed. This can suit connections where CGNAT or other provider arrangements constrain inbound access.&lt;/p&gt;

&lt;p&gt;The remote device connects to the Cloud Hub, rather than directly to the office’s public IP. An observer on a hotel or home network can still observe VPN traffic, but the directly addressed endpoint is the Cloud Hub, not an office VPN listener.&lt;/p&gt;

&lt;h3&gt;
  
  
  Control access after connecting
&lt;/h3&gt;

&lt;p&gt;HomeGrid VPN’s LAN ACL controls &lt;strong&gt;registered device × destination LAN (subnet)&lt;/strong&gt; permissions and defaults to deny. Enrolling a device alone does not permit access to every LAN.&lt;/p&gt;

&lt;p&gt;You can allow a workstation to reach a necessary destination subnet instead of granting every device the same access. This is not server-by-server, port-by-port or application-level authorization within one subnet. OS firewalls, application permissions, authentication and endpoint management remain necessary.&lt;/p&gt;

&lt;p&gt;LAN ACL does not replace OS login or application authentication. Changes can take up to five minutes to apply; test both permitted and denied access after propagation. See the &lt;a href="https://www.homegrid-vpn.com/guides/en/lan-acl/" rel="noopener noreferrer"&gt;LAN ACL guide&lt;/a&gt; for the current behavior and settings.&lt;/p&gt;

&lt;h3&gt;
  
  
  The customer does not operate a separate public relay
&lt;/h3&gt;

&lt;p&gt;HomeGrid VPN’s provider operates the Cloud Hub, so each customer does not have to provision and maintain a separate public AWS or VPS relay.&lt;/p&gt;

&lt;p&gt;Monitoring, updating and recovery still exist as work for the provider. The customer continues to manage Grids, client devices, LAN ACL permissions and business-system access.&lt;/p&gt;

&lt;p&gt;The Cloud Hub is part of the VPN path, with corresponding operational trust and availability dependencies. A service does not make those dependencies disappear.&lt;/p&gt;

&lt;p&gt;The distinction is a change in who operates the public VPN infrastructure, rather than a promise that all operational responsibilities vanish.&lt;/p&gt;

&lt;h2&gt;
  
  
  11. Reconsider public entry points without abandoning VPNs
&lt;/h2&gt;

&lt;p&gt;WireGuard’s silence is valuable against unauthenticated probing. It does not guarantee that an endpoint remains unknown when people use it over real networks.&lt;/p&gt;

&lt;p&gt;Outer IP metadata can be observed independently of encrypted tunnel contents. Wireless frames may also be recorded, with later interpretation depending on the encryption mode and available keys. That is a reason to distinguish layers, not a reason to abandon WireGuard.&lt;/p&gt;

&lt;p&gt;An outbound-only relay can keep the site free of a public VPN listener. A self-managed AWS or VPS relay can provide that architecture, but leaves its monitoring, updates, incident handling and security decisions with the organization operating it.&lt;/p&gt;

&lt;p&gt;For a small business, sustaining that work can be harder than getting the first connection running. A managed relay shifts part of that recurring work to a service provider while leaving customer responsibilities and dependencies in place.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WireGuard limits responses to strangers. Outbound-only design avoids a public office VPN listener. Managed infrastructure changes who operates the public relay.&lt;/strong&gt; These are three different properties.&lt;/p&gt;

&lt;p&gt;The decision is what to expose to the internet, and who will operate it over time.&lt;/p&gt;

&lt;h3&gt;
  
  
  Private connectivity can also support everyday work
&lt;/h3&gt;

&lt;p&gt;A dependable path to internal systems can make remote work and access while traveling easier to introduce.&lt;/p&gt;

&lt;p&gt;For CI/CD, a GitHub Actions self-hosted runner that can reach a deployment target through the VPN can automate deployments without exposing that target’s SSH or management port publicly. Keep runner permissions narrow, protect deployment credentials and avoid giving untrusted jobs access to internal networks.&lt;/p&gt;

&lt;p&gt;Cloud VPCs can separate development and production environments, with access granted to the appropriate networks. Real isolation also needs VPC routing, Security Groups and firewalls; a VPN alone does not establish every boundary.&lt;/p&gt;

&lt;p&gt;Prearranged access to an alternate site can support business continuity during a disaster or connectivity outage. A VPN does not replicate business applications or data. Prepare alternate power and connectivity, authentication recovery, backups and restoration, and test the switchover before relying on it.&lt;/p&gt;

&lt;p&gt;Reviewing a VPN architecture can therefore reduce exposed management services while helping remote work, deployment workflows and continuity planning.&lt;/p&gt;

&lt;h3&gt;
  
  
  Related reading
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://www.homegrid-vpn.com/blog/en/soho-office-virtualization-bcp/" rel="noopener noreferrer"&gt;Network design for remote work&lt;/a&gt; — separate workstations, office dependencies and cloud services.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.homegrid-vpn.com/blog/en/github-actions-private-deploy/" rel="noopener noreferrer"&gt;GitHub Actions deployments to private servers&lt;/a&gt; — choose where the self-hosted runner executes and how it reaches its targets.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.homegrid-vpn.com/blog/en/wireguard-reduce-attack-surface/" rel="noopener noreferrer"&gt;Separate development and production VPCs&lt;/a&gt; — reduce public management exposure and apply network boundaries.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.homegrid-vpn.com/blog/en/small-business-cyber-obligations/" rel="noopener noreferrer"&gt;Small-business security and continuity&lt;/a&gt; — assign operational responsibility and prepare for an unavailable office.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  References
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.wireguard.com/protocol/" rel="noopener noreferrer"&gt;WireGuard: Protocol &amp;amp; Cryptography&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.wireshark.org/docs/wsug_html_chunked/Ch80211Keys.html" rel="noopener noreferrer"&gt;Wireshark: IEEE 802.11 WLAN Decryption Keys&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.censys.com/docs/internet-scanning" rel="noopener noreferrer"&gt;Censys: Internet Scanning&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.shadowserver.org/what-we-do/data-collection/" rel="noopener noreferrer"&gt;Shadowserver Foundation: Data Collection&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://aws.amazon.com/agreement/" rel="noopener noreferrer"&gt;AWS Customer Agreement&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://azure.microsoft.com/en-us/support/legal/subscription-agreement/" rel="noopener noreferrer"&gt;Microsoft Online Subscription Agreement&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cloud.google.com/terms" rel="noopener noreferrer"&gt;Google Cloud Terms of Service&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.homegrid-vpn.com/" rel="noopener noreferrer"&gt;HomeGrid VPN&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Originally published at &lt;a href="https://www.homegrid-vpn.com/blog/en/wireguard-silence-outbound-only/" rel="noopener noreferrer"&gt;https://www.homegrid-vpn.com/blog/en/wireguard-silence-outbound-only/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>linux</category>
      <category>networking</category>
      <category>devops</category>
    </item>
    <item>
      <title>Build a Raspberry Pi Home Intercom with WebRTC and HTTPS</title>
      <dc:creator>HomeGrid VPN</dc:creator>
      <pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/homegrid_vpn/build-a-raspberry-pi-home-intercom-with-webrtc-and-https-kjj</link>
      <guid>https://dev.to/homegrid_vpn/build-a-raspberry-pi-home-intercom-with-webrtc-and-https-kjj</guid>
      <description>&lt;p&gt;A Raspberry Pi with a Camera Module, USB microphone and USB speaker can become a remote video intercom for a family home. &lt;strong&gt;HomeGrid VPN provides the remote network path, WebRTC carries video and audio, and Caddy provides browser HTTPS&lt;/strong&gt; , without port forwarding or DDNS on the family home’s router.&lt;/p&gt;

&lt;p&gt;This is an &lt;strong&gt;architecture and implementation guide, not a tested, ready-to-run application&lt;/strong&gt;. The examples explain which files call which functions and where camera, microphone and speaker devices connect to WebRTC.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2mezxhnclleekd30h6a8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2mezxhnclleekd30h6a8.png" alt="VPN connections and separate signaling and media paths" width="800" height="812"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Top: outbound VPN connections. Bottom: separate signaling and media paths within that VPN.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The example assumes an existing HomeGrid VPN Grid at your home. &lt;strong&gt;Register the Raspberry Pi itself as a Linux Spoke rather than adding a Grid at the family home.&lt;/strong&gt; Your computer also connects to the VPN and reaches the Pi’s VPN IPv4 through the Cloud Hub. The Cloud Hub is not necessarily the internet exit.&lt;/p&gt;
&lt;h2&gt;
  
  
  Part 1: Build the Raspberry Pi and WebRTC intercom
&lt;/h2&gt;
&lt;h3&gt;
  
  
  1. Hardware and media directions
&lt;/h3&gt;

&lt;p&gt;At the family home, prepare a Raspberry Pi 4 or 5 (at least 1 GB RAM recommended), a compatible Camera Module, a USB microphone, a USB speaker or echo-cancelling USB speakerphone, Raspberry Pi OS with systemd and a network connection. On the viewer’s side, use a Windows PC, Mac or smartphone with a microphone and speaker. &lt;strong&gt;The viewer does not need a camera.&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Direction&lt;/th&gt;
&lt;th&gt;Input&lt;/th&gt;
&lt;th&gt;Output&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Family home → computer&lt;/td&gt;
&lt;td&gt;Pi Camera Module&lt;/td&gt;
&lt;td&gt;Browser &lt;code&gt;&amp;lt;video&amp;gt;&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Family home → computer&lt;/td&gt;
&lt;td&gt;Pi USB microphone&lt;/td&gt;
&lt;td&gt;Browser &lt;code&gt;&amp;lt;audio&amp;gt;&lt;/code&gt; → computer speaker&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Computer → family home&lt;/td&gt;
&lt;td&gt;Browser microphone&lt;/td&gt;
&lt;td&gt;Pi USB speaker&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The Pi’s microphone can pick up its speaker output and cause feedback. An echo-cancelling device at the family home helps address this.&lt;/p&gt;
&lt;h3&gt;
  
  
  2. Check the camera and audio devices
&lt;/h3&gt;

&lt;p&gt;Update the OS, check camera detection and capture a still image:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;apt update
&lt;span class="nb"&gt;sudo &lt;/span&gt;apt full-upgrade &lt;span class="nt"&gt;-y&lt;/span&gt;
rpicam-hello &lt;span class="nt"&gt;--list-cameras&lt;/span&gt;
rpicam-still &lt;span class="nt"&gt;-n&lt;/span&gt; &lt;span class="nt"&gt;-o&lt;/span&gt; test.jpg
&lt;span class="nb"&gt;sudo &lt;/span&gt;apt &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nt"&gt;-y&lt;/span&gt; alsa-utils
arecord &lt;span class="nt"&gt;-l&lt;/span&gt;
aplay &lt;span class="nt"&gt;-l&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Record the capture and playback device identifiers for selection in &lt;code&gt;audio.py&lt;/code&gt;. Choose device numbers and sample rates for your actual hardware.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Add a Linux Spoke from the Dashboard
&lt;/h3&gt;

&lt;p&gt;In the HomeGrid VPN Dashboard, in the &lt;strong&gt;“Add a Spoke”&lt;/strong&gt; panel, click &lt;strong&gt;“+ Add Spoke (QR Code)”&lt;/strong&gt;, enter a device name and select &lt;strong&gt;“Linux (command)”&lt;/strong&gt;. The Linux installation command dialog opens.&lt;/p&gt;

&lt;p&gt;Click &lt;strong&gt;Copy&lt;/strong&gt; for the lower &lt;strong&gt;split (&lt;code&gt;--split&lt;/code&gt;)&lt;/strong&gt; command and run it in the Pi’s terminal. Copy the generated command rather than recreating or modifying it manually. Split mode sends VPN destinations through the tunnel while ordinary internet traffic uses the family home’s ISP. Do not publish the command containing your token.&lt;/p&gt;

&lt;p&gt;For the current installation workflow, see the &lt;a href="https://www.homegrid-vpn.com/guides/en/add-linux-device/" rel="noopener noreferrer"&gt;official guide to adding a Linux device&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;After setup, check the Pi’s VPN IPv4:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ip &lt;span class="nt"&gt;-4&lt;/span&gt; addr show dev wg0

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The address &lt;code&gt;100.64.0.5&lt;/code&gt; below is &lt;strong&gt;only an example&lt;/strong&gt;. Replace it with the assigned address. No inbound rule is required on the family home’s router for the outbound VPN connection. Spokes in the same tenant can communicate through the Cloud Hub. Verify on your actual setup that the selected WebRTC ICE candidate pair uses the VPN addresses and that the device firewalls allow the required UDP traffic.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Files on the Raspberry Pi
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;All these files live on the Raspberry Pi.&lt;/strong&gt; The server delivers &lt;code&gt;static/index.html&lt;/code&gt; and &lt;code&gt;static/client.js&lt;/code&gt;, but &lt;strong&gt;the HTML and JavaScript run in the computer or smartphone browser&lt;/strong&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/opt/webrtc-intercom/
├── app.py # aiohttp server and HTTP routing
├── webrtc.py # aiortc sessions and Offer/Answer
├── camera.py # Picamera2 → VideoStreamTrack
├── audio.py # USB audio and AudioStreamTrack
├── config.py # VPN IPv4 and audio device configuration
├── requirements.txt # Python dependencies
└── static/
    ├── index.html # Browser intercom page
    ├── client.js # Browser WebRTC and button handlers
    └── style.css

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The Pi uses &lt;code&gt;picamera2&lt;/code&gt; for the camera, &lt;code&gt;aiortc&lt;/code&gt; for WebRTC, &lt;code&gt;aiohttp&lt;/code&gt; for HTTP, &lt;code&gt;av&lt;/code&gt; / PyAV for media frames, &lt;code&gt;sounddevice&lt;/code&gt; / ALSA for USB audio, and &lt;code&gt;numpy&lt;/code&gt; for data processing. Install Picamera2 with attention to compatibility between Raspberry Pi OS Python packages and libcamera.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The web service and WebRTC backend are not separate Python processes.&lt;/strong&gt; &lt;code&gt;app.py&lt;/code&gt; starts one HTTP server and calls &lt;code&gt;webrtc.py&lt;/code&gt; in the same process when a request reaches &lt;code&gt;/offer&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. How the browser loads the intercom page
&lt;/h3&gt;

&lt;p&gt;An example development URL is &lt;code&gt;http://100.64.0.5:8080/&lt;/code&gt;. Browser microphone access normally will not work at this HTTP address; Part 2 adds HTTPS.&lt;/p&gt;

&lt;p&gt;On the Pi, &lt;code&gt;app.py&lt;/code&gt; defines the aiohttp routes:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;app&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;router&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;add_get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;/&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;index&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;app&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;router&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;add_post&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;/offer&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;handle_offer&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;app&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;router&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;add_static&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;/static/&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;BASE_DIR&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;static&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;GET /&lt;/code&gt; returns &lt;code&gt;static/index.html&lt;/code&gt;; &lt;code&gt;GET /static/client.js&lt;/code&gt; returns the JavaScript. The HTML provides media output elements:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;video&lt;/span&gt; &lt;span class="na"&gt;id=&lt;/span&gt;&lt;span class="s"&gt;"remoteVideo"&lt;/span&gt; &lt;span class="na"&gt;autoplay&lt;/span&gt; &lt;span class="na"&gt;playsinline&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/video&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;audio&lt;/span&gt; &lt;span class="na"&gt;id=&lt;/span&gt;&lt;span class="s"&gt;"remoteAudio"&lt;/span&gt; &lt;span class="na"&gt;autoplay&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/audio&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;button&lt;/span&gt; &lt;span class="na"&gt;id=&lt;/span&gt;&lt;span class="s"&gt;"startCall"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;Start call&lt;span class="nt"&gt;&amp;lt;/button&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;button&lt;/span&gt; &lt;span class="na"&gt;id=&lt;/span&gt;&lt;span class="s"&gt;"stopCall"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;End call&lt;span class="nt"&gt;&amp;lt;/button&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;script &lt;/span&gt;&lt;span class="na"&gt;src=&lt;/span&gt;&lt;span class="s"&gt;"/static/client.js"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/script&amp;gt;&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;client.js&lt;/code&gt; retrieves &lt;code&gt;remoteVideo&lt;/code&gt; and &lt;code&gt;remoteAudio&lt;/code&gt; using &lt;code&gt;document.getElementById()&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. client.js: connect the microphone and received media
&lt;/h3&gt;

&lt;p&gt;Bind the Start call button to &lt;code&gt;startCall()&lt;/code&gt; with &lt;code&gt;addEventListener("click", startCall)&lt;/code&gt;. The sequence is:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Request &lt;strong&gt;only the computer’s microphone&lt;/strong&gt; with &lt;code&gt;getUserMedia({audio: true, video: false})&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Call &lt;code&gt;createConnection()&lt;/code&gt; to create &lt;code&gt;new RTCPeerConnection({iceServers: []})&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Register the microphone for sending with &lt;code&gt;pc.addTrack(micTrack, stream)&lt;/code&gt;; audio uses bidirectional &lt;code&gt;sendrecv&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Request the Pi’s video with &lt;code&gt;pc.addTransceiver("video", {direction: "recvonly"})&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Register &lt;code&gt;pc.ontrack&lt;/code&gt; to display and play received media.&lt;/li&gt;
&lt;li&gt;Create the connection description with &lt;code&gt;pc.createOffer()&lt;/code&gt; and &lt;code&gt;setLocalDescription()&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Send &lt;code&gt;POST /offer&lt;/code&gt; to the same HTTP server.&lt;/li&gt;
&lt;li&gt;Apply the HTTP response with &lt;code&gt;pc.setRemoteDescription(answer)&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Start WebRTC media once ICE establishes a working path.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The main device bindings look like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;remoteVideo&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;document&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;getElementById&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;remoteVideo&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;remoteAudio&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;document&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;getElementById&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;remoteAudio&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;stream&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nb"&gt;navigator&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;mediaDevices&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;getUserMedia&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="na"&gt;audio&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;video&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;pc&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;RTCPeerConnection&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;iceServers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[]&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="nx"&gt;stream&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;getAudioTracks&lt;/span&gt;&lt;span class="p"&gt;().&lt;/span&gt;&lt;span class="nf"&gt;forEach&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;t&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nx"&gt;pc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;addTrack&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;t&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;stream&lt;/span&gt;&lt;span class="p"&gt;));&lt;/span&gt;
&lt;span class="nx"&gt;pc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;addTransceiver&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;video&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;direction&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;recvonly&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;

&lt;span class="nx"&gt;pc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;ontrack&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;event&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;event&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;track&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;kind&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;video&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nx"&gt;remoteVideo&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;srcObject&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;MediaStream&lt;/span&gt;&lt;span class="p"&gt;([&lt;/span&gt;&lt;span class="nx"&gt;event&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;track&lt;/span&gt;&lt;span class="p"&gt;]);&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;else&lt;/span&gt; &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;event&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;track&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;kind&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;audio&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nx"&gt;remoteAudio&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;srcObject&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;MediaStream&lt;/span&gt;&lt;span class="p"&gt;([&lt;/span&gt;&lt;span class="nx"&gt;event&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;track&lt;/span&gt;&lt;span class="p"&gt;]);&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;};&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;&lt;code&gt;pc.addTrack()&lt;/code&gt; registers local media for sending; &lt;code&gt;pc.ontrack&lt;/code&gt; receives media from the other peer.&lt;/strong&gt; Browser audio normally plays through the speaker or headphones selected by the OS. Autoplay restrictions may require a &lt;code&gt;play()&lt;/code&gt; call tied to the user’s call-start interaction.&lt;/p&gt;

&lt;h3&gt;
  
  
  7. From POST /offer to the Pi’s WebRTC session
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;client.js&lt;/code&gt; creates an Offer and sends its SDP and type as JSON through &lt;code&gt;fetch("/offer", {method: "POST", ...})&lt;/code&gt;. The implementation must wait for ICE gathering to complete or implement an exchange of additional candidates.&lt;/p&gt;

&lt;p&gt;Because &lt;code&gt;app.py&lt;/code&gt; registers &lt;code&gt;app.router.add_post("/offer", handle_offer)&lt;/code&gt;, a POST invokes &lt;code&gt;handle_offer()&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="c1"&gt;# app.py: bridge HTTP and WebRTC
&lt;/span&gt;&lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;handle_offer&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;request&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="n"&gt;data&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;request&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
    &lt;span class="n"&gt;offer&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;RTCSessionDescription&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;sdp&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;sdp&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt; &lt;span class="nb"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;type&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;])&lt;/span&gt;
    &lt;span class="n"&gt;answer&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;create_session&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;offer&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="c1"&gt;# Call webrtc.py
&lt;/span&gt;    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;web&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json_response&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;sdp&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;answer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;sdp&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;type&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;answer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nb"&gt;type&lt;/span&gt;&lt;span class="p"&gt;})&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;RTCSessionDescription&lt;/code&gt; comes from aiortc. &lt;code&gt;create_session&lt;/code&gt; is an ordinary Python function imported with &lt;code&gt;from webrtc import create_session&lt;/code&gt;. &lt;strong&gt;There is no second POST to a separate WebRTC web server.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Next, &lt;code&gt;webrtc.py&lt;/code&gt; creates an aiortc peer connection, registers the Pi camera and USB microphone, and attaches a handler that sends received browser audio to the speaker:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="c1"&gt;# Essential wiring in webrtc.py, not a complete implementation
&lt;/span&gt;&lt;span class="n"&gt;pc&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;RTCPeerConnection&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;span class="n"&gt;pc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;addTrack&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;PiCameraTrack&lt;/span&gt;&lt;span class="p"&gt;())&lt;/span&gt; &lt;span class="c1"&gt;# Pi camera → computer
&lt;/span&gt;&lt;span class="n"&gt;pc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;addTrack&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;MicrophoneTrack&lt;/span&gt;&lt;span class="p"&gt;())&lt;/span&gt; &lt;span class="c1"&gt;# Pi microphone → computer
&lt;/span&gt;
&lt;span class="nd"&gt;@pc.on&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;track&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;on_track&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;track&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;track&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;kind&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;audio&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="c1"&gt;# Pass track to the playback worker in audio.py
&lt;/span&gt;        &lt;span class="bp"&gt;...&lt;/span&gt;

&lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;pc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;setRemoteDescription&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;offer&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;answer&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;pc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;createAnswer&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;pc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;setLocalDescription&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;answer&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="c1"&gt;# Return pc.localDescription to app.py
&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;PiCameraTrack&lt;/code&gt; is a &lt;code&gt;VideoStreamTrack&lt;/code&gt; in &lt;code&gt;camera.py&lt;/code&gt; that converts Picamera2 images into PyAV &lt;code&gt;VideoFrame&lt;/code&gt; objects. &lt;code&gt;MicrophoneTrack&lt;/code&gt; is an &lt;code&gt;AudioStreamTrack&lt;/code&gt; in &lt;code&gt;audio.py&lt;/code&gt; that returns USB microphone samples as &lt;code&gt;AudioFrame&lt;/code&gt; objects.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The USB speaker is not a sending track&lt;/strong&gt; , so do not add it with &lt;code&gt;addTrack()&lt;/code&gt;. Pass computer microphone audio received by the Pi’s &lt;code&gt;pc.on("track")&lt;/code&gt; to the playback worker in &lt;code&gt;audio.py&lt;/code&gt;. Convert channel counts, sample rates and frame formats for the device, and keep synchronous device I/O from blocking the event loop.&lt;/p&gt;

&lt;h3&gt;
  
  
  8. Media after the Answer
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;app.py&lt;/code&gt; returns the Answer in the HTTP response and the browser calls &lt;code&gt;pc.setRemoteDescription(answer)&lt;/code&gt;. Once ICE establishes connectivity:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Media&lt;/th&gt;
&lt;th&gt;Pi side&lt;/th&gt;
&lt;th&gt;Browser side&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Video&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;camera.py&lt;/code&gt; → &lt;code&gt;pc.addTrack()&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;pc.ontrack&lt;/code&gt; → &lt;code&gt;&amp;lt;video&amp;gt;&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Family home’s voice&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;audio.py&lt;/code&gt; → &lt;code&gt;pc.addTrack()&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;pc.ontrack&lt;/code&gt; → &lt;code&gt;&amp;lt;audio&amp;gt;&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Viewer’s voice&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;pc.on("track")&lt;/code&gt; → USB speaker&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;getUserMedia()&lt;/code&gt; → &lt;code&gt;pc.addTrack()&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;&lt;code&gt;/offer&lt;/code&gt; is an HTTP round trip for connection setup, not an API that continuously receives video and audio POSTs.&lt;/strong&gt; In this design, WebRTC media uses separate UDP traffic. Keep the Pi’s peer connection alive after returning the Answer, close it at the end of the call or on disconnection, and release camera and audio resources.&lt;/p&gt;

&lt;p&gt;For an initial implementation, connect video and bidirectional audio together when Start call is pressed. Adding audio later to an existing video-only session can require renegotiation when tracks are added.&lt;/p&gt;

&lt;h2&gt;
  
  
  Part 2: Add Caddy HTTPS for browser microphone access
&lt;/h2&gt;

&lt;h3&gt;
  
  
  9. Why HTTP inside the VPN is insufficient
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;navigator.mediaDevices.getUserMedia()&lt;/code&gt; generally requires a &lt;strong&gt;secure context such as HTTPS or localhost&lt;/strong&gt;. Opening &lt;code&gt;http://100.64.0.5:8080/&lt;/code&gt; over the VPN does not make it a secure browser context.&lt;/p&gt;

&lt;p&gt;Place Caddy in front of the Python server:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Browser → &lt;strong&gt;HTTPS :443&lt;/strong&gt; → Caddy listening on the VPN IP.&lt;/li&gt;
&lt;li&gt;Caddy → &lt;strong&gt;HTTP 127.0.0.1:8080&lt;/strong&gt; → &lt;code&gt;app.py&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Caddy forwards &lt;code&gt;GET /&lt;/code&gt;, static files and &lt;code&gt;POST /offer&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;WebRTC media travels as &lt;strong&gt;UDP between aiortc and the browser&lt;/strong&gt; , rather than through Caddy.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  10. Bind Python to localhost and Caddy to the VPN IP
&lt;/h3&gt;

&lt;p&gt;Change &lt;code&gt;app.py&lt;/code&gt; to listen on localhost:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;web&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;run_app&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;app&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;host&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;127.0.0.1&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;port&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;8080&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Install Caddy on the Pi:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;apt update
&lt;span class="nb"&gt;sudo &lt;/span&gt;apt &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nt"&gt;-y&lt;/span&gt; caddy
&lt;span class="nb"&gt;sudo &lt;/span&gt;nano /etc/caddy/Caddyfile

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For the example VPN IPv4 &lt;code&gt;100.64.0.5&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight go"&gt;&lt;code&gt;&lt;span class="n"&gt;https&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt;&lt;span class="c"&gt;//100.64.0.5 {&lt;/span&gt;
    &lt;span class="n"&gt;bind&lt;/span&gt; &lt;span class="m"&gt;100.64.0.5&lt;/span&gt;
    &lt;span class="n"&gt;tls&lt;/span&gt; &lt;span class="n"&gt;internal&lt;/span&gt;
    &lt;span class="n"&gt;reverse_proxy&lt;/span&gt; &lt;span class="m"&gt;127.0.0.1&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt;&lt;span class="m"&gt;8080&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;tls internal&lt;/code&gt; issues a server certificate through Caddy’s internal CA. Validate and apply the configuration:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;caddy validate &lt;span class="nt"&gt;--config&lt;/span&gt; /etc/caddy/Caddyfile
&lt;span class="nb"&gt;sudo &lt;/span&gt;systemctl restart caddy
systemctl status caddy

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Caddy may fail to bind if the VPN address is not available during startup. Test service ordering and restart behavior.&lt;/p&gt;

&lt;h3&gt;
  
  
  11. Retrieve Caddy’s public root CA certificate
&lt;/h3&gt;

&lt;p&gt;Mac and Windows do not initially trust the internal CA. With the usual systemd installation, the Pi’s Caddy root certificate is normally at:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/var/lib/caddy/.local/share/caddy/pki/authorities/local/root.crt

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;root.crt&lt;/code&gt; is a PEM-encoded public X.509 certificate. &lt;strong&gt;Never distribute the private key, &lt;code&gt;root.key&lt;/code&gt;.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Copy only the public certificate to a location readable by your Pi user, then retrieve it on the Mac or Windows computer using SCP or another suitable method. Compare its fingerprint through a separate trusted channel and confirm it belongs to the Caddy instance you manage before installing trust.&lt;/p&gt;

&lt;h3&gt;
  
  
  12. Trust the CA in macOS Keychain
&lt;/h3&gt;

&lt;p&gt;Import &lt;code&gt;root.crt&lt;/code&gt; into the System keychain using Keychain Access and configure its trust. An administrator terminal example is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;security add-trusted-cert &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="nt"&gt;-r&lt;/span&gt; trustRoot &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-k&lt;/span&gt; /Library/Keychains/System.keychain &lt;span class="se"&gt;\&lt;/span&gt;
  ~/Downloads/caddy-root.crt

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Replace the file path with its actual location. Safari and Chrome normally use macOS certificate trust settings; Firefox and other browsers may require additional configuration.&lt;/p&gt;

&lt;h3&gt;
  
  
  13. Trust the CA in Windows
&lt;/h3&gt;

&lt;p&gt;Copy &lt;code&gt;root.crt&lt;/code&gt; to Windows. Choose Install Certificate, select the option to place all certificates in a specified store, and choose &lt;strong&gt;Trusted Root Certification Authorities&lt;/strong&gt;. To install it for the current user with PowerShell:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Import-Certificate&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-FilePath&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;".\caddy-root.crt"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-CertStoreLocation&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Cert:\CurrentUser\Root&lt;/span&gt;&lt;span class="w"&gt;

&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Installing a root CA means &lt;strong&gt;trusting the certificates issued by that CA&lt;/strong&gt; , not just one intercom page. Do not install a root CA whose origin you cannot verify.&lt;/p&gt;

&lt;h3&gt;
  
  
  14. Open HTTPS and verify WebRTC
&lt;/h3&gt;

&lt;p&gt;While connected to HomeGrid VPN, open the following on the Mac or Windows computer:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;https://100.64.0.5/&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Caddy forwards &lt;code&gt;GET /&lt;/code&gt; and &lt;code&gt;GET /static/client.js&lt;/code&gt; to &lt;code&gt;app.py&lt;/code&gt;. Start call asks for browser microphone permission, creates an Offer and sends it to &lt;strong&gt;&lt;code&gt;POST /offer&lt;/code&gt; on the same HTTPS origin&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Caddy forwards the request to &lt;code&gt;handle_offer()&lt;/code&gt; and &lt;code&gt;webrtc.py&lt;/code&gt; returns the Answer. Because &lt;code&gt;fetch("/offer")&lt;/code&gt; uses a relative URL, &lt;strong&gt;adding Caddy does not require changing this URL&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Verify that the selected ICE candidate pair uses the VPN addresses, that Pi video and microphone audio play on the computer, and that the viewer’s voice comes out of the Pi’s USB speaker.&lt;/p&gt;

&lt;h3&gt;
  
  
  15. Startup, access control and family privacy
&lt;/h3&gt;

&lt;p&gt;Run &lt;code&gt;app.py&lt;/code&gt; with systemd and manage Caddy as its own systemd service. &lt;code&gt;webrtc.py&lt;/code&gt;, &lt;code&gt;camera.py&lt;/code&gt; and &lt;code&gt;audio.py&lt;/code&gt; remain modules in the same Python application, rather than independent web servers.&lt;/p&gt;

&lt;p&gt;Devices in the same tenant, including invited family members’ devices, have a VPN route to the Pi Spoke. LAN ACL controls access to LANs behind Grids or site gateways; it does not restrict access to the Pi’s own Spoke address. Restrict that access with the Pi’s firewall and application authentication. Without authentication, any device that can reach &lt;code&gt;/offer&lt;/code&gt; may invoke it. &lt;strong&gt;VPN-only listening and certificate trust do not replace user authentication.&lt;/strong&gt; Authenticate and restrict callers, control concurrent sessions, release tracks on shutdown, handle failures and address audio feedback. Also, &lt;code&gt;iceServers: []&lt;/code&gt; alone does not confine WebRTC UDP to the VPN: inspect selected candidates and enforce firewall restrictions.&lt;/p&gt;

&lt;p&gt;Obtain the household’s consent before installing the camera or capturing audio and video. Agree on the camera’s field of view, call indicators and who may view it. If using a family member’s internet connection, obtain the subscriber’s consent and check the ISP contract conditions.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the components fit together
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;HomeGrid VPN:&lt;/strong&gt; registers the Pi as a Linux Spoke and provides a VPN path without port forwarding at the family home.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;app.py&lt;/code&gt; / aiohttp:&lt;/strong&gt; serves the page and receives &lt;code&gt;POST /offer&lt;/code&gt; on that same web server.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;webrtc.py&lt;/code&gt; / aiortc:&lt;/strong&gt; sends camera and microphone tracks with &lt;code&gt;addTrack()&lt;/code&gt; and receives the viewer’s audio with &lt;code&gt;on("track")&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;client.js&lt;/code&gt;:&lt;/strong&gt; sends the computer microphone with &lt;code&gt;addTrack()&lt;/code&gt; and attaches received tracks to HTML using &lt;code&gt;ontrack&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Caddy:&lt;/strong&gt; provides HTTPS and an internal CA whose public root certificate is trusted on the viewing computer.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The initial Offer/Answer HTTP exchange prepares the connection. Established WebRTC media then takes a separate path. Understanding that boundary helps when extending the intercom.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.homegrid-vpn.com/guides/en/add-linux-device/" rel="noopener noreferrer"&gt;HomeGrid VPN Linux device guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.raspberrypi.com/documentation/computers/camera_software.html" rel="noopener noreferrer"&gt;Raspberry Pi Camera Software&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/raspberrypi/picamera2" rel="noopener noreferrer"&gt;Picamera2&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://aiortc.readthedocs.io/" rel="noopener noreferrer"&gt;aiortc documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/aiortc/aiortc/tree/main/examples/server" rel="noopener noreferrer"&gt;aiortc server example&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia" rel="noopener noreferrer"&gt;MDN: getUserMedia&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://caddyserver.com/docs/caddyfile/directives/tls" rel="noopener noreferrer"&gt;Caddy TLS&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Originally published at &lt;a href="https://www.homegrid-vpn.com/blog/en/raspberry-pi-webrtc-intercom/" rel="noopener noreferrer"&gt;https://www.homegrid-vpn.com/blog/en/raspberry-pi-webrtc-intercom/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>raspberrypi</category>
      <category>python</category>
      <category>linux</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Push to GitHub, deploy to a private home server with HomeGrid VPN</title>
      <dc:creator>HomeGrid VPN</dc:creator>
      <pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/homegrid_vpn/push-to-github-deploy-to-a-private-home-server-with-homegrid-vpn-31j3</link>
      <guid>https://dev.to/homegrid_vpn/push-to-github-deploy-to-a-private-home-server-with-homegrid-vpn-31j3</guid>
      <description>&lt;p&gt;GitHub Actions can deploy to a private home server when a self-hosted runner has a network path to it. A runner inside the home LAN can do this without a VPN; a runner elsewhere can use an always-connected VPN path instead of joining a VPN for every job. HomeGrid VPN supports the latter design with a Spoke runner, a Cloud Hub, and a Grid connected to the destination LAN.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a hosted runner cannot reach your home LAN directly
&lt;/h2&gt;

&lt;p&gt;You push an application to GitHub and want the home server to update automatically. But pointing a standard GitHub-hosted runner at a private address such as 192.168.x.x does not create a route into your LAN. A private cloud server has the same problem unless you provide connectivity to its network. A VPS with a public address and publicly accessible SSH is a different configuration and can accept connections over that public route.&lt;/p&gt;

&lt;p&gt;With a reachable public IPv4 address, you could forward an SSH port through the home router. Dynamic addresses also require a way to track changes, such as DDNS. However, CGNAT and DS-Lite can prevent users from configuring the upstream port mapping. MAP-E services may restrict which IPv4 ports are available. Double NAT or a building’s upstream router can add another barrier.&lt;/p&gt;

&lt;p&gt;IPv6 direct access is another option, but it requires a global IPv6 address at home, IPv6 connectivity at the runner, and appropriate inbound rules on the router and server. Removing NAT port forwarding does not remove inbound firewall design.&lt;/p&gt;

&lt;p&gt;For deployment, the essential requirement is more specific: &lt;strong&gt;the runner must be able to reach the deployment target&lt;/strong&gt;. The server does not need to accept SSH connections from the whole Internet.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with the simplest option: a runner inside the LAN
&lt;/h2&gt;

&lt;p&gt;A self-hosted runner executes GitHub Actions jobs on a machine you manage. It initiates outbound connections to GitHub to receive jobs. You do not need to forward a home router port so GitHub can initiate an inbound connection. The runner still needs outbound access to the required GitHub services. &lt;a href="https://docs.github.com/en/actions/reference/runners/self-hosted-runners#communication" rel="noopener noreferrer"&gt;GitHub’s runner communication requirements&lt;/a&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Developer pushes code to GitHub
                   ↑
         Runner initiates connection
                   │
         Runner inside the home LAN
                   │ SSH
                   ↓
         Private application server

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If the runner and server share a LAN, a VPN may be unnecessary. You could also install the runner on the deployment target and update the application locally.&lt;/p&gt;

&lt;p&gt;A separate runner becomes useful when you want to keep build jobs away from production, place the runner on a VPS, or deploy to several locations. You then need a network path from that runner to each target.&lt;/p&gt;

&lt;h2&gt;
  
  
  The runner and deployment target are separate roles
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Component&lt;/th&gt;
&lt;th&gt;Responsibility&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Runner&lt;/td&gt;
&lt;td&gt;Execute jobs, tests, builds, transfers, and deployment commands&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Deployment target&lt;/td&gt;
&lt;td&gt;Run the application or service&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Network path&lt;/td&gt;
&lt;td&gt;Carry traffic between the runner and target&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A VPS-hosted runner can deploy to a home server, and a home-hosted runner can deploy to another site. A VPN supplies connectivity; SSH authentication and the application update procedure remain separate responsibilities.&lt;/p&gt;

&lt;h2&gt;
  
  
  Join a VPN per job, or keep the runner connected
&lt;/h2&gt;

&lt;p&gt;One approach is to connect a GitHub-hosted runner to a VPN at the start of each job and disconnect afterward. Depending on the VPN and identity system, short-lived credentials or OIDC may be available. That design adds connection setup, authentication, readiness checks, and routing checks to the job.&lt;/p&gt;

&lt;p&gt;With a self-hosted runner, you can instead maintain the VPN connection as a host service:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Host setup: register with VPN → connect → maintain connection
Each job: test → build → deploy over the existing private route

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The workflow uses connectivity that already exists. You still need to monitor the host, VPN connection, and routes. An always-connected design does not guarantee uninterrupted connectivity.&lt;/p&gt;

&lt;h2&gt;
  
  
  Connect the runner as a HomeGrid VPN Spoke
&lt;/h2&gt;

&lt;p&gt;Register the runner’s Linux host as a HomeGrid VPN Spoke, and provide a Grid connected to the home LAN. Both the runner and the home Grid initiate outbound VPN connections to the Cloud Hub. Once connected and authorized, the runner can reach the private server through that path.&lt;/p&gt;

&lt;p&gt;&lt;br&gt;
&lt;/p&gt;
Deployment route from a connected runner to a private server
&lt;br&gt;
A Spoke runner receives a GitHub Actions job and deploys through the Cloud Hub and home Grid to a private server. Both the runner and home Grid initiate outbound VPN connections to the Cloud Hub. The hub is a relay; no Internet exit is shown.&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
GitHub ActionsPush to main&lt;br&gt;
&lt;br&gt;
Job&lt;br&gt;
&lt;br&gt;
Outbound HTTPS&lt;br&gt;
&lt;br&gt;
Self-hosted RunnerSpoke · Always connected&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
Cloud HubVPN relay&lt;br&gt;
&lt;br&gt;
HOME LAN&lt;br&gt;
&lt;br&gt;
Home Grid&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
Private ServerSSH Deploy&lt;br&gt;
&lt;br&gt;
VPN route&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;em&gt;Jobs execute on the runner and deployment follows the green route. The runner initiates the connection to GitHub. VPN connections start as Runner → Cloud Hub ← Home Grid. The Cloud Hub is a relay, and no Internet exit is shown.&lt;/em&gt;

&lt;p&gt;The green deployment arrows show traffic after VPN connectivity is established. They do not mean that the Cloud Hub initiates a new inbound connection to your home’s public address.&lt;/p&gt;

&lt;p&gt;This design does not depend on home-side IPv4 port forwarding, a static public IP, DDNS, or direct inbound IPv6 access. It can work on CGNAT, MAP-E, or DS-Lite connections when the required outbound traffic to the Cloud Hub is permitted. The connection type alone does not guarantee success; ISP and local network restrictions still matter.&lt;/p&gt;

&lt;p&gt;See the &lt;a href="https://www.homegrid-vpn.com/guides/en/add-linux-device/" rel="noopener noreferrer"&gt;Linux Spoke setup guide&lt;/a&gt; for registration. &lt;strong&gt;Use &lt;code&gt;--split&lt;/code&gt; as the normal choice for a deployment runner.&lt;/strong&gt; Traffic for the configured LANs and tenant ranges uses the VPN, while GitHub HTTPS connections and package or container-image downloads use the runner’s own Internet connection. Check route refresh requirements when destination LANs change.&lt;/p&gt;

&lt;p&gt;The Linux Spoke defaults to a full tunnel. In that mode, Internet traffic also travels through the Cloud Hub and home connection. A runner hosted elsewhere can lose its connection to GitHub when the home connection or Grid fails, and downloads delivered back to that runner consume home upload bandwidth. Choose a full tunnel when you intentionally want the runner’s Internet traffic to exit through home. With &lt;code&gt;--split&lt;/code&gt;, deployment to a home server still depends on the home side being available.&lt;/p&gt;
&lt;h2&gt;
  
  
  Remove VPN enrollment from the workflow, not credential management
&lt;/h2&gt;

&lt;p&gt;Once the host maintains its VPN connection, a normal deployment job does not need a HomeGrid VPN enrollment token or a command to establish the tunnel each time.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Credential or configuration&lt;/th&gt;
&lt;th&gt;Where it remains relevant&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;VPN enrollment token&lt;/td&gt;
&lt;td&gt;Initial registration, rather than every deployment job&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;VPN keys and configuration&lt;/td&gt;
&lt;td&gt;Protected on the connected runner host&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GitHub runner credentials&lt;/td&gt;
&lt;td&gt;Runner registration and ongoing operation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SSH private key and trusted host keys&lt;/td&gt;
&lt;td&gt;Authentication to the deployment target&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Registry or cloud credentials&lt;/td&gt;
&lt;td&gt;Fetching or publishing artifacts, if required&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;VPN enrollment moves from job execution into host administration. If a runner is compromised or retired, revoke its GitHub registration, VPN device registration, and deployment credentials as appropriate.&lt;/p&gt;
&lt;h2&gt;
  
  
  Set up routing and SSH before registering the runner
&lt;/h2&gt;
&lt;h3&gt;
  
  
  1. Prepare a Linux host
&lt;/h3&gt;

&lt;p&gt;Use a home machine or a VPS with the resources your jobs require. Permit outbound access to GitHub and the Cloud Hub. Create a dedicated, unprivileged user for job execution. Keeping the runner separate from the application server makes the maintenance and permission boundaries easier to manage.&lt;/p&gt;
&lt;h3&gt;
  
  
  2. Register the host as a Spoke
&lt;/h3&gt;

&lt;p&gt;Register the Linux host with HomeGrid VPN using &lt;code&gt;--split&lt;/code&gt;. Confirm that the home Grid is online and that the destination LAN is registered. The application server behind the Grid does not itself need to be registered as a Spoke.&lt;/p&gt;
&lt;h3&gt;
  
  
  3. Grant access through LAN ACL
&lt;/h3&gt;

&lt;p&gt;Allow the runner device to access the destination LAN. Confirm connectivity after the change takes effect, and leave unrelated LANs unapproved. Use server firewalls for narrower host and port restrictions.&lt;/p&gt;
&lt;h3&gt;
  
  
  4. Configure SSH public-key authentication
&lt;/h3&gt;

&lt;p&gt;Create a deployment account such as &lt;code&gt;deploy&lt;/code&gt; on the target. Configure its authorized public key and prepare the private key, SSH configuration, and &lt;code&gt;known_hosts&lt;/code&gt; for the user that will run the runner service. A successful SSH session from an administrator’s account does not prove that the service user can connect.&lt;/p&gt;

&lt;p&gt;Verify the target’s host-key fingerprint through a trusted channel, such as its console. Accepting unverified &lt;code&gt;ssh-keyscan&lt;/code&gt; output alone does not authenticate the first connection.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ssh &lt;span class="nt"&gt;-o&lt;/span&gt; &lt;span class="nv"&gt;BatchMode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nb"&gt;yes&lt;/span&gt; &lt;span class="nt"&gt;-o&lt;/span&gt; &lt;span class="nv"&gt;StrictHostKeyChecking&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nb"&gt;yes &lt;/span&gt;deploy@192.168.1.100 &lt;span class="s1"&gt;'true'&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The private IP above is illustrative; replace it with your target. A static public IP is unnecessary, but keep the LAN address stable with a DHCP reservation or equivalent arrangement.&lt;/p&gt;

&lt;p&gt;Prepare &lt;code&gt;/usr/local/bin/deploy-app&lt;/code&gt; on the target. Implement artifact selection and retrieval, application updates, health checks, and recovery as appropriate, then test the procedure manually. Grant only the required permissions rather than unrestricted sudo access.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Register and run the GitHub runner as a service
&lt;/h3&gt;

&lt;p&gt;In the private repository, open &lt;strong&gt;Settings → Actions → Runners → New self-hosted runner&lt;/strong&gt;. Choose Linux and the host’s architecture. Follow GitHub’s displayed download, verification, and registration commands under the dedicated user, and add the custom label &lt;code&gt;homegrid-deploy&lt;/code&gt;. &lt;a href="https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/add-runners" rel="noopener noreferrer"&gt;GitHub’s runner registration instructions&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;After registration, Linux hosts using systemd can install the service from the runner directory. Replace &lt;code&gt;runner&lt;/code&gt; with your dedicated account:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo&lt;/span&gt; ./svc.sh &lt;span class="nb"&gt;install &lt;/span&gt;runner
&lt;span class="nb"&gt;sudo&lt;/span&gt; ./svc.sh start
&lt;span class="nb"&gt;sudo&lt;/span&gt; ./svc.sh status

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Stop any manually started runner process first. Confirm that GitHub shows the runner as available and that both the VPN and runner recover after a host reboot. A job must fail safely if it starts before connectivity returns. &lt;a href="https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/configure-the-application" rel="noopener noreferrer"&gt;GitHub’s service configuration instructions&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Run the deployment on a push to main
&lt;/h2&gt;

&lt;p&gt;Place this minimal workflow in &lt;code&gt;.github/workflows/deploy.yml&lt;/code&gt;. It assumes a trusted private repository, a protected main branch, and a Linux runner with the &lt;code&gt;homegrid-deploy&lt;/code&gt; label.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Deploy private server&lt;/span&gt;

&lt;span class="na"&gt;on&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;push&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;branches&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="pi"&gt;[&lt;/span&gt;&lt;span class="nv"&gt;main&lt;/span&gt;&lt;span class="pi"&gt;]&lt;/span&gt;

&lt;span class="na"&gt;permissions&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;contents&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;read&lt;/span&gt;

&lt;span class="na"&gt;concurrency&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;group&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;private-server-deploy&lt;/span&gt;
  &lt;span class="na"&gt;cancel-in-progress&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt;

&lt;span class="na"&gt;jobs&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;deploy&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;runs-on&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="pi"&gt;[&lt;/span&gt;&lt;span class="nv"&gt;self-hosted&lt;/span&gt;&lt;span class="pi"&gt;,&lt;/span&gt; &lt;span class="nv"&gt;linux&lt;/span&gt;&lt;span class="pi"&gt;,&lt;/span&gt; &lt;span class="nv"&gt;homegrid-deploy&lt;/span&gt;&lt;span class="pi"&gt;]&lt;/span&gt;
    &lt;span class="na"&gt;timeout-minutes&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="m"&gt;15&lt;/span&gt;
    &lt;span class="na"&gt;steps&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Deploy over private network&lt;/span&gt;
        &lt;span class="na"&gt;run&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="pi"&gt;&amp;gt;-&lt;/span&gt;
          &lt;span class="s"&gt;ssh -o BatchMode=yes -o StrictHostKeyChecking=yes&lt;/span&gt;
          &lt;span class="s"&gt;-o ConnectTimeout=15&lt;/span&gt;
          &lt;span class="s"&gt;deploy@192.168.1.100 '/usr/local/bin/deploy-app'&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The runner label selects where the job runs; it is not an authorization boundary. If you use environment approvals, configure the environment’s protection rules and specify the matching &lt;code&gt;environment&lt;/code&gt; in the job.&lt;/p&gt;

&lt;p&gt;This workflow invokes a target-side script, so it needs no source checkout on the runner. &lt;code&gt;contents: read&lt;/code&gt; limits the GitHub token’s permissions; it does not supply SSH credentials. If the runner also tests or builds the application, add checkout, tests, build, and artifact transfer before deployment. Pin any actions you introduce to reviewed full commit SHAs.&lt;/p&gt;

&lt;p&gt;The minimal example does not pass the pushed commit to the target. To guarantee that a push deploys its corresponding artifact, identify the artifact by commit SHA or image digest, pass that reference to the deployment procedure, and validate it before applying the update.&lt;/p&gt;

&lt;p&gt;Design deployment to stop if the route or authentication is unavailable. Implement health checks and rollback for your application. Serializing workflow runs does not, by itself, guarantee release order; reject stale artifacts when that matters.&lt;/p&gt;

&lt;h2&gt;
  
  
  Extend the design to VPS and private cloud networks
&lt;/h2&gt;

&lt;p&gt;The same connectivity model can serve a VPS whose management SSH is not publicly accessible, an AWS VPC, an Azure VNet, or another site’s development network.&lt;/p&gt;

&lt;p&gt;HomeGrid VPN can connect additional LANs using a Linux gateway inside the destination network. Give the runner a route and permission to that LAN, then deploy to the server behind the gateway.&lt;/p&gt;

&lt;p&gt;Registering a network does not guarantee access to every subnet. Check gateway-to-server reachability, registered address ranges, security groups, network ACLs, OS firewalls, and any necessary return routing. Overlapping address ranges require deliberate network design. &lt;a href="https://www.homegrid-vpn.com/blog/en/connect-lans-with-acl/" rel="noopener noreferrer"&gt;Connecting home, office, and cloud LANs&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The common layer is private connectivity. Operating systems, deployment procedures, application settings, and cloud IAM still need their own configuration.&lt;/p&gt;

&lt;h2&gt;
  
  
  Subnet ACLs, host firewalls, and SSH serve different purposes
&lt;/h2&gt;

&lt;p&gt;HomeGrid VPN LAN ACL controls which destination LANs or subnets a registered runner device may access. &lt;strong&gt;It does not provide per-server or per-port rules.&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;What it controls&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;LAN ACL&lt;/td&gt;
&lt;td&gt;Destination LANs or subnets available to the runner&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Host firewall and related controls&lt;/td&gt;
&lt;td&gt;Traffic and ports accepted by a server&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SSH authentication&lt;/td&gt;
&lt;td&gt;User and key allowed to log in&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;OS permissions&lt;/td&gt;
&lt;td&gt;Files and commands the deployment account may change or execute&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Use a dedicated deployment account, restrict its privileges, and keep SSH host-key verification enabled. Base source-address firewall rules on what the destination actually observes: a gateway or NAT may change the source address, so do not assume the runner’s VPN address always appears unchanged.&lt;/p&gt;

&lt;p&gt;If a target shares a subnet with personal computers or a NAS, account for the breadth of that LAN permission. A separate deployment subnet or VLAN may help when stronger separation is required. &lt;a href="https://www.homegrid-vpn.com/guides/en/lan-acl/" rel="noopener noreferrer"&gt;LAN ACL configuration&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Treat the connected runner as part of your trust boundary
&lt;/h2&gt;

&lt;p&gt;A job can use the runner’s network access and permissions. Untrusted code on a connected runner can become a foothold for lateral movement into accessible networks. Prefer private repositories, but do not treat repository privacy as sufficient protection.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Do not execute untrusted pull requests or unreviewed code on the deployment runner.&lt;/li&gt;
&lt;li&gt;Restrict eligible repositories and use runner-group controls where available.&lt;/li&gt;
&lt;li&gt;Protect main and workflow changes; use environment approvals when appropriate.&lt;/li&gt;
&lt;li&gt;Update the OS, runner, and dependencies, and manage files and processes left by jobs.&lt;/li&gt;
&lt;li&gt;Avoid running jobs as root, and restrict powerful interfaces such as the Docker socket.&lt;/li&gt;
&lt;li&gt;Protect VPN keys and deployment credentials; keep them out of logs and artifacts.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A compromised persistent runner can retain changes that affect later jobs. GitHub documents these risks in its &lt;a href="https://docs.github.com/en/actions/reference/security/secure-use#hardening-for-self-hosted-runners" rel="noopener noreferrer"&gt;self-hosted runner security guidance&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;You can separate build and deployment environments so the connected runner only distributes approved artifacts. Where stronger execution isolation is needed, consider runners whose execution environments are destroyed after each job.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Cloud Hub is not the Internet exit
&lt;/h2&gt;

&lt;p&gt;The Cloud Hub is a component on the VPN route between the runner and home. Traffic passing through it does not imply that Internet traffic exits through its public IP.&lt;/p&gt;

&lt;p&gt;For deployment, the private application server is the destination. There is no need to use the home connection as an Internet exit.&lt;/p&gt;

&lt;p&gt;If you separately select a full tunnel with a home exit, Internet-bound traffic follows the Cloud Hub, home Grid, and residential ISP before reaching the Internet. In that configuration, the exit is the home connection. With &lt;code&gt;--split&lt;/code&gt;, the configured private routes and ordinary Internet traffic follow separate paths.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cloud Hub ≠ Internet Exit.&lt;/strong&gt; Check LAN routing, access permissions, and Internet egress separately. The Cloud Hub remains part of the system’s operational and trust boundaries; target authentication and authorization are still required.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make deployment depend on a private route, not a public SSH port
&lt;/h2&gt;

&lt;p&gt;A runner inside the destination LAN can deploy without a VPN. A runner elsewhere needs a suitable route, which an always-connected VPN can provide.&lt;/p&gt;

&lt;p&gt;With HomeGrid VPN, a Spoke runner uses its existing connection to reach approved home or site LANs. That removes home-side port forwarding, a static public IP, DDNS, and per-job VPN enrollment from this deployment design, subject to outbound connectivity requirements.&lt;/p&gt;

&lt;p&gt;Start by choosing where the runner lives, which subnets it may reach, and which changes its SSH account may make. Validate manual deployment and recovery before enabling automatic execution. Then a push to GitHub can trigger an update to a private home server without making its management port public.&lt;/p&gt;

&lt;p&gt;Originally published at &lt;a href="https://www.homegrid-vpn.com/blog/en/github-actions-private-deploy/" rel="noopener noreferrer"&gt;https://www.homegrid-vpn.com/blog/en/github-actions-private-deploy/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>deployment</category>
      <category>devops</category>
      <category>githubactions</category>
      <category>networking</category>
    </item>
    <item>
      <title>Data Breach Prevention for Small Businesses: Reduce Exposed Entry Points</title>
      <dc:creator>HomeGrid VPN</dc:creator>
      <pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/homegrid_vpn/data-breach-prevention-for-small-businesses-reduce-exposed-entry-points-3oam</link>
      <guid>https://dev.to/homegrid_vpn/data-breach-prevention-for-small-businesses-reduce-exposed-entry-points-3oam</guid>
      <description>&lt;p&gt;Getting every data breach safeguard right from the start is difficult. Even so, small offices and home offices (SOHO), sole proprietors, and companies with just a few people can begin by reviewing entry points reachable from outside and the permissions attached to them—even without dedicated IT staff.&lt;/p&gt;

&lt;p&gt;This article focuses on three steps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Identify exposed entry points used for maintenance and close unnecessary direct exposure.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Allow a contractor’s device to reach only the LANs needed for the job.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Remove its VPN access from the dashboard when the work is finished.&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep necessary work running while reducing one entry point an attacker could target. Here is the reasoning behind that approach, followed by a configuration and workflow using HomeGrid VPN.&lt;/p&gt;

&lt;h2&gt;
  
  
  Are entry points opened for work still in place?
&lt;/h2&gt;

&lt;p&gt;You may need to reach a NAS in your home office from elsewhere, or let a contractor maintain a small company’s business server. A VPN or remote desktop connection may have been set up for that purpose.&lt;/p&gt;

&lt;p&gt;A connection that was necessary at the time can remain after the working environment or the person responsible has changed. A former contractor’s account may still exist. A port opened for testing may never have been closed. Nobody may know who is responsible for updating an exposed device.&lt;/p&gt;

&lt;p&gt;In a small business, the owner or a single employee may handle these tasks alongside their everyday work. Before investing in more infrastructure, reviewing the connections you already have is a practical step toward preventing data breaches.&lt;/p&gt;

&lt;h2&gt;
  
  
  A VPN can also become an attacker’s way in
&lt;/h2&gt;

&lt;p&gt;A VPN provides access to a network from another location. Encrypting traffic, however, is a separate matter from preventing compromise of the device or account that accepts the connection.&lt;/p&gt;

&lt;p&gt;Japan’s National Police Agency describes intrusions through internet-exposed VPN equipment and similar devices, using unpatched vulnerabilities, leaked credentials, weak passwords, or configuration errors. Attackers may then steal data and threaten to publish it.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://www.npa.go.jp/bureau/cyber/countermeasures/ransom.html" rel="noopener noreferrer"&gt;National Police Agency: Ransomware prevention measures (Japanese)&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It would be a mistake to attribute every incident to a vulnerability in a VPN appliance.&lt;/p&gt;

&lt;p&gt;An investigation report published in December 2025 by ASKUL, a major Japanese office-supplies retailer, describes unauthorized use of an administrator account belonging to a contractor. Multi-factor authentication had not been applied to that account as an exception. The report found no evidence of intrusion exploiting vulnerabilities in VPN equipment.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://www.askullogist.co.jp/pdf/20251212.pdf" rel="noopener noreferrer"&gt;ASKUL: Investigation into the ransomware attack and measures to strengthen security (Japanese PDF)&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Even a large company can be breached through an account issued to a contractor. Although the scale and architecture differ, small businesses face the same questions: who can connect, what can they reach, and do permissions remain after they are no longer needed?&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with one maintenance connection
&lt;/h2&gt;

&lt;p&gt;Trying to examine the entire network at once can make it difficult to get started. Choose one connection used by an outside contractor first.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Question&lt;/th&gt;
&lt;th&gt;Example&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;What is the connection for?&lt;/td&gt;
&lt;td&gt;Maintaining a NAS or updating a business server&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who uses it?&lt;/td&gt;
&lt;td&gt;Your employee or a current maintenance contractor&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Where do they enter?&lt;/td&gt;
&lt;td&gt;A public VPN endpoint, SSH, or remote desktop&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What can they reach?&lt;/td&gt;
&lt;td&gt;Only the target LAN, or other LANs too?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How long is it needed?&lt;/td&gt;
&lt;td&gt;For this job only, or on an ongoing basis?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who manages it?&lt;/td&gt;
&lt;td&gt;Your business or the contractor who configured it?&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Ask the contractor who set it up about anything you cannot determine. Close unused entry points after checking the impact on your work.&lt;/p&gt;

&lt;p&gt;For connections you still need, review device updates, authentication, and user permissions. Then consider this question:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does this connection require your business to accept incoming connections from the internet?&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  From accepting connections to initiating them
&lt;/h2&gt;

&lt;p&gt;When a VPN appliance at your premises accepts outside connections, you manage its public exposure, updates, and authentication. This arrangement can be operated with appropriate maintenance.&lt;/p&gt;

&lt;p&gt;Another approach is for the device at your premises and the contractor’s PC to each connect to a relay in the cloud.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Connection model&lt;/th&gt;
&lt;th&gt;What the device at your premises does&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Accept connections at your premises&lt;/td&gt;
&lt;td&gt;Listen for connections from outside&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Connect to a relay&lt;/td&gt;
&lt;td&gt;Initiate an outbound connection&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The second model reduces the need to create a direct entry point at your premises, such as forwarding a port on your router for maintenance access.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Exposed entry points still exist: this design consolidates them at the relay instead of exposing them separately at your premises.&lt;/strong&gt; The relay’s operation and availability are also factors to evaluate when choosing a service.&lt;/p&gt;

&lt;p&gt;You can build this type of configuration yourself or use a managed service. Compare the scope of public exposure alongside the effort needed to configure, update, and manage access permissions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Terms used in HomeGrid VPN
&lt;/h2&gt;

&lt;p&gt;HomeGrid VPN uses a hub-and-spoke design in which sites and devices connect to a relay in the cloud. This article uses the following terms:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Term&lt;/th&gt;
&lt;th&gt;Meaning in this article&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Cloud Hub&lt;/td&gt;
&lt;td&gt;A cloud relay that connects VPN paths between sites and devices&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Grid&lt;/td&gt;
&lt;td&gt;A device at an office or another site that connects its LAN to the VPN&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Spoke&lt;/td&gt;
&lt;td&gt;A participant that connects to the Cloud Hub; in the maintenance workflow, the contractor’s invited and registered device&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;LAN ACL&lt;/td&gt;
&lt;td&gt;A feature that controls which destination LANs each registered device may access&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;hub-and-spoke&lt;/td&gt;
&lt;td&gt;A topology in which sites and devices connect to a central hub&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Because the Grid at your premises initiates an outbound connection to the Cloud Hub, the design generally does not require port forwarding on your router or a direct connection to your public IP address.&lt;/p&gt;

&lt;p&gt;Once established, the VPN path carries traffic in both directions. Initiating a connection outbound therefore still requires access controls for the destinations reachable through it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Manage exposed entry points and permissions from the dashboard
&lt;/h2&gt;

&lt;p&gt;HomeGrid VPN combines changes to the connection path with registration, permission assignment, and removal of contractors’ devices.&lt;/p&gt;

&lt;p&gt;The following table compares this workflow with an arrangement that exposes VPN appliances or similar endpoints and distributes connection settings individually. It does not mean that every other VPN product lacks comparable features.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Common issue with the existing setup&lt;/th&gt;
&lt;th&gt;Configuration or workflow with HomeGrid VPN&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Each site exposes and manages its own VPN endpoint&lt;/td&gt;
&lt;td&gt;Each site connects outbound to the Cloud Hub, consolidating exposed entry points&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SSH or remote desktop is exposed directly for maintenance&lt;/td&gt;
&lt;td&gt;Move access through the VPN and close direct exposure that is no longer needed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Connection settings are distributed individually&lt;/td&gt;
&lt;td&gt;Generate an invitation link in the dashboard and send it to the person doing the work&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A contractor can also reach unrelated LANs&lt;/td&gt;
&lt;td&gt;The contractor’s device cannot access any LAN until permitted; allow only the required connections in the device-by-destination-LAN matrix&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;VPN access remains after maintenance ends&lt;/td&gt;
&lt;td&gt;Delete the Spoke from the dashboard; once the change takes effect, its existing key can no longer reconnect&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;LAN ACL is a stateful control that specifies which devices may initiate connections to which LANs and also handles return traffic for permitted connections. &lt;strong&gt;LAN ACL is default deny.&lt;/strong&gt; Inviting a contractor’s device does not, by itself, give that device access to your business LAN.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Invite the device, then allow only the LANs it needs.&lt;/strong&gt; That is the order for preparing access.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make inviting, permitting, and removing part of the maintenance workflow
&lt;/h2&gt;

&lt;p&gt;Arrange access for a maintenance contractor as follows:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Generate an invitation link from the dashboard.&lt;/li&gt;
&lt;li&gt;Send it directly to the intended person using an organization-approved channel, such as Slack, Microsoft Teams, or email.&lt;/li&gt;
&lt;li&gt;Have that person register their device by following the invitation steps.&lt;/li&gt;
&lt;li&gt;In the dashboard’s LAN ACL, allow the contractor’s device to access the LAN containing the maintenance target.&lt;/li&gt;
&lt;li&gt;Confirm that the settings have taken effect, then check that the target is reachable and unpermitted LANs are not.&lt;/li&gt;
&lt;li&gt;Perform the maintenance work.&lt;/li&gt;
&lt;li&gt;When the work is finished, delete the maintenance Spoke from the dashboard.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;An invitation link is valid for 24 hours and can be used once. Anyone who opens a valid link can register their device, so send it individually to the intended person rather than posting it in a public channel.&lt;/p&gt;

&lt;p&gt;For issuing, sharing, and registering with an invitation, see &lt;a href="https://www.homegrid-vpn.com/guides/en/invite/" rel="noopener noreferrer"&gt;Invite someone else’s device&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;LAN ACL changes can take up to five minutes to apply. Confirm that the dashboard shows the settings as applied before testing access. Deleting a Spoke may also take a few minutes to take effect. Do not assume access is revoked immediately after clicking delete; confirm that the device can no longer connect after the change has applied.&lt;/p&gt;

&lt;p&gt;Once deletion takes effect, the Spoke’s existing key cannot reconnect. The administrator can revoke access without relying solely on the contractor to erase settings from their PC.&lt;/p&gt;

&lt;p&gt;For configuration steps, see &lt;a href="https://www.homegrid-vpn.com/guides/en/lan-acl/" rel="noopener noreferrer"&gt;Control which devices can reach each LAN with LAN ACL&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Define network access before managing every individual operation
&lt;/h2&gt;

&lt;p&gt;Development and maintenance involve investigation, configuration changes, data checks, and other operations that vary with the task. Designing and maintaining detailed authorization for every operation can be a significant burden for a small business.&lt;/p&gt;

&lt;p&gt;Start with the scope you can manage at the network level: allow the LANs needed for the work, block unrelated LANs, and remove access when the job is finished.&lt;/p&gt;

&lt;p&gt;LAN ACL does not replace permissions within business applications. You can still review network access without waiting until a detailed authorization design is complete.&lt;/p&gt;

&lt;h2&gt;
  
  
  Close old entry points after preparing the new connection
&lt;/h2&gt;

&lt;p&gt;Adding HomeGrid VPN leaves old VPN appliances and exposed SSH or remote desktop endpoints as potential attack targets if they remain accessible.&lt;/p&gt;

&lt;p&gt;Once you have confirmed that necessary work can be done through the new path, close the settings that are no longer needed:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Unused port forwarding rules&lt;/li&gt;
&lt;li&gt;Unnecessary inbound firewall rules&lt;/li&gt;
&lt;li&gt;Old VPN accounts&lt;/li&gt;
&lt;li&gt;Access permissions for contractors whose contracts have ended&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Even when you outsource the work, go beyond confirming that the connection works. Check &lt;strong&gt;what was closed and what remains accessible&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;For a closer look at direct home VPN exposure and residential connection conditions, see &lt;a href="https://www.homegrid-vpn.com/blog/en/home-vpn-direct-exposure/" rel="noopener noreferrer"&gt;Home VPN Not Connecting? Consider Your Home IP Before Forwarding Ports&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review the remaining safeguards and start with one connection
&lt;/h2&gt;

&lt;p&gt;Reviewing exposed entry points and permissions does not complete every data breach safeguard. Protecting the Cloud Hub and dashboard, updating devices and Grids, and configuring permissions at the destination remain necessary.&lt;/p&gt;

&lt;p&gt;Apply multi-factor authentication to the administrative and business accounts you retain wherever the service supports it. Check that contractor accounts have not been made exceptions. Address vulnerabilities in public web applications, and separately maintain isolated backups and verify restoration.&lt;/p&gt;

&lt;p&gt;With those responsibilities in mind, choose one upcoming maintenance task:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Whose device should reach which LAN, and for how long?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;To start with HomeGrid VPN, consider a configuration with one Grid connected to your office LAN and a registered device for the maintenance contractor. The Grid needs power and a connection that can reach the Cloud Hub. Check that authentication and firewall settings at the maintenance target also allow the intended access.&lt;/p&gt;

&lt;p&gt;There are three Grid installation methods: the install command on a supported Linux machine, Docker on a NAS or Linux machine or through Docker Desktop on a desktop PC, and the virtual appliance on a mini PC or VM. Choose according to the equipment and its operating requirements.&lt;/p&gt;

&lt;p&gt;Once you have checked the intended connection layout, follow &lt;a href="https://www.homegrid-vpn.com/guides/en/add-grid/" rel="noopener noreferrer"&gt;Add a Grid&lt;/a&gt; for registration. Before installation, review pricing and terms on the &lt;a href="https://www.homegrid-vpn.com/en/" rel="noopener noreferrer"&gt;HomeGrid VPN official website&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Installing the service alone does not complete your safeguards. &lt;strong&gt;Even so, SOHO users and small businesses without dedicated IT staff can start by reducing exposed entry points while keeping necessary work running.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Originally published at &lt;a href="https://www.homegrid-vpn.com/blog/en/small-business-reduce-exposure/" rel="noopener noreferrer"&gt;https://www.homegrid-vpn.com/blog/en/small-business-reduce-exposure/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>networking</category>
      <category>security</category>
    </item>
    <item>
      <title>Home VPN Not Connecting? Consider Your Home IP Before Forwarding Ports</title>
      <dc:creator>HomeGrid VPN</dc:creator>
      <pubDate>Sat, 03 Oct 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/homegrid_vpn/home-vpn-not-connecting-consider-your-home-ip-before-forwarding-ports-clk</link>
      <guid>https://dev.to/homegrid_vpn/home-vpn-not-connecting-consider-your-home-ip-before-forwarding-ports-clk</guid>
      <description>&lt;p&gt;A direct home VPN is technically feasible. Before making your home public IP an internet-facing VPN endpoint, consider the exposure you need to maintain and the destination information visible when you connect from elsewhere. A design in which your home connects outbound to a relay is another way to reach your home network or use its internet connection.&lt;/p&gt;

&lt;p&gt;You installed WireGuard at home. It works on your LAN, but connections from outside fail.&lt;/p&gt;

&lt;p&gt;Perhaps you are checking port forwarding and firewall rules. Those are reasonable things to investigate. Before you finish opening that path, though, there is a separate design question:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does your goal require a direct VPN endpoint at your home public IP?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This is not an argument that WireGuard is unsafe or that forwarding a port causes a compromise. It is a discussion about the security, maintenance, and privacy trade-offs of a new home VPN deployment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Residential connections can carry someone else’s traffic
&lt;/h2&gt;

&lt;p&gt;On January 28, 2026, Google Threat Intelligence Group (GTIG) announced action against the IPIDEA residential proxy network.&lt;/p&gt;

&lt;p&gt;Residential proxies route traffic through IP addresses assigned by ISPs to homes and other consumer connections. Google described how devices joining IPIDEA made their network bandwidth and IP addresses available to the proxy network’s customers.&lt;/p&gt;

&lt;p&gt;During a single seven-day period in January 2026, GTIG observed &lt;strong&gt;more than 550 threat groups it tracks&lt;/strong&gt; using IPIDEA exit IP addresses to obscure their activities.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://cloud.google.com/blog/topics/threat-intelligence/disrupting-largest-residential-proxy-network" rel="noopener noreferrer"&gt;Google Threat Intelligence Group’s report on IPIDEA&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;A home connection can have value to someone else even when its owner thinks there is nothing valuable on the computer itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why use a residential IP address?
&lt;/h2&gt;

&lt;p&gt;Internet services may consider more than the country associated with an IP address. ISP and ASN information, hosting or data center classifications, and known VPN or proxy associations can also inform their decisions.&lt;/p&gt;

&lt;p&gt;A residential proxy sends traffic to the internet through a consumer ISP connection. That network context can differ from a data center’s.&lt;/p&gt;

&lt;p&gt;The relevant asset is therefore not just the data stored on a device. &lt;strong&gt;The connection itself can be used as a route for someone else’s traffic.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For more on network classifications, see &lt;a href="https://www.homegrid-vpn.com/blog/en/residential-vs-datacenter-ip/" rel="noopener noreferrer"&gt;Residential IP vs. Data Center IP: Why the Network Matters&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The FBI reported access to approximately 369,000 devices being sold
&lt;/h2&gt;

&lt;p&gt;In a March 12, 2026 FLASH, the FBI described compromised routers and IoT devices used by the SocksEscort residential proxy service through AVrecon malware.&lt;/p&gt;

&lt;p&gt;The FBI reported devices in approximately 163 countries and stated that SocksEscort was believed to have compromised and sold access to &lt;strong&gt;approximately 369,000 devices since 2020&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://www.fbi.gov/file-repository/cyber-alerts/avrecon-malware-infected-routers-exploited-as-residential-proxies-by-socksescort.pdf" rel="noopener noreferrer"&gt;FBI: AVrecon Malware-Infected Routers Exploited as Residential Proxies by SocksEscort (PDF)&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This case does not establish that forwarding a WireGuard port leads to the same outcome. Compromised residential proxy devices and a properly configured WireGuard endpoint are different situations.&lt;/p&gt;

&lt;p&gt;The lesson is narrower: a private household’s network should not be treated as having no value to outsiders.&lt;/p&gt;

&lt;h2&gt;
  
  
  An unadvertised service can still be discovered
&lt;/h2&gt;

&lt;p&gt;You might assume that nobody can find a home VPN if you never share its address.&lt;/p&gt;

&lt;p&gt;Internet-accessible systems can be examined automatically. CISA’s Internet Exposure Reduction Guidance lists services such as Shodan, Censys, and Shadowserver as ways to identify exposed assets.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://www.cisa.gov/resources-tools/resources/exposure-reduction" rel="noopener noreferrer"&gt;CISA: Internet Exposure Reduction Guidance&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Depending on service responses and public information, an exposed service can be discovered without someone first deciding to target a particular household.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WireGuard needs a qualification here.&lt;/strong&gt; Its design avoids responding to unauthenticated packets. An ordinary scan cannot necessarily confirm its presence in the way it might identify an SSH or web service. Delivering packets to an endpoint and confirming which service is listening are separate things.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://www.wireguard.com/talks/lpc2018-wireguard-slides.pdf#page=24" rel="noopener noreferrer"&gt;WireGuard’s official presentation on stealth, slide 24 (PDF)&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What an exposed SSH server illustrates
&lt;/h2&gt;

&lt;p&gt;The review should cover more than WireGuard’s responses: router management interfaces, exposure settings for other services, and the home public IP used as a destination from outside also matter. Forwarding a VPN port does not automatically expose all those services.&lt;/p&gt;

&lt;p&gt;An SSH experience illustrates the broader need to review exposure and maintenance.&lt;/p&gt;

&lt;p&gt;I once created an AWS server with SSH accessible from the internet. Within a few hours, its logs showed requests from IP addresses associated with several regions, including North Africa and Europe.&lt;/p&gt;

&lt;p&gt;I had not advertised a domain or announced the server’s existence. Requests arrived anyway.&lt;/p&gt;

&lt;p&gt;This is an example of unsolicited traffic to an exposed service, not evidence that a WireGuard endpoint responds in the same way.&lt;/p&gt;

&lt;h2&gt;
  
  
  A direct home VPN uses your home public IP as its destination
&lt;/h2&gt;

&lt;p&gt;There is another consideration that does not depend on a VPN service responding to a scanner.&lt;/p&gt;

&lt;p&gt;When you connect to a direct home VPN from a hotel, cafe, airport, or public Wi-Fi network, your device sends packets to your home public IP.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Remote device on public Wi-Fi
             |
             | Encrypted VPN
             | Destination: home public IP
             v
          Internet
             |
             v
      Home public IP
             |
             v
      WireGuard server

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;WireGuard encrypts the traffic inside the tunnel. The outer packets still need a destination address so that the network can deliver them to your home.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Encrypting the contents does not hide the outer destination IP.&lt;/strong&gt; A party able to observe that Wi-Fi network or an upstream path may be able to see traffic addressed to your home public IP.&lt;/p&gt;

&lt;p&gt;Using the VPN only for yourself does not make that destination invisible to network observers.&lt;/p&gt;

&lt;h2&gt;
  
  
  GeoIP is not a street address, but it can add context
&lt;/h2&gt;

&lt;p&gt;IP geolocation is not GPS. MaxMind explains that GeoIP locations are inherently imprecise and should not be used to identify a particular address or household.&lt;/p&gt;

&lt;p&gt;Depending on the product and available data, results can include a country, subdivision, city, postal area, estimated coordinates, and an accuracy radius. The detail and accuracy vary by network and database.&lt;/p&gt;

&lt;p&gt;Sources: &lt;a href="https://dev.maxmind.com/geoip/docs/web-services/#ip-geolocation-accuracy" rel="noopener noreferrer"&gt;MaxMind’s IP geolocation accuracy guidance&lt;/a&gt; and &lt;a href="https://dev.maxmind.com/geoip/docs/web-services/responses/" rel="noopener noreferrer"&gt;GeoIP and GeoLite API response fields&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It would be wrong to claim that knowing an IP address reveals an exact home address. It would also be too strong to say that approximate regional information can never contribute anything.&lt;/p&gt;

&lt;p&gt;The useful privacy question is what context can be combined, not whether GeoIP alone identifies a house.&lt;/p&gt;

&lt;h2&gt;
  
  
  The destination can become one piece of a larger record
&lt;/h2&gt;

&lt;p&gt;A hotel or Wi-Fi provider may retain connection records. A hotel may also be able to associate a guest with a stay and a time window. Airports, shops, and hotels may have camera footage.&lt;/p&gt;

&lt;p&gt;Separately, a home public IP can have ISP, ASN, and approximate location information associated with it.&lt;/p&gt;

&lt;p&gt;Where a party can lawfully access and correlate the relevant records, those sources may provide material for an association such as:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A person present at a place and time
                  |
                  v
         Wi-Fi usage records
                  |
                  v
Traffic to a home public IP address
                  |
                  v
    ISP / ASN / approximate region

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is a conditional privacy consideration. It does not mean that a VPN connection automatically reveals a person’s name, face, or exact home address, or that every network operator has access to all these records. The cited proxy reports do not demonstrate such identification of home VPN users.&lt;/p&gt;

&lt;p&gt;Still, the possibility of correlation is a reason to ask whether your everyday home IP needs to be the direct VPN destination you use from public networks.&lt;/p&gt;

&lt;h2&gt;
  
  
  Does your home need another internet-facing endpoint?
&lt;/h2&gt;

&lt;p&gt;A typical direct home VPN path looks like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Remote device
      |
      v
   Internet
      |
      v
Home public IP
      |
      v
Router / firewall
      |
      v
WireGuard server
      |
      v
   Home LAN

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;With the necessary forwarding and firewall permissions, packets from outside can reach the VPN server. You then have an internet-facing endpoint to maintain.&lt;/p&gt;

&lt;p&gt;That maintenance includes the router’s firmware, the server’s operating system, firewall rules, other software on the same device, and updates to those components.&lt;/p&gt;

&lt;p&gt;CISA’s guidance recommends assessing which assets actually need to be internet-accessible and reducing unnecessary exposure. That is a design principle, not a declaration that WireGuard is dangerous.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If an inbound endpoint is unnecessary for your goal, consider a design that does not require it.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  No manual port forwarding does not always mean no direct connection
&lt;/h2&gt;

&lt;p&gt;Port forwarding is only one mechanism. UPnP can create port mappings. Peer-to-peer systems may use NAT traversal, including STUN-assisted address discovery and other mechanisms, to establish direct communication.&lt;/p&gt;

&lt;p&gt;These technologies work differently, and their trade-offs differ too.&lt;/p&gt;

&lt;p&gt;The important distinction is that &lt;strong&gt;“no manual port forwarding” does not necessarily mean “no direct connection to the home.”&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A direct design may suit your needs. Evaluate the resulting path, maintenance, and privacy trade-offs rather than relying on a setup label alone.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with the outcome you wanted
&lt;/h2&gt;

&lt;p&gt;Most people do not build a home VPN just to configure a router. They want to reach a NAS or development environment, use their home LAN while traveling, or send internet traffic through their own residential connection.&lt;/p&gt;

&lt;p&gt;For someone abroad, that may mean using a home connection in their home country. The destination service’s terms, regional restrictions, and VPN policies still apply.&lt;/p&gt;

&lt;p&gt;For these goals, ask: &lt;strong&gt;must the home accept a new direct VPN connection from the internet?&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Let the home establish the connection outbound
&lt;/h2&gt;

&lt;p&gt;Another design has both the home device and the remote device establish connections to a relay or hub.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;             Cloud Hub
              ^ ^
              | |
       Outbound Outbound
              | |
             Home Remote

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;With an appropriate routing setup, this does not require the remote device to connect directly to the home’s public IPv4 address or global IPv6 address. It does not rely on creating an inbound IPv4 port forward or an IPv6 inbound firewall rule at home for that VPN connection.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outbound describes how the connection starts.&lt;/strong&gt; Once the VPN path exists, traffic can flow in both directions. You still need access controls for the home LAN, updates for the devices, and a network that allows the outbound VPN traffic.&lt;/p&gt;

&lt;p&gt;The goal is to keep the access you wanted while removing the requirement for a direct inbound VPN endpoint at home.&lt;/p&gt;

&lt;h2&gt;
  
  
  How HomeGrid VPN uses this design
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.homegrid-vpn.com/en/" rel="noopener noreferrer"&gt;HomeGrid VPN&lt;/a&gt; uses a hub-and-spoke design. The home Grid and the remote device connect to a Cloud Hub, with the home initiating its connection outbound.&lt;/p&gt;

&lt;p&gt;It does not rely on IPv4 port forwarding, IPv6 inbound rules, or a direct VPN connection from the remote device to the home public IP.&lt;/p&gt;

&lt;p&gt;The Cloud Hub remains part of the route and its trust boundary matters. Our policy is to record connection information such as source IP addresses and to respond to legally required disclosure requests for information we hold. &lt;strong&gt;This design does not provide anonymity from the operator.&lt;/strong&gt; It reduces the need for the home public IP to appear as the direct VPN destination on the remote network.&lt;/p&gt;

&lt;p&gt;Also, &lt;strong&gt;Cloud Hub does not mean Internet Exit.&lt;/strong&gt; When the home serves as the exit for IPv4 traffic, the path is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Remote device
      |
      v
  Cloud Hub
      |
      v
     Home
      |
      v
Residential ISP
      |
      v
   Internet

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The destination service sees the public IP used by the home ISP connection, rather than the Cloud Hub’s data center IP. The traffic actually travels through the home connection and leaves for the internet there.&lt;/p&gt;

&lt;p&gt;That changes the route and exit IP. It does not make GPS, cookies, browser information, or other device signals match those of a device at home. The exit service can still associate activity with the home public IP, and a hub-based path does not eliminate every possibility of correlation.&lt;/p&gt;

&lt;p&gt;For routing and operating conditions, see &lt;a href="https://www.homegrid-vpn.com/blog/en/how-homegrid-vpn-works/" rel="noopener noreferrer"&gt;What Is HomeGrid VPN? Use Your Home Connection as a VPN Exit&lt;/a&gt;. If the connection belongs to a family member or someone else, their consent and the ISP’s contract conditions are prerequisites.&lt;/p&gt;

&lt;h2&gt;
  
  
  A failed connection can be a useful design checkpoint
&lt;/h2&gt;

&lt;p&gt;If WireGuard works on your LAN but fails from outside, troubleshooting reachability is valid. Direct access is technically possible when the network and configuration support it.&lt;/p&gt;

&lt;p&gt;Before committing to that design, consider the bigger picture: residential connections can have value to third parties, public services need maintenance, and a direct VPN connection exposes its home destination IP to parties able to observe the outer traffic.&lt;/p&gt;

&lt;p&gt;None of those points means that port forwarding causes a compromise or that IP geolocation identifies your address. They are reasons to choose a path deliberately.&lt;/p&gt;

&lt;p&gt;You can want a home VPN without requiring your home to be a direct internet-facing VPN endpoint. HomeGrid VPN follows that outbound design approach.&lt;/p&gt;

&lt;p&gt;Originally published at &lt;a href="https://www.homegrid-vpn.com/blog/en/home-vpn-direct-exposure/" rel="noopener noreferrer"&gt;https://www.homegrid-vpn.com/blog/en/home-vpn-direct-exposure/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>networking</category>
      <category>security</category>
    </item>
    <item>
      <title>Disaster Recovery Is Not Just About Data — Can Your Team Still Work?</title>
      <dc:creator>HomeGrid VPN</dc:creator>
      <pubDate>Tue, 22 Sep 2026 12:39:02 +0000</pubDate>
      <link>https://dev.to/homegrid_vpn/disaster-recovery-is-not-just-about-data-can-your-team-still-work-1bea</link>
      <guid>https://dev.to/homegrid_vpn/disaster-recovery-is-not-just-about-data-can-your-team-still-work-1bea</guid>
      <description>&lt;p&gt;When engineers talk about disaster recovery, the first topic is usually data.&lt;/p&gt;

&lt;p&gt;Backups.&lt;br&gt;
Replication.&lt;br&gt;
Snapshots.&lt;br&gt;
Cloud storage.&lt;br&gt;
Recovery points.&lt;/p&gt;

&lt;p&gt;All of those matter.&lt;/p&gt;

&lt;p&gt;But there is another failure mode that is easy to overlook:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Your data survives, but nobody can reach the systems needed to work.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;That is the gap between data recovery and business continuity.&lt;/p&gt;


&lt;h2&gt;
  
  
  Imagine the office disappears from the network
&lt;/h2&gt;

&lt;p&gt;Consider a small company with one office.&lt;/p&gt;

&lt;p&gt;The office contains:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;employee PCs&lt;/li&gt;
&lt;li&gt;network equipment&lt;/li&gt;
&lt;li&gt;a VPN gateway&lt;/li&gt;
&lt;li&gt;perhaps a NAS or file server&lt;/li&gt;
&lt;li&gt;access paths to private systems&lt;/li&gt;
&lt;li&gt;a public IP address used in allowlists&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Then something happens.&lt;/p&gt;

&lt;p&gt;A flood.&lt;/p&gt;

&lt;p&gt;A fire.&lt;/p&gt;

&lt;p&gt;An earthquake.&lt;/p&gt;

&lt;p&gt;A prolonged power outage.&lt;/p&gt;

&lt;p&gt;Or simply an ISP failure that lasts much longer than expected.&lt;/p&gt;

&lt;p&gt;The company has already moved its important files to cloud storage.&lt;/p&gt;

&lt;p&gt;So the data survives.&lt;/p&gt;

&lt;p&gt;That is good.&lt;/p&gt;

&lt;p&gt;But the next morning, employees are working from home, a temporary office, a hotel, or another branch.&lt;/p&gt;

&lt;p&gt;Now a different question appears:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How do they actually get back to work?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If the answer still depends on the original office network, the recovery plan has a hidden dependency.&lt;/p&gt;


&lt;h2&gt;
  
  
  "But we already use Microsoft 365"
&lt;/h2&gt;

&lt;p&gt;For some businesses, this really does solve most of the problem.&lt;/p&gt;

&lt;p&gt;If almost everything your team uses is SaaS and securely accessible from anywhere, losing the office network may have relatively little impact.&lt;/p&gt;

&lt;p&gt;But many environments still contain systems such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;private cloud applications&lt;/li&gt;
&lt;li&gt;internal administration tools&lt;/li&gt;
&lt;li&gt;development environments&lt;/li&gt;
&lt;li&gt;databases that should not be exposed to the public Internet&lt;/li&gt;
&lt;li&gt;supplier or partner systems protected by IP allowlists&lt;/li&gt;
&lt;li&gt;legacy applications reachable only through a private network&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In those environments, protecting the data is only half of the problem.&lt;/p&gt;

&lt;p&gt;The other half is &lt;strong&gt;reachability&lt;/strong&gt;.&lt;/p&gt;


&lt;h2&gt;
  
  
  Your office IP can be a hidden dependency
&lt;/h2&gt;

&lt;p&gt;IP allowlists are a good example.&lt;/p&gt;

&lt;p&gt;Suppose an administration system only accepts connections from your office public IP.&lt;/p&gt;

&lt;p&gt;Normally:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Employee
   |
   v
Office Network
   |
   v
Office Public IP
   |
   v
Admin System
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The source IP is known, so the system allows the connection.&lt;/p&gt;

&lt;p&gt;This can be useful as an additional access-control layer when combined with proper authentication, MFA, and application-level authorization.&lt;/p&gt;

&lt;p&gt;But now imagine the office Internet connection disappears.&lt;/p&gt;

&lt;p&gt;An employee working from home has a completely different public IP.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Employee
   |
   v
Home Internet
   |
   v
Different Public IP
   |
   X
Admin System
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The application is still running.&lt;/p&gt;

&lt;p&gt;The credentials still work.&lt;/p&gt;

&lt;p&gt;The data is still safe.&lt;/p&gt;

&lt;p&gt;But the employee cannot access it.&lt;/p&gt;

&lt;p&gt;That means a BCP plan may need more than data backups.&lt;/p&gt;

&lt;p&gt;It may also need a &lt;strong&gt;backup network path&lt;/strong&gt; and, depending on the system, an &lt;strong&gt;alternative Internet exit&lt;/strong&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Alternative exits need preparation too
&lt;/h2&gt;

&lt;p&gt;You cannot wait until the disaster happens and then decide which IP address should be trusted.&lt;/p&gt;

&lt;p&gt;If a partner system or administration console uses an IP allowlist, the backup exit IP should be registered &lt;strong&gt;before&lt;/strong&gt; it is needed.&lt;/p&gt;

&lt;p&gt;For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Primary Office IP
        +
Backup Site IP
        |
        v
    IP Allowlist
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If the workflow requires a stable source IP, the backup connection must also provide one.&lt;/p&gt;

&lt;p&gt;The backup exit could be:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;another company location&lt;/li&gt;
&lt;li&gt;a secondary office&lt;/li&gt;
&lt;li&gt;a temporary recovery site&lt;/li&gt;
&lt;li&gt;a cloud-hosted environment&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The right answer depends on the business.&lt;/p&gt;

&lt;p&gt;The important part is that the alternative path exists and has already been tested.&lt;/p&gt;




&lt;h2&gt;
  
  
  Stop treating the office as the center of the network
&lt;/h2&gt;

&lt;p&gt;A traditional small-office architecture often looks like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Remote User
     |
     v
 Internet
     |
     v
Office VPN Gateway
     |
     v
Office LAN
     |
     v
Business Systems
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This works.&lt;/p&gt;

&lt;p&gt;But the office is doing a lot of jobs.&lt;/p&gt;

&lt;p&gt;It is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the workplace&lt;/li&gt;
&lt;li&gt;the VPN endpoint&lt;/li&gt;
&lt;li&gt;the network gateway&lt;/li&gt;
&lt;li&gt;sometimes the Internet exit&lt;/li&gt;
&lt;li&gt;sometimes the place where business systems live&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That creates a large blast radius when the office goes offline.&lt;/p&gt;

&lt;p&gt;A different architecture is to make the office just &lt;strong&gt;one place from which people connect&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Home --------\
Branch -------\
Mobile --------&amp;gt; Private Network ---&amp;gt; Cloud VPC ---&amp;gt; Business Systems
Office -------/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now the cloud environment can remain available even if the office disappears.&lt;/p&gt;

&lt;p&gt;The office is still useful.&lt;/p&gt;

&lt;p&gt;It just stops being a requirement for the rest of the company to operate.&lt;/p&gt;




&lt;h2&gt;
  
  
  Recovery should be a change of location, not a network rebuild
&lt;/h2&gt;

&lt;p&gt;Imagine the office is unusable and several employee laptops were damaged too.&lt;/p&gt;

&lt;p&gt;You ship temporary PCs to employees.&lt;/p&gt;

&lt;p&gt;That sounds simple, but a replacement laptop is not automatically a working environment.&lt;/p&gt;

&lt;p&gt;You may still need to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;install required software&lt;/li&gt;
&lt;li&gt;enroll the device&lt;/li&gt;
&lt;li&gt;distribute credentials&lt;/li&gt;
&lt;li&gt;recover MFA access&lt;/li&gt;
&lt;li&gt;install the VPN client&lt;/li&gt;
&lt;li&gt;validate endpoint security&lt;/li&gt;
&lt;li&gt;confirm access to private systems&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is why the best BCP test happens &lt;strong&gt;before&lt;/strong&gt; the disaster.&lt;/p&gt;

&lt;p&gt;The goal should not be:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Build the emergency network when the emergency happens.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It should be:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Use the same access architecture during normal operations, so the emergency changes the employee's location rather than the entire network design.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Normal day:

Office / Home
      |
      v
Private Network
      |
      v
Cloud Systems


Disaster day:

Temporary Location
      |
      v
Same Private Network
      |
      v
Same Cloud Systems
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That is a much easier recovery model to practice.&lt;/p&gt;




&lt;h2&gt;
  
  
  Outbound connectivity changes the recovery requirements
&lt;/h2&gt;

&lt;p&gt;There is another practical issue: inbound connectivity.&lt;/p&gt;

&lt;p&gt;A traditional self-hosted VPN often assumes something like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Internet
   |
   v
Public IPv4
   |
   v
Port Forward
   |
   v
VPN Server
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That can work perfectly well.&lt;/p&gt;

&lt;p&gt;But at a temporary or backup location, you may not control those conditions.&lt;/p&gt;

&lt;p&gt;You might encounter:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;CGNAT&lt;/li&gt;
&lt;li&gt;IPv4 over IPv6&lt;/li&gt;
&lt;li&gt;double NAT&lt;/li&gt;
&lt;li&gt;a building-wide upstream router&lt;/li&gt;
&lt;li&gt;an ISP that does not provide directly reachable IPv4&lt;/li&gt;
&lt;li&gt;firewall policies you cannot change&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is why outbound-oriented network designs can be useful for BCP.&lt;/p&gt;

&lt;p&gt;Instead of requiring the recovery site to accept inbound VPN connections, the recovery site establishes an outbound connection to the VPN infrastructure.&lt;/p&gt;

&lt;p&gt;That reduces the number of network assumptions that need to be recreated during recovery.&lt;/p&gt;




&lt;h2&gt;
  
  
  Where HomeGrid VPN fits
&lt;/h2&gt;

&lt;p&gt;Full disclosure: &lt;strong&gt;I'm the founder of HomeGrid VPN.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;HomeGrid VPN is one implementation of this model.&lt;/p&gt;

&lt;p&gt;It uses a Hub &amp;amp; Spoke architecture in which devices, locations, and cloud environments connect outbound to a Cloud Hub.&lt;/p&gt;

&lt;p&gt;A cloud environment can participate in the same private network as remote users and other locations.&lt;/p&gt;

&lt;p&gt;Conceptually:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Home --------\
Branch -------\
Mobile --------&amp;gt; Cloud Hub ---&amp;gt; Cloud VPC
Office -------/                   |
                                  v
                           Business Systems
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The Cloud Hub is part of the VPN path.&lt;/p&gt;

&lt;p&gt;It is &lt;strong&gt;not necessarily the Internet exit&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;That distinction is useful because private access to a cloud VPC and Internet egress are two different problems.&lt;/p&gt;

&lt;p&gt;For example, an organization could use:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Employee
   |
   v
Cloud Hub
   |
   +------&amp;gt; Cloud VPC
   |
   +------&amp;gt; Selected Internet Exit
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If a workflow depends on a specific source network or public IP, another location can be selected as the Internet exit.&lt;/p&gt;

&lt;p&gt;That alternative IP still needs to be prepared in advance if external systems use allowlists.&lt;/p&gt;

&lt;p&gt;For HomeGrid VPN, Cloud VPC connectivity is available with the &lt;strong&gt;Platinum plan (dedicated server plan)&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The architecture does not eliminate infrastructure dependencies.&lt;/p&gt;

&lt;p&gt;HomeGrid VPN still depends on its Cloud Hub and on Internet connectivity to reach it.&lt;/p&gt;

&lt;p&gt;What changes is that the organization does not have to make one physical office the center of every access path.&lt;/p&gt;




&lt;h2&gt;
  
  
  Cold standby can be enough
&lt;/h2&gt;

&lt;p&gt;Not every small company needs automatic failover.&lt;/p&gt;

&lt;p&gt;In fact, automatic network failover adds its own complexity.&lt;/p&gt;

&lt;p&gt;For many small businesses, a cold standby design can be reasonable.&lt;/p&gt;

&lt;p&gt;For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Normal:

Office Exit
    |
    v
Internet


Emergency:

Backup Exit
    |
    v
Internet
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The backup site does not have to carry production traffic every day.&lt;/p&gt;

&lt;p&gt;It only needs to be:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;configured&lt;/li&gt;
&lt;li&gt;reachable&lt;/li&gt;
&lt;li&gt;tested&lt;/li&gt;
&lt;li&gt;approved by any required IP allowlists&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;When the primary location fails, an administrator can switch to it manually.&lt;/p&gt;

&lt;p&gt;Simple recovery processes are often easier to understand and test than highly automated systems that are rarely exercised.&lt;/p&gt;




&lt;h2&gt;
  
  
  Three questions worth testing
&lt;/h2&gt;

&lt;p&gt;You can learn a lot about your BCP architecture without simulating an earthquake or flooding the office.&lt;/p&gt;

&lt;p&gt;Try asking:&lt;/p&gt;

&lt;h3&gt;
  
  
  1. What breaks if nobody can enter the office tomorrow?
&lt;/h3&gt;

&lt;p&gt;Do not start with servers.&lt;/p&gt;

&lt;p&gt;Start with business processes.&lt;/p&gt;

&lt;p&gt;Which systems become unavailable?&lt;/p&gt;

&lt;p&gt;Which workflows require the office network?&lt;/p&gt;




&lt;h3&gt;
  
  
  2. Which systems depend on the office public IP?
&lt;/h3&gt;

&lt;p&gt;Look for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;partner portals&lt;/li&gt;
&lt;li&gt;administration systems&lt;/li&gt;
&lt;li&gt;cloud firewalls&lt;/li&gt;
&lt;li&gt;IP allowlists&lt;/li&gt;
&lt;li&gt;database access rules&lt;/li&gt;
&lt;li&gt;third-party APIs&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you need a backup Internet exit, register its IP before the incident.&lt;/p&gt;




&lt;h3&gt;
  
  
  3. Can the company operate for one day without the office network?
&lt;/h3&gt;

&lt;p&gt;Actually test it.&lt;/p&gt;

&lt;p&gt;Have a small group work from home or another location.&lt;/p&gt;

&lt;p&gt;Do not let them use the office LAN.&lt;/p&gt;

&lt;p&gt;See what fails.&lt;/p&gt;

&lt;p&gt;The interesting problems are often not the ones documented in the BCP spreadsheet.&lt;/p&gt;

&lt;p&gt;They are the dependencies nobody remembered were dependencies.&lt;/p&gt;




&lt;h2&gt;
  
  
  The real BCP question
&lt;/h2&gt;

&lt;p&gt;A disaster recovery plan should absolutely answer:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Is our data safe?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;But there is another question worth asking:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;If employees cannot enter the office tomorrow, how many steps stand between them and being able to work again?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;If the answer requires:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;rebuilding the office LAN&lt;/li&gt;
&lt;li&gt;replacing a VPN appliance&lt;/li&gt;
&lt;li&gt;recovering a particular public IP&lt;/li&gt;
&lt;li&gt;recreating firewall rules&lt;/li&gt;
&lt;li&gt;changing employee access methods&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;then the business may still be more dependent on the office than it appears.&lt;/p&gt;

&lt;p&gt;A better goal is not to make the office unnecessary.&lt;/p&gt;

&lt;p&gt;It is to make the office &lt;strong&gt;replaceable&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Because disaster recovery is not just about preserving data.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It's about keeping the business connected.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>networking</category>
      <category>cloud</category>
      <category>security</category>
      <category>devops</category>
    </item>
    <item>
      <title>From "Hiding" to "Accurate Signaling": Reclaiming Your Digital Home with a Home-Exit VPN</title>
      <dc:creator>HomeGrid VPN</dc:creator>
      <pubDate>Sat, 27 Jun 2026 12:49:56 +0000</pubDate>
      <link>https://dev.to/homegrid_vpn/from-hiding-to-accurate-signaling-reclaiming-your-digital-home-with-a-home-exit-vpn-mld</link>
      <guid>https://dev.to/homegrid_vpn/from-hiding-to-accurate-signaling-reclaiming-your-digital-home-with-a-home-exit-vpn-mld</guid>
      <description>&lt;p&gt;Have you ever traveled for a business trip, a vacation, or a mid-to-long-term stay, only to open your favorite streaming service or website and be greeted with the dreaded message: &lt;em&gt;"This content is not available in your region"&lt;/em&gt;?&lt;/p&gt;

&lt;p&gt;Even though you legitimately reside in that region, hold a valid account, and pay your monthly subscription, your access is unilaterally denied simply because of your current physical location. This is an unreasonable restriction in our modern digital lives, turning legitimate consumers into false positives for geo-restrictions.&lt;/p&gt;

&lt;p&gt;Many turn to legacy VPNs to bypass this wall. However, we are currently witnessing a massive paradigm shift in how we choose and utilize remote access technologies.&lt;/p&gt;




&lt;h2&gt;
  
  
  1. Why Traditional "Anonymous VPNs" Fail to Bypass Restrictions
&lt;/h2&gt;

&lt;p&gt;Historically, the most common approach has been to use major commercial VPN services that route user traffic through shared servers located in data centers around the world. The goal is to hide your actual IP address and "spoof" your location by disguising yourself behind a shared data center IP.&lt;/p&gt;

&lt;p&gt;However, modern platform providers have implemented strict technical countermeasures. When thousands of disorganized requests flood in simultaneously from a single, unidentified data center IP range, platforms naturally flag and block it as suspicious traffic. Using a VPN merely as an "anonymizing tool" to sneak past restrictions is becoming increasingly ineffective against sophisticated security meshes.&lt;/p&gt;

&lt;p&gt;Furthermore, the root of the problem extends beyond accessing content from abroad; it lies in the inherent flaws of modern IP Geolocation. This technology, which estimates a user's physical location based on their IP address, relies heavily on proprietary third-party databases and frequently contains inaccuracies. &lt;br&gt;
For instance, even if you are using a static home connection that you've had for years, geolocation databases can mistakenly map your IP to a completely different city, locking you out of region-specific local services. Data center VPNs attempt to exploit these "estimation errors" to spoof locations, which is exactly why modern platforms explicitly detect and reject them.&lt;/p&gt;




&lt;h2&gt;
  
  
  2. Not "Spoofing," but "Accurate Signaling": A New Networking Paradigm
&lt;/h2&gt;

&lt;p&gt;This is where the next-generation approach of &lt;strong&gt;HomeGrid VPN&lt;/strong&gt; comes into play. Instead of assigning you an unfamiliar, flagged data center IP to mask your identity, &lt;strong&gt;it utilizes your own private base—such as your actual home—as the Exit Node.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No matter where you are in the world, your traffic connects back to your original home base through a heavily encrypted WireGuard tunnel. When your traffic finally exits to the open internet, it does so using your own genuine, household IP address.&lt;/p&gt;

&lt;p&gt;This is fundamentally different from "spoofing" your location to trick a platform. Rather than manipulating a signal to pretend you are somewhere you are not, it takes a signal that has been distorted by physical travel or inaccurate IP geolocation databases and aligns it back with your legitimate, permanent home base. We define this approach as &lt;strong&gt;Accurate Signaling&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;From the perspective of web services, they don't receive shady, anonymous data center traffic attempting to bend the rules; they receive honest, unaltered data indicating that a legitimate account holder is accessing the service from a standard household connection. HomeGrid VPN is not a tool for hiding; it is a remote access infrastructure that allows you to honestly present yourself as a legitimate user through your own trusted infrastructure.&lt;/p&gt;




&lt;h2&gt;
  
  
  3. Technical and Contractual Considerations When Using Someone Else's Infrastructure
&lt;/h2&gt;

&lt;p&gt;The most robust and easily justifiable use case for HomeGrid VPN is connecting back to your own home connection (under your own contract) while temporarily away. Within this scope, you are cleanly complying with geographical restrictions and the increasingly strict "Household" definitions enforced by streaming platforms.&lt;/p&gt;

&lt;p&gt;On the other hand, what if you have completely relocated or do not have a dedicated home internet connection in your home country? In such cases, some users ask a family member or a trusted friend to host a Grid Node (Exit Node) for them, sometimes reimbursing them for the physical space and electricity. How does this hold up technically and contractually?&lt;/p&gt;

&lt;p&gt;When utilizing a friend's connection (a legal third party), there are different layers of responsibility compared to using your own home, but with proper consent, it can be a highly effective private remote-access setup.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;ISP Terms of Service (ToS) and Financial Reimbursement&lt;/strong&gt;:
What most Internet Service Providers (ISPs) prohibit in their terms is the unauthorized commercial reselling or sharing of bandwidth to the general public. Accessing a network remotely for private use, based on explicit consent between specific individuals, falls well within standard technical usage (a feature built into many consumer routers). Any money exchanged between friends is not "buying bandwidth," but rather a private agreement to reimburse the physical costs of hosting a device (space and electricity). Therefore, it generally does not constitute commercial reselling. However, because specific ToS language and tolerances vary by ISP, the account holder should verify their contract.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Legal Responsibility and Trust&lt;/strong&gt;:
In the unlikely event of legal issues or network abuse stemming from the VPN traffic, the ISP and authorities will, on the surface, look at the account holder (your friend or family member) first. Therefore, this setup requires an absolute foundation of strong trust and explicit prior consent between both parties.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;System Security and Bandwidth Protection (FUP)&lt;/strong&gt;:
HomeGrid VPN is built on a &lt;strong&gt;Zero Trust by design&lt;/strong&gt; philosophy. Your private communication keys never leave your device. Neither the operating company nor the person hosting the infrastructure can intercept or read your traffic. Furthermore, the system automatically enforces a Fair Usage Policy (FUP/Traffic Shaping), ensuring that your connection never monopolizes the host's bandwidth or disrupts your friend's/family's internet experience.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  4. Technical Deep Dive: The Architecture of HomeGrid VPN
&lt;/h2&gt;

&lt;p&gt;For engineers interested in how this is implemented under the hood, HomeGrid VPN operates on a structured &lt;strong&gt;Hub &amp;amp; Spoke&lt;/strong&gt; topology designed to balance security, performance, and private residential routing.&lt;/p&gt;

&lt;h3&gt;
  
  
  WireGuard Tunneling (UDP 51820)
&lt;/h3&gt;

&lt;p&gt;All traffic between client devices (Spokes) and exit nodes (Grids) is encapsulated using pure WireGuard. This ensures near-line-speed throughput and minimal battery drain on mobile clients, and is less likely to be misclassified by generic deep packet inspection (DPI) systems that typically flag older protocols like OpenVPN.&lt;/p&gt;

&lt;h3&gt;
  
  
  Zero-Trust Key Exchange
&lt;/h3&gt;

&lt;p&gt;To eliminate the "trusted third party" vulnerability common in commercial VPN providers, cryptographic key pairs are generated entirely client-side (e.g., within the browser or client app). The central SaaS control plane only manages the routing metadata and configuration handshakes; the raw private keys are never stored on, nor transmitted to, any central servers.&lt;/p&gt;

&lt;h3&gt;
  
  
  Fair Usage Policy (FUP) via Linux Traffic Control (&lt;code&gt;tc&lt;/code&gt;)
&lt;/h3&gt;

&lt;p&gt;One of the largest hurdles when hosting an exit node at a friend’s or family member’s house is preventing bandwidth exhaustion. HomeGrid VPN mitigates this programmatically. The system tracks daily traffic quotas to ensure fair usage. Once a user approaches their designated daily threshold, the control plane triggers Linux Traffic Control (&lt;code&gt;tc&lt;/code&gt;) commands at the interface level, automatically shaping the traffic and throttling the speed to a sustainable, polite limit. This safeguards the host’s local QoS, ensuring that standard household internet usage remains entirely unaffected.&lt;/p&gt;




&lt;h2&gt;
  
  
  5. Reclaiming Your Consumer Rights: The EU Precedent
&lt;/h2&gt;

&lt;p&gt;Accessing your digital assets remotely via your home infrastructure is a legitimate technical measure to protect your rights as a consumer.&lt;/p&gt;

&lt;p&gt;A powerful real-world validation of this concept is the &lt;strong&gt;EU Cross-border Portability Regulation&lt;/strong&gt;. This framework requires online content providers to ensure that subscribers traveling temporarily to other EU member states can still access the exact same service and content they paid for in their home country. &lt;/p&gt;

&lt;p&gt;The regulation guarantees access to your &lt;em&gt;home&lt;/em&gt; content, not the right to unlock foreign catalogs—which perfectly aligns with the philosophy of connecting back to your actual home base. The intuitive sense of justice that says, &lt;em&gt;"I should be able to use my subscription, based on my home region, even when I am temporarily away,"&lt;/em&gt; is already officially recognized by modern international legislation.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;(Disclaimer: This service is not an anonymizing tool intended to hide communications from state actors or bypass censorship in non-democratic regimes. It is an infrastructure built for legitimate users operating within an open internet and states governed by the rule of law.)&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You no longer need to risk handing all your traffic over to opaque, third-party data centers. By turning your own home base into a private routing point, you replace unreliable location-spoofing with a robust, transparent networking model.&lt;/p&gt;




&lt;h2&gt;
  
  
  6. FAQ (Legality and Terms of Service)
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Q1. Is it legal to use a VPN routed through my home or a friend's house?
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;A.&lt;/strong&gt; In the vast majority of countries, individuals using VPNs or private networks for security and remote access is entirely legal. However, laws regarding bypassing geo-restrictions or VPN usage itself vary heavily depending on the country or region you are &lt;em&gt;physically located in&lt;/em&gt; (certain countries heavily regulate or ban VPN traffic). Always comply with the local laws of your current location.&lt;/p&gt;

&lt;h3&gt;
  
  
  Q2. Does this violate the Terms of Service (ToS) of streaming platforms?
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;A.&lt;/strong&gt; Streaming services enforce geo-blocking to protect regional licensing and strictly crack down on location spoofing via data center IPs. HomeGrid VPN provides the technology to accurately route your traffic through your own home base. However, compliance with the latest ToS of any specific streaming service, including their definitions of a "Household," and evaluating your viewing eligibility remains solely your responsibility.&lt;/p&gt;

&lt;h3&gt;
  
  
  Q3. If I pay a friend to host a Grid Node, does it violate their ISP's terms?
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;A.&lt;/strong&gt; Reselling a portion of an internet connection to a third party for commercial gain is prohibited by most ISPs. However, private arrangements via HomeGrid VPN are not bandwidth reselling; they are private agreements to cover the physical costs (electricity/space) of maintaining a device. Therefore, it generally does not constitute commercial reselling. Because specific ToS language and tolerances vary by ISP, we recommend that the account holder verify their contract. Additionally, since the external IP belongs to the account holder, mutual trust and clear prior consent are essential.&lt;/p&gt;

&lt;h3&gt;
  
  
  Q4. Can I route through a friend's house in another country to watch content only available in &lt;em&gt;their&lt;/em&gt; region?
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;A.&lt;/strong&gt; This falls outside the intended use of HomeGrid VPN. The core philosophy of "Accurate Signaling" is connecting back to &lt;em&gt;your own&lt;/em&gt; home base—the region where you are a legitimate, established resident—not adopting a region where you do not actually live.&lt;/p&gt;

&lt;p&gt;Even when the exit node is a real residential connection, routing through a location where &lt;em&gt;you&lt;/em&gt; are not a resident, in order to unlock that region's catalog, is functionally location spoofing: the residential IP belongs to your friend, but your viewing eligibility does not. This is a different act from reconnecting to the home you already hold an account and a residence in, and it may conflict with the streaming service's regional licensing and Terms of Service.&lt;/p&gt;

&lt;h2&gt;
  
  
  In short: returning to your &lt;em&gt;own&lt;/em&gt; home region while temporarily away is what this infrastructure is built for. Acquiring a region you don't belong to is not—regardless of whether the exit IP is residential.
&lt;/h2&gt;

&lt;p&gt;&lt;em&gt;Disclaimer: This article explains the technical characteristics and networking philosophy of HomeGrid VPN. It does not guarantee permanent legal compliance in any specific jurisdiction, nor does it guarantee compliance with the Terms of Service of specific web services or streaming platforms. The use of the service and adherence to local laws and ISP agreements are entirely the responsibility of the user.&lt;/em&gt;&lt;/p&gt;




&lt;p&gt;*Want to see how it works in practice? Learn more about HomeGrid VPN here: &lt;a href="https://www.homegrid-vpn.com" rel="noopener noreferrer"&gt;https://www.homegrid-vpn.com&lt;/a&gt; *&lt;/p&gt;

</description>
      <category>vpn</category>
      <category>privacy</category>
      <category>security</category>
      <category>wireguard</category>
    </item>
    <item>
      <title>I Got Tired of Carrying My Entire Dev Environment Around. So I Built a Network I Actually Own.</title>
      <dc:creator>HomeGrid VPN</dc:creator>
      <pubDate>Thu, 18 Jun 2026 14:59:01 +0000</pubDate>
      <link>https://dev.to/homegrid_vpn/i-got-tired-of-carrying-my-entire-dev-environment-around-so-i-built-a-network-i-actually-own-170m</link>
      <guid>https://dev.to/homegrid_vpn/i-got-tired-of-carrying-my-entire-dev-environment-around-so-i-built-a-network-i-actually-own-170m</guid>
      <description>&lt;p&gt;Have you ever felt a chill run down your spine the moment you stepped away from your laptop at a café to grab your coffee, thinking "what if someone just took that?"&lt;/p&gt;

&lt;p&gt;Unpublished code, sensitive data, infrastructure access keys. Everything sitting in your local environment is exposed the moment you lose the device.&lt;/p&gt;

&lt;p&gt;When people hear "don't carry data around," most engineers picture the heavy, locked-down thin client or VDI their company forces on them. What I'm proposing is the exact opposite.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Because I can pull my own on-premises environment and cloud resources toward me from anywhere, I can choose to keep my local machine empty&lt;/strong&gt; — not as an externally imposed restriction, but as an autonomous, deliberate choice.&lt;/p&gt;

&lt;p&gt;Your laptop just needs to be a screen. A beautiful screen that connects you to the world.&lt;/p&gt;




&lt;h2&gt;
  
  
  1. Bringing Physical Risk to Zero
&lt;/h2&gt;

&lt;p&gt;HomeGrid VPN gives you the freedom to turn your laptop into a fully stateless terminal without sacrificing any development efficiency.&lt;/p&gt;

&lt;p&gt;Heavy workloads and datasets stay in your home private lab. Production databases stay isolated in the cloud. Nothing lives locally. That means you no longer need to lug around a heavy machine packed with a high-end CPU and terabytes of storage. One lightweight device with decent battery life is all you need to fully leverage the most powerful resources sitting at home.&lt;/p&gt;

&lt;p&gt;If you ever lose your device, just open the dashboard on your phone and remove it. The backend's autonomous sync logic completely purges that device's access credentials from every relay node. Even if someone physically steals your device, the entry point into your network disappears promptly.&lt;/p&gt;




&lt;h2&gt;
  
  
  2. Your Own Isolated Safe Zone in Network Space
&lt;/h2&gt;

&lt;p&gt;HomeGrid VPN is an auto-provisioned ZTNA (Zero Trust Network Access) solution that dynamically assigns each user a fully independent private network space.&lt;/p&gt;

&lt;p&gt;Strict policy-based traffic control at the relay plane prevents any possibility of your traffic mixing with another user's — enforced at the kernel level. The moment you initiate a connection, wherever you are in the world, a safe zone connecting only you and your lab is quietly established.&lt;/p&gt;




&lt;h2&gt;
  
  
  3. Zero Trust Means Zero Trust — Including Me
&lt;/h2&gt;

&lt;p&gt;HomeGrid VPN is built on the philosophy that you shouldn't have to trust the service operator.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Your private key is generated exclusively on your own device.&lt;/strong&gt; The only thing sent to and stored on the server is the public key needed to establish the peer connection. Because the private key never leaves your device by even a single bit, the architecture makes man-in-the-middle attacks and interception by the operator structurally impossible — a true zero trust model.&lt;/p&gt;




&lt;h2&gt;
  
  
  4. Not a Box You're Given — A Playground for Your Own Hacks
&lt;/h2&gt;

&lt;p&gt;What HomeGrid VPN provides isn't a set of restrictions. It's a blank, secure network with all communication friction removed.&lt;/p&gt;

&lt;p&gt;How you make your environment stateless is entirely up to you as an engineer.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Connect directly to your home server via VS Code Remote and work from anywhere&lt;/li&gt;
&lt;li&gt;Write code from a browser-based IDE on your Android device&lt;/li&gt;
&lt;li&gt;Securely access a powerful local LLM running at home from a lightweight device on the road, and run inference remotely&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Source code, API keys, model weights — none of it needs to touch your local device.&lt;/p&gt;




&lt;h2&gt;
  
  
  5. The Reality of Local Cache — and the Infrastructure-Side Last Line of Defense
&lt;/h2&gt;

&lt;p&gt;"But browser and editor session caches still end up on the local machine, right?"&lt;/p&gt;

&lt;p&gt;Absolutely true. Given the architecture of modern OSes and applications, it's impossible to bring local temporary cache down to zero.&lt;/p&gt;

&lt;p&gt;That's exactly why &lt;strong&gt;one-click revocation from the dashboard&lt;/strong&gt; is the last line of defense.&lt;/p&gt;

&lt;p&gt;It doesn't matter how much cache is left locally when you lose a device. Remove the device and the relay plane completely purges its access credentials. The moment the tap is shut off, every piece of leftover data on that local machine becomes meaningless debris that can never reach your assets again.&lt;/p&gt;




&lt;p&gt;Unlike a thin client where someone else draws the box and hands it to you —&lt;/p&gt;

&lt;p&gt;I pull the most powerful resources from anywhere I need them, and control the risk from the infrastructure side with a single kill switch. That's the answer I built.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Give it a try and see for yourself.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If this resonates, check out HomeGrid VPN:&lt;br&gt;
&lt;a href="https://www.homegrid-vpn.com" rel="noopener noreferrer"&gt;https://www.homegrid-vpn.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>devtools</category>
      <category>security</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
