<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Cgnat - vo.rs</title><link>https://vo.rs/tags/cgnat/</link><description>Latest from the Cgnat desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Thu, 15 Aug 2024 09:15:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/cgnat/" rel="self" type="application/rss+xml"/><item><title>Beating CGNAT: Reaching a Homelab With No Public IP</title><link>https://vo.rs/story/beating-cgnat-reaching-a-homelab-with-no-public-ip/</link><description>&lt;p&gt;The first sign is usually a service that used to be reachable from outside the house and suddenly isn&amp;rsquo;t. You check the router, the port forward is still configured exactly as it was, the local service is up, and yet nothing gets through. Then you check what IP address your router thinks it has on the WAN side, compare it against what a &amp;ldquo;what&amp;rsquo;s my IP&amp;rdquo; site says from outside, and they don&amp;rsquo;t match. That mismatch is CGNAT — Carrier-Grade NAT — and once an ISP has put you behind it, port forwarding is not broken, it&amp;rsquo;s simply irrelevant, because your router was never handed a public address to forward a port on in the first place.&lt;/p&gt;</description><pubDate>Thu, 15 Aug 2024 09:15:00 +0000</pubDate></item></channel></rss>