<?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: expedition pre-define http mismatch actual firewall in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-pre-define-http-mismatch-actual-firewall/m-p/331434#M2641</link>
    <description>&lt;P&gt;We are looking into the issue and have a ticket internally.&lt;/P&gt;</description>
    <pubDate>Wed, 03 Jun 2020 16:24:44 GMT</pubDate>
    <dc:creator>azuniga</dc:creator>
    <dc:date>2020-06-03T16:24:44Z</dc:date>
    <item>
      <title>expedition pre-define http mismatch actual firewall</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-pre-define-http-mismatch-actual-firewall/m-p/330689#M2623</link>
      <description>&lt;P&gt;We had migration activity that causing the outage. After review the technical detail. we notice when merge service object, TCP-80 over write service-http.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;the actual firewall service-http use port 80 and 8080. Expedition pre-define as 80 only, that causing the problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One more thing, when show running security policy and nat policy, palo alto not sort output of ip address, service, it's very painful to compare the result that make migration more challenge and risk.&lt;/P&gt;</description>
      <pubDate>Sat, 30 May 2020 13:54:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-pre-define-http-mismatch-actual-firewall/m-p/330689#M2623</guid>
      <dc:creator>ZHOUJO5</dc:creator>
      <dc:date>2020-05-30T13:54:11Z</dc:date>
    </item>
    <item>
      <title>Re: expedition pre-define http mismatch actual firewall</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-pre-define-http-mismatch-actual-firewall/m-p/331434#M2641</link>
      <description>&lt;P&gt;We are looking into the issue and have a ticket internally.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2020 16:24:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-pre-define-http-mismatch-actual-firewall/m-p/331434#M2641</guid>
      <dc:creator>azuniga</dc:creator>
      <dc:date>2020-06-03T16:24:44Z</dc:date>
    </item>
  </channel>
</rss>

