<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[NAT with public routed pool]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">I am new to the forum but not new to pfsense. So far I was able to realize several setups with multiple WAN and LAN segements fine. The task on hand is somehow much more complicated.</p>
<p dir="auto">Background: for a large wifi installation several private LAN segments shall be NATed indiviually to public IPs thar are provided by our ISP. Therefore a /28 public IP block is routed to one of our our WAN addresses by our ISP (we have a different /26 block there). We want to use other IPs for the the solution for internal reasons. We have done such a setup once but used Juniper SRX routers wich is not possible in this case for monetary reasons. We have a dedicated box for the given solution.</p>
<p dir="auto">Given IPs (as private for privacy reasons)<br />
pfsense WAN: 10.1.61.203/26<br />
WAN ISP GW: 10.1.61.254/26<br />
routed IP block: 192.168.2.48/28<br />
simple static routing configured in ISP router<br />
client segments: 172.20.[0|8|16|24].0/21 in separate VLANS directly attached</p>
<p dir="auto">We planed for four individual NAT pools with 4 public IPs each wich is used by a larger private segment behind.</p>
<p dir="auto">The hint or direction to a maybe existing writeup of somethin is someho concentrating of how to get pfsense to route the IP block (firewalling/filtering shall be made during NAT) to our ISP and make it usable for the NAT pools?</p>
<p dir="auto">We already tested NAT pools with some other of our main public adresses but did not really see the round robin working as we did have only a few clients availabe this time. Testing it with something like Cisco's TRex system might be overfill and very timeconsuming (would be a first for us).</p>
<p dir="auto">Thkans in advance for any hint!<br />
MP.</p>
]]></description><link>https://forum.netgate.com/topic/166172/nat-with-public-routed-pool</link><generator>RSS for Node</generator><lastBuildDate>Sun, 11 Oct 2026 03:04:37 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/166172.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 29 Aug 2021 12:12:09 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to NAT with public routed pool on Wed, 01 Sep 2021 18:21:54 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/viragomann">@<bdi>viragomann</bdi></a><br />
I am stunned... <em>THAT</em> was an easy trick. Damn. Though much more complicated stuff involved...<br />
Thank you very much!<br />
Now I have to figure out why NAT-Pool with HASH is not working properly, the GUI does not accept the setting with a pool of four of the named adresses. Strange.<br />
Again, thank you!<br />
MP.</p>
]]></description><link>https://forum.netgate.com/post/999766</link><guid isPermaLink="true">https://forum.netgate.com/post/999766</guid><dc:creator><![CDATA[mp45]]></dc:creator><pubDate>Wed, 01 Sep 2021 18:21:54 GMT</pubDate></item><item><title><![CDATA[Reply to NAT with public routed pool on Tue, 31 Aug 2021 21:06:43 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mp45">@<bdi>mp45</bdi></a><br />
You have add each IP of your /28 block as virtual IP of type <em>IP Alias</em> to your WAN. Then the IPs can be used in the outbound NAT settings.</p>
<p dir="auto">For instance to NAT 172.20.0.0/21 to the 192.168.2.48/30 pool, simply add an outbound NAT rule where the source is 172.20.0.0/21 and the translation address is <em>other subnet</em> &gt; 192.168.2.48/30 and select the proper pool option.</p>
]]></description><link>https://forum.netgate.com/post/999599</link><guid isPermaLink="true">https://forum.netgate.com/post/999599</guid><dc:creator><![CDATA[viragomann]]></dc:creator><pubDate>Tue, 31 Aug 2021 21:06:43 GMT</pubDate></item></channel></rss>