<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>CGNAT on Mahendra | Random Tech</title>
    <link>/tags/cgnat/</link>
    <description>Recent content in CGNAT on Mahendra | Random Tech</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 10 Sep 2026 14:13:00 +0000</lastBuildDate>
    <atom:link href="/tags/cgnat/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How I Bypass My ISP&#39;s CGNAT To Host This Website At My Home Without A Public IP Address</title>
      <link>/posts/selfhosted-apps-routed-from-vps/</link>
      <pubDate>Thu, 10 Sep 2026 14:13:00 +0000</pubDate>
      <guid>/posts/selfhosted-apps-routed-from-vps/</guid>
      <description>&lt;h1 id=&#34;hosting-websites-from-home-behind-cgnat-without-a-public-ip&#34;&gt;Hosting Websites from Home Behind CGNAT (Without a Public IP)&lt;/h1&gt;
&lt;p&gt;Hosting web services and applications on a home server provides complete control over your data, access to your own hardware, and eliminates recurring compute fees. However, modern residential internet connections present a major roadblock: &lt;strong&gt;Carrier-Grade NAT (CGNAT)&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&#34;the-problem-why-port-forwarding-wont-work&#34;&gt;The Problem: Why Port Forwarding Won&amp;rsquo;t Work&lt;/h3&gt;
&lt;p&gt;With usual broadband, your ISP assigns your you a publicly routable IPv4 address. Directing web traffic to a home server was as simple as forwarding incoming requests on ports 80 (HTTP) and 443 (HTTPS) to your local server&amp;rsquo;s internal IP address.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
