<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Self-Hosting on BoulderWiMax.com</title><link>https://www.boulderwimax.com/tags/self-hosting/</link><description>Recent content in Self-Hosting on BoulderWiMax.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>BoulderWiMax.com</copyright><lastBuildDate>Sat, 15 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.boulderwimax.com/tags/self-hosting/index.xml" rel="self" type="application/rss+xml"/><item><title>Why 5G Home Internet Has No Static IP: CGNAT Explained</title><link>https://www.boulderwimax.com/post/5g-home-internet-cgnat-static-ip-remote-access-boulder/</link><pubDate>Sat, 15 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.boulderwimax.com/post/5g-home-internet-cgnat-static-ip-remote-access-boulder/</guid><description>
&lt;p&gt;A remote worker who wires up a home security camera, assigns it a fixed local address, forwards port 8080 on the router, and then can't reach the camera from outside the house has just run into carrier-grade NAT — not a router misconfiguration. It's an easy thing to chase for an evening before realizing the router did everything right and the problem sits one layer further out, on the carrier's network. This explainer covers what carrier-grade NAT (CGNAT) actually is, why 5G home internet and satellite providers default to it, what it does and doesn't break for VPNs and remote access, and the workarounds people actually use to get around it.&lt;/p&gt;</description></item></channel></rss>