<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Options to NAT Porxy Server in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/options-to-nat-porxy-server/m-p/567039#M114562</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/153075"&gt;@jlombardo&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Check if this &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClhwCAC" target="_self"&gt;article&lt;/A&gt; helps you.&lt;/P&gt;</description>
    <pubDate>Fri, 24 Nov 2023 15:26:55 GMT</pubDate>
    <dc:creator>SutareMayur</dc:creator>
    <dc:date>2023-11-24T15:26:55Z</dc:date>
    <item>
      <title>Options to NAT Porxy Server</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/options-to-nat-porxy-server/m-p/561138#M113722</link>
      <description>&lt;P&gt;Background:&amp;nbsp; 10000 or so clients connect to the Internet through a cluster of proxy servers.&amp;nbsp; The proxy servers sit on the inside of the network and share a single outside NAT address.&amp;nbsp; So all external web related requests come from the same outside NAT address.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Problem:&amp;nbsp; Cloud services using Akamai and Amazon will periodically block our proxy servers outside NAT addresses.&amp;nbsp; IT appears that the proxy server outside address is getting blocked because it exceeded some rate limit implemented by the cloud service provider.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One solution we are investigating is to create a dynamic ip and port nat policy for the proxy servers with multiple outside public addresses.&amp;nbsp; But how does that work?&amp;nbsp; In my experience a dynamic ip and port policy will uses the first IP in the pool until all the ports are exhausted.&amp;nbsp; So we would have to have 65000 or so concurrent web requests before the pool would roll over to the next ip.&amp;nbsp; This wouldnt fix our problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It there a way set a NAT policy so the Palo will round robin each address in the pool?&lt;/P&gt;
&lt;P&gt;What have other engineers done to fix this problem?&amp;nbsp; We cant be the only ones that have run into this issue?&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Joe&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2023 16:21:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/options-to-nat-porxy-server/m-p/561138#M113722</guid>
      <dc:creator>jlombardo</dc:creator>
      <dc:date>2023-10-10T16:21:32Z</dc:date>
    </item>
    <item>
      <title>Re: Options to NAT Porxy Server</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/options-to-nat-porxy-server/m-p/567039#M114562</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/153075"&gt;@jlombardo&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Check if this &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClhwCAC" target="_self"&gt;article&lt;/A&gt; helps you.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2023 15:26:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/options-to-nat-porxy-server/m-p/567039#M114562</guid>
      <dc:creator>SutareMayur</dc:creator>
      <dc:date>2023-11-24T15:26:55Z</dc:date>
    </item>
  </channel>
</rss>

