<?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 Palo HA in Azure - traffic flow in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/palo-ha-in-azure-traffic-flow/m-p/487666#M1561</link>
    <description>&lt;P&gt;I have a pair of VM300 gateways running 9.1.13 in Azure. I'm using a 'load balancer sandwich' approach to provide active active HA.&lt;/P&gt;&lt;P&gt;The public load balancer in front of the firewalls does a good job of delivering inbound traffic.&amp;nbsp; However, routing to the internal destinations from the inside of the firewalls isnt ideal currently.&amp;nbsp; I find i have to source nat the traffic to each firewall's internal interface if i want the replies to take the correct return path. This loses the original internet client's real IP.&amp;nbsp; Without this source natting, even if the return traffic routes correctly to the firewall pair, it may not egress out the same gateway that it entered through. Making the traffic lose state.&lt;/P&gt;&lt;P&gt;Is there another way i can use two firewalls in active active HA and have the return traffic flow correctly?&lt;/P&gt;</description>
    <pubDate>Tue, 17 May 2022 05:58:31 GMT</pubDate>
    <dc:creator>JimMcGrady</dc:creator>
    <dc:date>2022-05-17T05:58:31Z</dc:date>
    <item>
      <title>Palo HA in Azure - traffic flow</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/palo-ha-in-azure-traffic-flow/m-p/487666#M1561</link>
      <description>&lt;P&gt;I have a pair of VM300 gateways running 9.1.13 in Azure. I'm using a 'load balancer sandwich' approach to provide active active HA.&lt;/P&gt;&lt;P&gt;The public load balancer in front of the firewalls does a good job of delivering inbound traffic.&amp;nbsp; However, routing to the internal destinations from the inside of the firewalls isnt ideal currently.&amp;nbsp; I find i have to source nat the traffic to each firewall's internal interface if i want the replies to take the correct return path. This loses the original internet client's real IP.&amp;nbsp; Without this source natting, even if the return traffic routes correctly to the firewall pair, it may not egress out the same gateway that it entered through. Making the traffic lose state.&lt;/P&gt;&lt;P&gt;Is there another way i can use two firewalls in active active HA and have the return traffic flow correctly?&lt;/P&gt;</description>
      <pubDate>Tue, 17 May 2022 05:58:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/palo-ha-in-azure-traffic-flow/m-p/487666#M1561</guid>
      <dc:creator>JimMcGrady</dc:creator>
      <dc:date>2022-05-17T05:58:31Z</dc:date>
    </item>
    <item>
      <title>Re: Palo HA in Azure - traffic flow</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/palo-ha-in-azure-traffic-flow/m-p/489846#M1565</link>
      <description>&lt;P&gt;Hi Jim.&amp;nbsp; You should not need to be using source NAT to maintain session symmetry in Azure.&amp;nbsp; Which load balancer are you using on the inside?&amp;nbsp; Basic, Standard SKU?&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2022 17:16:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/palo-ha-in-azure-traffic-flow/m-p/489846#M1565</guid>
      <dc:creator>sthornton</dc:creator>
      <dc:date>2022-05-23T17:16:22Z</dc:date>
    </item>
    <item>
      <title>Re: Palo HA in Azure - traffic flow</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/palo-ha-in-azure-traffic-flow/m-p/490069#M1567</link>
      <description>&lt;P&gt;Hi Scott. Traffic initiated from internet passes through the outside load balancer (standard public SKU) to the Palo pair, and then straight to the backend servers.&amp;nbsp; I am using port Natting between the outside LB and the Palo pair to allow traffic differentiation. Without a source NAT, the reply traffic uses the user defined route which sets the inside load balancer (standard sku internal) as its next hop. a traffic capture sees this delivered to either Palo, not necessarily to the one the original traffic came through.&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 01:38:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/palo-ha-in-azure-traffic-flow/m-p/490069#M1567</guid>
      <dc:creator>JimMcGrady</dc:creator>
      <dc:date>2022-05-24T01:38:58Z</dc:date>
    </item>
  </channel>
</rss>

