<?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 External IP Rotation]]></title><description><![CDATA[<p dir="auto">Would it be possible to implement instead of random external IP, a circular IP rotation based on time?  For example every minute go to next IP address but keep the entire network on one IP for that time?  (External)</p>
<p dir="auto">I'd also have no problem paying for this feature.</p>
]]></description><link>https://forum.netgate.com/topic/115917/nat-external-ip-rotation</link><generator>RSS for Node</generator><lastBuildDate>Mon, 15 Jun 2026 07:53:01 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/115917.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 20 May 2017 02:27:23 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to NAT External IP Rotation on Thu, 15 Jun 2017 21:22:16 GMT]]></title><description><![CDATA[<p dir="auto">What about a script to change the Address Pool every X hours?  Then I can have 1 Subnet active per hour and rotate them through each.</p>
]]></description><link>https://forum.netgate.com/post/706044</link><guid isPermaLink="true">https://forum.netgate.com/post/706044</guid><dc:creator><![CDATA[KenBeanNet]]></dc:creator><pubDate>Thu, 15 Jun 2017 21:22:16 GMT</pubDate></item><item><title><![CDATA[Reply to NAT External IP Rotation on Sun, 21 May 2017 13:33:48 GMT]]></title><description><![CDATA[<p dir="auto">It's down to what the PF implementation that comes from FreeBSD can do. Quote from the manual page:</p>
<pre><code>
POOL OPTIONS
     For nat and rdr rules, (as	well as	for the	route-to, reply-to and dup-to
     rule options) for which there is a	single redirection address which has a
     subnet mask smaller than 32 for IPv4 or 128 for IPv6 (more	than one IP
     address), a variety of different methods for assigning this address can
     be	used:

     bitmask
	   The bitmask option applies the network portion of the redirection
	   address to the address to be	modified (source with nat, destination
	   with	rdr).

     random
	   The random option selects an	address	at random within the defined
	   block of addresses.

     source-hash
	   The source-hash option uses a hash of the source address to deter-
	   mine	the redirection	address, ensuring that the redirection address
	   is always the same for a given source.  An optional key can be
	   specified after this	keyword	either in hex or as a string; by
	   default pfctl(8) randomly generates a key for source-hash every
	   time	the ruleset is reloaded.

     round-robin
	   The round-robin option loops	through	the redirection	address(es).

	   When	more than one redirection address is specified,	round-robin is
	   the only permitted pool type.

     static-port
	   With	nat rules, the static-port option prevents pf(4) from modify-
	   ing the source port on TCP and UDP packets.

</code></pre>
<p dir="auto">It's likely that the pfSense devs are going to say no to feature requests involving additional address rotation schemes and just "pass the puck" to FreeBSD developers.</p>
]]></description><link>https://forum.netgate.com/post/700909</link><guid isPermaLink="true">https://forum.netgate.com/post/700909</guid><dc:creator><![CDATA[kpa]]></dc:creator><pubDate>Sun, 21 May 2017 13:33:48 GMT</pubDate></item></channel></rss>