<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Unifi on wasteland</title>
    <link>https://wasteland.snrkl.org/topics/unifi/</link>
    <description>Recent content in Unifi on wasteland</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 snrkl</copyright>
    <lastBuildDate>Tue, 23 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wasteland.snrkl.org/topics/unifi/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>A Second Public IP on UniFi Without the Pain</title>
      <link>https://wasteland.snrkl.org/blog/a-second-public-ip-on-unifi-without-the-pain/</link>
      <pubDate>Tue, 23 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://wasteland.snrkl.org/blog/a-second-public-ip-on-unifi-without-the-pain/</guid>
      <description>If your ISP hands you an extra public IP as a &lt;strong&gt;framed route&lt;/strong&gt; — a single &lt;code&gt;/32&lt;/code&gt; routed&#xA;to your existing WAN address rather than delivered on the WAN segment — the internet&#xA;will tell you that you need to do something elaborate to use it on UniFi gear. You&#xA;don&amp;rsquo;t. Modern UniFi Network does it natively with two NAT rules.</description>
      
    </item>
    
  </channel>
</rss>
