<?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: ASA Migration - TCP/UDP source port rules not migrated in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/asa-migration-tcp-udp-source-port-rules-not-migrated/m-p/238880#M773</link>
    <description>&lt;P&gt;Is there a solution to work around this in Expedition? I am also experiencing this issue&lt;/P&gt;</description>
    <pubDate>Wed, 07 Nov 2018 15:12:49 GMT</pubDate>
    <dc:creator>yaz3636</dc:creator>
    <dc:date>2018-11-07T15:12:49Z</dc:date>
    <item>
      <title>ASA Migration - TCP/UDP source port rules not migrated</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/asa-migration-tcp-udp-source-port-rules-not-migrated/m-p/238691#M767</link>
      <description>&lt;P&gt;Noticed that many rules with source ports defined are not migrated over.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Instead, it creates a service only for the destination port/range and allows all ports through.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Below are a few rules. Is it a known behavior?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The first two allowed all udp and tcp ports &amp;gt; 1023&lt;/P&gt;
&lt;P&gt;The third rule allowed all TCP ports&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;access-list OUT2IN extended permit udp any4 eq domain any4 gt 1023 &lt;BR /&gt;access-list OUT2IN extended permit tcp any4 eq ftp-data any4 gt 1023 &lt;BR /&gt;access-list OUT2IN extended permit tcp any4 eq ftp-data any4&lt;/P&gt;</description>
      <pubDate>Tue, 06 Nov 2018 04:34:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/asa-migration-tcp-udp-source-port-rules-not-migrated/m-p/238691#M767</guid>
      <dc:creator>ROHO</dc:creator>
      <dc:date>2018-11-06T04:34:04Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Migration - TCP/UDP source port rules not migrated</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/asa-migration-tcp-udp-source-port-rules-not-migrated/m-p/238826#M771</link>
      <description>&lt;P&gt;Not currently supported. Will add a feature request for this.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Nov 2018 09:05:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/asa-migration-tcp-udp-source-port-rules-not-migrated/m-p/238826#M771</guid>
      <dc:creator>sjanita</dc:creator>
      <dc:date>2018-11-07T09:05:28Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Migration - TCP/UDP source port rules not migrated</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/asa-migration-tcp-udp-source-port-rules-not-migrated/m-p/238880#M773</link>
      <description>&lt;P&gt;Is there a solution to work around this in Expedition? I am also experiencing this issue&lt;/P&gt;</description>
      <pubDate>Wed, 07 Nov 2018 15:12:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/asa-migration-tcp-udp-source-port-rules-not-migrated/m-p/238880#M773</guid>
      <dc:creator>yaz3636</dc:creator>
      <dc:date>2018-11-07T15:12:49Z</dc:date>
    </item>
  </channel>
</rss>

